RE: Re: xPLRioNet beta v3.7d

["Tony Tofts" <tony@xxxxxxxxxx>]

Hi all,

That was tricky to find, but easy to fix :-)

Version v3.7e, which will be published shortly - just looking at a genre
tag
issue, will fix this.

Basically when the next track starts it waits for a signal from the rio
that
the previous one has really finished (necessary to ensure the rio display
is
updated at the right time).

I'd allowed 10 seconds for the rio to buffer any queued remaing data, and
then play out the buffer. If the signal wasn't received within 10 seconds
then the track was aborted (not very well as it turns out) as it was
assumed
something had gone wrong.

This lead to the software being in a state where it thought it was playing
but wasnt, so when you then pressed stop it went off into oblivion.

The 10 seconds appears to have been on the border line, as I found it
difficult to reproduce the problem here.

Anyway the 10 seconds is now 60 seconds, way over the top, and the player
is
flagged as not playing anymore if an abort is raised.

Regards
Tony