RuneAudio+R e4

[klassikmann]

[Sonic]

Made a discovery concerning the sometime problem of not being able to access the system page, and possibly the recently reported webradio issue.

Following a recent update (20200717), I discovered I could no longer access the system page again. After trying a full MPD database rebuild and reboot, I still couldn’t open the system page.
So I then remotely accessed the ‘/srv/http/data/webradios’ directory and deleted all the containing files, and then checked that library Webradio icon showed no containing files.
Having not previously empted ‘/mnt/MPD/Webradio’ directory after importing my webradio files for the first time. I simply reimported the files using the import webradio addon, went back to the menu – and lo and behold, up pops the system page.

To make sure this wasn’t a fluke, I tried updating again with the next update (20200718). Same situation – update, no access to the system page, delete all files in the ‘/srv/http/data/webradios’ directory, import the files again via the webradio addon… bingo – up pops the system page.

I don’t know whether deleting and reimporting the webradio files after an update will resolve the reported issues some are having with webradio files. But mine are working.

Hope this helps

Best... Sonic

[ceejayemm]

Rern

It appears that the Merus-Amp is not being loaded:

root@raamp1+R e4:~ # aplay -l
aplay: device_list:274: no soundcards found...

root@raamp1+R e4:~ # /srv/http/bash/mpd-data.sh | jq .
amixer: Mixer attach default error: No such file or directory
aplay: device_list:274: no soundcards found...
/srv/http/bash/mpd-devices.sh: line 34: ((: == 0 : syntax error: operand expected (error token is "== 0 ")
Invalid card number.
parse error: Expected value before ',' at line 1, column 46

/boot/config.txt

over_voltage=2
hdmi_drive=2
force_turbo=1
gpu_mem=32
initramfs initramfs-linux.img followkernel
max_usb_current=1
disable_splash=1
disable_overscan=1
dtparam=audio=off
dtparam=i2s=on
dtoverlay=merus-amp

I hope this helps.

Chris

[klassikmann]

[klassikmann]

[Beelzebassie]

Had the same error as Klassikmann, wrote a fresh image, and now I cannot make contact with my NAS via NFS.

When I try to mount, Rune adds quotation marks to the IP-address: 192.168.1.10 becomes "192.168.1.10

[R101]

I also get the same update failure as klassikmann.

[Garrido33]

[jaygothard]

Just installed RuneAudio+R e4 using the DIY method. things went smoothly and I was happy to see that it is running MUCH faster than e3 did. I cannot tell you how many minutes I spent staring at the pulsating "Rune Audio" logo while moving between screens before I gave up, but it was a lot.

The sound quality seems good, at least on my headphones and all of my music was easy to find and update, but I have found two issues. One minor and the other a potential deal breaker.

1. Using the Chrome browser on my PC I don't have the Library and queue tabs unless I enable "bars on small screen". All is well on my PC, but if I use my phone I cannot use swiping. So if "bars on small screen" is selected I get tabs on both my PC and phone and if I de-select it I don't get tabs in either place.

2. I cannot mount a NAS share. I enter all of the pertinent information and then nothing happens. The information that I am using works on other MPDs including earlier version of Rune, but no luck in this version. I searched the forum and someone else had the same issue. He said he was able to mount the NAS manually, but I'm not sure how to do that.

[steffe]

I updated from the regular RuneAudio 0.3-beta to this version. The update was very easy and the system works nicely, but I have an issue with Spotify. I edited /etc/spotifyd.conf with my username and password, and I can see that spotifyd is active. The problem is that I cannot find, in the RuneAudio interface, where to select the music from Spotify. In the old system I had a place in the central tab to switch from MDP to Spotify, and also in the Library tab there was an icon I could click to access Spotify playlists. Now I just cannot find any way to access Spotify. Probably it's a silly issue, but I would appreciate if anyone could help.
Thanks.