RuneAudio Forum

People have pointed out that you need the latest night release in order for the Android control to work. I should point out that you only need the latest night release for the Android app to discover the player. Once it has discovered it you can roll back to your previous version. I run the latest stable release (ie not the night release) on Raspberry PI 2. I just booted my PI temporarily on the latest night release and then reloaded the original software. You can even use a different SD card if that is easier. Works a treat. Thanks for the nice work guys!

This weekend I noticed that the Android Remote app does not always recover after a manual reboot to my Rpi 2 w. HiFiBerry Dac+. (meaning compared to the Web UI)

On reboot, the web UI shows a spinning circle for just the time it takes the Pi to reboot and the login prompt to appear (about 30 sec).

The remote app just stays on the spinning circle, indefinitely. Player Discovery does nothing in this case, neither does clicking on the player name below that.

Same thing occasionally (not always) happens if the tablet I use for the Remote App loses the WiFi connection to the player, for example when I am carrying it from room to room.

ACX wrote:

BayleeWylie wrote:I know this is a long shot since it just came out... But is there any plans for an iOS version of this app?

Yes, we'd like to replicate the same also for iOS if possible.

Good news.

Until that, there is an alternative on ios app to control runeaudio?

Playing one album how can I choose/see only those musics?

Thanks

What algorithm does it use to find players? http://runeaudio.local is working on my desktops (Ethernet connected), but are not working on my wifi-connected tablet. Neither is the RuneAudio Remote Control for Android. My server seems to be running all the usual protocols:

[root@runeaudio ~]# netstat -tna
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:6600 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5002 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:82 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:83 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 198 0 192.168.86.106:80 192.168.86.22:36199 ESTABLISHED
tcp 0 0 192.168.86.106:22 192.168.86.2:46062 ESTABLISHED
tcp 168 0 192.168.86.106:80 192.168.86.22:36222 ESTABLISHED
[root@runeaudio ~]#

Hi RussNelson,

What algorithm does it use to find players?

It uses avahi see here?

Frank

Not sure if any others have reported this problem, but when using the remote, sometimes it will crash the pi/cause a hard lock.
I've replicated this while having an ssh session open to rune - when crashing, the ssh session becomes unresponsive, the web interface doesnt work and the application goes into a spinlock. No idea what cause, but if there are any logfiles I should check please let me know

-D

hondagx35 wrote:Hi RussNelson,

What algorithm does it use to find players?

It uses avahi see here?

Frank

I already saw that. Sorry that I didn't tell you. So RunAudio Remote Control does some avahi-thingie like call into a library or spawn some executable, and when avahi throws up its hands and says "I can't find runeaudio MPD", there's nothing to be done? Here's what I get from my desktop:

nelson@d2:~/Slic3r$ avahi-browse-domains -a -t | grep Music
+ eth0 IPv4 runeaudio Music Player Daemon local

Sure looks like runaudio is holding up its end of the protocol. I downloaded this: https://play.google.com/store/apps/deta ... jour&hl=en to my phone, and when I run it and ask to look at "local.", it says that there is a _mpd._tcp as well as a Remote Audio Output Protocol, which may actually be the Chromecast.

So it looks like my phone is able to use Avahi to find _mpd._tcp. What algorithm is RuneAudio Remote Control using to find the RuneAudio server?

Hi RussNelson,

What algorithm is RuneAudio Remote Control using to find the RuneAudio server?

it is all documented here.

What is your problem?

Frank

Russ-

Discovery is based off of the "_http._tcp" and not the music player daemon. When you use Bonjour Browser, you should actually see a response like "RuneAudio [host] [xx:xx:xx:xx:xx:xx]. This response from the server is only available from 0.4/nightly builds on.

If you are not running 0.4, you can either 1) add the service, which is documented in the help section mentioned in the forum, or 2) from the app, go to SUPPORT AND CREDITS and manually add your device.

Hope this helps-
Elliot

The app is awesome. thanks