Program Monitor bug that makes Premiere Pro unusable
The program monitor is not showing work. Only a solid black or white box is visible. It also gets permanently cropped when resized until restart. This is a very serious bug that is causing Premiere Pro to be unusable. Same applies when view your project in full screen (Ctrl+`)
Connar Lorimer
shared this idea
25 comments
-
harley davis
commented
More info... Check your playback controls. There may be several software clashes going on.
First, I found that Adobe DV and the immersive environment both have a few issues when there are external enhancers in front of audio or video. Overlay enhancers, fps enhancers, anything and everything that sits between adobe and the main driver will initially cause problems. That's because the enhancer does a pull data pass, and adobe does a push.
Without going any further I can give you several possible solutions.
For me, turning off a dolby enhancer allowed me to pass Adobe DV through. Turn it off before starting the app, turn it on afterward. The "Enhancer" on my system isn't really an enhancer, it just allows me access to all of my speakers, not just left\right. I have a subwoofer and the speaker power level can be much higher than the standard system provides, requiring me to turn on the enhancer to fully activate my speaker system. When I turned this off, Adobe DV was capable of playback again. I suspect it always was, but it didn't get sync info from the enhancer the way it would from the audio system driver.
If you have any Video enhancers in your drivers, turn them off, start the program and begin playback, during playback turn the enhancer back on and determine if the video stops. If not, leave it be. Stop playback and start again to be sure. If it quits, then keep your enhancer turned off while working.
I think it's inteligent that adobe passes graphic data to a driver in such a fashion that you can actually have it sent out to external devices in a similar mode, and be synchronized. The downside is that it doesn't give you the ability to choose which hardware device id it uses to do so. It lets you choose a compatible synch driver, like adobe DV or immersive, but it doesn't let you select what path they use to get out. IF you send data to an enhancer, it only acts on the data and passes it out to a hardware driver, not necessarily back to the place the data came from (sometimes the hardware driver passes the data through the enhancer on its own, but if you have to activate the enhancer, chances are it interrupts the data transmission path and looks like a driver enough to be mistaken by some software). -
harley davis
commented
So... ...I've now made another discovery... ...If I turn off adobe DV, everything is fine. I'm wondering if it wasn't part of the DV library structure that was just removed from windows that might be causing this.
No it wasn't "Physically" removed, it just cannot be run any longer. It's kind of sad really, that windows is locking out all the library files that older software uses to actually function fully. That means that most software that uses it for playback will start getting errors.
This is only backed by the fact that some versions of these files are included with some utilities I've downloaded, and are placed in their respective folders to allow access. When these files (same name but older version) are taken out of the folder and replaced with the newer, they function fine. Remove the files completely, and they fail at first. That means that any projection passthrough like adobe dv will fail to function.
This could also be due to some missing dlls, I've recently removed a lot of vc+ libraries that came with software I no longer need and this really started fouling up. How about an installer that puts it all in Adobe? Not just the "Neccessary" files in the main folder, but actually check for dependencies in the updates, and overwrite once in a while. Even with my beat up SSD I'd take that over missing functions. -
harley davis
commented
And by rendering, I mean preview cache.
-
harley davis
commented
So it's definitely a mercury graphics problem. I got the same behavior in after effects after rendering a few times.
-
harley davis
commented
Turn off mercury transmit in premiere, turn on in after effects... ...weird.
-
harley davis
commented
I turned off Mercury transmit and it all came back up in premiere. The problem is, now after effects has a larger issue as well.
I have a feeling this has to do with DV support and the linkage to dvcam devices being dropped in Windows. It's not a big deal, as most can be captured with new shuttle and transfer devices, but most consumer grade are a heaping, stinking pile. So far, premiere is the only one i've been able to use to passthrough a VCR through DV ilink without having a tape in the dvcam, and since most DV footage can be played back natively in AVI, using an intermediary like Adobe DV might just put more strain on the whole system. It's mercury transmit that's causing the problems in playback. Try it without that. -
Pete Rose
commented
While I have always been a great fan of Premiere, I am now finding it to be profoundly useless- white program windows when switching between sequences; unpredictable crashes; an overly complex title interface; etc. What is going on at Adobe? Does anyone there actually try to use the software?
-
Brett Naples
commented
Just updated to 14.0 2019 and having same issue when I switch to the lumetri window. It makes premiere completely unusable. It boggles my mind that Adobe releases something that doesn't work. I cannot switch myself but I tell everyone who asks me about this program the truth. I interact with a lot of editors and videographers and I tell everyone about how glitchy Adobe is and it simply cannot be trusted. I have now wasted hours on this and as always Adobe refuses to accommodate users for THEIR broken software that we pay actual money for.
-
Peter Rose
commented
All of a sudden the program window has started going completely white when opening a new sequence- this was never an issue and it is VERY troubling. I upgraded to High Sierra to no avail. But I did find that turning my external monitor off and then on again often fixes the issue. Come on Adobe, get with it. Too many people are complaining about this.
-
Daniel
commented
Same here. I'm happy to report that resetting the preferences on start-up with Command + Option worked for me.
I did nothing except add a Warp Stablizer to some bouncy footage, then slide the basic Lumetri orange/blue balance, and change Workspace view. Got some white screens, force quit a few times, then black screens. Play didn't work, obviously, but I could still add cuts and so on.
-
Joseph Bastien
commented
Try resetting your Premiere prefs. On startup, hold Cmd + Option. You'll get a pop up that asks to reset. Had this issue today. Did this reset and it seemed to fix it. Just be aware, you'll need to go back into your preferences and redo anything that you set there like project locking or autosave stuff. Obviously, a pref reset will remove all that stuff. Good luck!
-
Les
commented
I get a Black Program Monitor if I choose 200% and stray too close to the edge of the content area. Once it snaps to the outer edge the box goes black and stays that way until I restart PPro. Running V13.1.2 Build 9
-
Anonymous
commented
I wanted to add to my previous comment, Turning off Safe Titles brought back the video. For programmers who will hopefully troubleshoot anf fix the problem, Lumetri Scopes were still responding to video even when the program monitor was black.
-
Anonymous
commented
This bug just happened to me. Everything has been working perfectly after upgrading to Mojave last week. Including having safe titles on. For no apparent reason, program monitor wouldn't work unless i set it to 100% any other option gave me black with white line at the edge of the screen.
-
Anonymous
commented
I'm having the same issue - a white line has now appeared at the bottom of the screen in the program monitor. No video playback is available, it does play the audio. fml
-
Anonymous
commented
I Have the same problem. Using MBPro 2018 on Mojave. Prem Pro 2018 works totally fine, but that version won't recognise my 2019 Media Encoder app. Renderingg all my NLE work here useless.
I can't create proxies to run the 4K footage through.
I am very close to quitting this program entirely.
-
Scott Middough
commented
Same thing for me. Fully updated, new macbook pro. re-installed. Tried it all. Nothing is working and I'm going to have to use another NLE to keep working.
-
Blume
commented
Same problem here it's not usable anymore! If the error is once in the project its damaged... only way is restart your edit and never pus on the tab colors otherwise its ********* again. so no color correction anymore... you have to force to qute then.
-
Blume
commented
Same problem here it's not usable anymore! If the error is once in the project its damaged... only way is restart your edit and never pus on the tab colors otherwise its ********* again. so no color crrection anymore...
-
Christian
commented
I have exact this problem. I am a professional editor and I can't work anymore with premiere. I quit with this buggy company