Light Artifacts/Glitches in Final Render Files.

It appears that a recent change in SeeMusic, likely within the past week, is causing all of my final render files to display random light artifacts/glitches (see video for example). I rendered at the best quality, in 4K, at 60FPS, on a Late 2013 MacBook Pro on macOS Mojave. I rendered the exact same file about a week ago and the output looked perfectly fine. Nothing has changed in my local environment except for updating SeeMusic this week. Is anyone else experiencing this issue?

Great thank you - yes, I definitely know exactly what's causing it - it's the new rendering system introduced by Unity. I've reached out to the video render plugin developer, and hopefully we will be able to find a direct fix.

If not, I'll probably have to look into providing an option to run the app using the old render system - but that would definitely not be ideal, so we'll look for a fix first.

I'm currently following up with the Video Capture plugin developer to investigate this issue - we aren't able to replicate the issue on a wide variety of Mac computers, including a 2012 MacMini... so we may need you to run a test version of an app to isolate the issue on your computer, if you would be willing?

Yes - I actually thought about this more yesterday - in Version 1.18, I've added a "Show Render Preview" button in Create Video Settings that adds the option to disable the video preview while rendering.

If you can try to DISABLE the preview while rendering using that button, that could theoretically fix this issue.

Version 1.18 is waiting for review by Apple, and should be available on the App Store later today or tomorrow.

I updated to macOS Catalina, disabled the render preview, but unfortunately still experience visual glitches in the generated files. I've attached another video to show how bad it can get. I've provided my laptop specs below.

The switch that occurred in the update that caused this issue for you, is that the app now renders using GPU acceleration, instead of just the CPU.

I haven't had a single other report of this issue occurring so far, so the likely issue here seems like it would have to be the graphics card in your laptop - if that's the case, there's just nothing I would be able to do.

I know it would be very frustrating to feel like you were able to use the app, and now you can't - but I'm not able to revert the app to the old way, because it now depends on the GPU-acceleration that has been incorporated since that update.

If you want to send me your email address and are prepared to do testing of custom builds in a timely fashion, I'm happy to try to debug this a little more over the next few days. Otherwise, the best solution might be to try the app again with a new device.