Satish, email me. I might be able to provide some input, contacts and steer you to some peer help. There is no reason to re-invent all of this. Parts and pieces are already laying about for examples. DDogg1953 >at< hotmail.com

What's 'frameserving'?

Frameserving (actually audio too) is the ability to pipe the timeline into another aplpication without having to first render out the asset to take up disc space as /an intermediate media file/s

Adobe Premiere has one [actually more if you like to edit text files], VideoServer (videotools.net).

VideoToaster[3] takes the whole concept a bit further. It does the equivalent of wrapping a .VEG file for use as an AVI. Saving the screen space area of all the required running apps, and probably some memory resources and also allowing you to use the edit-project files indirectly within the NLE. It of course uses different file types altogether from that of Vegas, but so is only an intellectual comparison.

I wish for either type of frameserving with Vegas4.

Forgot to mention, the Premiere version exports as uncompressed video (YUY2 I think) - so it will be interesting if SoFo do it the same way or give you a choice of output format too!

Frameserving allows the user to make the choice of which of his/her available tools are the best for the job without being trapped inside one application.

This is just off the top of my head, but imagine this somewhat fanciful scenario as an example of the power of video "Inter Process Communication"/frameserving (both IN and OUT):
1> You have a 30 gig raw video file as source and your HDs are nearly full (always it seems). These could be ANY files that Windows Directshow or VFW can open.
2> You use VirtualDub or an AviSynth script to open and apply multiple complex filters to that source and frameserve the output to Vegas. See note "a" below.
3> Do all the wonderful things that Vegas does.
4> Frameserve from Vegas to another app like AfterEffects, Premier or VDub and use whatever tools you need in those applications. Remember you have not created any intermediate files!
5> Frameserve from that application to Procorder or CCE for final render as mpeg.

This allowed you to use the best tools that YOU felt were best, all without one intermediate file being created. Maybe more importantly to Vegas folks, you save all the TIME it takes to create those intermediate files. Number 4 is the only stumbling block as Vegas cannot frameserve outbound. (Q:Can AfterEffects export like Premier?)

Note a: We have parts 1-3 right now with a small workaround. Vegas will not open the >native< AVS or VDub frameserving files. A workaround using VFAPI does work quite well but converts to RGB24 and slightly slows the process. I have been told by the Avisynth programmers that opening native avisynth AVS files should be trivial using the Windows VFW interface for most applications. SoFo would have to be the judge of that. Plenty of free help to SoFo programmers are available to them on this subject if they so desire to seek it. I might be able to help if SOFO wishes it and certainly would be willing to invest some personal time if it could be useful by gathering information and contact info to speed the process. DDogg1953 >at< hotmail.com

Here are a few threads concerning how to frameserve today TO Vegas:
Frameserving - Avisynth 2.5 to Vegas/other apps:
http://forum.doom9.org/showthread.php?s=&threadid=47194
Frameserving from VDub to Vegas/other apps:
http://forum.doom9.org/showthread.php?s=&threadid=47483