After the 5.0.0 upgrade, the LC 6000 not connecting to the SC 6000.
I tried different cables and ports and any settings to no avail.
On both players BTW
it happened to me too
I’m sure a 5.0.1 bug fix will be released soon… I hope
it will be on the corner i hope too mate
Very well said!
Lc6000 no longer works on this update, please fix
same with the sc5000
Hi Everyone,
I’m wondering if anyone else is experiencing issues with the LC6000 after updating their SC Live 4 to Engine DJ 5.0.
Before the update, my LC6000 units worked perfectly with the SC Live 4 (plug & play). Since moving to v5.0, the console no longer recognizes the expansion controllers. I’ve tried different cables, external power for the LC6000s, and various power-up sequences, but nothing seems to work.
I know this pair is technically “unsupported” according to official docs, but it was a rock-solid setup until now and a huge part of my 4-deck workflow.
Is anyone else seeing this? If you have an SC Live 4 and an LC6000, could you check if your unit still connects under 5.0?
I’ve already contacted support, but I wanted to see if this is a widespread bug in the new firmware.
Thanks!
Immediate? But you’ll want the “hot fix” beta tested though, right? That’ll mean more of a structured, thorough fix taking time to investigate, program, test and release; rather than “immediate”.
In the meantime, you can roll back to the previous firmware, knowing that those new firmware features have been worked on, are coded and are waiting in the wings for LC6000 users too, in due course.
The subject of how beta testing simply cannot catch every single variation and permutation of usage. The main difficulty being when to stop testing.
For example: If I gave you one pair of those “Spot the difference” pictures and asked you to find “all” the differences… but didn’t tell you how many differences there were… when would you stop looking for differences? After a minute? After 15 minutes? After a day of searching? An hour after you’ve found the most recent difference?
And that’s just the dilemma of a flat 2D printed picture … The Primes have so many modes, so many features, so many connection methods, so many user preference menus and settings etc - and just think… with all those many many many multipliers of permutations to test a new feature on, there’s standalone mode or computer/midi mode, which pretty much doubles all those permutations … instantly.
Sure, it’s a bit of a shame that it happened, but I’m sure they’ll fix it
Care to elaborate ? Do you mean that an LC6000 doesn’t work when connected to an SC5000 ?
Ditto, the LC6000 is waiting for information from the mothership but the mothership does not seem to be sending that information across. Had to roll back to 4.3.4 to use my LC again.
Let’s not assume this wasn’t tested, and let’s not assume it wasn’t working on any beta builds. I’m fairly certain plenty of Beta Testers use various setups with an LC-6000 and had it working with all the various compatible hardware.
Haven’t you considered that it’s possible the LC6000s worked perfectly on all the beta versions tested, and that for some reason, such as a last-minute patch for the official release, this could have caused a bug preventing the LC6000s from being detected?
So yes, you’ll probably say that this last-minute patch should also have been part of a beta testing phase, but I bet you would have been the same person complaining that Denon is dead, that nothing has been released for months, or that Denon is too slow to release updates.
Not working even after manually updating… I use a SC Live 4 with a LC6000. The LC6000 shows up under Settings → About/Update but that’s about it. No way to load a track onto it whatsoever
This appears to be the case; all EngineOS devices seem to be affected by this bug, including the Prime 4/4+ and SC5000/60000 players.
It’s highly likely that the development team is already aware of the issue and is working on a fix.
My LCs are not connecting any longer.
(with ext power supply’)
br olaf
I have the same problem after updating SC6000M. The LC6000 lights up but does not work anymore.
Hello everyone, I respect everyone’s opinions, but I think this is a serious mistake. I mean that it is not an effect that doesn’t work or a problem with the library or any other minor thing. Here we have our LC6000s stopping working. I think it is an error that can be corrected quickly, I don’t doubt that, but it needs to have a quick fix or correction. We cannot wait for an update to fix all the detected errors because it will take a long time to solve. This is my sincerest opinion, and yes, by downgrading to version 4.3.4 they work again, but that is not the solution. The solution is to fix it as soon as possible.
OK that ■■■■■. I’d advice you to file a report at InMusic support so this gets the attention it deserves.
Wishing the lc6000 issue gets fixed today so no need to manage this 
Moved, I think, all LC issues to this topic for housekeeping.
Some of us don’t understand how this happened either, as it is/was still working while testing, but suddenly not in the released version.