Debugmode Frameserver revisited

Lou van Wijhe wrote on 1/15/2014, 6:14 PM
Some time ago I used to frameserve from my previous editor, Puremotion Editstudio V6, to Vegas Pro 10 because ES6 had a nice function that VP didn't have but ES6 only had a rendering possibility for MPEG-2 HDV 1440x1080 whereas I needed HD 1920x1080. Debugmode's Frameserver solved this.

I have re-installed the latest Debugmode Frameserver. I can now frameserve from both ES6 and VP12 but when I frameserve FROM ES6 to VP12, the latter doesn't recognise the input, it cannot open the signpost file. I have tried both the 32 and 64-bit frameserver version.

Any tips? Have I overlooked something? I now transfer footage from ES6 to VP12 using uncompressed intermediate AVI files but frameserving obviously is more convenient.

Lou

Comments

Warper wrote on 1/16/2014, 4:58 AM
Is ES6 in 64-bit version?
Lou van Wijhe wrote on 1/16/2014, 6:02 AM
Thanks for responding! No, ES6 is 32-bit. In VP12 I tried both 32 and 64-bit but neither worked (export worked, import not).

Lou
Lou van Wijhe wrote on 1/30/2014, 10:37 AM
My problem isn't solved yet. I got the following response from Satish:

I haven't tested with VP12 so not sure what could be the issue.. given that it works in an older VP version, have you asked about it in the Vegas Video forums? May be one of the Vegas engineers would know..

When I frameserve from ES6 I can play the signpost file in Windows Media Player but there is no sound. VLC Media Player says it doesn't recognise the DFSC format. I suspect the appropriate codec is missing or misplaced. MediaInfo says the file contains a VFW (PAL) videostream. Should I need a codec for that? Any ideas?

TIA,
Lou

P.S.
I have been googling for a VFW codec and found this one. It has VFW in the file name but when I start it, it also mentions installing an MPG2 and H264/AVC codec. I am reluctant to try it because I don't want to mess up my system with codecs I don't need. Do you think it is safe to proceed?
Lou van Wijhe wrote on 2/3/2014, 3:58 AM
Anyone?
dxdy wrote on 2/3/2014, 10:00 AM
I believe that johnmeyer had a post on frameserving into Vegas a number of years ago, a search on the forum should find it. It pre-dates Vegas 12, so may not apply.
john_dennis wrote on 2/3/2014, 10:14 AM
I installed debugmode frameserver a couple weeks ago and was successful serving "out" data from Vegas 10, 11, and 12 but have been unsuccessful at having 64 bit Vegas read the signpost .avi file. Though I've searched quite a bit, I haven't found a solution to date.

I'm interested in the process and will work on the issue again when my time permits. When I have the time I can test the codec, since I have current images of the systems that I use.
Lou van Wijhe wrote on 2/3/2014, 12:28 PM
Thanks very much for responding!

@dxdy: In the past I have succesfully frameserved to VP10. I know the technique but I wasn't succesful in reading signpost-files in VP12 64-bit.

@John Dennis: As you have the same symptoms, it apparently isn't some setting I overlooked. I'm very interested to know your test results in due course. After a system crash and corrupted backup files I'm hesitant at the moment to temper with my recovered system. I hope you don't mind my letting you pull the chestnuts from the fire...

Lou

wwaag wrote on 2/3/2014, 12:44 PM
Here is one JohnMeyer post that describes the process using Avisynth and VfapiConv.

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=880697

If you want to put the output of the AVISynth script back into Vegas, you can either first render from VirtualDub (the Cineform codec works well), or you can use VFAPIConv to change the output of the AVISynth AVS script into an AVI file that a second instance of Vegas can import. Using this workflow you have one instance of Vegas serving out the video and a second instance of Vegas doing the rendering. This completely eliminates the need to have to deal with codecs inside of VirtualDub.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. Current cameras include Panasonic FZ2500, GoPro Hero5 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Lou van Wijhe wrote on 2/3/2014, 3:29 PM
Thanks. I looked into it but I'm afraid it's a bit over my head. I think all I need is a VFW-decoder that VP12 can use, so that there's no need for intermediary files.

Lou
john_dennis wrote on 2/3/2014, 11:23 PM
I downloaded and installed the x264vfw codec that you mentioned in an earlier post. It's not a silver bullet. Just having it installed doesn't make Vegas Pro 12 recognize the file being frame served out of the other instance of Vegas. I couldn't quickly find any instruction of how this program is used. It looks like a command line or script based encoder...

I also installed Vegas 8.0c (32 bit) and served frames but Vegas Pro 12 won't open the file.

Serving frames from Vegas 12 to Vegas 8: Vegas 8 sees the audio but not the video using YUY2. Vegas 8 sees the video and audio using RGB32 and PCM audio. The audio always seems to be rendered as 44.1 kHz in spite of the source audio and project properties being 48 kHz.

Interestingly, Sound Forge 9 can open the Vegas 12 Signpost.avi file and handle the audio.

I can leave this machine in this state for a few days or until I try something that breaks it completely.

P.S. I had forgotten how Vegas Pro 8 burns your eyeballs out.
Lou van Wijhe wrote on 2/4/2014, 4:50 AM
Thanks for sharing, John!

Lou