DietPi-Software | GMediaRender: "sysdefault" does not work in every case #3348
Comments
|
@kikigarel
This can only mean that the IP line is still empty when the service is started. Strange, since this is started long after dietpi-boot.service where network interfaces should be fully initialised.
Does the RPi otherwise play music fine, outside of GMediaRender? |
|
Thanks for your consideration. Well, that's really strange because the RPI has a static IP address on my network. In dietpi.txt, CONFIG_BOOT_WAIT_FOR_NETWORK=1 I didn't modify anything. I use ethernet. An IP address issue would make sense since the music won't play on the target playback device. Yes, I have used the RPi with RoPieeeXL and it played music without any problem. |
|
@kikigarel The following should resolve the autostart issue:
|
|
@MichaIng
I have added the three uncommented lines as advised and rebooted the RPi. However, the service still fails to start autoimatically but now it won't even start manually!
Here is what DietPi returns when I run journalctl -u ifup@eth0; journalctl -u dietpi-boot
root@DietPi:~# journalctl -u ifup@eth0; journalctl -u dietpi-boot
-- Logs begin at Mon 2020-01-20 21:05:33 CET, end at Mon 2020-01-20 21:40:06 CET
. --
janv. 20 21:05:35 DietPi systemd[1]: Started ifup for eth0.
janv. 20 21:05:35 DietPi dhclient[452]: Internet Systems Consortium DHCP Client
4.4.1
janv. 20 21:05:35 DietPi sh[416]: Internet Systems Consortium DHCP Client 4.4.1
janv. 20 21:05:35 DietPi sh[416]: Copyright 2004-2018 Internet Systems Consortiu
m.
janv. 20 21:05:35 DietPi sh[416]: All rights reserved.
janv. 20 21:05:35 DietPi sh[416]: For info, please visit https://www.isc.org/sof
tware/dhcp/
janv. 20 21:05:35 DietPi dhclient[452]: Copyright 2004-2018 Internet Systems Con
sortium.
janv. 20 21:05:35 DietPi dhclient[452]: All rights reserved.
janv. 20 21:05:35 DietPi dhclient[452]: For info, please visit https://www.isc.o
rg/software/dhcp/
janv. 20 21:05:35 DietPi dhclient[452]:
janv. 20 21:05:36 DietPi dhclient[452]: Listening on LPF/eth0/dc:a6:32:53:6b:eb
janv. 20 21:05:36 DietPi sh[416]: Listening on LPF/eth0/dc:a6:32:53:6b:eb
janv. 20 21:05:36 DietPi sh[416]: Sending on LPF/eth0/dc:a6:32:53:6b:eb
janv. 20 21:05:36 DietPi sh[416]: Sending on Socket/fallback
janv. 20 21:05:36 DietPi sh[416]: DHCPDISCOVER on eth0 to 255.255.255.255 port 6
7 interval 7
janv. 20 21:05:36 DietPi dhclient[452]: Sending on LPF/eth0/dc:a6:32:53:6b:eb
janv. 20 21:05:36 DietPi dhclient[452]: Sending on Socket/fallback
janv. 20 21:05:36 DietPi dhclient[452]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
janv. 20 21:05:43 DietPi dhclient[452]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
janv. 20 21:05:43 DietPi sh[416]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
janv. 20 21:05:43 DietPi sh[416]: DHCPOFFER of 192.168.1.26 from 192.168.1.254
janv. 20 21:05:43 DietPi sh[416]: DHCPREQUEST for 192.168.1.26 on eth0 to 255.255.255.255 port 67
janv. 20 21:05:43 DietPi dhclient[452]: DHCPOFFER of 192.168.1.26 from 192.168.1.254
janv. 20 21:05:43 DietPi sh[416]: DHCPACK of 192.168.1.26 from 192.168.1.254
janv. 20 21:05:43 DietPi dhclient[452]: DHCPREQUEST for 192.168.1.26 on eth0 to 255.255.255.255 port 67
janv. 20 21:05:43 DietPi dhclient[452]: DHCPACK of 192.168.1.26 from 192.168.1.254
janv. 20 21:05:43 DietPi dhclient[452]: bound to 192.168.1.26 -- renewal in 17996 seconds.
janv. 20 21:05:43 DietPi sh[416]: bound to 192.168.1.26 -- renewal in 17996 seconds.
janv. 20 21:05:43 DietPi sh[416]: eth0=eth0
-- Logs begin at Mon 2020-01-20 21:05:33 CET, end at Mon 2020-01-20 21:40:06 CET. --
janv. 20 21:05:35 DietPi systemd[1]: Starting DietPi-Boot...
janv. 20 21:06:16 DietPi systemd[1]: Started DietPi-Boot.
root@DietPi:~#
|
|
Here is the content of the SVG file: |
|
Okay here the relevant part, visualised in browser: The journal entries show that @kikigarel
|
|
I have applied a static IP via dietpi-config > Network Options: Adapters, but it didn't change anything. Here is the requested info: |
|
@kikigarel must be |
|
I have corrected the missing slash and now the service starts normally. However, I still don't get music to play :-( Audirvana detects DietPi as endpoint/renderer but when I click "Play" nothing happens and the icon is grayed. Really strange :-/ |
|
@kikigarel Could you try to start the binary manually as root (or via sudo)? If still no music, try without any gstout settings: |
|
@MichaIng root@DietPi: |
|
There is one strange thing: each time I select dietpi as renderer, the volume is set to -1.2db. Not sure if it is related to the issue (it should be 0db)? |
|
Here is the result of the first command: root@DietPi: (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.715: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gmediarender:3282): GStreamer-CRITICAL **: 01:00:24.716: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed ** (gmediarender:3282): CRITICAL **: 01:00:26.552: file gstdtlsagent.c: line 192 (gst_dtls_agent_init): should not be reached ** (gmediarender:3282): CRITICAL **: 01:00:26.552: gst_dtls_agent_set_property: assertion 'self->priv->ssl_context' failed |
|
Second command: root@DietPi: (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.715: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.716: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.716: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (gmediarender:3595): GStreamer-CRITICAL **: 01:08:26.716: INFO [2020-01-22 01:08:26.723877 | connmgr] Registering support for 'subpicture/x-dvb' ** (gmediarender:3595): CRITICAL **: 01:08:30.553: file gstdtlsagent.c: line 192 (gst_dtls_agent_init): should not be reached ** (gmediarender:3595): CRITICAL **: 01:08:30.554: gst_dtls_agent_set_property: assertion 'self->priv->ssl_context' failed |
|
@kikigarel
|
|
No, after running the first command Dietpi is no longer detected (I get a "Peripheral not connected" message in Audirvana) |
|
Same thing with the second command (without restarting the service) |
|
@kikigarel Btw is it onboard sound? Did you configure it via dietpi-config? |
Yes it was stopped
I'm not sure I understand what you mean. I'm trying the play a file from Audirvana to the DAC via the RPi/Dietpi. Yes, the DAC is detected and configured as sound card in Dietpi-Config.
There you go: root@DietPi:~# cat /etc/asound.conf ctl.!default { root@DietPi: |
|
Hi @MichaIng, I confirm the service was stopped while running the command. And I couldn't play music while the command was running, or after. Please find below the journal: |
|
@kikigarel To rule it out, could you install the package from APT repo: Lets see if this works instead. It did not work for other users, which was the reason we compiled own binaries which solved the issues reported before. If the same errors happen/music does not play as well, to revert: We then need to do some more research. What you could as well test is simply another client instead of Audirvana. |
|
Hey @MichaIng, So... Dietpi is being a bad boy :-) Installing the package from APT repo didn't help. Actually, it made the endpoint name change from "dietpi" to "gmediarender on dietpi", and I couldn't select it anymore ("peripheral not connected" error message). I have reverted everything. I have used another client as well: DS Audio, the app that is bundled with the Synology NAS. It can stream to Dietpi but again nothing happens: playback just doesn't start, exactly like with Audirvana. That's is really puzzling. Could the issue be related to the autologin? An incompatibility issue with RPi 4? Also, in Dietpi-Config / Audio Options, I realized that I have two auto detection options: usb-dac (USB Audio DAC, any) or hw:1,0 (UD503 USB Audio). I had selected the second one from the start since UD 503 is the model of my DAC. I tried selecting the first one but it made no difference. |
|
@kikigarel About audio card selection:
Autologin cannot be related. GMediaRender runs as systemd service, independently from any login. I am as well puzzled. Last idea I have so far is to check and play with We maybe need to open an issue on https://github.com/hzeller/gmrender-resurrect/issues. Probably hzeller has some idea based on those error messages: #3348 (comment) |
|
Hi @MichaIng, I have just opened a ticket here, let's see if someone finds out what's wrong :-) |
|
Workaround: hzeller/gmrender-resurrect#205 (comment)
|
MichaIng
changed the title
|
For reference, PM from sudeep from Allo:
Actually we want ALSA to be used, since this is what DietPi-Config and DietPi-Software configures for everything and what is expected. Still strange that either due to |
Warning: Long text below, mostly for myself and documentation reasons, scroll down for relevant part 😅So I ran some tests and indeed So using Using We overwrite the Playing a test file using PCM name Using Of course we can also overwrite the But before changing too much around, the easiest thing is indeed to use So to me it looks like a good convention to take There is btw an alternative, using this: This leads to correct default sound devices being used, keeping the default ALSA So for now we'll keep things as they are but use the PCM name @kikigarel and check whether things work just the same as with the workaround before, where you used |
+ DietPi-Software | GMediaRender: Use correct PCM name, assigned to the chosen sound device via dietpi-config: #3348 + DietPi-Software | GMediaRender: Add dummy icon files. Those are not required but on service start and every access, error logs are created if missing. + DietPi-Software | Consequently use network-online.target in favour of network.target, which is now available on all supported Debian versions (since Stretch). This target is reached when all network interfaces have been configured, while network.target has not much practical meaning for services with network demand: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
MichaIng
added
Solution available 🥂
|
I'll reopen to keep this up for testing, at least until sudeep verified this working reliable on Sparky SBC as well. |
|
FWIW, changing Only problem I still have is that the gmrender service tries to start before dhcpcd has acquired an IP address: I do have Could try adding a sleep statement, but that seem dodgy. Do we really need the IP address? |
|
@dsnyder0pc Generally network, hence an IP address needs to be up before GMediaRender can bind to it. The workaround above should work for you as well: #3348 (comment) I see that generally the problem with missing DHCP assignment is not yet solved, regardless with which DHCP server. Either we need to switch to a ping-based network check during boot and/or we need to change |
|
i am owner of allo sparky usbridge and after update to 6.28 my gmrender does not work. also i would really like to change starting volume to 100 (in bubble upnp it always starts with 97 !) I am newbie to all this so please can you help me to get sound back on. thank you |
|
I tried changing asound.conf like this that you suggested in my Allo usbridge: pcm.!default { ctl.!default { pcm.!sysdefault { ctl.!sysdefault { and now music plays when --gstout-audiodevice=default Alsa info for flac 16bit 44100hz stereo file is: access: RW_INTERLEAVED | format: S24_3LE | subformat: STD | channels: 2 | rate: 44100 (44100/1) | period_size: 441 | buffer_size: 8820 Still when i look at gmrender status log it says --gstout-audiodevice=sysdefault So it seeems to me that gmrender status log and gmrender service file are not same thing. Still, as i said my knowledge is only basic but i would like to be able to have working startup volume at 0, and possibility to search song position with slider of dlna controler (now if i try allo usbridge freezes and have to be unplugged from electricity socket. Thank you |
|
@ejokic |
|
In the beggining i changed simply in dietpi-explorer the file. Now after your message i searched internet and found command ctl.!default { and used systemctl daemon-reload Now it is also working and i have startup volume at 100 (thank you very much) /etc/systemd/system/gmrender.service[Unit] [Service] [Install] i hope it is ok like this. Can you maybe also point me where can i find more information about gmrender slide and search position in song via dlna controllers possibility? |
|
@ejokic
That is out of my knowledge as well, would require me to read into the topic. I guess best is to start reading through the specific DLNA controller/client documentation 🤔. |
|
Ah about the volume: https://github.com/hzeller/gmrender-resurrect/blob/master/INSTALL.md#--gstout-initial-volume-db Done: fcfd6d7 |
|
Excellent. |
|
Btw, is this that we are talking about old version of gmrender or new, updated version called gmrender-resurrect? |
|
@ejokic |
Hi,
I use Dietpi on an RPI 4 to stream music files from my PC, running Audirvana, to my DAC. I run the latest version of Dietpi (6.28) and couldn’t use it before to stream music as other people experienced issues with the abnormal start of the GMrender service (Issue #3263). Well, GMrender still fails to start! When I start the service manually I can see Dietpi as an available endpoint in Audirvana but no music will play!
Here is the service status log :
Could you help me please ? This issue is very frustrating.
Cheers
The text was updated successfully, but these errors were encountered: