HDR effect does not work with MEP2014, 2016 or VPX7 on new machine with new Win10 Pro installation

Scenestealer wrote on 3/8/2016, 4:12 PM

I have recently built a new desktop PC (see specs. in my signature) and have struck a problem with the HDR effect malfunctioning, seemingly on all (64bit) versions of Magix MEP/VPX. The preview monitor becomes very dark as soon as the HDR slider is moved off zero, almost as though the Selective Brightness slider has been swung right over to the left.

It appears it could be some incompatibility with HW acceleration in DX12 as it does not occur if “Always Use DX9” is selected in the Program Settings or if VFW compatibility mode is selected. It also behaves correctly on my Microsoft Surface Pro3 Tablet on Win 8.1 Pro with the Intel i5 integrated HD4400 graphics but this uses DX11.
My new system has only the Intel HD5300 Graphics and this performs very well, even with the New Blue Titler plugin which is not supposed to even work with Intel IGPU’s. I have installed the latest Graphics and chipset drivers from Intel and flashed to the latest Bios from Asus for the Z170 Pro Gaming motherboard. I have tried resetting the programs to defaults – no luck.
DX12 HW acceleration is definitely working with the preview of other effects.

The only thing I have discovered with much trial and error is that the HDR problem corrects itself if a New Blue Effect like “Auto Contrast” is applied first to the clip….! It also keeps working if the preset "Reset to none" is subsequently selected in the NBlue effects window.

I have not seen mention that others have seen this problem in the Magix forum and wonder that this may not be a problem if you upgrade to W10 from W8.1 which has DX11.2 in it, instead of DX12 as in my clean W10 installation)

Has anyone else come across the problem or have any ideas on its cause or solution?

Maybe having a discreet graphics card instead of the integrated Intel graphics would make a difference...?

Unfortunately using DX9 means some of the effects are not optimized in their acceleration and the scopes (measuring tools) don’t work in VPX, so that is not a great workaround.

Peter

Back to post

Comments

terrypin wrote on 3/13/2017, 6:36 AM

Hi Peter, John,

Wonder if we should try methodically registering some of those DLLs one at a time?

johnebaker wrote on 3/13/2017, 7:38 AM

Hi Peter and Terry

Is installing DirectX 11 an option? If so see this article re installing DirectX 11.

OT:

. . . . the New Blue Titler plugin which is not supposed to even work with Intel IGPU’s . . . .

I commented, 7 months ago, that the New Blue Titler started working on Intel HD graphics chips once MEP 2016 was installed.

John EB

terrypin wrote on 3/13/2017, 9:06 AM

Hi John,

I'd personally be reluctant to drop back from version 12 to 11, as I'd be nervously waiting for some unwanted side effect.

--------------------

I submitted a Support Request on 11th March and copied Ralf. It's almost identical to my post up-thread, except for its opening and a footnote, which I've copied below FYI. I'd like to believe our latest suggestions might be tried by Magix... 🙁

This concerns the long-standing problem with HDR, which you're aware of.

[My first post about Procmon output.]

I assume that you're aware of the 'workaround' I mention above? It was discovered by Scenestealer and is currently the only way that those of us suffering from this problem can use HDR. It simply requires FIRST
adding a NewBlue effect to the object, BEFORE using HDR.

More in this thread:
https://www.magix.info/uk/forum/hdr-effect-does-not-work-with-mep2014-2016-or-vpx7-on-new-machine-with-new-win10-pro-installation--1161947/#ca1309487

Scenestealer wrote on 3/13/2017, 5:29 PM

Hi John and Terry

A useful article there John about installing earlier versions of DX and this maybe worth a shot considering John CB installed an earlier version of DX9 at some stage and is (maybe coincidently) not experiencing HDR problems on that machine.

Terry - In the article it says that installing an earlier version of DX will not conflict with later versions and I guess if we create a restore point prior then we should be covered. The article goes on to detail how to extract and install specific .dlls from the dx runtime download so I might see if I can see if there are some relevant dlls in earlier versions that are not in later ones.

Meanwhile I might just wait and see if you get any further with support, but if I do try another DX version I would probably try DX11.2 as this was on my Surface Pro3 when Win10 updated from 8.1, and that continues to add HDR correctly.

Peter