Mercury Transmit/Video Preview Bug

Broken Mercury Transmit SOLVED for Premiere Pro CC 2020

I have a system with 2 monitors for workspace, and 3rd for viewing the Mercury Transmit. I've just switched to this set up having got rid of an old HD CRT broadcast monitor and Blackmagic card. So I was excited to have this working.

It didn't..

But, there are 2 solutions.

The CAUSE:
If you have say 2 monitors only, and one would be for Premiere UI and the other for monitoring, naturally you Maximse Premiere on one screen to make best use of it. Mercury Trasmit LIKES this, presumably because Premiere is not running in Windowed mode then...?

THE PROBLEM
If you have 3 monitors, two for PPro UI and one for monitoring, if you Maximise PPro, with Windows 10 natively it maximises to just one of the 2 monitors. And Mercury Transmit works. But, your UI is crammed into one screen, and the 2nd one is just showing Windows UI or whatever else you have got open.

So you do what is natural to you, and resize PPRo UI as big as possible by hand across the two monitors for UI. Maxmimse vertically with native Windows 10 function, and drag as wide as possible by hand left and right. Yes?

Mercury Transmit ... no likey! It stops working. If you're lucky, if you don't have the option set to hide the output when you minimise PPro, you see the static image preview when you minimise PPro which disappears when you return to your 'full screen' manual sized UI.

Boooo.

THE SOLUTIONS

Option 1)

this option also makes media playback in Windows (so say, a 16:9 video) play on both screens, but half on each screen, with the monitor bezel in the middle, so may not be ideal for what you wish to achieve. But, if you go to your Geforce Control Panel, enable Surround display mode. Include your 2 UI monitors in the configuration, but not the 3rd monitoring one. Here, the nVidia drivers 'remap' the two monitors into one single wide display. Windows 10 then sees in Display properties that you have only 2 screens now, wide 32:9 (or whatever based on your screen resolutions) and one second 16:9 (or whatever your monitoring screen is).

Now, you can do real Maximise size of Premiere UI and it fills both your main screens. Because it is now 'full screen', the system knows exactly the UI location, and is happy to let Mecury Transmit work successfully!

Option 2)
If having 2 screens seen as one single one by Windows, messes your head, or you don't like how 16:9 media plays back within windows in the centre across bezels of a 32:9 display, then try this....

In my set up, my 3 monitors are Left and Centre screen for PPro UI, and right monitor for Monitoring .. -

I take PPro UI, use Windows 10 native 'vertical' maxmise function (drag the top edge of PPro to the top of the screen to see the 'snap' and it vertically maximises itself); then drag the PPro left edge as far left of screen 1 left monitor so it is as wide left as possible.

Then take the right edge of PPro as far right as possible, of my middle screen.

You're probably thinking "yeah, that's what I did already, and you described this at the start of this whole post".
Indeed.

But, Mercury Transmit doesn't work now.

So, it seems that the SIZE of the Window and its position being so close to the edge of Monitor 3 upsets things...

So, take the right edge of PPro UI, and I drag it left a few pixels, 3, 5, 6 pixels, just a small amount.

Now, with the separation between Monitor 2 and 3, my center and right screens, Mercury Transmit seems to be happy with the separation and suddenly springs back into life and works again!

Final
I was able to repeat this process over and over to prove to myself that it works and was not a fluke.
Hopefully these options solve thi for you.

I just was having this problem in 17.0.3 and finally figured out that if I press the "maximize window" button on top right of the main AE window then mercury transmit starts working again on the other monitor. 

My main AE window was not leaning into the other monitor at all I don't think, but it looks like AE was trying to make sure that the video preview would not obscure the main UI window. 

This bug is still not fixed. On one of our machines, the entire premiere crashes when enabling mercury transmit. The timeline suddenly wont play and there is no image in program or source when scrubbing footage. We are on a brand new machine with i9 9900k, RTX 2080ti, 64GB ram ++. Everything else works fine.

We are a marketing company and we pay alot for this software to work. We are strongly considering leaving premiere for davinci as we have had bugs with premiere for the last full year on many of our workstations.

ADOBE: We need a fix ASAP! We expect this to be a priority as it costs us alot of money working on bugged software all the time. Please give us a respond on how you are planning to resolve theese issues.

I'm completely with "lucyb91785867" on this one!  Adobe, we still have mercury transmit problems in AE 2019 16.1.3 version! Client monitor isn't working and that's a very big deal! It's not a game, we actually pay for it.  

It just stops working after some short period of time. Minimizing and maximazing app window doesn't help, turning Mercury ON/OFF in settings, doesn't help, switching to a different monitor doesn't help either.... 

Well thank you for the reminder on language Kevin, but lets focus on what actually at stake here than worry about some delinquent's expansion in verbal expressions: What exactly is adobe doing to fix this issue?? This is an issue that has persisted and has tremendous impact on our work flow, deadlines and ability to deliver. Yet with a new update it screwed it up even more, I couldnt even roll back a version on my project, and now have to persist with this ridiculous bug for the next coming weeks which is adobe's bad developing, and  I have to explain to clients why the hell they are not able to view the film on an actually bloody monitor, not to mention the fact that the mercury transmit is choosing my main monitor and blocks out half my computer screen and in order to get rid of it I have to quit boot up again! I mean really now, we have to pay to be made fools of in our professional environments. Not to mention the time Premiere deleted all my files off my hardrive, which at the time i thought was a worm only to find out actually it was disastrous, pathetic, mind numbingly stupid coding which deleted all my files!? I simply did not have time to complain [content removed] What actually is being done to remedy this?

I hope my language suffices to the forum rules, because if I really had to express my anger and hatred towards adobe, [content removed].

Kind regards

L

Moderator warning: Content was removed. Please do not discuss legal issues. Please do not issue threats. These are against Adobe Community policy.

Adobe! What the F*&%?? I am STILL experiencing this bullsh%$ mercury transmit issue, spending hours just to be able to work with client who need to see the client monitor and yet I have updated now to the latest version and STILL it persists! How the hell can you allow such a broken application to see the light of day? We are professionals paying for this piece of SH$T and we have to face these issues! I dont think you realise how serious this is!

FIX IT!!!

Three identical monitors. In version 13.0.3 everything works fine. Updated to 13.1.2. Premiere uses the settings of the previous version and Mercury works on the monitor I need. But keyboard shortcuts doesn't work (don't know why — same bug on few PC's). I reset settings (Alt + Shift + Click) and — Bam! — Transmit is stuck. On the monitor, which I do not need. Without the ability to change this.

If anyone else is experiencing this bug still, please post here to bring attention to the problem.  Apparently this is not a priority to fix. 

I'm running on PP on a late 2013 Mac Pro OS 10.13.6 w/ AMD FirePro D500.  Mercury transmit was working just fine then, I think even after updated Adobe software to 13.1.2, until an unknown reason crash––then transmit stopped working. Maybe it did stop working after the update but I do think it was working OK up until the crash.  Please please fix!

Any updates on this bug!?