"Save Wtih Timmed Media" Problem

2G wrote on 5/14/2004, 9:45 AM
I have a V5 project that has about 20 ~5sec clips out of a 1hr AVI. When I save with trimmed media, it creates 7 ~9sec AVIs as I would expect. But then it creates one more clip that is 18min. Granted, all the remaining clips are somewhere in this big clip. But I would have expected 20 9sec clips instead of what I got.

A possible related concern is that when I went to edit list view just to see if I could figure out what was going on, several of the clips had take-start and timecodes that were values that were 1hr+. These are standard 1hr tapes. No way that I know of that the timecodes could be over an hour. (Yet the project plays correctly)

I'm not expecting anybody is going to be able to debug my specific problem. But I'm just curious if anybody has seen anything like this. Also, if any Sony reps are lurking, I am willing to assist in debug and can send veg files, etc.

Does this ring any bells with anybody?

Thanks.

2G

Comments

smhontz wrote on 5/14/2004, 11:24 AM
Did you have an speed changes in any of the clips? I had that problem in V4, haven't checked V5 yet. If I had a 1 GB avi, that I took, say, 5 secs from, and either sped it up or slowed it down, it would save the entire 1 GB file when I tried to use "Save With Trimmed Media".
2G wrote on 5/14/2004, 1:00 PM
Bingo! This is a wedding reflections segment. Everything is slo-mo.

Has Sony acknowledged anything related to this problem? Or do you know if they are even aware of it?

2G
SonyEPM wrote on 5/14/2004, 2:46 PM
Its not a bug- we don't render fx, resampling, processing etc into the source media during a copy or copy/trim.
2G wrote on 5/14/2004, 3:32 PM
I don't think that was what I was asking for.

So you are saying that if I have a 5 second clip and save with trimmed media, you'll create a 9 sec AVI file.... but if I slo-mo that 5 seconds to 6 seconds, you now save the "trimmed" source for that same 5 second clip as a 4GB 20minute AVI file?????? (that's what's happening) And this is working as designed???? Sorry, I don't see any rationale for that to be correct.

I'm not asking for rendering the media with save. I simply want the same 5 second clip saved as a 9sec AVI file. The veg file will continue to perform the slo-mo on the clip just as it did before the save. The fact that the project slo-mo's that clip should be totally irrelevant to trimming the source clip and creating an AVI file.

Sorry to disagree with you. But it IS a bug. I think you may have misunderstood what the problem is.
smhontz wrote on 5/14/2004, 6:29 PM
I'm with you, 2G. I thought it was a bug when I first ran into it, still do, and it's terribly inconvenient. I think my workaround at the time was to just render out the clip where I changed the speed to a separate AVI file and brought it back into the project to replace the original one. I shouldn't have to do that, but I didn't want to store a huge file.
SonyEPM wrote on 5/15/2004, 7:04 AM
please send the .veg file to dr.dropout@sonypictures.com
VMP wrote on 6/22/2004, 11:09 AM
I have also had problem with some trimmed "Avi" file sizes, for example one clip which was only 9 seconds on the timeline was renderd as a 13 gig avi file.

I think this is because I used "Event velocity" to change the speed on that clip.
The only solution for this which I have found is, to render the Clip, which has "velocity envelope" to new track before I trim save my project.
And make sure that there is no clip on the timeline, which has speed shift.
Otherwise Vegas (4/5) saves an extra hour to the trimmed AVI file.

I hope that this problem will be solved soon, because rendering the clip to new track causses a slight lose of sharpness.
And you can't change back the Velocity of that clip because it's renderd : - (.
VMP wrote on 6/23/2004, 5:53 AM
I have installed Vegas 5.0b ( Build 160 ) and the problem still is not solved.

( And also the track motion
presets option on the tracks, is still not there )

v_gts
Pcamp wrote on 6/23/2004, 6:55 AM
I struggled with this problem also. It turned out that the file being rendered fully was not being recognized as a proper DV file even though it seemed to be and was captured the same as the other files. Check the properties of the file within Vegas. The only solution that worked was to re-render the problem file as a DV files and re- import it to the project before trimming.
Paul
VMP wrote on 6/23/2004, 11:57 AM
yes sadly that is the only way :-((

v_gts
VMP wrote on 6/23/2004, 11:57 AM
yes sadly that is the only way :-((

v_gts