How do I lock the output of the lumetri panel to the program monitor?

[Andrew C. Brinsmead]

Is there a way to lock the output of the lumetri panel to the program monitor?

As I grade a clip in my program timeline using the lumetri colour panel, the video output of my system (and therefore my reference scopes) will constantly default to what ever is loaded into my source monitor as soon as I finish making an adjustment to a clip in lumetri; the system video output swaps to make my source window active, not the clip that I'm working on in my timeline through the Lumetri panel.

I've tried resetting my preferences multiple times (& clearing my cache), but resetting my preferences doesn't stop the video ouptut defaulting to whatever is in the source monitor.  The only solution is to clear everything out of my source monitor - if any clip is present there, the lumetri colour panel is itching to refer to it.

Is there a way to lock the output of my system to my program monitor when I'm using the  Lumetri colour panel?

MacBook Pro (16-inch, 2021)

Apple M1 Max

64gb ram

Mac OSX 15.1

Premiere Pro 24.6.3

[R Neil Haugen]

As noted on Facebook, I've never even heard of this happening. It's bizarre and would drive ya nuts.

Do you have selection follows playhead 'on'?

[Andrew C. Brinsmead]

I usually have "selection follows playhead" deselected, as I find it annoying, but when I'm grading I do try to remember to switch it on.  However either way, I'm getting the same problem - as soon as I adjust a parameter for a clip on the Lumetri panel, the output flicks over to the source monitor (unless I've cleared the monitor). Often I'll have the source clip in the monitor, and this gets very annoying, as I think I'm working on the clip in my timeline, but seeing the source clip, and my adjustments aren't showing…😖

[R Neil Haugen]

Is the Program monitor on a screen different than Premiere's menu bar?

[Andrew C. Brinsmead]

I have a video monitor connected to the HDMI output from my macbook pro, so the program monitor is visible on my apple cinema display (along with the apple menu bar), while the video output is sourced to my video monitor

[R Neil Haugen]

Ok ... so which is on the screen with Premiere's menu ... the Source or Program monitor?

As if the Program monitor is not on the screen with Premiere's menu bar, the program can be cranky.

[Andrew C. Brinsmead]

both source and program monitors are displayed on the same screen which has the apple menu bar on it. I have a second screen set up with the lumetic scopes & panels on it.  My video output from Premiere Pro is set to go out via HDMI cable to a video monitor

[R Neil Haugen]

Premiere's menu bar is not on that screen ... ?

As noted, if the Program monitor is not on the same screen as the Premiere program menu bar ... there can be issues.

[Andrew C. Brinsmead]

the apple menu bar is on the screen - apple screenshot only included the active window.  This is my standard set up for editing

[R Neil Haugen]

Sometimes Premiere can also be wonky if the "main" Premiere window is not on the 'main' screen as far as the OS is concerned. This has been a royal pain for many users with laptops running additional larger monitors connected to the laptop.

Some don't seem to have issues, but many do. On both PCs and Macs. And sometimes screen scaling can cause wonkiness.

Also ... if you have two or more screens, with the main Pr window on one, panel groups of Premiere on the others ... if any of those panel groups on another screen 'touches' another screen in the "OS" view of total screen real estate, there will be wonky.

I have asked for the ability to select particular screens within Premeire for workspaces. So far, can't get it. As in, put this part of the workspace on X screen. Resolve can do that somewhat sort of. Premiere, not at all.

So I always size my other-screen panel groups such that there is a sliver of screen background visible outside the panel group. Ticks me off but what the hay.

[Andrew C. Brinsmead]

Thanks, but I have my windows sized to fill each screen and not overlap the edges; I've been working this way for years without this issue, it's just crept in on this project while I've been editing in the last couple of weeks; I'm not sure if it's related to working in a productions workflow (this is my first productions workflow, and I've been having lots of significant issues).

Jarle Leirpoll has suggested toggling the "mercury transmit" setting (under video playback settings) off & on, and this appears to be a solution (I need to test it further), which would suggest a preference issue; which is annoying as I've rebuilt my preferences a few times recently (some days, multiple times each day, due to the other ongoing problems)

[R Neil Haugen]

Puzzled by the issues with Productions. Have you read through their Productions guides, and the Long Forrm and Episodic white paper, written mostly by Jarle, which is about the best information on working in Premiere out there?

[Andrew C. Brinsmead]

Yes, and I've watched all of Karl Lee Soule's videos on working with Productions (they're quite good).

TBH, I'm having a world of pain working in the productions workflow - I've had numerous issues with this project since I graduated it to the productions work flow.  I've tried every variation on rebuilding my production project (importing projects into brand new projects inside a brand new production), but this hasn't resolved any of the key issues (and there have been a lot - about 5 or 6 signficant issues; many of them listed by me on the Facebook group "Adobe Premiere Pro Editors of Facebook" in the last couple of weeks)

[R Neil Haugen]

I've seen a couple of them.