I am having some stability issues with tRio (alpha 5)... A receiver will stop working sometimes, and the console on my linux machine says "Got connect from /10.0.0.90" (Rio IP address) over and over.. like this:

Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90

Rio screen says searching for tRio server. Sometimes this happens frequently (like every 20 minutes) and sometimes it happens after a day.. I haven't figured out a pattern. The only way to fix it that I've found is to kill the tRio server and restart it. I'm running on Redhat 9.

Has anyone seen this? Does anyone have a suggestion?

Thanks,
Mike

Can you spot any pattern to what makes it crash out? Is there anything in particular you're playing at the time (shoutcast, mp3, ogg etc.)? Or is it completely random.

As you're on linux, try the following:

1. rename /tftpboot/10.0.0.90/sbin/no-test to test

2. power up the receiver. this should get no further than "Found music server"

3. wait 30 seconds or so and then "netcat 10.0.0.90 5001". you should find yourself in a very basic shell in the sbin directory - type "ls" to confirm

4. type "riot" to run the client and let me know what it says when it crashes

Cheers
Paul

Paul,

Well, I found one problem.. ARM was still running on my Windows machine and the Rio was booting from it. I uninstalled ARM.. I'll let you know what happens. Hopefully that was the problem! Thanks for your help and kick ass software

-Mike

Paul,

Okay.. So on the server side, here is what it says: (I was playing an internet radio station.. mp3, 128kbps):

got header: icy-metaint: 8192
got header: icy-br: 128
got header: icy-irc: #shoutcast
got header: icy-icq: 0
got header: icy-aim: N/A
PlayerStream (/10.0.0.90) - sent Purge(). dataLen: 52
PlayerStream (/10.0.0.90) - sent Play()
java.lang.OutOfMemoryError
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90
Got connect from /10.0.0.90

And on the Rio side:
[MP3] Error Decoding MP3 (257) - lost synchronization
[MP3] Error Decoding MP3 (259) - forbidden bitrate value
[MP3] Error Decoding MP3 (259) - forbidden bitrate value
[MP3] Error Decoding MP3 (259) - forbidden bitrate value
[MP3] Error Decoding MP3 (260) - reserved sample frequency value
[MP3] Error Decoding MP3 (261) - reserved emphasis value
[MP3] Error Decoding MP3 (259) - forbidden bitrate value
[MP3] Error Decoding MP3 (260) - reserved sample frequency value
[MP3] Error Decoding MP3 (261) - reserved emphasis value
[MP3] Error Decoding MP3 (257) - lost synchronization
[MP3] Error Decoding MP3 (565) - bad main_data_begin pointer
[AUDIOBUFFER - ENC] start of block for data. readPos: 63517, writePos: 63517, r
ead: 159
[AUDIOBUFFER - ENC] start of block for data. readPos: 64925, writePos: 64925, r
ead: 1567

The out of memory error is interesting. Any thoughts?

Thanks
Mike

Yup, the OutOfMemoryError is most likely the problem. What's the spec of the machine you're running the tRio server on?

I've got a Celeron 400 with 384 megs of RAM.. the interesting thing is that when tRio is running normally, it takes ~6.8% of memory.. but when it breaks, it takes ~23%. This time when it broke it did this:

PlayerStream (/10.0.0.90) - sent Purge(). dataLen: 11
PlayerStream (/10.0.0.90) - sent Play()
Unprocessed metadata attribute: H∩┐╜WO∩┐╜∩┐╜╚╕∩┐╜n∩┐╜▼zmE∩┐╜∩┐╜∩┐╜∩┐╜∩┐╜∩┐╜∩┐╜∩┐
╜
r�ܬ�
c∩┐╜∩┐╜↓>6∩┐╜T∩┐╜J∩┐╜A)∩┐╜9∩┐╜∩┐╜╓½∩┐╜∩┐╜∩┐╜╘¡↕∩┐╜∩┐╜q=2╥å↕N&∩┐╜I∩┐╜o∩┐╜∩┐╜5_∩┐╜

n)�I��9g"�t�-6��Q
Unprocessed metadata attribute: Zl$RA)∩┐╜∩┐╜h∩┐↕ F∩┐╜∩┐╜╥╛∩┐╜,∩┐╜%P∩┐╜∩┐╜

tg∩┐╜8∩┐╜╥ò∩┐╜┬¿∩┐╜Q∩┐╜d]MW5π▒â∩┐╜∩┐╜$2▼=¶∩┐╜∩┐╜]∩┐╜`∩┐╜∩┐╜Ju╘¢∩┐╜∩┐╜C►J∩┐╜R∩┐╜∩
┐╜
{y∩┐╜∩┐╜∩┐╜o♠∩┐╜e+
Unprocessed metadata attribute: ∩┐╜∩┐╜∩┐╜§J2├╡B∩┐╜1∩┐╜∩┐╜*aI╥àaq,∩┐╜∩┐╜∩┐╜
M∩┐╜∩┐
╜
d:♥R]┌╗ ∩┐╜:∩┐╜{ 0b:
∩┐╜]iL0∩┐╜∩┐╜♥∩┐╜∩┐╜∩┐╜∩┐╜∩┐╜b∩┐╜(∩┐╜$∩┐╜B∩┐╜∩┐╜∩┐╜∩┐╜▼∩┐╜∩┐
╜∩┐╜∩┐╜
U∩┐╜∩┐╜v}H§%6∩┐╜!∩┐╜∩┐╜↕∩┐╜*∩┐╜Z∩┐╜∩┐╜∩┐╜2+∩┐╜?#∩┐╜d∩┐╜↕∩┐╜( ☻∩┐╜∩┐╜∩┐╜▲ZΘì½♥L'∩
┐╜
a∩┐╜3╨»=╧╖∩┐╜∩┐╜∩┐╜┬∩┐╜∩┐╜▌»_∩┐╜∩┐╜Ω¿¿±(∩┐╜∩┐╜∩┐╜0∩┐╜∩┐╜∩┐╜∩┐╜∩┐╜π§∩┐╜Q∩┐╜∩┐╜♪V∩
┐╜∩┐╜
⌐∩┐╜
X[$H○∩┐╜↕■∩┐╜○ ∩┐╜∩┐╜↕∩┐╜E∩┐╜S┌∩┐∩┐╜■∩┐╜∩┐╜∩┐╜∩┐╜7∩┐╜∩┐╜∩┐╜∩┐╜J┌¥▼∩┐╜∩┐╜'∩┐╜∩┐╜∩
┐╜
?L∩┐╜♂∩┐╜A∩┐╜↨∩┐╜┤└ O∩┐╜∩┐╜►↕IN∩┐╜-∩┐╜╬₧∩┐╜⌐∩┐╜∩┐╜☻1∩┐╜∩┐╜∩┐╜#Z_[%∩┐╜∩┐╜►6∩┐╜.∩┐
╜
3:∩┐╜┼∩┐╜∩┐╜∩┐╜∩┐╜╬╖∩┐╜∩┐╜∩┐╜∩┐╜-∩┐╜Θ║╡∩┐╜▬∩┐╜∩┐╜∩┐╜∩┐╜_∩┐╜∩┐╜±7▄║∩┐∩┐╜∩┐╜∩┐╜∩┐╜
Ң

Then, out of memory, got connect, etc..

-Mike

Well your spec should be more than good enough to run tRio, so I think we're dealing with a good old fashioned bug here.

By the looks of this latest error, it's getting its knickers in a twist processing the embedded metadata within your shoutcast stream. What's the URL for the station you were playing? It'll be a lot easier to fix if I can recreate this myself.

Cheers
Paul

Paul,

Sorry for the delay getting back to you.. I'm in Portland, OR and the weather has been crazy for the last week or so.

Here is one station that causes the problem:
<station name="Radio Paradise" url="http://www.shoutcast.com/sbin/shoutcast-playlist.pls?rn=8866&amp;file=filename.pls"/>

But it doesn't only happen playing the radio.. I've seen mp3s cause the problem too. I had trio running on Windows before I moved it to my Linux machine and I don't believe that it was acting flakey on the Windows machine.. Is there anything that could be different in the Java settings? I'm using the trio2.sh script that comes with the package and jdk, although JAVA_HOME points to the jre directory within the jdk.

Thanks
Mike

Sorry Mike, I lost track of this one. There doesn't seem to be an obvious explanation for your problems.

I've spent a huge amount of time over the past 2 weeks completely rewriting the way in which tRio sends audio data to the receivers. It's starting to look pretty stable now, so why don't we give it a try on your Linux set up. If you're keen I'll send you the files - just PM me with your email address.

Cheers
Paul