Premeire cs6 Bloating again – Beware when using Warp Stabilization

[Garrett Gibbons]

It doesn’t seem like an acceptable solution to me to have to fork a project file several times just because one plugin creates bloated, problematic metadata. Either the metadata should be stored alongside the source media (as in FCP7), or in the system cache, or really anything else. This has been going on since CS4 and isn’t resolved. Mind-blowingly bad response from Adobe.

http://www.garrettgibbons.com

[Walter Soyka]

[Garrett Gibbons] “It doesn’t seem like an acceptable solution to me to have to fork a project file several times just because one plugin creates bloated, problematic metadata. Either the metadata should be stored alongside the source media (as in FCP7), or in the system cache, or really anything else. This has been going on since CS4 and isn’t resolved. Mind-blowingly bad response from Adobe.”

I’m not really suggesting that you fork your project, but rather that you isolate the elements that require stabilization and pre-process them externally.

I do agree with you that stabilization data should be stored in a sidecar file or separate cache and treated as an independent project element instead of storing it directly in the project file.

Warp Stabilizer was new in Pr CS5.5, if I recall correctly.

Your input will reach the engineers who need to hear it better as a feature request [link] than a forum complaint. I have already filed mine, and since you feel so strongly, I hope you will too.

Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]