One Mac is updated to Engine Desktop 4.0.0 and I have not noticed the freezing issues there that a few others report. After update to Engine OS 4.0.0 firmware on my 2 SC6000 connected via digital to the x1850 mixer there appears to be some communication issues. When one SC6000 is playing and the other is turned on, the playing unit freezes while the other is booting. This is not a momentary freeze, which never bothered me.
In addition, periodically one or the other units will freeze for long periods and all controls are dead.
Also, Sync is misbehaving at times. The second unit may not recognizes the BPM on the master and it appears to randomly set the BPM to 123.6.
Has anybody else with this setup noticed issues? I will continue to troubleshoot on my end.
Dose the unit do this when not connected to the ethernet?
Try running the unit in pure standalone, i.e just as a single player & audio cables no usb or ethernet.
See if it happens, by the way, dose your unit also require a hard rebot or just recovers after time…
Thanks. Traveling sans units. Before leaving I tried SC6000 to SC6000 ethernet connection and except at startup there were no pauses and sync worked the way I use it (on to match bpm/beats then off).
I did put the ethernet links back into the x1850 to see the difference. Either way, when player 2 is playing and then I turn on player 1, you get the pause on player 2. If player 1 is playing and you turn off player 2, you get the pause on player 1. I don’t remember this behavior with 3.4. If everything is started at the same time and I wait, it seems all is well. Sync working correctly is hit-or-miss on boot. If not, I reboot. Once everything is working, smooth sailing.
When I return, I’ll try new ethernet cables and your suggestions. Although, I’m a little reticent to reset the x1850. It’s on 1.7 firmware and comments make me think it’s fussy.
I’m curious to know a situation where both decks would not be switched on simultaneously or within a few seconds of each other, before a.tune is played, thereby avoiding this niche behaviour
This long pause didn’t happen under 3.4. Now I’m aware. In the past, both units might be running when I realize, at some point, sync and match aren’t working. My assumption is this is some kind of communication error. The remedy being to reboot a deck. So, I’ll check all that out at the beginning.
I’m going to replace the ethernet cables to see what happens.
This won’t be an issue with the Prime 4+, which is next on the purchase list unless Algoriddim gets its act together and supports the Rane Four.
