Serato Video General Discussion

Talk about Serato Video and Video-SL.

Serato Video "Glitchy" on MacBook Pro M3 MAX

muzik326 11:45 PM - 27 August, 2024
I recently purchased a new MacBook Pro M3 Max. Everything runs great except the videos glitch from time to time. The audio is fine just the video gets pixelated and washed for a second or 2. This files never did that on my M1 Max or i9 16".

I am having a hard time finding any similar issues online to help solve this.

Thanks
popnwave 1:04 PM - 28 August, 2024
I think most of us gave up on the video plug in long ago and moved over to Mix Emergency.
Marlene495Hadley 11:11 AM - 13 September, 2024
Hello!
If your new MacBook Pro M3 Max has video glitches, try updating macOS and your video apps, resetting NVRAM/PRAM (Option + Command + P + R), testing different resolutions, and checking external display connections. If the issue persists, contact Apple Support for further assistance. www-panoramacharter.com
djpipes 5:09 PM - 10 October, 2024
i was having the same issue, until i turned of "Hi Res Display" in the settings. Now it runs smooth without issues.

Hope that helps
Jackop 10:27 AM - 29 December, 2024
Hi Bertax, it sounds like you're having trouble enlarging the waveform in Serato. Make sure you're using the correct keyboard shortcuts for your version, typically the "+" and "-" keys to zoom in and out. If it still doesn't work, try restarting Serato or check your settings to ensure there are no conflicts. For more details, you can check out this link: newtoki.blog.
DJ Tecniq 7:53 PM - 29 December, 2024
Never had an issue w/ Serato Video and I’m on a M1 Pro w/ Ventura. Could be the video file itself however you said it never occurred on your previous Mac. Could also be a transition effect is on and you aren’t aware.
MarkMarkMark 11:42 AM - 14 January, 2025
I've noticed applying any of the "OutFX" sound effects when using Serato Video in 3.2 release kills the video output. Do you have any audio FX selecting (even at 0% seems to kill output)?

This wasn't the case in 3.1.x so possibly related to the changes around the end of iZotope licensing deal :-(

I have a on-going support request at the moment around this issue so would be interested if this affects others too (especially those that have Video Pack but not the new $$$ Fx pack)