can you remeber me all the avisynth wrappers to create a fake .avi?

[marcorocchini]

Hi, but please I remember you that I'm a real cat: low ram usage, low cpu capabilities


[Attachment 50288 - Click to enlarge]

excluding AVFS I exactly don't remember what utility/programs can generate a fake .avi from an .avs script.

Please note that AVFS expose an output uncompressed, but in generally I try to understand what is all the rest of programs that do this including the specific fourcc inside the fake .avi file.

I have try avs2avi over a .avs script that have as source a large video file: but maybe because of the limit 2GB the output in my NLE result as truncated.

about AVFS: each time you load an .avs to a fake .avi you use a certain amount of ram that which could also become considerable when many clips are loaded.

But I wonder: what is the rest of all utulity/programs that to this? thanks

[poisondeathray]

makeavis - from old ffdshow

avs2avi - note there are several different programs with the same name. Only one of them is the "fake avi" emulator
see post #4
https://forum.videohelp.com/threads/348212-Looking-for-copy-of-avs2avi-wrapper-v0-3

[aedipuss]

didn't you also have to be running an emulator or something? and is that old program still viable on current o.s.'s?

[poisondeathray]

didn't you also have to be running an emulator or something? and is that old program still viable on current o.s.'s?

Not sure, last time I used one of those old ones was on Win XP




Newer CLI based AVFS versions work well - x86/x64 versions, v210 emulation as well (in the vapoursynth version, for professional programs)

The fourcc depends on what pixel format avisynth sends. The old AVFS PFM based version allows you to edit this in the script, even though the actual pixel format is something else. So you get garbage usually, because even though the "label" said one thing, it was actually something else

You need the actual pixel format to change, not just a label. For windows editors 8bit422 compatible fourcc and pixel format would be "UYVY". That usually "unlocks" everything, such as real YUV treatment (instead of RGB conversion, clipping). Avisynth is usually "YUY2" for 8bit422, although avisynth+ can use "YV16" or 8bit422 planar

The enable_v210 switch in vapoursynth changes the actual pixel format, 10bit422 interleaved (instead of P210, packed). v210 is accepted in all windows editors.



But he's trying to use a dinosaur, discontinued x86 NLE. So good luck with that and lack of memory problems. Have fun trying to edit UHD footage.