That shoud be enough just to make AVFS work and load created serve avi file into Magix Vegas (former Sony Vegas). That could be a good (no 4:2:0 conversion is needed in script) or bad thing (conversion cannot be controlled (but Cedocida should do a good job) if using AviSource in vapoursynth script instead of ffms2, then dvsd codec is needed, like having Cedocida codec installed, but then AviSource would capture 4:1:1 NTSC DVavi as 4:2:0. ffms2.dll (not sure where I have it from, there is one here ) and also put into vapoursynth64\plugins directory put into that portable directory, into vapoursynth64\plugins directory audio plugin BestAudioSource.dll, download link (I think, I just copied mine dll from some earlier portable directory of mine). python portable version 3.10.7, dumped in the same directory (not sure if Python 3.11 is already supported for vapoursynth)
portable Vapoursynth R60 download link, Videos used were NTSC DV avi, which are 4:1:1, that gets more complicated rather than PAL 4:2:0 Using a python/vapoursynth portable setup, all in one directory. I was fighting this beast in the past, so I tested it again using AVFS.exe. Newer versions of vegas can be set to operate in studio or computer RGB In vegas <18, those pixel would get "studio RGB" treatment automatically instead of "computer RGB". Those are "magical" pixel formats for most windows NLE's including vegas, and those formats get passthrough treatment. It has pixel format emulation such as "IYUV" for 8bit 4:2:0, "UYVY" for 8bit 4:2:2 and "v210" for 10bit 4:2:2. In some versions of vegas, you might have to convert to RGB in the script for avfs to work in vegas (not that bad, because vegas will be converting anyways at least you can control the type of conversion in the avs script) Not necessarily in terms of pixel format conversions -Īll versions of Vegas work in RGB, and if source/script work in YUV, there will be some conversion, and that is a type of loss if the conversion is not done in float. A slow script can be hard to handle in vegas and make timeline performance sluggish But a "losless" AVI can serve the same purpose, and can make it easier to edit in vegas (the script filters are "baked" into the AVI). Is frameserving a way to save on a generation-loss of rendering? Yes, in terms of lossy compression "losses".
0 kommentar(er)
