Trying to get vp17 stable

bvideo wrote on 8/11/2019, 11:31 AM

Trying the demo, I thought I got vp17 stable by installing the latest driver for Intel UHD 630 (built-in graphics). I have the I7 8700K and no external graphics card, running Windows 10 1803.

Then after buying vp17 I found it *sometimes* unable to load some previously saved projects from the demo as well as projects saved in vp16. Then *ouch* I found vp16 no longer opens some of its projects. In both cases, the program seems to load up the bin, then load up the timeline, then disappear with no visible message or diagnostic. Some of these projects are just jpgs with pans & crops & titles & occasional fx like colors/levels. There are related events in the Windows event log.

For both vp17 and vp16 I worked around this by disabling "Enable QSV Encoding and Decoding (where available)". So it seems clear the new driver triggered a new problem for both versions.

For vp17 demo with the older Intel driver, the program would hang after loading and starting to edit. These hangs could happen seemingly any time, though noticeably often when playing somewhere in a Sony "Titles & Text Plug-In" event. When it hangs, there does not seem to be a way to generate any diagnostic. I never found a way to reliably reproduce this. And it went away when I updated the Intel driver.

With the new driver, both vp17 and vp16 disappear and generate Windows error events when opening their own projects when "Enable QSV ..." is set. Here's one:

Faulting application name: vegas170.exe, version: 17.0.0.284, time stamp: 0x5d3fba32
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x1b54
Faulting application start time: 0x01d5505f7d86024b
Faulting application path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 39f39434-d757-4c75-b801-54ab0fdd7822
Faulting package full name:
Faulting package-relative application ID:

Bottom line, I'm up and running without the QSV enc/decode, and otherwise there are some problems that seem related to the Intel driver, but I have no reliable way to reproduce them. I will report the diagnostic above to Magix. Otherwise, I need to come up with a simple project that reliably causes these problems or else come up with a version of the Intel driver that cures both problems.

Comments

fr0sty wrote on 8/11/2019, 12:09 PM

The hardest part of squashing bugs, finding ways to reliably reproduce them. Thanks for the detailed efforts to do so, please let us know when you get it narrowed down a bit further. Definitely file a support ticket with Magix.

bvideo wrote on 8/11/2019, 2:58 PM

OK, thanks. Ticket filed!

bvideo wrote on 8/11/2019, 4:17 PM

Here's some good news: I installed *the newest* Intel UHD 630 driver, i.e. directly from Intel (Aug 1), as opposed to the newest one blessed by the MB maker (Gigabyte). Now VP17 and VP16 work right with "Enable QSV Encoding and Decoding (where available)". Warnings on both Gigabyte's and Intel's driver pages recommend using the one blessed by the MB maker, so now what bad things could happen?

Anyway, all good now except for the Boris problem.

fr0sty wrote on 8/11/2019, 7:03 PM

Good to hear. I want to say that issue with Boris got solved, or at least there was a workaround found that enabled people to re-install it. Check around here, your solution might be waiting.

As for the question about the driver, don't sweat it. If it works, it works.