Comments

johnmeyer wrote on 9/20/2003, 10:52 AM
You don't have to create an intermediate file. These can consume more disk space than you may have. Also it lets you do everything in one step instead of two. This is less time spent sitting next to the computer waiting for one process to finish and then starting another.
Former user wrote on 9/20/2003, 3:38 PM
One reason some people frameserve out of Vegas is to use another mpeg encoder. Some people like TMPGEnc or another encoder and this allows them to encode through that without having to create an intermediary AVI file.

You might framserve into Vegas if you are ripping from a DVD and want to encode to another format.

Dave T2
johnmeyer wrote on 9/20/2003, 3:43 PM
DaveT2's point is really important, and I missed it in my first response. Let me reiterate it: By frameserving, you can send the actual raw video to another application without first going through an intermediate file format that, for most people's hard disks, would require a format with some compression, and therefore degradation. Frameserving lets you, in essence, "save" each frame as an uncompressed AVI file (in memory) and pass this frame to another application. If you were to actually save the entire video as uncompressed AVI, your hard disk would fill up quickly. Thus, you can transfer video between multiple applications with zero degradation and without using up hundreds of gigabytes of disk storage space.
Maxter wrote on 9/20/2003, 4:54 PM
That sound pretty cool...

I cant get it to work

I choose render...and frameserve...open new VV instance....then what?
Grazie wrote on 9/26/2003, 8:51 AM
. . I'm waiting for the other shoe to drop . . . shall I search on this Forum ?. . . yeah, Grazie, Go Knock Yerself out!!

.. . g .
johnmeyer wrote on 9/26/2003, 10:36 AM
I choose render...and frameserve...open new VV instance....then what?

and from Grazie:

. . I'm waiting for the other shoe to drop . . . shall I search on this Forum ?. . . yeah, Grazie, Go Knock Yerself out!!

I guess you were still waiting for someone to answer. I just installed and used frameserver last night. It took less than a minute to get it going and completely understand it. Like the Nike ads say: just do it.

Once installed, you set up, in Vegase, the video that you want to supply to another application. You can select a region and use that region, if you wish. Go to File -> Render As and under "Save As Type" select the newly installed "PluginPac Frameserve (*.avi)" option. Give it a file name. However, instead of a render dialog, you get a frameserver dialog (you don't need to check the audio box unless you have a problem). When the dialog says "frameserving" you can go to your other application (which I guess could include another instance of Vegas) and open the "AVI" file you just began "rendering." In point of fact, nothing except a "signpost" has been created at this point. Vegas is just sitting there, like a horse in the gate, waiting to be let loose and send video galloping to your application. As soon as your application opens the AVI file, the PluginPac frameserver and Vegas supply whatever part of the AVI file requested.

Now, the really neat part about what Satish did is that your application can request to go backwards and forwards through the AVI file. This means you can do multi-pass editing, and scrub back and forth. The way I used it yesterday, I used some Virtualdub filters, loaded into Vegas via PluginPac, to clean up a video captured off the air. However, since this video originated on film, I wanted to do inverse telecine (IVTC) to remove the pulldown prior to rendering in MPEG. I don't know of any way to to IVTC in Vegas, but TMPGEnc has a dynamite IVTC. So, I frameserved the edited, cleaned-up video from Vegas, opened the AVI file in TMPGEnc. did the IVTC, and since TMPGEnc has an excellent MPEG encoder, I just went ahead and let it do the encoding (even though it is slower than Vegas).

Hope this helps!