RuneAudio 0.5-beta for most Raspberry Pi models

[logitech_Z-640]

-Not able to access the Rune web interface using anything other than the IP address.

-Not able to access the web UI at all using my phone connected to the hotspot. Stays of the spinning arrow "connecting" screen forever.

I can confirm that accessing the web interface is not possible with domain name from mobile devices. I'm only able to access the web interface using the IP address (tested from three different Android devices):
Mobile phone: Android 4.4.2 with Chrome 69.0.3497.91
Tablet: Android 5.0.2 with Chrome 68.0.3440.91 and Firefox 61.0.2
Mobile phone: Android 6.0 with Chrome 69.0.3497.100

All devices are connected to the same wireless LAN as the RPi with RuneAudio. Strangely enough, if I ping the device from either WIN or Linux, it's working with runeaudio (WIN) or runeaudio.local (Linux).

I also used fing (Android app for network stuff) to check which devices are connected. I can see the RuneAudio device (with name runeaudio and the IP), but I'm only able to ping it with IP from fing.

Hence, the RuneAudio remote player app is also not working for me at the moment (was working with v0.3-beta before).

Additionally changed the hostname in the settings menu, but same result: accessible from WIN via name, but not from Android.

BR Frank

[cmh714]

That has less to do with Rune and more on your local DNS and junk.....you can use the IP in the Rune Remote App if you werent aware. Swipe to the right, select Support and Credits, then add player Manually.

hth

[hondagx35]

Hi,

did you also try "http://runeaudio." ?

From our docs:
(Windows) open the following address in your browser: http://runeaudio or http://runeaudio. (works if an Avahi/Bonjour client is installed) (OSX / Linux / Android) open the following address in your browser: http://runeaudio.local

Frank

[DarthG]

Hi,
good to see, that the devolopement of RuneAudio goes on now.

Reported Bug/New Feature:
Playing of CD-Rips consisting of: one .cue FIle and one .tak file isn't playing.

I would appreciate this.

[thisisjay]

After I typed in "http://runeaudio", "runeaudio" started working, so I'll accept user error on that one/

Network share working absolutely fine in Volumio:

Volumio.jpg (251.85 KiB) Viewed 1825 times

Dead in the water with Rune using identical settings:

Dead in The water.jpg (198.87 KiB) Viewed 1825 times

I already unplugged the USB drive and even rebooted. WTH?

wtf.jpg (254 KiB) Viewed 1825 times

[janui]

Hi DarthG,
Try this… First upgrade to the latest version with a git pull, see the first post in this thread for instructions. Then log in with SSH and create a file called /home/your-extra-mpd.conf with the command

Code: Select all

nano /home/your-extra-mpd.conf

Copy and paste the following lines into the file

Code: Select all

#########################
## your-extra-mpd.conf ##
## Add playlist plugin ##
## type '.cue'         ##
#########################
#
playlist_plugin {
    name "cue"
    enabled "true"
}
#############################
## end your-extra-mpd.conf ##
#############################


If there are any empty lines generated by the paste just delete them. Exit nano by entering <ctrl>o then <ctrl>x. If you screw up using nano, just try again. Then change the protection of the new file with the command:

Code: Select all

chmod 644 /home/your-extra-mpd.conf

Reboot then Update the MPD Library from the Sources UI. The xxxx.que files should now be recognised by MPD, the xxxx.tak files should already be recognised as a file supported by the ffmpeg library which is used by MPD.
janui

[janui]

Hi thisisjay,

Dead in the water with Rune using identical settings:

Yes, I see, if you could give me the NAS/server type I will look into it. This code is very old and has not been changed for many versions. I was planning to do a rework for the next Rune version, maybe it's possible to improve it in the short term.

I already unplugged the USB drive and even rebooted. WTH?

This is an old bug which I thought was fixed, I will fix this one at the weekend.
Thanks again for the feedback.
janui

[thisisjay]

I have the Raspberry PI and a Windows PC connected to a Linksys router via Ethernet. I'm just using Windows sharing to share out the music folder on the Windows PC.

I tried disabling the username and password requirement in Windows and it still won't connect to my share.

[logitech_Z-640]

That has less to do with Rune and more on your local DNS and junk.....you can use the IP in the Rune Remote App if you werent aware. Swipe to the right, select Support and Credits, then add player Manually.

hth

I would have configured that, but I would just get the startup screen, and then after searching for RuneAudio players a blank black screen.
Swiping right to configure anything did not work.

I did solve it though: installed the RuneAudio Remote Player on the tablet, and there the connection was working. Uninstalled the player app on my smartphone, installed it again, and now it's working. Seems the app does remember some old settings from v0.3-beta, or the DNS stuff is weird at Android.

It's still strange that fing can find the device with the name, but can't ping it. Anyway, it's working now. I agree that this is some weird DNS stuff on Android.

Hi,

did you also try "http://runeaudio." ?

From our docs:
(Windows) open the following address in your browser: http://runeaudio or http://runeaudio. (works if an Avahi/Bonjour client is installed) (OSX / Linux / Android) open the following address in your browser: http://runeaudio.local

Frank

I didn't need to test with http://runeaudio. from WIN, since it was already working with http://runeaudio
It just wasn't working from Android. But please see above.


BR Frank

[janui]

Hi thisisjay,

I tried disabling the username and password requirement in Windows and it still won't connect to my share.

See here, this seems to be the solution: windows-10-share-mount-error-112-t6261.html#p24730 I will attempt to automate the selection of the correct vers=x.x value. Will get back to you when you when the update is avalable.
janui