Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Posted in:
  • 17. Mai 2020 at 4:51 #48800

    Thank you for looking into possible installation issues with Ampache. I will check back and re-install Ampache with an updated installer depending on what you might find and report my results here. Will also let you know if I try building another Max2play RPi-4b to test if a new install of MPD and YMPD works better.

    Recently purchased a Rock Pi4b, which has much in common with original RPi-4b, but adds onboard NVME.m2 interface, faster RAM (DDR4-3200mhz) …etc. I have worried about original RPi micro-SD card R/W longevity issues, as SD spec was originally designed for very different use cases: digital cameras, music players. These devices do many sequential memory reads and very few writes over the life of the SD. Any OS, but especially Linux which inherently does lots of logging is not a good fit for SD memory, in my opinion. This is why I plan to try installing M2P-OS into an NVME.m2 drive on the Rock Pi4b. I think other users of Rock-Pi4b configure the Linux-OS to boot from an EFI partition on the SD, but control is then quickly passed to the full Linux install on the NVME.m2 drive, which runs much faster and I hope more safely from NVME.m2 than uSD card.

    I do not expect the M2P org to support M2P OS Linux image on the Rock Pi4b, but would be grateful if you have heard from other users of any specific issues that arise from Rock Pi4b hosting M2P. If enough customers want to use Rock-Pi boards in the future it might create another market opportunity for M2P.


    — mark in Seattle

    12. Mai 2020 at 9:55 #48756

    Sorry to discover you are battling multi-room audio sync issues. This issue is very annoying and difficult to remove.

    In my experience multi-speaker, multi-amplifier syncing works very well using Squeezebox server (LMS) and squeezebox clients. The older original Squeezebox receivers in our house (3 units) and squeezelite running on a Raspberry-Pi3b with a HiFiBerry Amp2 stacked on top, can play songs from the LMS server all day staying perfectly in sync. It is amazing technology, to stay in sync, which I did not appreciate until I tried other music server and receiver options: DLNA digital speakers and others which drifted in an out of sync as unfortunately you are describing. Our LMS server is hosted by the same Raspberry-Pi3b mated to the HiFiBerry Amp2. The max2play OS runs squeezelite locally directing audio output thru the HiFiBerry Amp2. My Squeezeboxes are on ethernet, but thru multiple switches. For a while one was connected to the LMS via WiFi. Didn’t matter, they all stayed in sync regardless of digital transmission paths.

    When experimenting with (6) Insignia brand, model# CSPGASP2 DLNA digital speakers (WiFi links only) I believe the fault of not staying in sync for them was due to poor design of the server software and not the technology in the speakers themselves (a german company I believe designed the WiFi speakers). These speakers had chips with „stay-in-sync-reference-timing-clocks“ built in the speaker electronics. Some music server software knows how to use this shared reference clock technology to sync the speakers and other servers do not. Squeezebox server (LMS) seems to enable it’s own receivers to use a shared reference timing clock, so the audio always stays synced.

    My point in mentioning this is to suggest keeping multi-room speakers „in-sync“ is not an accident due to the absence of transmission delay, variable path effects …etc. In-sync audio across multiple digital delivery paths is a deliberate and specific function enabled by the architecture of the music server software communicating and re-characterizing, during playback, the amount of delay injected to each receiver channel to KEEP everything in sync for our benefit. This is active control by the server utilizing feedback from the receiver/speakers. Perhaps some receivers also utilize electronic circuitry built into the receiver/amplifiers that make accepting synchronization control instructions from different server software possible, not just one proprietary version (LMS, Sonos) … don’t know for sure.

    I do know Squeezebox receivers have this built-in. Change the signal path, they still stay in sync. The Insignia speakers also have a „stay-in-sync-reference-clock“ design, but the truly awful Google Home app that must be used to initially configure Insignia speakers could not broadcast an audio stream to keep them all in sync. However, under the right conditions, in certain modes, I could get my Squeezebox server (LMS) with a DLNA plugin to use „stay-in-sync-ref-signal“ with the Insignia speakers and all (6) stayed in sync throughout our house. That was very nice.

    Just suggestions as to how to approach the issue. Hope it helps your experiments ultimately be successful.

    11. Mai 2020 at 11:14 #48748

    ADDENDUM: Should add following information to original post above:

    When YMPD client did not attach to the local RPi MPD server I tried installing Ampache MPD-client onto M2P v2.52 RaspberryPi (HiFi-Berry-Amp2) system using the M2P web interface tab page = „Music Player – MPD“ selecting the [INSTALL] button under „Install latest version of Ampache„. However, the Ampache installation process seemed to hang after 5 – 10 minutes of apt-get progress updates. Waited another 20 mins of no activity then rebooted RPi. RPi rebooted OK.

    To continue/fix the prior possibly broken Ampache install: logged in with SSH from Fedora 32 linux machine and elevated with „su“ to user = root on RPi. On RPi from cmd line ran „apt-get update“ which finished OK, then „apt-get upgrade“ also finished OK. So it is possible my first attempt to install Ampache from M2P http interface has left the M2P RPi mis-configured somehow and that is interfering with install of MPD and YMPD ??? The M2P „Music Player – MPD“ web interface tab lists Ampache as „Ampache is NOT installed yet!“. No other music player (web tab „Audioplayer“) is auto-started at boot: unchecked Squeezelite [ ], left Shairport [ ] unchecked also.

    — TEST BUILD ANOTHER M2P RPi-4b TO RUN Music-Player-Daemon —
    As a last resort, I am willing to build another M2P RPi using a RPi-4b card I have as a test, flashing a new micro-SD memory card with the latest M2P v2.52 for HiFi-Berry adding an AudioPhonics I-Sabre v4 DAC hardware daughter card. Then test another installation of MPD and YMPD, without installing Ampache. This is not my first choice. I planned to work on the RPi-4 with M2P only when more time was available and after learning from mistakes made and corrected on my exisiting RPi3 system running LMS (squeezebox server) with HiFi-Berry Amp2 daughter card and hopefully MPD.

    Hope this additional info helps troubleshoot the problems experienced installing MPD and YMPD-client on M2P RPi.

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