Engine OS 4.3.1 visual bug: one deck’s waveform appears to drift/bleed visually even if BPM of both tracks is set perfectly and audio is perfectly synced too
I have experienced a weird bug after updating to version 4.3.1 - randomly during a session tracks start to bleed visually, even though the BPM of the songs is the same and output audio is synced and beatmatched, and this happened with songs I’ve been playing previously (on other OS versions), meaning they their beatgrid is correct and they have been correctly analyzed.
I was not able to artificially re-implement the issue and I couldn’t identify exactly what causes it, nor there is any workaround which I could find to fix it rather than rebooting the device completely or downgrading to Engine OS 4.2.0.
What I’ve noticed is that this visual drifting happens on a “slave” track and never on “lead” track.
First time it happened after about 5 hours of continuous playing, but after few tracks the issue disappeared and then again appeared.
The other night it happened after 2,5 hours, but after reboot didn’t happen again until the end of the session which lasted 3 more hours after reboot (the last video is from another night). Also had a weird issue that changing the bpm fader didn’t change the bpm visually on the display (visible on one of the videos at the start), then the same issue happened with the other track, but it seemed that I “fixed” it by pressing “Shift” + “-” range button under the BPM pitch fader.
Some additional info (might be irrelevant and this might not triggeres this issue happening): after updating to 4.3.1, I’ve synced library from Engine Desktop OS to the SD using the sync function, I did no prior re-analizing of tracks, since it was the same library I’ve used on same device during previous Engine OS version 4.2.0 and just wanted to sync updated grids/cues/etc to the Desktop OS and then back to USBs (I’ve synced from SD card to Desktop Engine OS using the circle sync button next to the drive name in the drive browsing view, which syncs only new changes to tracks to the Desktop Engine OS files)
Yup, I have just observed the same behaviour. Note that the waveforms drift into sync at the vertical line representing the play head. It’s almost as if one of the waveforms has a slightly different horizontal zoom
It happened to me on Sunday! If I use sync (I never use it) but on Sunday I tried to use it, and after having deactivated it the problem happened to me too, last night I tried, if I don’t use sync everything works normally, it does it after using sync
I encountered this recently on a Prime 2 on 4.3.1 while using tempo sync. Ejecting and reloading a track fixed it most of the time, but it only went away fully after a reboot. I haven’t encountered this issue on my Prime 4+.
Yeah, I can confirm this as well…
Started happening a few days ago…
it is pretty random and always appears somewhere mid set.
for me it is mostly the second deck, that does it…
I can still beatmatch the tracks by ear and they stay beatmatched. but the waveform is drifting.
So I guess it is a visual Glitch only…
I had the same issues recently, I think this gets triggered by using sync, because I almost never really used it before.
I had a back to back with a friend and we used sync the whole evening and the problem always appeared just like the others mentioned.
I hope this gets sort out quickly, I looked and felt like the zoom of the slave track is sacled weirdly.
I tried to change the playhead position, resetting the screen, calibrating the jogwheels and zooming in and out of the wave view, but it didn’t really help.
Only restarting the controller and not using sinc seemed to help, but I’m still not 100% if sync really was the cause.
I’m holding off on this version. I noticed that its not listed on the site 4.3.1 but when turned my SC6000 they came up with a notification of an update to 4.3.1. I ignored and will keep using 4.2.0 for now.
Yes, that’s it. It’s the “SYNC curse”! It affects everyone who uses SYNC and has been included in the latest firmware releases to target and punish those who use that button! In fact, there’s a title “Don’t push that blue SYNC button!”
Obviously I’m kidding.
Anyway, yes, it happens in the latest versions by pressing the SYNC button even just once (OFF/ON) to quickly synchronize the two tracks when you are in a hurry to change tracks. It happens to me too sometimes, maybe after 10 minutes of use, maybe after an hour, it is not related to the time of turning on the console but by a specific sequence of key presses and pitch fader position. I have not yet managed to replicate the bug, but it happens sometimes.
Some say that you can get out of this bug by pressing “Beat Jump” a few times: I tried, sometimes it works and sometimes it doesn’t.
Yes, can confirm – have seen this visual offset once with 4.3.1. Decided to ignore it during mix and discovered it was magically resolved by the end of mixing the same track. So issue lasted for 3-4 minutes and was resolved by some action during mixing. “SYNC curse” sounds logical
Hey, to anyone on this thread, I recommend getting in touch with Engine support Support | Engine DJ as they may be able to get you access to a special build to test this fix.
