Frameserver error: Couldn't locate a decompressor for fourcc DFSC

vbencev wrote on 6/6/2024, 5:54 AM

I want to render a video from Sony Vegas through Debugmode Frameserver. I have used this method successfully in the past. For example I loaded camcorder mts files into Vegas, edited them, then run Debugmode Frameserver and could load the output avi file with AviSource into the encoder.

Recently I have edited an .mpg file, but AviSource doesn't open the Debugmode Frameserver avi output of that project. I says: 'Couldn't locate a decompressor for fourcc DFSC"

I thought maybe the problem is that though the Debugmode Framserver output is an avi file, in reality the content is mpeg. So I copied DGDecode.dll to the AviSynth+ plugin library, and Tadaam, the Mpeg2Source command opened the Debugmode Framserver avi output. Rendered the video successfully.

BUT, today I noticed there was some problem when I edited the video in Vegas, so I corrected the errors. Then I moved onto rendering the project again with Debugmode Frameserver and Mpeg2Source, and it no more works. The error message I get: DGIndex.exe is missing. I thought, okay I copy DGIndex.exe as well to the plugin library of avisynth. But this way nothing happens, CMD.exe is started when running the script, but it freezes.

So what can I do in this case?

This is the Mediainfo of the mpeg file being edited:
 

General
Complete name                            : C:\Users\bencuri\Videos\Obligatoire\primus.mpg
Format                                   : MPEG-PS
File size                                : 268 MiB
Duration                                 : 5 min 35 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 6 688 kb/s
Frame rate                               : 25.000 FPS
Writing library                          : (dvd5: Oct 27 2015)

Video
ID                                       : 224 (0xE0)
Format                                   : MPEG Video
Format version                           : Version 2
Format profile                           : Main@Main
Format settings                          : CustomMatrix / BVOP
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Custom
Format settings, GOP                     : M=3, N=15
Format settings, picture structure       : Frame
Duration                                 : 5 min 35 s
Bit rate mode                            : Variable
Bit rate                                 : 6 171 kb/s
Maximum bit rate                         : 7 000 kb/s
Width                                    : 720 pixels
Height                                   : 576 pixels
Display aspect ratio                     : 4:3
Frame rate                               : 25.000 FPS
Standard                                 : PAL
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Bottom Field First
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.595
Time code of first frame                 : 00:00:00:00
Time code source                         : Group of pictures header
GOP, Open/Closed                         : Closed
Stream size                              : 247 MiB (92%)
Writing library                          : (dvd5: Oct 27 2015)
Color primaries                          : BT.601 PAL
Transfer characteristics                 : BT.470 System B/G
Matrix coefficients                      : BT.601

 

Comments

john_dennis wrote on 6/6/2024, 8:54 AM

Which Sony Vegas version and build are you using?

mark-y wrote on 6/6/2024, 12:48 PM

What Debugmode Frameserver version are you using?

I know nothing about AviSource. You would need to check compatibility of that with the Frameserver output, which doesn't involve Vegas directly.

mark-y wrote on 6/6/2024, 12:54 PM

The main page for AviSource makes no mention of Debugmode Frameserver, only Avisynth.

http://avisynth.nl/index.php/AviSource

Howard-Vigorita wrote on 6/6/2024, 7:01 PM

@mark-y The Vegas FrameServer plugin uses AviSynth libs to connect it to another app that can input from the signpost FrameServer makes, so the connected app can perform the render instead of Vegas. Metadata says the writing library is dvd-5 so it's probably a compatibility issue with Vegas not recognizing the app script's output file.

@vbencev: If you can't get the rendering app to output the end-format you really want, I suggest connecting with a script to a more capable app. Vegas works fine with Frameserver outputting to ffmpeg and Riguya encoders which I use allot with v5 of DegugMode FrameServer. Those encoders support a variety of output formats compatible with Vegas. But if you fashion your command-line script for the output you really want, transcoding would be unnecessary. If you prefer keeping your workflow with the extra step, try ShutterEncoder which transcodes from more input formats than Vegas.

mark-y wrote on 6/7/2024, 7:46 AM

Thank you, Howard. I've used Frameserver since Satish Kumar ported it to Vegas Video 2 from Premiere, twenty-two years ago. I'm pretty sure he did not write the Avisynth Frameserver libraries, and I don't believe those are being used in Debugmode plugins for Vegas and other editors. Documentation needed.

Perhaps @vbencev can get it working with mediation by VFAPI or similar. No direct experience.

A long long time ago, Satish "did" write a frameserver plugin for Vegas TO Avisynth, I found this:

How do I frameserve from Premiere/Ulead/Vegas to AviSynth?

Install the AviSynth compatible frameserver PluginPace frameserver (by Satish Kumar) for frameserving from SonicFoundry Vegas (and earlier Vegas Video/VideoFactory versions), Adobe Premiere, Ulead MediaStudio Pro or Wax to AviSynth (discussion).

http://avisynth.nl/index.php/FAQ_frameserving

 

Howard-Vigorita wrote on 6/7/2024, 7:59 AM

Thank you, Howard. I've been using Frameserver since Satish Kumar ported it to Vegas Video 2 from Premiere; I find that was twenty-two years ago. I'm pretty sure he did not write the Avisynth Frameserver libraries, and I don't believe those are being used in Debugmode plugins for Vegas and other editors.

The Vegas framserver plugins are the only ones I'm familiar with. I don't think the source code is public. The only render apps I've used it with are ffmpeg and Rigaya encoders and the source code for those are public. They both use avisynth libs to connect to the frameserver signposts. For example detailed build docs, see: https://github.com/rigaya ... not to mention the older QsvEncC fork in my signature.

mark-y wrote on 6/7/2024, 10:22 AM

What are the "The Vegas framserver plugins?" Link needed.

The only current one I am familiar with is Debugmode, also the topic of this discussion thread.

Howard-Vigorita wrote on 6/7/2024, 11:59 AM

What are the "The Vegas framserver plugins?" Link needed.

The only current one I am familiar with is Debugmode, also the topic of this discussion thread.

I'm using the current v5 free Vegas plugin from the DebugMode download page which installs the Vegas and/or Adobe plugin:

http://www.debugmode.com/frameserver.html

I also have the v5 CuminCode Vegas plugin which is functionally identical but had commercial licensing removed when it was moved back to DebugMode. I think the CuminCode web page was taken down after the move. They both work fine for me in all versions and builds of Vegas from 16 through the latest 21 release. They should be able to channel a Vegas feed to any render or viewer app that is AviSynth compatible as long as you get the command line to invoke the app correct.

john_dennis wrote on 6/7/2024, 3:52 PM

We seem to be experiencing a lack of input from @vbencev, but I'll report that I was able to successfully serve frames to Shutter Encoder in about 53 seconds from downloading the current installer from the Debugmode Frameserver site. That should serve as an indication of just how bored I am.

I did have to contend with this "Help From Microsoft to do My Job".

mark-y wrote on 6/7/2024, 5:29 PM

...apparently leaving Debugmode Frameserver to AVS/AviSource a really good "ottabee," otherwise known as "feature request."

I seem to recall a long time ago frameserving from VDub to AviSynth; perhaps that also is what the OP recalls doing.

vbencev wrote on 6/9/2024, 2:02 AM

Which Sony Vegas version and build are you using?

Sorry, I forgot the notifications of replies go to my old email.

I am using Vegas 12 64 bit. I use Debugmode Frameserver 2.14, and select install 64 bit plugin. I cannot use later versions of the frameserver because they don't work with my version of Vegas.

I see I made a mistake in the first post that I did not clarify what I open the Debugmode Frameserver output with. This is because I thought most users use the frameserver to open it with AviSynth. I see this is not the case. That is what I use actually. And that does not work with it. Earlier it worked, but now it does not. I get the error that I mentioned in the title of this post. AviSource is the source filter that opens the avi from frameserver normally, but that does not open it in my case.

But I figured out meanwhile, that the 32 bit AviSynth works, it is only the 64 bit that doesn't. I don't know why, however.