Build 361 hangs when using Prodad Mercalli stabilizer

ken-dehoff wrote on 5/30/2018, 2:26 PM

All:

A tough problem here. I've got gopro 4k/30 protune videos I want to stabilize. Each 4 gigabyte file records about 8:30. When I apply the Analyze phase of Mercalli stabilizer, it gets to 100% completion and then frequently (not always) hangs - vegas pro stops responding and I have to force the app to die. So I'm running ver 361, windows 10 1803 which were both big upgrades, and the mercalli filters are the only thing that hasn't changed in this mix which is why I'm thinking OS or 361 is at fault here. Can anyone shed some light?

Prodad's input has been to make sure the pointer is on the timeline and that the project resolution matches the gopro resolution (they do) .

Any suggestions are welcome.

Quick overview of my system - 32GB memory, intel 7700k cpu acting as primary video display (so hevc works!)

Comments

Kinvermark wrote on 5/30/2018, 2:50 PM

Frame rate matched too?

So are you saying you were able to stabilize these clips (or same codec/size/etc.) without trouble prior to the latest updates?

ken-dehoff wrote on 5/30/2018, 2:54 PM

yes 29.97 and 29.97

Kinvermark wrote on 5/30/2018, 3:44 PM

And my second question? (sorry, I edited same time you were posting.)

Third question: is this the original mp4 from the gopro or converted to cineform avi?

ken-dehoff wrote on 5/30/2018, 4:15 PM

yes I've been using vegas/mercalli since december without issue on gopro video files- probably gone through 500gb. The Gopro files are originals from the camera - haven't been processed at all

Kinvermark wrote on 5/30/2018, 5:06 PM

I have done some testing, but don't have any long clips of Gopro 4k/30 footage. Hopefully someone else with the appropriate footage can replicate the problem.

In the meanwhile, I may be worthwhile to transcode to cineform avi (using GoPro studio if you still have it) to see if that makes a difference. Could also check if turning off hardware acceleration in Mercalli helps.

fifonik wrote on 5/30/2018, 5:12 PM

At this moment I'm working on another project using VP15 (build 361) and using Mercalli Stab plugin (version 4.0.482.1) almost on every fragment (50+ fragments in the project). Do not have such issue.

However, my sources are m2ts 1080-60p, not 4K and fragments are shot (5 - 30 seconds each)

My system is also very different: Ryzen CPU, AMD RX470 GPU, 16GB RAM, windows 10 1803.

I'd try to disable QSV temporarly in VP15 and to re-install GPU drivers.

fifonik wrote on 5/30/2018, 5:17 PM

Could also check if turning off hardware acceleration in Mercalli helps.

It is disabled by default (btw, is it possible to change default Mercalli's settings to enable it for example? I could not find a way to do this).

I personally do not enable it as it does not improve speed dramatically on my system and Mercalli's UI is... a bit hard to use to enable it (multiple sections should be opened before you are able to access the checkbox).

Former user wrote on 5/30/2018, 5:54 PM

The plugin version of Mercalli V4 for Vegas is very problematic and full of bugs. I stopped using it due to a number of problems it presented.

I am currently using the native stabilizator (Vegas Stabilize) and am very satisfied. You just have to be careful to leave the preview at Good Full at the time of the analise to have a great result.

You can also parse multiple clips at the same time using the Vegas Batch Stabilize extension.

Peter_P wrote on 5/31/2018, 1:08 AM

So I'm running ver 361, windows 10 1803 which were both big upgrades, and the mercalli filters are the only thing that hasn't changed in this mix which is why I'm thinking OS or 361 is at fault here.

@ken-dehoff

Do you have any chance to go back to windows 10 1709 ? There are may problems reported with Vegas pro (15) and the new (buggy) Windows 10 release.

ken-dehoff wrote on 5/31/2018, 8:50 AM

well I will say that I tried to back out of 1803 on my laptop and it caused an incredible number of errors in the OS, so I ended up reloading that machine from scratch. I wouldn't recommend the backout procedure to anyone - I agree that this new OS has been the absolute worst microsoft patch ever!

To update this - I have two systems running - 6700k and 7700k - both on 1803. I backed out to build 321 on the 6700k and left hardware acceleration on - works great. On the 7700k I left in 361 and disabled hardware acceleration and that worked as well.

So the problem appears to be associated with QSV on 1803 and build 361. I've got what I need to get my project done - will do more troubleshooting when I have some time.

Peter_P wrote on 6/1/2018, 1:15 AM

So the problem appears to be associated with QSV on 1803 and build 361.

Up to now, I have no problems associated with QSV on my i7-8700k with build 361 running Windows 1709.

AVsupport wrote on 7/7/2018, 2:30 AM

internal 'Vegas Stabilize' [=mercalli20.dll] Crashes here with 2K/25p MP4 footage from DJI Mavic. At ~80% (clip length: 5'48")

AVsupport wrote on 8/1/2018, 4:23 AM

btw, on my system, I can use VP14 and stabilize (vegas plugin) no problem. but how to manage a multitude of clips and can this be used prior to editing the project in VP15?

i am erikd wrote on 8/3/2018, 5:56 AM

I had to rollback to build 321 because of Vegas no longer recognizing my DJI Osmo video files. I can confirm that the Mercali stabilizer does work fine in build 321 as well. Disappointing to see new bugs created in the last release of V15!