1. Choose menu "File > Render As" to open the default render dialog (make sure your project uses 8/16 bit audio, they are the supported formats).
2. Enter a valid filename for the output file. This file is called the "signpost" file.
3. Choose "Debugmode FrameServer" as the output type.
4. Click "Save" to start FrameServing.

1. From timeline, choose menu "File > Export > Movie" and choose "Debugmode FrameServer" in the list of output formats.
2. Enter a valid filename for the output file. This file is called the "signpost" file.
3. Click "Save" to start FrameServing.

1. From the timeline, choose menu "File > Create > Video File" to open the default render dialog.
2. Enter a valid filename for the output file. This file is called the "signpost" file.
3. Choose "Debugmode FrameServer" as the output type.
4. Click "Save" to start FrameServing.

1. From the timeline, choose menu "File > Build Movie" to open the default render window.
2. Choose "Debugmode FrameServer (project settings)" as the preset to use and click Next.
3. Enter a valid filename for the output file. This file is called the "signpost" file.
4. Click "Finish" to start FrameServing.

1. From the timeline, choose menu "Share > Create Video File" and select the "Custom" template to open the default render dialog.
2. Enter a valid filename for the output file. This file is called the "signpost" file.
3. Choose "Debugmode FrameServer" as the output type.
4. Click "Save" to start FrameServing.

Click here for information about network frameserving.

Premiere Pro can handle YUV video data natively. If your Premiere project uses clips that are in YUV format (like DV AVIs) then Premiere processes them in the same colour space wherever possible. When frameserving such a project, the FrameServer plugin asks Premiere for YUV data first and if not found asks for RGB data. So your input clips in YUV space will be processed by Premiere in YUV space and given to the frameserver, which gives the data in the same colour space to the target application.

Not all applications can handle YUV data directly. Most apps expect only RGB space video so check with your encoder/target app for the frameserver to make sure it can handle YUV space AVI files before using the YUV mode. The frameserver has only been tested with Windows media player >=8.0 and CCE >=2.67 successfully for YUV frameserving.

Finally a few important notes:

1. Premiere Pro does not work in pure YUV format, it works in AYUV (alpha+YUV) format internally. But the alpha data is not used by the frameserver.
2. The frameserver does not work in pure YUV format either. It serves data in YUY2 format which subsamples the U and V colour data. Pure YUV format data takes 3 bytes per pixel of video and YUY2 format data takes only 1.5 bytes per pixel so less data to transfer between the frameserver and the target app. So there is an implicit conversion from AYUV that Premiere Pro gives, and the YUY2 that the frameserver actually serves but this conversion is less processor intensive and better quality than a full AYUV->RGB->YUV (PremierePro->Frameserver->target app which does MPEG encoding).
3. In NLEs other than Premiere Pro, the frameserver always gets RGB data from the NLE. So if you enable YUY2 mode in these NLes then the RGB input is converted by the frameserver to YUY2 and served. This option is not very useful except for experimenting to see if it takes lesser time than a direct RGB serving.

1) There are some issues with audio serving from Vegas 4.0b and earlier (not in Vegas 4.0c), so seeking back in audio will cause any subsequent audio reads to return empty samples. In such cases, use the "Write audio as PCM samples in AVI" option. This can also be used in other software which are unable to read the FrameServer audio.

2) If audio is not saved as PCM with AVI file, seek operation may fail if started from the middle of the served video.