Teetertank

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • 4. Dezember 2020 at 14:19 #50414

    OK, thanks for the info.

    Will investigate further and try asking Micheal. Otherwise will try the Pi as a server but the Odroid has served me well so far and seems to perform very well otherwise.

    All the best.

    4. Dezember 2020 at 12:51 #50410

    Thanks for the response Mario,

    If I’m looking in the right place the log file in LMS under settings, then yes there seems to be a recurring error code: 429

    Version of Max2play is: 2.53

    The load on the health checker seems low: Pi is showing CPU Load:0.01 when stopped (but should be playing); when streaming the load is: 0.09 to 0.14 (CPU temp is less than 50)

    Here’s the Debug info from the Pi as a player:

    #### SQUEEZELITE VERSION ####
    Squeezelite Max2Play v1.0.3 based on v1.8.7-999, Copyright 2012-2015 Adrian Smith, 2015-2017 Ralph Irving.

    #### SQUEEZELITE BUILDOPTIONS ####
    Build options: LINUX ALSA EVENTFD RESAMPLE FFMPEG VISEXPORT IR GPIO DSD CONTROLSBS ALSASYNC BLUETOOTHSYNC

    #### AUDIOPLAYER CONFIG ####
    ### Configuration of Audioplayers
    SQUEEZELITE_PARAMETER=-o sysdefault:CARD=Headphones -a 80:4::
    SQUEEZESLAVE_PARAMETER=-n plugequal
    SHAIRPORT_PARAMETER=-d plug:jack
    USE_USB_DAC=0
    USE_EQUALIZER=0
    SYSTEM_USER=pi
    GMEDIARENDERER_ALSA_DEVICE=plug:jack

    #### SQUEEZELITE -l ####
    Output devices:
    null – Discard all samples (playback) or generate zero samples (capture)
    jack – JACK Audio Connection Kit
    pulse – PulseAudio Sound Server
    equal
    plugequal – Equalizer for plughw:0,0
    default:CARD=Headphones – bcm2835 Headphones, bcm2835 Headphones – Default Audio Device
    sysdefault:CARD=Headphones – bcm2835 Headphones, bcm2835 Headphones – Default Audio Device
    dmix:CARD=Headphones,DEV=0 – bcm2835 Headphones, bcm2835 Headphones – Direct sample mixing device
    dsnoop:CARD=Headphones,DEV=0 – bcm2835 Headphones, bcm2835 Headphones – Direct sample snooping device
    hw:CARD=Headphones,DEV=0 – bcm2835 Headphones, bcm2835 Headphones – Direct hardware device without any conversions
    plughw:CARD=Headphones,DEV=0 – bcm2835 Headphones, bcm2835 Headphones – Hardware device with all software conversions
    usbstream:CARD=Headphones – bcm2835 Headphones – USB Stream Output

    #### SHAIRPORT (SYNC) VERSION ####
    3.3.1-OpenSSL-Avahi-ALSA-soxr-sysconfdir:/usr/local/etc

    #### OUTPUT SOUND DETAILS CARD 0 ####
    access: MMAP_INTERLEAVED
    format: S16_LE
    subformat: STD
    channels: 2
    rate: 44100 (44100/1)
    period_size: 884
    buffer_size: 3536

    #### OUTPUT SOUND DETAILS CARD 1 ####

    4. Dezember 2020 at 5:40 #50409

    I’m afraid I don’t know how far the Pi can be from the screen. I only ever use without a screen. I suspect what you are trying to achieve may be too far, but someone else could maybe advise. I know people can run HDMI for upto about 10m but the touch screen uses a different cable that may be more limited.

    In case you haven’t found them already, there are some links that may be helpful to decide on the hardware and setting it up:

    For the hardware you could take a look at this:

    Multiroom Audio Configurator

    And instructions here:

    Build your own multiroom audio system

    3. Dezember 2020 at 1:12 #50397

    Hi Mischa,

    That’s good that you have run network cable everywhere. THis should make things work nice and smooth.

    For you multi room audio I would suggest something like:

    8 x Raspberry Pi3 (as audio player for each room)
    1 x Raspbarry Pi4 (as server and audio player for living room)
    9 x DAC hats – something like HiFiBerry DAC+ (one each Pi)

    This assumes you provide other amplification for each room. You could alternatively substitute the DAC hats with hat amps instead – something like: IQaudIO Pi-DigiAMP+ instead of the HiFiBerry DAC.

    You would configure the Pi4 as the server by installing Logitech Media server from Max2play interface. To this Pi4 you also configure as an audio player and also install Kodi for your video needs (also from the Max2play interface).

    The other Pis for each room you configure as players (Squeezeplayer) by using the Squeezelite option in Max2play.

    To control it all you install an app for your smart phone. If Android then you can use Orange Squeeze and if Apple-based you can use iPeng.

    If you want displays too, you can choose an option from the store. For example there is a 7 inch screen with holder for Rasperry pi on the back. You may find an elegant means to mount it or otherwise could purchase a case to house the display and Pi.

    Using Pi 4 all round may be a better solution due to gigabit connections, but either should be fine.

    Hope that helps as a starter.

    24. Juli 2019 at 11:39 #46465

    For many months I struggled with this hard drive never sleeping issue.

    Worked ok on other Odroids but not XU4. My view was that it was the software/functions that come prepackaged from the manufacturer on the hard drive to enable security/passport/recovery etc. If you can, try a different (basic) hard drive or try deleting all supplier functionality and prepackaged files from the hard drive and ideally then reformarting the whole drive.

    Mine is working fine now with a Seagate drive, don’t remember which but I got the most basic possible with no preinstalled fancy stuff. (It was Westen Digital Pasport that gave me all the headaches).

    11. Januar 2018 at 3:11 #33348

    I am still having problems trying to update to latest Kodi version.

    I tried pasting https://launchpad.net/~team-xbmc/+archive/ppa link into the ‚Choose Kodi/XBMC-Package by http-link‘ for update on the Kodi tab of the Max2play web interface.

    There were some errors during installation, but at the end it said installation complete.

    When trying to start Kodi, I now get the following error:

    Trying to launch … NOT successful Click here to show detailed information
    Use Interface eth0 with -m 00:1e:06:31:13:96
    Stopping Squeezelite
    Stopping Shairport
    rm: cannot remove ‚/tmp/shairport.pid‘: Operation not permitted
    sudo: no tty present and no askpass program specified
    /opt/max2play/start_xbmc.sh: 35: /opt/max2play/start_xbmc.sh: /usr/local/bin/xbmc: not found

    Would you be able explain how to fix or to show me which Kodi update link I need for an Odroid XU4 please? Would be great if you could include an update button on the next version of Max2play.
    Thanks.

    28. Februar 2017 at 22:28 #27354

    Thanks for the response Heiner. I’ve looked on every tab of the Max2play Web interface but don’t see an option to disable destop autostart.

    Is this function accessed on the browser interface or does it require somekind of terminal login to change this setying? (Device is an OdroidXU4).

    18. Februar 2017 at 18:06 #27012

    After numerous fresh installations and frustrating hours I am happy to report that I now have a reliable hard drive mount point!

    When I tried installing a fresh copy of the latest operating system and connecting my USB hard drive, I had the usual difficulties of the drive not being recognised but there was an indication in the yellow box at the top of the screen that there was a problem. I had never seen this warning come up previously. I think it was something in the latest Ubuntu 16.04 version. I don’t remember the exact message but it advised to run check disk or something, I wish I could remember the exact message but it was about a month ago now.

    So I plugged USB drive into Windows PC and ran the recommended fix (I think it was check disc). Since running the fix my USB drive has always been recognised by Max2play even after a reboot.

    I now even removed the USB hub and connect portable drive direct to Odroid and drive is still recognised and powers up fine and does not randomly get forgotten or not recognised after power down.

    My only problem now is that the dive won’t spin down once it starts up. Other than that the system is now rock solid as a Squeeze box server and am so much happier.

    Hope the Windows drive fix may help others with similar issues.

    Please let me know if there is a fix to make the drive spin down, it used to work on the old system fine.

    18. Februar 2017 at 17:35 #27011

    Hi,

    I have what seems to be the exact same issue with my WD Passport drive connected to Odroid XU4. If I reboot the system the drive spins down and enters standby mode (led slow flashing on hard drive and no whirring disc) but if I play music and then stop music so nothing is playing the hard drive never sleeps again.

    Like your issue, if I have rebooted the drive will go idle but then later spin up for no apparent reason and never go back to idle – this is even if I haven’t asked the sever to do anything and I do not have any auto music scanning active.

    Sorry i can’t help your issue, but if there’s a solution to fix I’d be grateful to know. My drive has been spinning constantly now for weeks and am concerned it will wear out faster in this state.

    15. Oktober 2016 at 2:30 #23422

    Hi Christoph,

    Thanks for looking into it.

    I tried downloading a fresh image and installing on the XU4 but still get same message that resize is not successful.
    The image reference I downloaded is still m2p-2.34, same as one I downloaded previously – has anything updated or is it the same?

    I read on another forum that Ubuntu 16.04 resizes the file system automatically though. Could this be the case?

    My eMMC module is 8gb and these are the details in the debug info (so maybe ok?):

    #### FILESYSTEM ####
    Filesystem 1K-blocks Used Available Use% Mounted on
    udev 759012 0 759012 0% /dev
    tmpfs 203864 10852 193012 6% /run
    /dev/mmcblk0p2 7383016 4116592 2983148 58% /

    I still can’t get any USB drive or pen drive to mount on this system. They are sometimes recognised (not always) and when they are I get a message

    <name of drive> in not mounted (Device /dev/sda2 with UUID 18A03768A0374C0E)
    Set fixed Mountpoint to prevent directory switching on reboot:

    Have you any ideas, I tried so many times and nothing will mount.

    • This reply was modified 8 years, 1 month ago by Teetertank.
    10. September 2016 at 22:16 #22978

    Hi,

    I am still having the same issues with USB hard drives becoming undetected and not found in LMS after a reboot/power down.

    I have three Odroids: XU4, U3 and U3+ and have experienced the same issues with each. I have tried with two different USB drives too.

    I noticed in your last reply that you recommended using a powered USB hub. Previously I ad hard drives connected directly. So as this problem is still persisting I bought this week a powered USB3 hub with as strong external power supply. Unfortunately when rebooting Max2Play the hard drive disappears and LMS can not see it.

    I have obviously tried ticking the ‚Set fixed Mountpoint to prevent directory switching on reboot‚ but doesn’t seem to work for me.

    Other than this issue, the system seems excellent as a Squeezebox server. I notice others have reported similar issues too. If there was a means to solve this it would be perfect.

    I hope there can be some development in this area. If there is any more information I need to provide to assist this, please let me know.

    Thanks.

    22. März 2016 at 0:56 #19399

    Thanks for the reply Stefan.

    I finally got the video output working. I had the display resolution on the settings page set to auto before. I had tried a few other likely display resolutions before with no luck and also tried different HDMI cables so gave up.

    I tried again different display resolutions and found that when I set to ‚1080p noedid‘ I got the display output working fine on my TV with the main Max2play interface. Once the output was set, Kodi installed fine first try. So it seems it was user error I’m afraid, though would have hoped that the ‚Auto resoluton‘ option would have worked.

    8. März 2016 at 1:56 #19167

    I tried again a few tines to install Kodi and still no joy.

    I downloaded a fresh Max2Play image again from the website (Verson 2.22)
    I downloaded Win32DiskImager from the link Heiner kindly supplied above.
    I reformated eMMC moddule (to FAT32) just to be sure.
    Used Win32Disk Imager to burn a new image to eMMc module.
    Max2Play booted fine – I the expanded the file system and confirmed.
    I updated to version 2.27 (I also tried te latest beta version too with same results)
    Then I tried installing Kodi from the ‚Start Kodi‘ button on M2P Kodi tab.
    I still get no video output even for sandard Max2play interface – screen is just blank
    I get a similar error message when trying to start Kodi (as shown below)
    …says: „unable to resolve host OdroidXU4“ ….is that something to do with the problem?
    Error message pasted below:

    Trying to launch … NOT successful Click here to show detailed information
    sudo: unable to resolve host OdroidXU4
    Use Interface eth0 with -m 00:1e:06:31:13:96
    Stopping Squeezelite
    Stopping Shairport
    pulseaudio: no process found
    sudo: unable to resolve host OdroidXU4
    sudo: no tty present and no askpass program specified
    /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
    warnings.warn(str(e), _gtk.Warning)
    xdpyinfo: unable to open display „:0“.
    Traceback (most recent call last):
    File „/usr/local/share/kodi/FEH.py“, line 174, in
    if (1 == 1 and badColorDepth()):
    File „/usr/local/share/kodi/FEH.py“, line 153, in badColorDepth
    return bitDepth
    UnboundLocalError: local variable ‚bitDepth‘ referenced before assignment

    11. Februar 2016 at 15:33 #18460

    Thanks once again Heiner.

    I will try this when I get home later. Is there a preferred file system to format the eMMC module in before burning the operating system image.

    The instructions on your link say to format the card but with what system? FAT, FAT32, NTFS?…

    10. Februar 2016 at 17:52 #18454

    Thanks for the reply Heiner,

    The first thing I did on the initial boot was hit the ‚Expand file system‘ button (with no other USB devices connected).

    If there is a way to verify if I have done this correctly to confirm and that the file system has been expanded then please let me know.

    I’m using an eMMC module which I formatted to FAT32 before flashing the image.

    Should there be a desktop viewable over HDMI for the normal Max2play interface or does it only come alive when Kodi is active. Presently I only interact with Max2play through a web viewer. When I try and view the output over HDMI screen is black, though TV seems to recognise a 16:9 input.

Viewing 15 posts - 1 through 15 (of 15 total)