Shaky Waveform when Projecting Video Out

Device: MacBook Pro (16", 2019)
Processor: 2,6 GHz 6-Core Intel Core i7
Operating system: 15.6 (24G84)
Djay version: Djay Pro 5.4.2
Hardware/controllers used: N/A (happens with or without controller connected)

Summary of the issue:
Waveform gets jittery as soon as I cast the master video out onto an external display. Makes me feel like I am dizzy with blurry vision!
See video illustration to demo it. Please do NOT maximise the video. If downloaded video, Use VLC media player to appreciate the waveform shaking (frame-rate issues).

How to reproduce the issue:
Play a vdieo file AND project master video onto an external display - waveform starts jerking
Unshow video from external display- waveform gets smooth.

This behaviour happens in all djay modes for as long as there’s a video being projected out onto an external display. The frequency of the jerkiness slows down the more the size of the djay app interface is reduced…fastest jitteriness is observed in full-screen but if I resized djay to a tiny size in the middle of the primary screen, the jerkiness is slowed down to a definite frequency (like after every 2-3beats, etc)

1 Like

Thanks for the details and video @Armigo - very helpful! I’ve shared this with engineering for review and comment. Let’s keep the discussion in this topic instead of the other one going forward.

1 Like

Hi there…
Did the team manage to demonstrate this or make a comment?
It’s a persistent issue still.
I have done all sorts of optimisation procedures I could ever google about, in vain.

Yes, the team was able to replicate this and is investigating further…

1 Like

I was so hopeful the “various bugfixes” of v5.5.1 fixed this issue, but, alas, just done the v5.5.1 update - bug not fixed. Waveform still shakes once projection starts.

Any chance this bugfix is “near-completion” or is it one of those that is unlikely to be fixed?

Something strange I discovered: When I wirelessly connect to Hisense VIDAA smart tv via AirPlay, the shaking seems to go away. Does this point to something?

Thanks for checking in @Armigo. A fix for this was not included in 5.5.1. The team is still working on this. I don’t have a timeline or any other news to share at the moment. When I have updates I’ll post them here. Thanks!