Stabilization & veg size

Simes wrote on 6/11/2012, 3:35 AM
Stabilizing an event of only a few minutes (and one that only needs very modest stabilization) leads to a very substantial increase in veg file size. I'd like to request the option to 'offload' the stabilization info/data into a sidecar file. Also, I'm not sure yet, if the stabilization is removed from an event, the veg file goes back to its original (pre-stabilization) size.

Comments

Steve Mann wrote on 6/11/2012, 7:59 AM
The veg file is relatively small and contains the entire project. WHY would you want Sony to even consider modifying a long established platform base? If the hiccups and stumbles in incorporating GPU support wasn't a lesson, then thry this: If It Ain't Broke, Don't Fix It
Simes wrote on 6/11/2012, 11:16 AM
Dear Steve, yeah, but actually have a think about these figures:

Without stabilisation (for 34 min project): 26KB
With only 59 seconds of stabilisation in the 34 mins (very low level setting): 6482KB

Given I need to stabilise a track in the project of 34 mins - that means my veg file will be approx 220388KB (i.e. 220MB) - which, I think, for a base project file, is a crazy size.

Incorporating stabilise info into the veg is a relatively recent development & was not part of the original veg spec. Therefore, I think it would make far more sense to have them as sidecar files - especially in terms of reducing the chance of any veg file corruption happening on huge files.
Chienworks wrote on 6/11/2012, 11:19 AM
Actually i would say it has been in the .veg file spec for a long time, even way before the feature existed. It makes use of track motion keyframes, and those have been part of the .veg file for many years.
Simes wrote on 6/11/2012, 11:36 AM
Hi Chienworks, I see what you mean, though I'm not sure it's using track motion keyframes in the way they were originally intended - i.e. veg & keyframes were designed/envisaged to hold 10's/100's, whereas I guess this implementation is using 100,000's+!

Anyway, the issue is - is a 220MB+ veg file workable/safe... or is there a better way to hold the info...
Steve Mann wrote on 6/11/2012, 3:56 PM
I can just see the cascade of "unrelated" problems when this feature is added to Vegas.

And I repeat, If It Ain't Broke, Don't Fix It!

riredale wrote on 6/11/2012, 5:50 PM
May I humbly suggest using the truly-excellent free "DeShaker" script. A LOT more functionality and a clever edge-fill capability with NO veg file changes. Yes, it requires a certain amount of "nerd" to set up, but not much, but then the actual usage is simple and the results are remarkable. DeShaker creates a new "Take" for the selected clip, so you can switch back and forth easily. Don't know if the built-in stabilizer uses the same idea.
Simes wrote on 6/12/2012, 5:42 AM
Thanks riredale - am going to give the DeShaker script a go.
Simes wrote on 6/12/2012, 5:45 AM
Hi Steve,

===
'I can just see the cascade of "unrelated" problems when this feature is added to Vegas.

And I repeat, If It Ain't Broke, Don't Fix It!'
===

Yeah - I hear you - and know exactly what you mean - I too consider: 'If It Ain't Broke, Don't Fix It!'' one of the great truths of life :)

Am going to give the deshaker script a go.
Simes wrote on 6/19/2012, 11:25 AM
After getting grips with deshaker & it's amazing deshaking - I have to agree all the more with Steve, that it would be best to leave vegas' inbuilt stabilisation as it is. I'm not actually sure why the vegas developers didn't focus more on an inbuilt deshaker interface instead. It's still not too late for that - as it strikes me the script method & frameserver method both have the advantages which might be combined in some manner.

I don't know if the deshaker log size (i.e. the log deshaker builds of adjustments to apply for stabilisation) is directly comparable with the info vegas stores for stabilisation in the veg file - but compared to the 220MB veg file described above the full deshaker logs for the same video is 8.5MB