![]() ![]() ![]() If FFmpeg returns an error at any point, the script aborts without deleting the temp files, since they may help with debugging.įor video, keep this in mind: the output will always be in the RGB colorspace / pixel format, because these scripts assume RGB input and attempt to preserve the color information. You'll see some temporary files being created during the run ( "TMP*"), but unless something goes wrong, the script cleans up after itself when it's done in fact all files starting with "TMP" in the current directory will be deleted, so try not to have any. If the output filename is omitted, the script will use the same name as the input appended with "_OUT". The Youtube video sample will show you the effect in motion, but here are a few still-image results at a higher resolution: Which includes everything you'll need, except for FFmpeg itself of course. This script (a Windows batch file only, at least for now) will let you perform a CRT transform on an image or a video of the original-resolution material. If you know of a way around these shortcomings, that'd be nice to know.) (FFmpeg can also be told to use the GPU, but not for everything - also, its GPU acceleration isn't portable and doesn't seem to make things very much faster, anyway. Of course, there are a ton of shaders for use in your favorite emulator which do it on the GPU in real-time, but I don't know of a decent way to just apply them to a stand-alone image or video file without tearing your hair out. I'm not kidding about "slow" - if you actually want to apply this to a video of more than a few seconds, in good quality, prepare to be outpaced by a glacier running a marathon through molasses. That's mostly due to the speed of doing this all on the CPU. You won't get much serious use out of this, even if we pretend that there is such a thing as "serious use" for simulating CRT monitors. This is just a fun little experiment which I've been tinkering with here and there lately. ![]()
0 Comments
Leave a Reply. |