I ran into this issue sometime ago and was referred to a forum that discussed the same issue - here's the fix (at least for me it was):

Check your projects audio properties - I believe there are issues with DebugMode Frameserver when the audio properties are set to 48khz - set your projects audio properties to 44khz 16bit and you should be able to work with it.

Cliff Etzel - Solo Video Journalist
bluprojekt | solo video journalism blog

Thanks Cliff! Worked for me too (my properties had been 48/24).
Now I have to figure out why the BD video stream TMPGEnc is creating is crashing DADA5....

I frame serve regularly to On2 Flix Pro to create my FLV's - a much better solution IMO compared to built in encoders like Adobe's Media Encoder.

Quicktime Pro doesn't like the frame served files FWIW - it throws an error about 8% into the encode to h.264 MP4.

Cliff Etzel - Solo Video Journalist
bluprojekt | solo video journalism blog

I was reinvestigating the frameserver after some discussion in another thread, and it seems it only outputs square pixels.

That makes it pretty limited for most current formats, right? Is there a way to get widescreen out? I found I can frameserve to Super but it is squished 4:3.

Does this mean that the workflow I've been using, h.264->Super->FLV is still the best for 16:9, or is there some some setting / trick I'm missing?

Answered my own question --

If I set the Super output to 432x240 (or 864x480) and stretch the output, I get a usable widescreen FLV from the Satish Frameserver.

I check the Direct Code Decode switch in Super to get it to work.

I will do some more comparisons, but this seems like a slick solution to the Vegas-to-FLV question. Going to try that other converter mentioned too.

The Frameserver should be outputting exactly what you give it without making any sort of pixel conversion. That's the whole point of the frameserver.

There are other problems with it that basically boil down to it being a free tool that is good enough but not polished. For instance, I think on occasion the settings you see may not really reflect the settings it's using, especially after a crash or failure. You may need to manually find and delete a signpost file, change and rechange settings...it's not perfect but it does a very specific and unique thing.

Never had a problem with 48k audio but I don't use it nearly as much as cliff does.

Rob Mack

It's not 48K audio it has a problem with, it's 24 bit. instead of 16 bit.

**The Frameserver should be outputting exactly what you give it without making any sort of pixel conversion.**

My captured footage and project properties are 16:9 Widescreen NTSC DV, 1.21 PAR.
The frameserver sends out 720x480 1.0 PAR (square pixels) VFW. The distortion is obvious.
I have previously rendered this project to DVD Widescreen and MPEG-4 Widescreen.
I haven't found any setting for aspect in the frameserver.
It looks like it hasn't been updated to do this.

If there is an easy workaround that you know of in Vegas without stretching to fill a custom project frame size I would like to know about it.From an

Cliff,

Hmmm. Okay, you want it to apply a PAR. I think my point stands. You're using a 720x480 project and that's what it's outputting. Seems pretty straightforward. There is no PAR, just pixels.

It's up to your receiving program to apply an interpretation to that frame. If you're going Vegas to Vegas then you'd adjust the media's properties in the project media window

Rob

Actually, I agree more with your original statement .

I just don't think it's there yet. I don't know if there is any plan to continue development either.
I don't want to "apply" a PAR, but like you I was hoping it would preserve the PAR.

"It's up to your receiving program to apply an interpretation to that frame."
Ideally the frameserver, like other renderers, would pass the source PAR to the output.
Without that information, one would need to manually adjust the source dimensions or the destination

PAR is strictly a display flag. It does not affect the resolution or cause any change of quality. A DV video is 720 x 480 pixels, NTSC. A flag for 16 x 9 is inserted by programs in order for the video to be displayed as widescreen. When the flag is applied does not affect the quality or cause any "pixel conversion" of the video file.

Widescreen itself does affect the display quality. Although we are used to seeing it since that is the way that SD Widescreen DVDs have always been created. It is taking 720 pixels and stretching them to 873 or so pixel widths.

Dave T2