Hi Andrew - thanks for responding. I don't use BM desktop as I have no I/O. The weird thing about what I'm seeing is that even the path options dialog does not work. This was on my laptop system - I'll try tomorrow with my desktop system and see if I can reproduce there. Could be something odd with the laptop and its two GPUs, one Intel

Haven't used it from MC for a bit and I just tried with MC 2018.5 (Fusion Studio 9.0.2, Fusion Connect 9.0.2) and the UI inside MC does not respond to the 'Edit' button in the Fusion Connect effect editor window nor does it respond to the path configuration (options) button. The other buttons in the Fusion Connect effect editor dialog work

Not really - I thought it was resolved in the last year and my memory if pretty foggy on this issue. I observed the glitches in the rendered image so that much I recall... lol

Sounds similar to the GPU glitch bug reported several versions ago (GPU threading issue during background transcode / rendering introduced glitches). I wonder if this is another manifestation of the same issue?

Luca - my point is that solving this issue for MC doesn't really solve the overall problem unless you don't use the 3rd party plugins I referenced.

Are you running BCC 11? I ask because prior to BCC 11 I was able to activate my license on two machines and then move my dongle for MC back and forth. Now with BCC 11 it seems that I can only activate on a single machine at a time. I'm asking you because I'm wondering if I lost an activation somewhere along the way or perhaps Boris changed its

It gets much worse if you are using 3rd party products like BCC, Sapphire and Waves audio plugins because they each require deactivation on one system before transferring the license to another. Sapphire is particularly bad because you actually have to uninstall the product to deactivate it.

I was told that you have to set the Windows scaling to 200% - have you tried that? Thanks again for the feedback - Cheers

Are you running the latest Media Composer? 2018.4? Thanks for the feedback. I would very much like to hear from Avid on this because any threads I could find suggested that MC was now compatible with High DPI monitors... Cheers

Really. So how do you suppose c. was able to get it working?