I would also like an answer to this question. Interestingly, VideoFactory tells you the size before rendering any project.

Hi Don,

I actually had very few problems with Studio 8, but there are many things it won't do such as PIP, multiple video tracks , and especially pan and zoom (and many others).

PS: It seems that I remember your name from the Studio forums. If so, it's good to "see" you again.

Steve

Swimmer is right...VideoFactory does have this feature, and it is really nice for what you want to do.

I have posted something about this before (to add this option to VV), but I think people thought it was more like a Wizard or some hand-holding tool that beginners might need, (it is helpful though), and it went nowhere after that.

However, you can find out your file size by (first selecting a 'Loop Region') (you must have a 'Loop Region' selected in your event first)...

... then click: Tools -->Burn CD-->Multimedia CD--> then, the file size will show up. (Cheinworks showed me this).

If you uncheck the 'Render loop region only' box.....the 'Estimate size' and 'Free space' boxes will disappear! Try it, actually VF has more information about your file than VV!

Now, when I want to figure out my file size, transfer time, and stuff like that...I import my DV AVI file to Video Factory, and render to the format that I want my file to be.

If you are wondering what I am talking about, open VideoFactory with one of your own clips, or events with VideoFactory, then hit the "Make Movie" icon, then click on what you want to do (ie: Print your Movie to DV tape, or many other choices).

Let me know if I am missing something, or if I'm wrong. (I'm using VV 3.0c).

Jon

There really is no way to *very accurately* predict the size of a file before rendering to mpg2, winmedia, etc., though there are quite a few tools that come close for mpg2. It's even harder when you use multi-pass vbr, which you should be considering you want the most quality in the least space.

In general, once the encoded file starts being written, you can get an idea if you're somewhere in the target range using windows calculator, dividing the file size by the percent rendered - this can get tricky when doing 2 pass encoding as vegas only shows one percentage figure for the whole process.

Personally, for full motion video in wmv for download from the web, I'd try dual pass peak vbr at 320 x 240, with the peak set between 1.8 & 2.0 M, average set to 1.3 to 1.5 M, and adjust from there, reduce bitrates until quality drops below what you can live with, and talking heads etc. of course require a lot less bandwidth. For streaming you more or less have to live within whatever bandwidth restrictions set by the anticipated audience. For streaming you can also combine multiple bandwidth versions as an option.

Going to a smaller frame size, 320 or less for example, lets the graphics card take on a lot of the load if you wanted the video displayed larger - can rely on the viewer to set whatever player window size, or specify playback size on a web page displaying the video, or in an asx file you link to I think.

And whenever going to something like wmv, the quality of the source has a lot to do with the quality and final size - try and filter out any noise if present.