Comments

Grazie wrote on 4/18/2014, 4:42 PM
Not here. I'm using 2.0.116, I reinstalled after my OS install. You might want to consider this, but I don't see it on the ProDad site - which is weird?

Anyway, it IS working and that was today.

G


Rv6tc wrote on 4/18/2014, 5:45 PM
Thanks Grazie,

Here's what I learned, with some help from FlyingSki.

I have a project that I threw about 60 clips on the time line. Attempting to stabilize one of those clips resulted in a consistent crash. Then I restarted VP13 and placed a SINGLE clip on the timeline and it stabilized just fine.

Then the weird part. After I do that, if I re-open the original project that crashed Mercalli, and I stabilize the exact same clip that crashed it before, it now WORKS. After that, you can stabilize any of the clips without any problem.

So it's a work around..... a crappy one, but a work around nonetheless.

(Except my workaround is to stick with VP11, which is working very well)

Keith
Rv6tc wrote on 4/20/2014, 6:09 PM
For anyone that experiences this, I have determined that if you turn GPU acceleration OFF, you can stabilize with no issues.


My question for those that are knowledgeable... I'm using an older NVIDIA driver, that has worked well for VP11. Is there any chance that could be the cause, and that SCS developed VP13 with newer video drivers?
-Keith
flyingski wrote on 4/20/2014, 10:17 PM
On my old system I'm running the 296.10 driver with a 560Ti on VP12. Mercalli worked perfectly until I moved from VP12 build 486 to 770, then Mercalli was nearly unusable unless I worked with a single clip. Following Rv6tc's experience I turned GPU off and now Merrcalli works. I'll try it on my new system with a 770GTX which had identical problems as soon as I'm home. I suppose I could revert to build 486 but then I'd be giving up all the other bug "fixes". I'm trying to decide if I want to take a chance on VP13. Mercalli and frameserving are absolute deal breakers for me.
wuzabeeb wrote on 10/27/2014, 12:46 PM
Hi.. I've had the same .. but the latest happening is really weird. The Mercalli works perfectly, and the timeline preview window - even on fullscreen shows stabilised video. However, if I render out the SAME section of the timeline .. there is NO STABILISATION. I have recently added in a new K620 graphics card .. but have disabled graphics acceleration as recommended to try and fix this .. no change even after a reboot. The rendered files seem to ignore the Mercalli preset action despite the timeline preview showing it perfectly. Anyone else noticed this? Build 373
johnmeyer wrote on 10/27/2014, 1:49 PM
I reported this problem back in January 2012, and in that thread referred back to a July 2011 thread.

This problem -- or one just like it -- has been around a LONG time, and makes using Mercalli inside of Vegas almost impossible. However, you can work around it. You'll find my workaround instructions in the following old thread:

[linkn=http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=796335]Anyone Figure Out Mercalli Render Bug Fix?[/link]

I would certainly try rendering without GPU. That was not the cause of the problem when I reported it way back when, but perhaps it is now.

There sure are a LOT of Vegas problems that keep getting reported year after year, but never get fixed:

Poor deinterlacing
Poor scaling algorithms
Mercalli crashing when rendering
GPU render problems, including blank frames and random frame appearance

I'm sure others have their favorites to add. Some of these sure seem pretty fundamental to me.
wuzabeeb wrote on 10/27/2014, 3:37 PM
Thanks John .. well .. the scaling stuff I can identify with .. as I found a load of old rock video tapes in DV that I had shot on live concert gigs. My 'spare' edit suite runs on Vegas 10. I captured DV and rendered to HD ... amazing quality compared to the same done in Vegas 13 .. why? De-interlacing .. I used to use DV Filmaker ... then Vegas seemed better .. but nowadays I find the best is to select do not resample on the timeline, and render to twice the framerate. This gives an improvement in quality making a pseudo progressive double framerate video. I also use Twixtor for creating intermediate high res frames if it is a serious project. Render to half speed but at the same framerate .. then use the half speed rendered video played at twice the speed to double the temporal framerate. Worked a treat on some old WWII HD transfers to get them up to 59.94P. Looked just like video ;-) Mind you - the originals were 35mm shot by John Fords crew. Will take a look at your link. Many thanks.
wuzabeeb wrote on 10/27/2014, 3:53 PM
Got it John .. I opened some 50P footage in a 59.94P project .. DOH! ... didn't notice .. then that link reminded me ... sometimes working late is a mistake?

Regarding the deinterlace and scaling issues .. the scaling is the most obvious one to me since Vegas 10 ... and I've been working in 3D with a few obvious bugs that were reported in V12 but are still there in 13 .. I guess they prioritise on bug fixes. Mine was non-critical .. the reverse option for video doesn't work in 3D files. Not something a load of people would use. Also, if you look at Windows performance graphs - when using Mercalli, it seems to be trying to access virtual memory rather than just direct .. my 4 core i7 shows 100% usage, and I get lockup on long clips which means that I have to cut them into smaller ones. Once it hits 100% .. it sometimes locks up .. couple of screen windows flash white .. then it starts again ... but occasionally it drops out the render and messages that user stopped process ...nope - it wasn't me. This seems to be worse these days. The old Mercalli 2.0 works a treat when it's going. Mercalli conned me into buying the standalone V3 as an 'upgrade'. But it only renders out to mp4 and doesn't recognise Cineform codecs .. and a load of others for some reason. I've asked for a refund.