V6 Nested .veg performance.

Jackie_Chan_Fan wrote on 4/20/2005, 5:08 AM
I've played around with the demo some. Vega's performance takes a huge hit when you nest .veg files into the vegas timeline.

Has anyone experienced this? I mean its virtually useless as the .vegs i've nested brought vegas to its knees (bypass fx was on too)

Compared to other nested timeline systems, vegas is the only one i really notice a huge performance hit.

Are there any guidelines for working with nested timelines in vegas that will improve performance?

Comments

Jackie_Chan_Fan wrote on 4/20/2005, 5:41 AM
BTW i tried searching but used the wrong search :) The search on top of the webpage looks to be the forum search but as i found out.. it is not :)
logiquem wrote on 4/20/2005, 5:57 AM
I tried a small two track compo: a background texture with a glow fx an a rotating text in overlay.

original NTSC DV project : around 9,5 fps (preview: good auto in 360 x 240)

the same original project nested in a new NTSC DV project (single track, no other events, same project properties) : around 1,5 fps... (preview: good auto in 360 x 240)

Wow! 6 times slower! Want to laugh a little more? You can also put your project in itsefl!
The same slow performance... :-)
jlafferty wrote on 4/20/2005, 6:37 AM
That's strange -- V5 and V6 showing the same preview performance for me. I even created a project similar to the one you described -- upper track rotating text event (720 degrees over about 30 secs); lower track a video file with Sony Glow set to .300/2.00/.300 -- both avg. about 9fps, and peak at about 12fps.

However, dropping the same .veg into V6 and I'm getting less than 1fps. I get great fps when there's just straight FX and no compositing in a veg.
rmack350 wrote on 4/20/2005, 6:46 AM
You mean that you created the project in V5, checked playback performance, then nested that project in V6 and checked the performance there?

Asking because your post doesn't mention nesting and sounds like a simple straight-up playback comparison.

Probably should create the project in V6 and then nest it in another V6 project, just to cancel out any question of this being an interaction of V5 projects in V6.

And the big question is whether there are some situations where a nested veg file plays back just fine.

Rob Mack
jlafferty wrote on 4/20/2005, 8:03 AM
I did this:

Created a project in V6; checked its playback. Avg. FPS was about 9.

Opened V5, copy/pasted the same project from V6 into V5, and played it. Same preview settings and it avg'ed the same FPS -- about 9.

Then, went back to V6, saved the project as a .veg, and dropped it onto the timeline. Tried playing it but got less than 1fps -- about .89 on average.

Dropped some random .veg's onto the V6 timeline -- basic multi-track veg's with some CC and other filters applied to the media, cuts and fades, etc -- but no compositing. Playback was as if I was playing straight from the timeline.

edit: it's definitely a compositing related issue -- just dropped the "cube with shadow.veg" from the sample projects available from Sony and .... it ..... crawls. Perhaps these composite .veg's need to use the new flatten tracks function to work properly...

edit: ...err, I guess I misunderstood "track flattening." Seems it's a DSE term that's not in the Sony Help files. It's automatic, just what happens when a .veg is brought into the project. However, it's not properly working for me -- I'm getting on avg. about .6fps (that's point six) with the cube with shadow .veg when it's dropped on the timeline as an event. Opening the .veg in Vegas, on the other hand, I get about 7fps.

- jim
BrianStanding wrote on 4/20/2005, 9:06 AM
I just put three 20-minute veggies on a V6 timeline. After the initial render, they play back just fine: full-frame rate; no problems.

Granted, the original .VEG files don't have a lot of FX or transitions on them, mostly just straight DV, cuts and dissolves, 6-8 tracks. I'm also viewing at "Preview/Full" in the Video Preview window.

I don't have a super-duper machine, either: Athlon XP 2700+ w/ 1 gig of RAM.

What kind of projects are you looking at where you're experiencing slowdowns?
rmack350 wrote on 4/20/2005, 9:12 AM
Got it. That's very clear and good info.

Maybe composited veg files are a good case for making a render and "saving project info" in the rendered file. It's a step away from nesting but still allows you to return to the original project for additional editing.

Rob Mack
johnmeyer wrote on 4/20/2005, 9:20 AM
jlafferty,

Click on the Support -> Email Support button at the top of this screen and report your findings to Sony.
pelladon wrote on 4/20/2005, 9:33 AM
One thing I noticed, on some files (veg), V6 is building or rebuilding .sfk's or .sfap0 files. Even if the .sfk's already exists! Aaarrrghh!
FrigidNDEditing wrote on 4/20/2005, 9:38 AM
I for one can't get enough of these nested Veggies, I'm making tons of space available, by haveing just the veg files, for lower thirds, and certain masking info etc... in a veg, instead of an uncompressed AVI or various other format.

Seriously - like 30K for a Veg - and I can keep it around for a good long time, and not have to "free up" space to be able to have them handy.

Dave
chaboud wrote on 4/20/2005, 9:53 AM
Pelladon, this happens because these files have changed in some way and the existing data is no longer valid.