I’m having a really serious error. I was using the Prime2 as a controller with VDJ for the 95%. Now I wanted to use the P4+ as a standalone next week.
While checking and preparing, the following happened, as you can hear in the video.
I’ve had this happen on the P2 before and was able to fix it. But now I can’t get it to work. Especially… which other tracks are affected?
I only have MP4 files at a constant 320 kb/s.
The wondering is in the PC software: during preview, it plays OK… so I suspect it might be a flag or tag that’s triggering this. Does anyone know what it is? How do I get it to play normally?
I’ll probably give preference to VDJ again. This is making me a bit nervous.
I’ve already tried Reanalyze.
I think I re-encoded the MP4 at the time, simply exporting it from 320 kb/s to 320 kb/s in Audacity. But that’s probably not the solution. Especially since I don’t know which tracks are affected…
Restarting the P4 didn’t solve the problem either. Which is probably difficult to do during a gig.
…You’re right, and the best part is, I can find them all really quickly and re-encode them in 44.1.
Thank you so much!!
These are some really, really old tracks from the very beginning when I was still a Resident, making my first MP3 experiments with ATOMIX. On top of that, they have to be tampered with anyway, at only 96 kb/s, which is really bad.
I’ll still take the little box with VDJ with me just in case…
You never know!
But so far, Engine DJ is working really well, except for the
stems that can’t be placed on the fader or the filter knob… it does what I need, albeit a bit slower. But that’s just how it feels.
Might be VDJ actually, it plays some tracks slower to macht the overall speed, I had this on the pioneer when played on vdj it all spunds good but on cdjs its all off, just need to half the speed manually on the pitch controls
