When using the sc5000M players in HID mode with Serato DJ, does it severely increase your cpu usage?? Mine goes through the roof, so bad that i can’t record a mix. I had the sc5000 players before, never had any issue!
Im using the x1800 as my mixer
All firmware, drivers and Serato versions are up to date, i even upgraded my HDD to an SSD and increased the RAM from 8GB to 16GB but that hasnt really helped. Iv done all the system optimization on my laptop that Serato asks.
Any guidance would be greatly appreciated
Also, its a windows 10 laptop but has the same affect on my mac mini, so please, none of the usual ‘buy a mac’ responses!
Its an intel dual core i5, 2.5ghz x 2. Iv never had issues with any other equipment, even the sc5000s were flawless. Would there be a problem with the moving platters? Like they send extra midi info or somthing? Im hoping there is just somthing i need to turn off or on in the serato settings to fix it but cant see anything!
If you are using serato bare bones sure you can get away with dual core, but once you start using FX, KeyLock, PNT it will struggle.
It’s common knowledge in the Serato forums even though their documentation states otherwise.
These are simply the minimum requirements to run Serato DJ Pro and the Serato DJ ProExpansion Packs. For best performance and for use in professional situations we recommend you use a higher spec computer, preferably with an Intel processor.
How’d you get VDJ to not do weird things with the Ms? Am I supposed to be using the USB 3.0 B connector cables into a powered muti TT USB 3.0 capable hub into a USB 3.0 capable port?
If Engine OS just sounded roughly as good as Gemini or American Audio near zero pitch or with keylock off, I wouldn’t even be bothering with demoing the full VDJ at home. Many hours spent modding and troubleshooting.
I think playing out I won’t bother usually with VDJ even if this gets working fully, but practicing at home or streaming in a controlled environment, it’s been worth the effort so far even with an overall slight increase in response latency.
The big hassle is just the Ms now. I have to turn slip on and disengage the motors if any tracks are playing on the Ms before loading and analyzing any more lossless tracks from Tidal. It’s a hassle, but I’m making it work so far. Hopefully there’s a solution.
I’d also like to try implementing my key changing layout from that Beast Mode interface mock-up. Right now VDJ doesn’t even show the new keys you’re changing to on the + and -.
I do have most of what I don’t want hidden sufficiently from the screens, though, and fixed some other issues with the maps and skins.
I’m also reminded of just how far we’ve come with Engine OS and the various suggestions we’ve asked for that have been implemented, like soft takeover override on track load, that VDJ is lacking.
