Hi Michael,
I'm wondering this bug also affect some MPD clients. For instance, I can see the pls in M.A.L.P. in android, but not in MPDluxe in ios
PLS files were always shown in the majority of Android Clients I tried and of course YMPD. However the situation is not the same with other Linux desktop clients for example.
I will do a further research to see if it's a mistake from my side although I highly doubt it.
I will do a further research to see if it's a mistake from my side although I highly doubt it.
Last edited:
Surprised by the simplicity and quality of Archphile. Sounds even better. The additional Librespot is a big plus for me.
@pinkdot thanks for the feedback!
As some of you may have noticed, music reproduction using a usb dac and a NAS via ethernet is really bad with the new RPI 3B+.
This is not Archphile related and I will try to upload a new image when all these issues are resolved.
I was very optimistic to name this image a beta. It should really be an alpha version.
As some of you may have noticed, music reproduction using a usb dac and a NAS via ethernet is really bad with the new RPI 3B+.
This is not Archphile related and I will try to upload a new image when all these issues are resolved.
I was very optimistic to name this image a beta. It should really be an alpha version.
I have a very similar experience with Michelangelo from Volumio project:
The new Raspberry PI 3B+ audio-related review * Volumio
If you read the post update you will notice that he has the same issues with me.
I suppose it's a driver issue and hopefully it will be resolved very soon with a new kernel.
The new Raspberry PI 3B+ audio-related review * Volumio
If you read the post update you will notice that he has the same issues with me.
I suppose it's a driver issue and hopefully it will be resolved very soon with a new kernel.
I’m using 2 power supplies for the dac hat and pi. When I turn them on every now and then, I encounter alsa initialization issues and need to reboot. Is there a way to delay alsa driver initialization or run a command to re-initialize instead of reboot?
I have both wall warts plugged into an adapter which is plugged into a dlink WiFi Smartplug. I use IFTT with iOS workflow to control the power up and SSH shutdown/poweroff sequence via my iPhone so both the dac and pi turn on at more or less the same time.
@freeplay,
I believe that the best solution for you is to delay the boot process. You can try adding the following option:
in
The example above causes a delay of 3 sec.
You can try different values until the delay is enough for your dac to power on.
Please note that I haven't tested this option yet as I currently don't have access on a RPI.
I believe that the best solution for you is to delay the boot process. You can try adding the following option:
Code:
boot_delay=3in
Code:
/boot/config.txtThe example above causes a delay of 3 sec.
You can try different values until the delay is enough for your dac to power on.
Please note that I haven't tested this option yet as I currently don't have access on a RPI.
Last edited:
I noticed I've been getting mixer errors like cannot load mixer controls: Remote I/O error after the change. Not sure if it's due to that
To answer my own question.. all my issues are hw related and the root cause is power supply that screws up the alsamixer. Hooking up to a powerbank seems to fix the issue in the meantime.
Archphile rox!
Because the new higher bandwidth Ethernet chip on the Pi3+ which shares the same USB host port on the RPi as the USB "DAC" port is unthrottled and trys to use all the available USB Host bandwidth.
The original 100M Ethernet port chip "naturally" limited its host USB port B/W usage - which is not the case with the 1Gigabit Ethernet port chip on the Pi3+
In fact, on the Pi3+ the USB host controller is unable to meet the 1Gigabit Ethernet B/W requirements which is why RPi claim faster Ethernet not 1Gigabit Ethernet!
On the new RPi3+ with its 1Gigabit Ethernet controller max's out all the available USB interface B/W leaving there no spare USB B/W for the DAC...
Broadcom REALLY need to use a real hardware USB PHY internally on the next spin of SoC.... its a real shame that the greatest weakness of the RPi is its lack of a hardware USB PHY...
Last edited:
I have such settings but tidal dont works
# <grouptitle>Tidal streaming service parameters</grouptitle>
# <var name="tidaluser" type="string"><brief>Tidal user name.</brief>
# <descr>Your Tidal login name.</descr></var>
tidaluser = xxxxxxxx
# <var name="tidalpass" type="string"><brief>Tidal password.</brief>
# <descr>The password for your Tidal account.</descr></var>
tidalpass = xxxxxxxx
# <var name="tidalquality" type="cstr" "values="low high lossless">
# <brief>Tidal stream quality.</brief> <descr>'low' and 'high' are aac
# streams. 'lossless' is FLAC and will only work if your subscription
# allows it.</descr></var>
tidalquality = lossless
# <grouptitle>Tidal streaming service parameters</grouptitle>
# <var name="tidaluser" type="string"><brief>Tidal user name.</brief>
# <descr>Your Tidal login name.</descr></var>
tidaluser = xxxxxxxx
# <var name="tidalpass" type="string"><brief>Tidal password.</brief>
# <descr>The password for your Tidal account.</descr></var>
tidalpass = xxxxxxxx
# <var name="tidalquality" type="cstr" "values="low high lossless">
# <brief>Tidal stream quality.</brief> <descr>'low' and 'high' are aac
# streams. 'lossless' is FLAC and will only work if your subscription
# allows it.</descr></var>
tidalquality = lossless
Attachments
What causes these errors?exception: Failed to register /var/lib/mpd/music/nas-nfs/Albums/Jazz: inotify_add_watch() has failed: No space left on device