Sc6000 odd play button behaviour

hi collective hive mind, a little help please, whilst creating a playlist on my sc6000 twice now the layer A play button stops responding, it lights up but does nothing, Switch to layer B load same track and it works fine, suggesting not the button itself, Restarting the player makes it work again suggesting software not hardware. when the button fails even the fader start option on my x1850 is unresponsive, fader up buttons lights on air led lights on the player but no playback when its failed i can start the track with shift&play but it if i then hit cue it it returns to cue point but its still not working. it appears fine when just using playback, just a playlist edit seems to trigger… thoughts please.

Hell @Djmattyshizzle Did you tried to switch off the vinyl mode, and check if playback works then?

Have a try an let me know, I think, it could be one of the typical issues… But let’s rule out other things first with the test, I mentioned.

Hi, I wasn’t in Vynl mode at the time, if I get it to do it again, should I try to select and deselect vynl mode and see if that cures it?

You can try. A video when it happens would be helpful to troubleshoot it maybe too. Try to film it and note the steps you took before it happened.

I’ve seen this a few times where it will register that you hit play and light up the play buton, but it just won’t start the track. This seems to happen from either corrupted Engine database library and/or corrupted drive, especially when the Engine Connect network link for drive sharing is active, especially when the player trying to start the track is getting said track over the network link. While getting the track from a drive over the link makes this more likely, I have never see this on a drive with no previous Engine folder, with a fresh Engine library database folder created with the Engine DJ desktop app, or using tracks downloaded live from a streaming service with no drive connected or at least no drive actively in use (i.e. you’re in read-only mode and get the message). An early indicator this problem above will eventually afflict you and a more common one is that the on screen HUD data such as moving waveform will not entirely generate for the track, but you will still be able to play the track. Sometimes this early symptom is accompanied by only a chunk of the track being playable but not the rest of the track.