[slinkelist] cdj sending an erroneous "playing" response

[Mike Macgirvin]

> That's because this is what is acutally happening. Sometimes CDJ plays through very slightly into the next song for one reason or another.
>  
> Colby

Don't know if there are other reasons (timer granularity, etc.), but I 
noticed that I would often get play through of the following song for a 
few seconds or more (up to 30) as I exhausted memory; since it took that 
time for CDJ to swap back in from disk and send the next command. I 
could hear the disk thrashing heavily whenever it occurred.

Tends to happen on a regular basis if you have a well-known web browser 
running for a long period of time leaking memory. :-)

I doubled the system memory, started doing my browsing on other 
machines, and haven't had a problem since.


> -----Original Message-----
> From: slinkelist-admin@nirvis.com [mailto:slinkelist-admin@nirvis.com]On Behalf Of Marc Hebert
> Sent: Friday, January 05, 2001 2:26 PM
> Cc: slinkelist@nirvis.com
> Subject: [slinkelist] cdj sending an erroneous "playing" response
> 
> Hello.
> 
> I'm using an app I wrote, which communicates over a socket with the HASE Slinkx Socket Server to monitor what CD's currently playing.  I send the "notify_playing_item[on]" command and start receiving the expected async "playing" responses.
> 
> The hitch is this- every now and then I get an extra, erroneous response, and it always occurs like in this example:
> 
> What actually plays:
> 
> player 1, disk 33, track 6,
> player 3, disk 140, track 9
> 
> What's indicated in "playing" responses:
> 
> player 1, disk 33, track 6,
> player 1, disk 33, track 7,
> player 3, disk 140, track 9
> 
> So, every now and again (maybe every one in 10 or 15 transitions), it reports a track just after a last played track, that wasn't in the playlist and indeed did not play.
> 
> If I notice any more pertinent details, I'll post them.  Anything I should look for?
> 
> Thanks,
> Marc