[Mikhail Petrushin]

Vegas deinterlacer is the problem, imho.

I’m using other tools for deinterlacing and upscaling my PAL Widescreen videos before uploading them to Vimeo/Youtube or editing in Vegas.

P.S. I’m using SimpleSlugUpscale (it uses AVISynth with some plugins and VirtualDub). If you upload somewhere a piece of your source I can upscale it with this technique for you. After that you will decide if it worth to use it or not.

[Mikhail Petrushin]

It could be that your original video not just shakeable, but also has motion blur. For example if you shot with not enough light that the movement of camera make this motion blur. You can see this motion blur if you will see your source footage frame by frame (Alt+Arrows).
When you stabilized the video the camera motion is stabilized but the blur is on place. It looks like the video become unfocused on some positions.
You can’t do anything with this (at least I don’t know what can be done). I tried different stabilizers and they all do the same.

Also, during stabilization the video is cropped and upscaled a bit. This add some blur to every frame. You can try to deal with this blur by adding sharpness a little. Some stabilizers (DeShaker for Virtual Dub for example) can rebuild borders using information from neighbour frames. Unfortunately, Sony Stabilizer can’t do that.

[Mikhail Petrushin]

https://www.sonycreativesoftware.com/vegaspro/gpuacceleration

NVIDIA
Requires a CUDA-enabled GPU and driver 270.xx or later. GeForce GPUs:
GeForce GTX 4xx Series or higher (or GeForce GT 2xx Series or higher with driver 285.62 or later).
Quadro GPUs: Quadro 600 or higher (or Quadro FX 1700 or higher with driver 285.62 or later).

[Mikhail Petrushin]

I’ve experienced exact problem 2 years ago when I used Womble MPEG Wizard for editing my mpeg2 sources.
Unfortunately, I haven’t found a solution then and that program didn’t allow me to play with so many encoder options.
I know that later they’ve moved to Mainconcept codec and the problem was fixed.
Not for me, because they wanted money for upgrade which was just bug-fix in my case.

I’ve also found that re-multiplexing fixed the problem so I’ve done it with all my resulting videos.

In Vegas you can try to change many different encoder’s options.
Unfortunately, I can’t point on exact option that causes the problem, but for start I would change “Insert sequence header before every GOP”, “Use closed COPs” and “Write sequence end code” encoder options after reading about them.

[Mikhail Petrushin]

1. Yes, it is loseless
2. Yes, it works fine under Win7 64 but with Vegas 11 b4-bit

The latest version could be downloaded from official web-site: https://lags.leetcode.net/codec.html

Unfortunately, looks like Lagarith + Vegas are not fully compatible. If your sources are lagarith-encoded and you render your project (8-bit colour depth) into Mainconcept MP4 that the resulting video will be darker 🙁

> But when I drop them into the timeline and then render, everything is fine … what am I missing here?

When you edit it on timeline in Vegas, Vegas do NOT read all frames. As a result the navigation looks OK. However, when you start preview in Vegas it will be choppy as well.

[Mikhail Petrushin]

Correction: Bitrate for uncompressed 1080-50p video — >2500 Mbit/s = 312 MB/s

[Mikhail Petrushin]

Try to get sources in the best possible quality.
You can resize/re-compress it to lower resolution/quality if you like.

[Mikhail Petrushin]

Vegas likes uncompressed files – editing them is usually faster than editing compressed h.264 or AVCHD files.

It depends.
Uncompressed video files are huge and for working with them your HDD have to read incredible amount of data. For example my HDD (7200rpm SATA2) are not fast enough even for working with 1080-50p videos compressed with huffyuv codec. However, it works OK with the same video compressed by lagarith (a bit better compression).

Just “numbers”:
– My HDDs max linear read speed — <150 MB/sec
– Bitrate for uncompressed 1080-50p video — >2500 MB/s

If your footage has smaller resolution or framerate you will not have such problem.

[Mikhail Petrushin]

I never found a need for subclips, Everything here is edited on the timeline

I need only part on the media to be stabilized.
The reasons are simple:
1. It is faster to stabilize a little peace that is required than whole media
2. If I stabilize the whole media that required piece will be stabilized in a different way because stabilization process look for whole stabilized media.

Stabilization can be applied only for media, so the only way — create subclip and stabilize it.
I don’t use subclips for any other tasks.

Your veg file crashes at the end of the stabilization.

I know, I saw it many times 🙂

I used your original m2ts file and applied the Sony Stabilizer to it – no problems.

I know. I stabilized many medias and many subclips. I’ve never had crashes during stabilizing whole media.

I made a subclip from it, applied the Sony Stabilizer, no problems.

I know. The stabilization crashes for some subclips only. Usually I have one crash for approx. every 10th stabilizations. Probably it depends on where the edges of the subclips are. I wrote that if I had a crash I can “take” original media (from context menu) cut just one frame from the beginning/the end, create the new subclip and in most cases the new subclip will be stabilized without problem.

Yes, I’ve found this workaround for myself but I do not like these annoying crashes as I have to press Ctrl+S all the time (I do it before subclip creation), I lose history, current position etc.

I just wanted to show you that Vegas 11 crashes in some cases on rock-solid stable PCs as well 🙂
If you’d like to re-produce the crash from the scratch you can do following steps:
1. Open my project and delete all from timeline
2. Put my media (m2ts) on timeline
3. Cursor Position (Ctrl+G) 0.47 ENTER (frame 47)
4. Split (S)
5. Cursor Position (Ctrl+G) 2.2 ENTER (frame 102)
6. Split (S)
7. Delete the first and the last parts (this does not necessary)
8. RMB over the only part | Create subclip
9. RMB over the subclip | Media FX | Sony Stabilize | OK | Apply
=> Crash

This is not the media problems. It crashes if I take another region (1.47 — 3.2 for example) or another media (from the same Panasonic TM700 camcorder).

P.S. I’ve made a smaller example-project and uploaded it to Sony.

[Mikhail Petrushin]

I already have and use not expensive tripod when possible (good tripod wont be cheaper anyway). Also, I have and use Hague MMC camera stabilizer (also when possible).
However, it is impossible to use all this stuff while filming kids at home, on the beach etc 🙂

I’ll give it a shot here if you want.

Here you are (~75MB, the smallest piece that crashed during my workflow):
https://depositfiles.com/files/ja2h8hl00
(I use file-sharing services rarely so I don’t know what is the best one)

Unpack it, open project and try to stabilize the single subclip that is already created (RMB | Media FX | Sony Stabilize | Apply).

The workaround: delete the subclip, cut one frame from the beginning or from the end, create subclip, stabilize.

P.S. I prefer that Sony take a look at this problem 🙂