Hi Terry

I think maybe the driver might not install without the hardware, but who knows, maybe just download a driver from AMD or Nvidia and run the installer.

As I said in my last post, it did not help in any configuration if the discreet card was not selected in MEP Program settings and the card would need to be present for you to select instead of the Intel iGPU.

...after you!

Hi Terry

I still have the problem with and without the Nvidia drivers installed, card or no card,

As in this comment from my earlier post, I have effectively tested your scenario of "just the driver" by pulling a card I had installed previously and leaving the Nvidia driver = No change in the HDR problem.

I have also just finished updating all my drivers from Intel and the Asus site but no change.

No idea what to try next.

Peter

Hi Peter,

You're right, I'd missed that, sorry. That makes it pointless for me to try it. And your comprehensive mobo and Intel update gives me an excuse to postpone the same for a while.

Re 'What next?', I'd like to hope Magix are on the case but I'm not optimistic based on experience to date.

#1. Would it be worthwhile our sharing comprehensive MEP/VPX settings, to rule out any obscure differences?

#2. Ditto Local Services list? (Long; 248 entries in my case.)

#3. If you still monitor the German forums, any helpful threads there recently? Perhaps you and John could compose a brief post seeking others' experience?

#4. In view of the findings you've made, this looks to me more and more like an OS and/or hardware issue than down cleanly to MEP/VPX. Perhaps #3 in English as a cross-post to a few Win 10 forums/groups? e.g.
http://superuser.com/questions/ask
Usenet: Windows10 and 'Video' groups that experts here might respect?

This follows up on my last post, item #4. I'm pretty well out of my depth here, but I've pasted below some comments from a Win 10 group in which I raised the topic in case they offer any further lines of enquiry.

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

https://www.extremetech.com/computing/210703-intel-core-i5-vs-core-i7-which-processor-should-you-buy
  "The Core i7 features quad-cores with Hyper-Threading enabled and
  Intel’s HD Graphics 530 solution. The Core i5 family offers quad-cores
  without Hyper-Threading, and either HD Graphics 530 or 510 GPUs."

So the difference is whether or not there is hyperthreading and which
video controller is included on the chip.  I had assumed you (i7) and
your buddy (i5) had the same video driver.  Maybe not if he has an i5
with the HD 510 video controller.

http://www.pcmag.com/article2/0,2817,2422874,00.asp

If hyperthreading is the differentiating factor then maybe you disabling
it for your i7 might show if the Magix program then works okay.  Maybe
Magix doesn't know how to handle virtual cores.  Users have complained
that enabling hyperthreading results in BSODs or unstable systems
(probably due to a defective CPU) or even decreased performance for
multi-threaded processes (e.g., [M]SQL) when compared with
hyperthreading off.  There can be racing problems or deadlocks in code
with hyperthreading (not a defect of the processor but in the code, like
not handling race conditions between threads).  Thread stalling is
another problem with hyperthreading.  I've seen some forum posts where
users complained that Magix did not use all cores in the multi-core
processor and also did not use hyperthreading.  To me, hyperthreading is
like GPU acceleration in web browsers: sometimes helps but if not then
disable it.  See https://en.wikipedia.org/wiki/Hyper-threading.

Some users report that stutter disappears after disabling
hyperthreading:

https://www.reddit.com/r/fo4/comments/5fjbz2/pc_i7_hyperthreading_and_the_microstutter_problem/

Maybe disabling the i7's extra features so it has only those in the i5
will get Magix to operate properly.

https://software.intel.com/en-us/articles/how-to-determine-the-effectiveness-of-hyper-threading-technology-with-an-application/
"Hyper-Threading Technology cannot have performance expectations
equivalent to that of multi-processing where all the processor resources
are replicated."

So reports from users that performance was worse with hyperthreading
enabled is even supported in Intel's description.  Simulated hardware
isn't as fast as real hardware.

If it's a driver issue, you might have to test prior versions of the
driver for your CPU (i7) to see if one works.  As I mentioned, the
latest driver is not necessarily the best one.  For some programs
(games), I had to find the latest prior driver that still worked with
them.  The latest video driver wasn't the best one and sometimes the
worst one.

Just to be sure, are you you (i7) and your friend (i5) using the HD
graphics controller within the CPU?  Or might your friend have a video
card?  The embedded Intel video graphics is particularly strong in the
graphics arena.  Performance of CPU-embedded graphics is very low.

http://www.videocardbenchmark.net/gpu.php?gpu=Intel+HD+530

For graphics editing, I would think you would want something better than
what is essentially a backup GPU: you revert back to it when your video
card dies and until you get a replacement.

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

@johnebaker

it had a GTX 1070 card in, however this was pulled for testing to ensure only the HD 530 was used,

Just to be clear John, you did remove the whole card from the machine and not just unplug the monitor cable?

Whenever testing for the fault you made sure you restarted MEP when switching Program settings> Display Options > Preview in the arranger > Intel HD530 or GTX1070? It does not always warn you to do this.

@terrypin

Thanks for doing some more investigation in those other forums. The hyperthreading tip might be worth trying although I am still keeping in mind that Ralph confirmed a while back when I reported the anomaly that they had reproduced it and that it appeared to occur with "some Intel graphics Hardware" and had been forwarded to the dev's. I have had no response to queries about progress on the issue other than he thought a recent patch to VPX might have fixed it. Unlikely as it occurs on all versions of Magix NLEs that have the HDR function!

As far as the German Forum goes it has not been reported there at all as far as I know, hence Support putting it on low priority. Most of the Mods and usual responders tend to have discreet cards in their machines however.

Peter

Hi Peter

Card was pulled and one monitor plugged into motherboard before installing MEP to ensure no interference from the GTX1070 during installation.

I do not know is how the computer was 'tweaked' for gaming performance, neither does the owner.

. . . . As far as the German Forum goes it has not been reported there at all as far as I know . . . .

Same here, I would have expected some mention of this issue.

John EB

.

.

I've used SysInternals Procmon with filters to show two sets of results operating on a single JPG in MEP 2016 Premium under Win 10 Pro. I'm hoping that the experts here will find clues by comparing these. Perhaps a crucial DLL or whatever, present in the NewBlue set that we can isolate. And then add to affected Win 10 PCs, independent of NB, avoiding the jerky preview that's the downside of that work-around. Not optimistic, but worth a shot!

Applied HDR only
Filtered the hundreds of thousands of entries from a few seconds processing to show only those 81 events with Process = Videodeluxe.exe, OR Path contains 'intel', OR Path contains 'hdr'.

Full text at https://dl.dropboxusercontent.com/u/4019461/MEP-HDR-Problem-ProcMon-HDRonly.txt
Mostly in this screenshot:

Applied NewBlue effect first, then HDR
(I used the 'Reset to None' effect.)
Filtered to show only those 342 events with Process = Videodeluxe.exe, OR Path contains 'intel', OR Path contains 'hdr'.
Full text at https://dl.dropboxusercontent.com/u/4019461/MEP-HDR-Problem-ProcMon-NBthenHDR.txt
The first 70 or so (showing all NB and some HDR) in this screenshot:

Hi

I have run the HDR / DX12 problem past Magix support and while they have been able to reproduce it they say they have not had any other reports from customers and consequently it is a low priority.

If others have this problem please contact Magix as soon as possible!

Peter

This happened to me a few days ago in a trial version of Pro X

Hi v850tw

Thanks for the feedback. Can you tell us about the configuration of your computer system in terms of it's similarity or difference (see our components in "+SIGNATURE" at the bottom of our posts) to others reporting the problem in this thread?

Thanks

Peter

Hi Terry

Thanks for running and filtering that monitor but it is a bit beyond me also.

Things like:- "C:\Program Files\MAGIX\Movie Edit Pro 2016 Premium\RegModule_x64\GPUComponents\MxVfxHDR_x64.dll NAME NOT FOUND" make you wonder if that dll is missing somewhere or corrupted....? If I google the name of that dll not much comes up except those "find and fix .dll error" type download exe's which identify the dll as a Magix one, but I do not trust them to install especially as google results mention MxVfxHDR_x64.dll could be a virus! I suppose if it is malicious it might explain why so few of us are experiencing problems, but I don't think so at this point.

Peter

Hi Peter,

Thanks. I too am not hopeful this will help in our forensics, but I'll also send it to Support to see if the programmers can spot any clues.

Terry

Hi

On my PC the VPX MxVfxHDR_x64.dll is located in

C:\Program Files\MAGIX\Video Pro X\8\ImageProcessingPlugins

and is version 1.1.22.1576 with original name MxVfxHDR.dll

there is also an associated file MxVfxHDR.vsx

Can you check that there are multiple entries in the registry specific for VPX

I found 3 pairs of references to the dll - one references the dll as named the other the dll name with multiple random characters at the end.

Note: if you have MEP and Photostory versions, that support HDR installed, you will also find entries for these

HTH

John EB

Hi John,

I have two versions of MxVfxHDR_x64.dll, for MEP 2016 Premium and MEP 2017 Premium respectively

And here are all the possibly relevant registry entries I could find:

REGISTRY ENTRIES CONTAINING STRING 'MxVfxHDR'    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\013C91A0277BF1234BEAC3B97E1AF11C
Value name    984AE01386C7E7042A646D009368748F
Value data    C:\Program Files\MAGIX\Movie Edit Pro 2016 Premium\ImageProcessingPlugins\MxVfxHDR_x64.dll
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\013C91A0277BF1234BEAC3B97E1AF11C\984AE01386C7E7042A646D009368748F
Value name    File
Value data    _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\03DEAD392B48894349650EBB16CAE4C6
Value name    AC93EFCBAA4DEAF4DB2031CC0F4D058A
Value data    C:\Program Files\MAGIX\Movie Edit Pro Premium\2017\ImageProcessingPlugins\MxVfxHDR_x64.dll
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\0FED4FB4AA3ABCE37AD7AEC2AD17D681
Value name    660137C7242D8664C82E210ECAD66AEF
Value data    C:\Program Files\MAGIX\Movie Edit Pro Premium\2017\ImageProcessingPlugins\MxVfxHDR_x64.dll
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\0FED4FB4AA3ABCE37AD7AEC2AD17D681\660137C7242D8664C82E210ECAD66AEF
Value name    File
Value data    _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\3270C9ECD9720C43586E91C629D9DDEF
Value name    D2B55DE7B66A3C445BAA1245AAD14510
Value data    C:\Program Files\MAGIX\Movie Edit Pro Premium\2017\ImageProcessingPlugins\MxVfxHDR_x64.dll
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\3270C9ECD9720C43586E91C629D9DDEF\D2B55DE7B66A3C445BAA1245AAD14510
Value name    File
Value data    _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\D29B59C833657ED33AEAB30BE5991FE3
Value name    B92146E085249B44084364C4E68278D8
Value data    C:\Program Files\MAGIX\Movie Edit Pro 2016 Premium\ImageProcessingPlugins\MxVfxHDR_x64.dll
    
Key    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FB1CC9184FD1B383EB0B8C39E39DADB6
Value name    313F12BABBEB5304E8FF33A8DCBFEDC3
Value data    C:\Program Files (x86)\MAGIX\Movie Edit Pro 2014 Premium\ImageProcessingPlugins\MxVfxHDR.dll

Hi Terry

These are my versions of the MxVfxHDR.dll files - I have include the VPX 8 file for John CB

MEP 2016

MEP 2017

VPX 8

Did you make a typo on your MEP 2016 version, if not it is older than mine despite the same date/time value.

What version no. is your MEP 2016 ? Mine is 15.0.0.107.

The registry keys you have posted match mine with the exception of the key name, which is to be expected.

There are other values for the _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx showing the version number, did you leave these out of your post ?

John EB

Hi Terry

These are my versions of the MxVfxHDR.dll files - I have include the VPX 8 file for John CB

MEP 2016

MEP 2017

VPX 8

Did you make a typo on your MEP 2016 version, if not it is older than mine despite the same date/time value.

Which number do you mean? My MEP 2016 version is same as your. I didn't include it in my post. That only gave versions of MxVfxHDR_x64.dll. (Both 'file version' and the apparently identical 'Product version'.)

What version no. is your MEP 2016 ? Mine is 15.0.0.107.

The registry keys you have posted match mine with the exception of the key name, which is to be expected.

There are other values for the _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx showing the version number, did you leave these out of your post ?

Don't follow you on that. I searched Registry for the string specified, not_mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx .

Hi Terry

. . . . Which number do you mean? My MEP 2016 version is same as your. . . . .

If you look at the image of the table comparing the dll's in this comment above and reproduced below, your MEP 2016 MxVfxHDR_x64.dll is 1.020.885 whereas mine is 1.0.20.985

. . . There are other values for the _mxvfxhdr_x64.dll_v1zd1vs5n7420332zvc0e51dx showing the version number, did you leave these out of your post ?

. . . .Don't follow you on that . . .

This is an example of the value I am referring to in regedit

John EB

Hi John,

Understood, see what you meant now. No typo, I pasted that version in to a spreadsheet.

Will take closer look in the morning, back on PC, but at first glance that seems strange, as we both have same versions of MEP 2016. Could you email me a copy of your later version of the DLL please and I'll see what effect it has.

So, I have the same .dll version and date as John EB for MEP2016 and 2017.

VPX8 V1.1.22.1576 12/9/16

VPX7 V1.0.20.1 12/5/16

MEP2014 V1.0.18.1 14/6/14 (in X86 program files)

MEP2015 V1.0.20.0 4/6/2014 (This is on my Surface pro3 which is not experiencing the HDR darkening effect BTW)

And one that appears in a Folder C:\MATS\Backup........VPX8\.......ImageProcessingplugins which on googling, appears to be a backup for Program Files and Program Data that was created when I ran that Microsoft uninstaller Tool that fixed my problem with VPX8 showing as a trial version after I tried to re install in January. The version is V1.1.21.1004 19/2/16 ie older than the current one above but I put this down to the fact that the MS Tool backed up the data from the Trial version which must/would have been older.

So nothing stands out so far.

@ Terry

As the problem goes away when NB FX are added, as these invoke Open GL acceleration I wonder if it might be worth running that process monitor and including a filter for an OpenGL.dll......(err maybe something like igfxogl.dll or something....sorry can not put my finger on a correct file name but the "ig" relates to Intel or integrated) with and without the NB FX.

Peter

Hi John, Peter,

First that puzzling version discrepancy: my fault! Rather than show images of the
MfxHDR_x64.dll Properties window (for both MEP 2016 and 2017) I opened it and used an OCR tool to copy selected text into an Excel spreadsheet. I've repeated it umpteem times this morning and it now consistently delivers the same as yours: 1.020.985. Can't believe the DLL has somehow been changed, so have to assume my normally quite reliable OCR had temporary myopia and read '9' as '8'.

(Searching emoticons for a red herring, unsuccessfully!)

I ran ProcMon again. MEP 2016 with JPG selected. Added NewBlue effects as before. Closed ProcMon after about 7 seconds. Could find no string containing variations of 'gl', 'opengl' etc. And filtering for any path containing the string 'newblue' gave 51 events, all of which refer to either NewBlueESAutoContrast64.dll or NewBlueESAutoContrast64.vsx.

However, I then tried filtering on paths containing 'igfx'. This was prompted by both your post and a suggestion I had earlier in the alt.comp.os.windows-10 newsgroup from a helpful expert, indicating that MEP appears to be looking in vain for 'D3D10' registry entries. Those events are from DWM.exe, which I see is 'Desktop Windows Manager'.

Here's his comment too, in case that helps:

"In your first trace, I see Magix looking for D3D10 registry entries. Does that mean it is a D3D10 only product? Do the special effects or hardware acceleration only work there?"

Twice tried adding another image here, but it failed to appear. Trying again. That failed too, so I'll try a link instead:

https://dl.dropboxusercontent.com/u/4019461/MEP-HDRproblem-d3d10.jpg

Hi Terry

DWM handles all the fancy windows visual effects and other items - see here.

Try turning off some of the effects following this method.

HTH

John EB

Thanks John. Reading on iphone. Will try that as soon as I get back to PC.

LATER: None of those options enabled here. Set for 'Best Performance'.