FrameServer 4.21 released, supporting ffmpeg/Resolve/more..

poz_cumincode wrote on 10/1/2021, 5:23 PM

Hi all,

We just pushed out version 4.21 of CuminCode FrameServer a few minutes ago. You can try it out from https://www.cumincode.com/frameserver/

This version comes with 2 new, big features:

A "virtual uncompressed AVI" capability, which is the default setting. The frameserved video appears as an uncompressed AVI in the file system, so it can be opened by any NLE/encoder easily. We tested with Resolve, TMPGenc, Resolve, ffmpeg and many others. These didn't open the AVI produced by previous versions of FrameServer.
- With this option enabled, the frameserver files now appear under "c:\ccfs\virtual" folder.
Set a command to run automatically on FS start, and close FS when the command finishes. This is useful to run an encoder such as ffmpeg. FrameServer doesn't ship with any such encoders and you'll have to get ffmpeg or other software separately, but you can simplify your workflow by chaining CCFS with them easily.

If you already have a license to CuminCode FrameServer, you'll get these updates for free. The next release will likely include FrameServer plug-ins for Resolve and After Effects.

Thanks to @wwaag and Marco for helping with testing this release.

Do you have any feature requests for FrameServer? What can make your render workflow simpler/better/easier ?

- Poz

https://www.cumincode.com/frameserver/

Back to post

Comments

Howard-Vigorita wrote on 3/23/2023, 8:15 PM

@GJeffrey Thanks for that. V210 makes a significant difference. More like Voukoder 13...

rgb32 ... psnr: 30.6171; ssim: 9474; vmaf: 40.1038
vouk .... psnr: 38.1276; ssim: .9448; vmaf: 51.0709
v210 .... psnr: 38.3352; ssim: .9465; vmaf: 52.5895

But unfortunately when v210 is selected, the avi signpost is not recognized by vp20. Don't know if VRQ can load it without vp20 so I can measure it. Btw, v210 appears to be 4:2:2. Doesn't look like there's a 4:2:0 10-bit option.

Howard-Vigorita wrote on 3/23/2023, 10:26 PM

Just tried QsvEncC64 and that worked like a charm with FrameServer. Used this command line which I think I got right to match the x265 ffmpeg command line I used above with v210:

qsvencc64 -i d:\temp\fs.avs -c hevc --vbr 24000 --max-bitrate 48000 --vbv-bufsize 48000 --output-depth 10 -o d:\temp\fs.mkv

Got these results with Intel Qsv ... psnr: 38.3507; ssim: .9473; vmaf: 53.2081

Btw, the v210 x265 render took 3m 14s while the v210 QsvEnc took 58s.

Howard-Vigorita wrote on 4/1/2023, 1:15 PM

New version 7.36 of qsvenc came out a few days ago so I reran everything with a more explicit command line in both versions:

qsvencc64 -i d:\temp\fs.avs -c hevc --input-csp yuv422p10le --vbr 24000 --max-bitrate 48000 --vbv-bufsize 48000 --output-depth 10 -o d:\temp\fs.mkv

Found that with the new version, leaving out the convertto line in the avs text file ran slightly faster at higher quality. Here's what I got before and after the qsvenc update and then dropping the convertto:

Note that the FrameServer v210 format natively converts my 4:2:0 10-bit input clip to a 4:2:2 10-bit sign-post. Which qsvenc then converts back to 4:2:0 10-bit. I would not be surprised if all that needless back-and-forth might affect both performance and quality.