Here's a link to download the latest version of DMFS which is now compatible with Vegas 23. https://www.debugmode.com/frameserver.html
Note that this version is compatible for all Vegas versions from 13 to 23.
Much appreciation is extended to the developer of this venerable Vegas tool, Satish Kumar.
Sorry got a bit confused with this. How is this used? Is it a standalone? The new version of HOS just released has version 6.0 of DebugMode FrameServer included does this replace that? Is an updated version of HOS being released with Ver 7? Any significant differences between ver 6 and 7?
Sorry for any confusion regarding HOS. The new version of HOS installs the latest build of DMFS (7.0). The difference between 6.0 ad 7.0 is support for Vegas 23. No need to install DMFS again since HOS has already installed it.
Running Render+ with 1.0.3.37 shows DebugMode FrameServer is v6.0 when paused and you click about.
Under the hood, it is 7.0. The file version info as shown has been corrected when downloaded from the DebugMode website. I have also updated the HOS installer to reflect the correct version number. You can always download the setup file again by opening the help tool in HOS. Click on the Check Now button and you will see this dialog.
Great thanks, all worked well and showing correct version.
Accessing Frameserver via HOS is probably the easiest since it automates installing all the pieces and connecting it with scripts to supported apps like ffmpeg and rigaya renderers. I've been running the various incarnations of frameserver for years, however, installing all the pieces manually and writing my own scripts. Here's how...
1. Install AviSynth. It provides the transport connection between the Frameserver plugin and apps like ffmpeg that support it for input. I've been using 64bit Avisynth+, now up to v3.7.5.
2. Install the external renderer. I'm using ffmpeg v7.1.1 at the moment but pre-release v8 is also out. Put it in a folder that is in your app search-path... I have a c:\util folder on my search-path and put utilities like ffmpeg and rigaya renderers there. Or put it in a Program Files folder and modify your search-path to include it.
3. Install the DM Frameserver plugin. v7 came out the other day and now supports up to vp23. It'll ask you to choose versions of Vegas and other apps which support it and will connect-up all the ones you pick.
Once the plugin is installed, it shows up like this in vp23 if you set the filter to show all... I also typed fs as the render file name which will put the avi-signpost in my D:\temp folder where I do all my test renders:
Here's the dmfs settings screen I use when I click Render:
I get the highest 4k quality from v210 and point it to the powershell execution script I use to run apps like ffmpeg. Note that the fs.avi signpost is mentioned at the bottom of the screen. In addition to the powershell script, there also needs to be another file for AviSynth named "fs.avs"... I put them both in the signpost folder, d:\temp in this case. My fs.avs file doesn't usually change unless I put the signpost somewhere else. They look like this:
My fs.avs just tells AviSynth where the signpost is. The powershell script runs ffmpeg 7.1.1 telling it to get it's input from where fs.avs locates the signpost... that particular script is what I used to do a 28mbps CBR 10bit Nvidia render.
Thanks for the explanation on how the work-flow works.