Printing to tape from the timeline.

SHTUNOT wrote on 12/5/2001, 12:11 AM

What real gains do I get from this feature? Its nice and all but I just tried it...It gave me a warning that said that it would have to prerender over 80% of my 1hour and 7 minute movie. I read the manual and it states that "Prerendering a DV project uses approximately 228MB/minute,so plan accordingly". So why don't I just render it first then print...how much time are you really saving me? I knew that there was some buffer issue involved of course...I thought that maybe you did another trick with the ram thing...It prerenders...goes into ram...prints...guess not. Then I thought that maybe it needed space enough to start the prerendering procedure...after a gig or 2 then It will start erasing what it had done prior and continue in a sort of a loop,using the same harddrive space. Of course before erasing it would have then printed to tape what it had started. This way you wouldn't need all that HD space and be finished really quickly...or do I have a great imagination and should lay off the bong hits for a little while. Am I missing something? Later.

Comments

HPV wrote on 12/5/2001, 9:36 AM

It gave me a warning that said that it would have to prerender over 80% of my 1hour and 7 minute movie.
-------------------
Two things could be going on here.
1: FX(filters), graphics, transitions, track motion, pan/crop and speed changes all need to be rendered. How much of you project is unaltered clips?
Sounds like you may have used filters on all clips or a track fx. Track fx will render the whole track even where the fx is set to none.
2: You don't have the right project properties or render template set.

Craig (Pass the bong) H.

SHTUNOT wrote on 12/5/2001, 10:05 AM

I'll check on all of those and post back...Thanks guys.

SonyEPM wrote on 12/5/2001, 11:20 AM

If you have to render everything in the project, there is no benefit in terms of drives space saved.

Print from the timeline does do some frame buffering (unlike Video Capture), therefore there is less of a chance of dropping frames while printing, so there's still a plus.

SHTUNOT wrote on 12/5/2001, 1:14 PM

This is what I've worked out so far...
1. When I first captured the video in March I didn't own anything except the newest version of acid...I was getting into scoring so this was a great way to start off. I worked with a person on his indie film...1hour 10 minutes or so. I had to install a ulead capturing software to get it to my hard drive. I think that I must have brought it into my computer as an uncompressed dv. Reason being that if I had captured it as NTSC DV right off the bat then vegas would "smart render" the file and only have to prerender any fx/pan crop/crossfades/etc...which is none except for the cossfades that I put in at times.
This is why I guess it took nearly nine hours to render out my 1hour 7minute movie[final cuts done]. Or maybe a possible bug in this area as well...read on.
2. When I rendered I didn't specify how long to render...I just thought that when the last bit of information ends that it usually stops right there...done. Not so...I found a file with just black space+no sound after the movie had been finished off. It was 4 gigs of nothing[and it wanted to keep rendering for a undefinate amount of time...why didn't vegas realize this,I thought that it did in the prior version. Next time I'll specify a time length and see what happens.
I think that I'll have better results next time I use it...I hope.
3. I'm using Windows 98 second edition with dx 8.1. I'm having a B!tch of a time trying to keep this program stable. My .VEG files are becoming corrupted after being saved[even if I specify a numerator difference:ie:EBSA,EBSA1...BOTH GET CORRUPTED] I WORKED AROUND IT I THINK BY PLACING A SAVE IN ONE FOLDER AND MY OWN BACK UP IN ANOTHER...It doesn't create a .BAK file after any save. In acid 3 when you save a file you get a veg file and then a .bak file of the same name. CRAP! If I do anything too quickly and make my proceesor have to rush at all in rebuilding the peaks on the timeline I get stuff moved around and misplaced. Video that was synched perfectly AND LOCKED into place gets shifted over by a few seconds...or even a few video clips from say 1/2 way in the movie,all the way to the last clip ,gets UNLOCKED and shifted about 8-9 minutes down the timeline. If I move too quickly again I had my cpu reboot in the middle of a operation. I was editing volume in certain portions of the video...I liked the results...Hit the space bar to pause and go to a different section. Hit spacebar,screen goes black,computer reboots, I had to go 1/2 hour back and redo my edits.[I will save more often].
4. I don't know how this came about...I had "open last project" selected in the preferences screen. A project opened...the second clip that I placed in the time line had the VIDEO of the third clip in it!!!!!!AHAHAHAHAHAHHHAHAHAHAHAHAHHAHAHAHAHAHAAHAHAHAHAHAHAHAHA! And the Veg file was corrupted too so I couldn't even role back at all.F@ck!!! All that work that I had to do to fix it...opened another template of vegas[2 running at the same time] Copy stuff from one to the other. Luckily I had the video already done with the audio in a vegas 2.0h veg file so my work was cut down a bit. This is where I had the whole end section unlocked and moved over a few minutes. Plus when I selected all of the audio tracks to be copied over to the new template, not all of the volume and pan settings carried over...out of 20 or so tracks like 4 or 5 had them. Not stable at all...did not have this much hassle with 2.0h on my exact same system[with the exception of DX8A instead of 8.1].

Tech support said that some people using windows 98se have been having similar problems as myself so I'm not crazy. I wish everyone else the best of luck and a word of caution in using this program with 98se [at least]

I'll keep you guys updated. Later.

SHTUNOT wrote on 12/6/2001, 5:28 PM

I just came from the cretive cow web site and a moderater "DSE" gave me this answer to the long render time...When you captured using Ulead's capture tool, you used a different codec than SOFO uses in 2.0. This is why the video was recompressed/rendered. It has nothing to do with Vegas. So I guess that clears things up. Thanks...sorry nothing to report other than I've been having a blast with the audio side of things with vegas...mixed down 26 tracks yesterday...and 19 today...looking forward to the update in january. Later.