-
Nesting to the trimmer. Slowdown problem.
I captured 2hrs worth of footage with scene detect, (Consisting of over 500 clips) put it all on the timeline and saved the project as ‘footage.avi’.
I used the new nesting feature of Vegas 6 and put this file in the trimmer. From the trimmer I
set in and out points and add to the timeline.What I want to know is would this cause heavy overhead on my computer? Is Vegas
working overtime to read all those scene detect files, there’s over 500 of them?I’ve been working on this project for a week and it’s now 30mins in length and things are
becoming really really slow and weird. I don’t know if it’s due to this nesting I did or if it’s something
else.Previously I used to render out the scene detect clips as a new AVI. I never had any problems then
but still I don’t know for sure if this slowdown is caused by the nesting or something else..The question is: Will nesting a large amount of clips cause undue overhead in comparison to having 1 large AVI file in the trimmer?
-Frankie
-
2 Replies
-
You saved a PROJECT as “footage.avi”??? Should that not have been “footage.VEG”?
If you wanted a single file, it would have been preferable to capture with Scene Detect turned off. At this point if I wanted a single AVI – instead of using a nested VEG I think I would have simply rendered to a single AVI file and deleted the individual pieces.
What I would REALLY do at this point is to simply add the clips to the timeline (as you have), mark the pieces I wanted to keep using regions on the timeline, and use the “Extract Good Clips” tool in Excalibur. Then I would delete the original pieces from the timeline.
Edward Troxel
-
I need the footage captured with scene detect for the sole reason of trimming 1 second from the end of each camera cut. It’s a lot easier to find the end of a camera cut when captured with scene detect ON rather than having it off. Then for the main edit I need the whole footage as 1 ‘file’ which is why I used a nested veg file in the trimmer.
In the past, I would put my scene detected clips on the timeline and render it all out as a single AVI for use in the trimmer for my main edit. I always edit using the trimmer.
What I did this time was use a nested VEG file in the trimmer instead. What I’m trying to find out is this:- Is using a nested VEG file in the trimmer which contains over an hour of footage, more CPU intensive than using a rendered out AVI file in the trimmer utilising the same amount of footage.
I’ve been having mass system slowdown and I’m trying to work out if it’s because of this large nested VEG file I’m using.
-Frankie
>f you wanted a single file, it would have been preferable to capture with Scene Detect turned off. At >this point if I wanted a single AVI – instead of using a nested VEG I think I would have simply rendered >to a single AVI file and deleted the individual pieces.
Reply to this Discussion! Login or Sign Up