That sounds great. Is there a website that explains frameserving in connection with VP?

Frameserving gets you uncompressed output without creating a file or using oodles of disk space. Uncompressed frames are very quick to create because there's no encoding involved. Very useful if you want to output picture to an secondary encoder.

Rob

Google "debugmode"

Does anyone know if the new SVP 13 build allows the debug frameserver to work now?

Answering my own question: No.

Installing Debugmode Frameserver to ver 13.310 causes the Render As dialog to crash.

Tried uninstalling/reinstalling 13, still crashed.

Uninstalled Frameserver, 13 render dialog works fine.

Frameserver still works on 12.

Chris Dolan says he'll reach out to Satish and Satish says he has asked the Sony folks about it. This is a deal-breaker for me so hopefully they'll find each other in cyberspace and get it working.

Short version: we've got a plan, but it's still in progress.

Satish and I have been working on this together. I believe it will require a new build of Frameserver with a new compiler -- I can't seem to find a workaround on the Vegas side. Since Frameserver is open source, I've been trying myself to upgrade it to a newer Visual Studio version (vs2012), but the SCons build environment is unfamilar to me so I've been tripped up a few times.

If anyone out there has ever used SCons or likes to program in Python, this worthy project could use some volunteer help.

Google "debugmode"

I did that, albeit not with Google, which I avoid, installed it in my Vegas 12, and Vegas can render to it. Alas, when I tried to open the frameserved file in anything else, from HandBrake to VirtualDub, nothing could open it (and yes, the frameserver was still running inside Vegas). They all either said it was in an unsupported format (i.e., HandBrake) or the codec was missing (i.e., VirtualDub and everything else I tried).

So it seems rather useless.

I frameserve all the time from VP12 to Ripbot and honestly couldn't live without it.

You should be able to frameserve vfw AVI to VirtualDub. Likely using the wrong format.
You cannot frameserve to Handbrake. Never could, because it has a scan pass.

@ Red Prince

Why do you avoid Google?

Just curious.

Why do you avoid Google?

No privacy there. This is what I use instead.

Likely using the wrong format.

It only gave me three choices, RGB24, RGB32, and YUY2. I picked RGB24...

You cannot frameserve to Handbrake.

OK then, thanks.

I frameserve RGB24 all the time to VirtualDub.

So, what is your secret, Nick?

I frameserve RGB24 all the time to VirtualDub.

+1. Simply open the signpost avi file in Virtualdub. I've never had a problem doing this. I'm currently using version 1.9.11.

wwaag

Are you using the 64-bit version or the 32-bit version of Virtual Dub? I have the 64-bit version. Maybe that is the problem?

32-bit version 1.9.11

OK, thanks, Nick.

MusicVid10,

I wonder what in the scan pass is what is preventing the frameserve to Handbrake? The strang e thing is that Ripbot actually demuxes video streams to be transcoded and saves them in a work directory and it frameserves perfectly from VP12. Talk about a heavy duty scan pass.

Handbrake is definitely asking for some type of handshake that the frameserve won't allow though.

Dunno. Possibly the cross-platform interface.

Handbrake is designed to make more than one pass over the input file. That is the sole reason why it cannot work with a frameserver.

You can think of frameserving as rolling marbles through a pipe and the pipe is one way only. You can only read the marbles in linear order, and once the marble is removed from the pipe you cannot read it again.

An application can detect that the file it is reading from is actually a pipe and save the stream to disk if it wants to do random access.