Source/Program Monitor Mirror Glitching

[katieto]

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!

[MyerPj]

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/

[jamieclarke]

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.

[katieto]

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]

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.

[katieto]

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.

[katieto]

Thanks Jamie! I realize that. I'll turn show audio units on when doing microadjustments on the sync as needed if I discover an area that's off by just a bit and needs that micro nudging, which is what I was doing when this all kicked off. I generally don't edit in that on a whole but thanks for pointing it out.

Importantly, I wanted to also report that despite grabbing that driver, the mirroring issue is still haunting me so unfortunately I don't think that was the culprit so, it's still there.

[jamieclarke]

Hi @katieto - I would say install the current latest Studio driver 566.36, since we know thats not the problem.  Do you have any features in the Nvidia app that are enabled?  Have you identified any reproducible steps or is it still random?

[katieto]

Nope, no reproducible steps came to light because of it being quite random and also present in many projects, so not tied to one particular thing far as I can tell. I think I already gave you all the project file I consistently saw it in when I wrote this report.

As for Nvidia app, is there something more specifically you're asking if enabled or not? I don't have any overlays if that's what you mean. At any rate, I'll go ahead and update that driver back to recent.

[jamieclarke]

Hi @katieto - Can you take a screenshot of the entire window next time it happens again.  There a bunch of tweaks you can do in the Nvidia app in the settings section there are features labeled Nvidia overlay and game filters and photo mode.  In the System setting you can change video enhancement modes. and in the graphics settings there are global settings.  If you didn't manually change any of these then we can rule that out.

[katieto]

Thanks again for checking in Jamie! So it's happening and I'll try to explain what was going on while it did. I was playing back from my selects sequence timeline which shows up in Program normally. The source panel just looks like I've loaded that same shot in, but I didn't and instead should contain the multicam sequence loaded there. See my screenies.

Program mirrored over the Source Panel this time. It had what I can best call a 'screen tearing' on the very left end of the mirrored Program video playing over Source as if it wasn't fully there copying it, which you've maybe seen already in my attached vid from initial report since I captured it live playing back.

When it happened, I went to use the snipping tool to take screenie, and it's as though Premiere refreshed during me clicking and back, which is why it looks "fine" like a clip loaded to source. I even tried my shortcut screenie command but that seemed to refresh it too. Went ahead and moved the scrubber again, still there, only this time I took a phone pic to more clearly highlight and retain this 'screen tear' I mentioned. Sometimes it's a small one like this, sometimes 1/3 of that panel is see-through past the glitch thing.

I feel like it's related to something with how things are refreshing? Somewhere? don't know how or why exactly or if I'm just cursed lol? Hope that makes sense. 

What a mystery indeed!!

here is how it should look:

Here is when it did the mirroring from the Program panel over my Source, no tearing but still wrong, the left source side should have the multicam from my other screenie:

Close up of the 'screen tear' type thing I described via my phone so it wouldn't refresh and look "normal":

[jamieclarke]

Hi @katieto - What type of cable are you using to connect to your monitor?  Is it plugged directly into the graphics card?  In the Nvidia Control Panel do you have g-sync enabled?

[katieto]

the hdmi cable is directly into the gfx card, and I don't have a gsync enabled monitor. I've been on this same build of pc, as I built it for primarily editing but as bonus works good for gaming too. Which up to now, both were without tearing issues or the like. So far any has only been happening to me in Premiere, and I guess only in v25. Not sure if Win 11 has any part in it too. 

[MyerPj]

My Win11 (23H2) is working fine. We are using 25.1, I believe you are too, but you didn't say that in your recent post. There's a difference you know. I've been on Nvidia 566.36 (studio of course) and it's been stable.

[katieto]

hey thanks for the reply. Good to know! oh, I put that info up top in my initial report posting that I was on Operating System: Win11 Pro 64-bit on a PC but will also include that is version 24H2 (OS Build 26100.2894) if at all helpful. Appreciate any thoughts!

[katieto]

*sigh* sorry I went on about windows, clearly didn't caffeinate enough today. you were asking about Premiere. I did put that in the report too, it is Premiere version: Premiere Pro v25.1.0(Build 73)