[Mikhail Petrushin]

I agree that the system which is used for video editing should be tidy (especially from different “codec packs”) and this will eliminate many problems.

However, quite often the programs are buggy and tidy system with the latest drivers will not help.

I can send you an example project that crashes every time when I am trying to stabilize subclip.
Yes, I prepared this example, but Sony doesn’t interested in it. The send me messages that new build is out and probably the problem was fixed, but they don’t bothe to download my example and check for the bug.

Usually every 10th (or so) stabilization is crashed in my case. Very annoying. And quite unexpected for program that cost five hundreds bucks.

I tried to reinstall OS but this doesn’t help. Also, other people reproduced this crash on absolutely different systems.

P.S. I know, that Sony stabilization plugin is not the best, but I can’t afford to spend for my hobby another $200 for Mircali stabilizer.

[Mikhail Petrushin]

AMD Phenom 840, 8 GB DDR3 RAM, AMD 6850 Video, 7200rpm HDD.

The long render time is not exactly my problem.
https://www.neatvideo.com/nvforum/viewtopic.php?p=2658#2658

Intel i7 2600, 3.4GHz, fast RAM — 6.4fps with radius=1. Intel i7 2600 is much faster then my CPU (and more expensive).

[Mikhail Petrushin]

Source: 1080-50p
Output: 1080-50p, Mainconcept AVC, High Profile, 2 passes encoding, Avg Bitrate: 28Mbps
NeatVideo settings: Adaptive Filtration, Temporal Filter Radius = 2, Noice Reduction Amount: 100/70/40, High Quality Filtering, Hight Resolution, Sharpening: 50/20/10, Conservative. NeatVideo performance 1.93 frames/sec.

NeatVideo filter is applied not for all fragments (~50% fragments).
~14 mins (~42000 frames) video was rendering for 11 hours in version 3.1 and 14 hours in version 2.6 (without my trick, for longer project I will try to use it)

[Mikhail Petrushin]

> Version 3 is at least 2x as fast as V2 (2.6 etc) when only using your CPU

It’s not true.
The developers say: “The exact speedup factor can vary in the range x1.0-x2.5, depending on the filter and project settings”

In my case (I work with 1080-50p) the speed is increased by 20% only (1.2 times faster). However, I use AMD CPU and do not have NVidia video card.

[Mikhail Petrushin]

Just checked two my bugs:

– Crash during stabilization some subclips still not fixed (very annoying for me) 🙁
– Bug when encoding to Mainconcept AVC + with GPU acceleration enabled lasts forever if Sony ProType Titler generated media was used is fixed in this build (not mentioned in release notes).

[Mikhail Petrushin]

If you render your project using 2 passes encoder’s settings that you can try to reduce your render time almost twice by spliting the render into 2 steps:
1. Render the project into temp file using loseless codec (lagarith for example).
2. Open the resulting file in Vegas and render it with settings that you need.

NeatVideo plugin is extremely slow (and very effective as well) and if you render with 2 passes encoding it does its job twice.
If you render it to a temp file (loseless) it will work only once.
Unfortunately, you need a huge amount of free space for the temp file.

P.S. This is just an idea, I haven’t tried it yet 🙂

[Mikhail Petrushin]

I have AMD 6850 video card with Phenom 840 CPU and 8 GB DDR3 RAM. My HDDs are not SSD (just typical 7200 and 5400 RPM drives). I use Vegas Pro 11 64bit (build 595). You may notice that my system is worse then yours.

However, I do _not_ have any frame drops in preview (Best | Full) when I am working with 1080-50p footage (m2ts files from Panasonic TM700 camcorder).
But I have frame drops on transitions as well as if I add some effects on video.

So for me it looks like you have a problems system/Vegas.
I would recommend you to reinstall motherboard chipset driver (the latest one 11.1.0.1006 as I know), video driver (the latest one — 12.4) and Vegas itself (build 594/595 are the latest atm). It’s a good idea to fully remove old drivers first, re-boot your system and then install the new drivers.

P.S. Do you have any anti-virus software installed? Try to disable it for a while during tests.

[Mikhail Petrushin]

Looks like your source files are someway “broken”.
You can transcode them (Virtual Dub + Lagarith loseless codec) before processing using Vegas.

[Mikhail Petrushin]

You can check the CPU temperature easy. Just download CoreTemp, HWiNFO or other similar tool (these tools are free).
Unpack, Run it, Configure for writing CPU temperature into a log file and the start encoding.

[Mikhail Petrushin]

One more thing you have to look at: your video card.
During render it could be used by encoder and sometimes could causes problems. At the beginning you have to try disable GPU usage in Vegas Preferences as well as encoder preferences.