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


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.


. . . . 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

Last changed by johnebaker on 3/13/2017, 7:38 AM, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

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:

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.


System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1909, MEP2016, 2020 (V19.0.1.23) Premium and prior, VPX7, VPX11 (V17.0.2.44). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.