Major improvements to Smart Trim in Vegasaur were introduced in V2.4, based on efforts by Nick Hope in this thread. http://www.sonycreativesoftware.com/forums/showmessage.asp?messageid=932826 I spent awhile trying the new feature using different footage and thought I'd share a few observations. In all cases, I imported one or more files for each media type and then 3 created three events with simple cuts editing. I then selected the three events and created a trimmed file for each event using the Vegasaur Smart Trim feature. I then imported the trimmed files on a new track for comparison with the original events.
First, if you use GoPro footage, you'll be delighted since trimmed files corresponded exactly with the original events. I used both 2.7K and 4K footage.
I then followed the same procedure with some other footage I had: AVCHD 1080 60P footage from 2 different Sony Handycams (consumer), AVCHD 1080 60P footage from a Panasonic FZ200, and finally some old HDV footage from a Sony HC1. Unlike the GoPro, in no instances were the trimmed files the same as the events on the timeline. Mostly, they appeared to be a bit shorter, although a few were longer. Clearly, they did not match up with events on the timeline.
There is an option to add frames at both the start and end of each event. I ended up adding 60 frames to both ends. In all instances, the trimmed files started "before" the event start and ended "after" the event end--good news, at least for archiving.
However, it would be nice to "trim" the trimmed files inside of Vegas and thus replace the original long media clips with the trimmed clips. Actually, this turned out to be a walk in the park using PluralEyes. After adding the the trimmed files to a new track, they were easily synchronized with the original media files on the timeline. Back inside Vegasaur, I then created Regions for each original timeline event. Then select the new tracks and use the option to "Keep inside regions". Close gaps and you're done. You now have the trimmed files in exact correspondence to events on the timeline. You can then discard the original tracks containing the much longer media files. Clearly, this procedure is best done during the early "cuts editing" phase of one's project.
In any case, the procedure seemed to work very well. Just thought I'd share.
wwaag
First, if you use GoPro footage, you'll be delighted since trimmed files corresponded exactly with the original events. I used both 2.7K and 4K footage.
I then followed the same procedure with some other footage I had: AVCHD 1080 60P footage from 2 different Sony Handycams (consumer), AVCHD 1080 60P footage from a Panasonic FZ200, and finally some old HDV footage from a Sony HC1. Unlike the GoPro, in no instances were the trimmed files the same as the events on the timeline. Mostly, they appeared to be a bit shorter, although a few were longer. Clearly, they did not match up with events on the timeline.
There is an option to add frames at both the start and end of each event. I ended up adding 60 frames to both ends. In all instances, the trimmed files started "before" the event start and ended "after" the event end--good news, at least for archiving.
However, it would be nice to "trim" the trimmed files inside of Vegas and thus replace the original long media clips with the trimmed clips. Actually, this turned out to be a walk in the park using PluralEyes. After adding the the trimmed files to a new track, they were easily synchronized with the original media files on the timeline. Back inside Vegasaur, I then created Regions for each original timeline event. Then select the new tracks and use the option to "Keep inside regions". Close gaps and you're done. You now have the trimmed files in exact correspondence to events on the timeline. You can then discard the original tracks containing the much longer media files. Clearly, this procedure is best done during the early "cuts editing" phase of one's project.
In any case, the procedure seemed to work very well. Just thought I'd share.
wwaag