PDA

View Full Version : Play oddities with 2005-07-24 6.1.2 nightly



jbm
2005-07-24, 15:02
After installing SlimServer_6_1_x_v2005-07-24.dmg on my Mac OS 10.4.2 machine, I tried playing an MP3 file on my two synchronized v2 players. The info showed up correctly on the displays, but there was no music and the elapsed time count stayed at 0:00. I tried an MP3 stream; the music played, but the elapsed-time counter stayed stuck at 0:00.

I unsynchronized the players, and things seemed to work okay. When I re-synchronized them, they still worked correctly and are doing so now.

So... I doubt I can reproduce this now, but I thought I'd just post in case this rings a bell for someone who understands the code.

jbm
2005-07-24, 15:18
It wasn't clear to me whether I should post this sort of report here or over in Beta (or somewhere else?) A few weeks back I posted a report about a nightly in slimserver-discuss, and was directed to "the developer list".

-Jeff

Rob Holden
2005-07-25, 01:13
I get the same thing with the 6.1.1 release, and I can reproduce it easily.

1. Synchronise players
2. Start listening to the first track
3. Hit fast forward
- at this point, the display updates, but the next track doesn't start.
4. Hitting play starts the track, or FF again moves to the next which
starts playing
5. Hold pause (stop)
6. Hit play - current track starts
7. Hit FF
- again, the display updates but the track doesn't start.

steps 4-7 are the ones to repeat it over and over.

My system: Compiled slim.exe on Windows 2003 server, synchronised Squeezebox2s.

Regards,
Rob

On 24/07/05, jbm <jbm.1sp2eb (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
> After installing SlimServer_6_1_x_v2005-07-24.dmg on my Mac OS 10.4.2
> machine, I tried playing an MP3 file on my two synchronized v2 players.
> The info showed up correctly on the displays, but there was no music
> and the elapsed time count stayed at 0:00. I tried an MP3 stream; the
> music played, but the elapsed-time counter stayed stuck at 0:00.
>
> I unsynchronized the players, and things seemed to work okay. When I
> re-synchronized them, they still worked correctly and are doing so
> now.
>
> So... I doubt I can reproduce this now, but I thought I'd just post in
> case this rings a bell for someone who understands the code.
>
>
> --
> jbm
>

dean
2005-08-02, 15:04
Rob,

This has been opened as bug 1869:

http://bugs.slimdevices.com/show_bug.cgi?id=1869

Vidur has a few questions in there, can you update the bug with details? Thanks.