Skip to main content
Participating Frequently
January 17, 2025
Question

Source/Program Monitor Mirror Glitching

  • January 17, 2025
  • 15 replies
  • 1156 views

Issue:
Both source and program monitors are behaving oddly during playback as if a glitch or bug, I'm not sure what. What it's doing is creating a mirror image of itself on either side of itself, consistently but at random times throughout multiple projects. Like a ghost that will not stop haunting me! hah.

For example, if I've loaded a multicam to source and hit play, sometimes I suddenly see a duplicate of the same source window (with obviously multiple angles of footage in multicam view) over where Program monitor is. It doesn't entirely cover it, just most of it. And begins to act laggy and strange when this happens and tips you off something is going wonky.

How to encounter the bug & Workflow: 
This admittedly might be trickier. I've created dozens of multichannel multicam using go pros and a main A/B cam angles (Sony FDR-AX100, can include a clip if you need!) but it's even doing it just with gopros stacked so camera doesn't seem to influence it.

Frustratingly, this bug glitch thing doesn't happen every single time I hit play, more like it happens randomly so could be once and not again for awhile - or could be that it sticks around while I hit spacebar toggling play and stop over and over. So I do suspect it'll be problematic to recreate but here's the report on it anyway.

Because we tend to load our multichannel multicams into source, this happens the most for me in Source playback, but occasionally with Program playback from timeline. When I'm playing direct from timeline to Program monitor, it'll mirror to the left now over where source window hangs out. The Source/Program monitors are side by side per usual in my layout by the way, so you can picture what I mean when I say to the left or right, and included a screenshot.

Steps for multichannel multicam:
All footage and audio get synced and labeled, then I create a new sequence, set it up to match framerate (29.97 in this case) along with it being multichannel, load it from the grouped sequence, then assign it proper channels and all that jazz. Then, I open it in source, enable multicam, and modify audio channels for mono for however many # tracks there are.

What was expected vs. what happened:
What should have happened is what we all expect, for everything to play as normal in source or program monitor without any weird mirroring duplicate windows occurring. And instead, that is what keeps happening to me! This has consistently gone on for days now. I've been in all sorts of projects, made new ones, hopped in already made ones, doesn't matter. I'm slowly losing a bit of sanity every day though and would love to get this solved! 

I do not have any third party plugins or panels installed presently to add into this mix.

Operating System: Win11 Pro 64-bit on a PC
Premiere version: Premiere Pro v25.1.0(Build 73) that's as up to date as can be.

Specs:
CPU - AMD Ryzen 7 3700X 8-Core (16CPUs),~3.6GHz
GPU - NVIDIA GeForce RTX 4070 Ti
GPU Driver - GEForce Game Ready Driver Version: 566.36 Released Thu Dec 5, 2024 (NOTE: I did try first installing the Studio Driver and encountered same issue, swapped to Game Ready, and it continued)
RAM - 32768MG 
Hard Drive - 1TB internal ssd and 5TB external hard drive via USB 

I've attached everything I could think to send including the entire project, screenshot of it doing that mirror thing as described, a very overtired phone vid of me capturing it doing it live, and a quick spec on the actual footage for gopro and the Sony FDR-AX100 clip.

Please let me know if you need anything else. I did try to be thorough!

15 replies

katietoAuthor
Participating Frequently
January 17, 2025

Yes forgot to say, I've installed that 566.14 studio driver and will report back. As of now, it hasn't done it though that's not surprising since it was occurring whenever before. I'll keep working and project hopping to test things about and let you know if or when I see it again.

jamieclarke
Community Manager
Community Manager
January 17, 2025

Hi @katieto - Were you able to find and install the 566.14 studio driver?

 

I just noticed from your video that you are in sub frame editing mode, to get out of this mode click the hamburger menu next to your sequence and deselect "show audio  time units". Sub frame is great for audio edits but I wouldn't suggest it while editing all day.

katietoAuthor
Participating Frequently
January 17, 2025

Thanks for your thoughts! I had studio driver on with the same result, swapped it to game one to test that too in case of another result. I have reinstalled the Studio one. Totally agree the gopros can be bit rough all stacked up pre-proxies, most it would do in past is lag a bit but bearable on 1/4th quality, if I gotta get by in pinch. I'd just never seen it do -this-!

jamieclarke
Community Manager
Community Manager
January 17, 2025

Hi @katieto - As Myerj has said, Adobe recommends always using the studio driver in Premiere Pro.

 

I haven't seen this issue before can you try rolling your driver back to 566.14 and see if that helps.

Thank you for your video if you can get consistent reproducible steps please let us know.


Sorry for the frustration.

MyerPj
Community Expert
January 17, 2025

I would suggest not using the Game driver, stick with the Studio. Perhaps you are hitting the edge of your computing horsepower? GoPro footage is not easy on the machine. You might proxies or to transcode the 4k gopro footage to something like ProRes LT or even Proxy.

 

Use Shutter Encoder if you want to transcode, otherwise create the proxies via PP/Media Encoder.
https://www.shutterencoder.com/en/