Cannot open AVS file in VirtualDub 1.10.4

[poisondeathray]

Is that all you are doing in vdub? change the framerate ? You should be able to do that ffmpeg directly

Can you describe exactly what is going on in terms of the framerate in the desired output? If the output file has unique frames (nothing blended, or duplicated, or inserted, or dropped compared to the PSD) , and the number of frames is identical, yet the frame rate is 24.0 fps, then that's what the frame rate is. You set -r 24 in ffmpeg as the input ouption . You can skip vdub and lossless intermediates in that case and encode using libx265 in ffmpeg directly .

[DarrellS]

Now you've gone and taken all the fun out of it I use Photoshop to create the .psd (all the layers of my animation, usually less than 100, sometimes only 10 or 15), GMG to set the speed of the animation, catch any mistakes and fix with live edit in Photoshop. Some animations I need one frame to stay open longer than the next (say I'm using text that can't be read in 5 seconds). Then Virtualdub to set the framerate, maybe put transitions between frames, add audio if it's a music video, test the way it plays and make sure that I haven't missed anything like black on the edge of a white background where there was transparency that I didn't get covered before encoding to x265.

How would I batch convert a folder full of .psd files with the same resolution? I tried "*.psd" for input but that's no go.

[poisondeathray]

Now you've gone and taken all the fun out of it I use Photoshop to create the .psd (all the layers of my animation, usually less than 100, sometimes only 10 or 15), GMG to set the speed of the animation, catch any mistakes and fix with live edit in Photoshop. Some animations I need one frame to stay open longer than the next (say I'm using text that can't be read in 5 seconds). Then Virtualdub to set the framerate, maybe put transitions between frames, add audio if it's a music video, test the way it plays and make sure that I haven't missed anything like black on the edge of a white background where there was transparency that I didn't get covered before encoding to x265.

Ok, if you need to do other manipulations, of course you can't pipe directly to ffmpeg and encode the final format

Variable frame delays in gif are essentially "VFR" in video. Vdub doesn't support VFR because of it's AVI/VFW heritage. But you can do the equivalent of VFR in CFR terms by inserting duplicate frames - the functional equivalent of an increase in frame on screen time (of course, that's less efficient, even with b-frames in HEVC or AVC). MKV and MP4 containers do, however support native VFR - you would need to mux in a timecodes if you wanted VFR. (Not sure if libx265 / x265 has it yet , but x264 has --tcfile-in to encode VFR directly)

How would I batch convert a folder full of .psd files with the same resolution? I tried "*.psd" for input but that's no go.

It's basically the same syntax as you would use for a ffmpeg batch

eg. convert a folder of .psd RGB to hevc/mkv YV12 using Rec709

It might look something like this

for %%a in ("*.psd") do "convert.exe" "%%a" rgb:- | "ffmpeg.exe" -f rawvideo -s 1920x1080 -pix_fmt rgb24 -r 24 -i - -c:v libx265 -crf 18 -pix_fmt yuv420p -vf colormatrix=bt709:bt601 -an "%%~na.mkv"   

pause

The paths have to be specified, or the binaries to be in the search path, or setup as an environment variable . (And if you still needed Vdub , you could still use the old one as a batch with huffyuv or utvideo or ffv1 in AVI )

So you would need a different batch for different resolutions and/or framerates - and enter your encoding parameters you normally use for x265 using -x265-params if you were using HEVC (that part is essentially the same as you would do with a vdub external encoder template) . Supposedly there is a way to have tiered logic in the batch - where if it detects "x" width or height then do this; sort of IF/THEN conditionals, but it's way beyond me for scripting those sorts of complex batches

[DarrellS]

I've still been trying to get convert.exe and ffmpeg to work but although ffmpeg claims to support a bunch of ultra high definition files, I'm not getting any encodes higher that 1920x1200 to work. I guess that Wilbert's Imagemagick program is just way too old to support very high resolutions. I know there were large Tiff files back then but nobody was using them in video files since videos larger 128x96 - 352x288 were hard to find.

MY PC isn't fast enough and doesn't have enough memory to do 8K anyway but it does 4K fast enough. x264 was slow also trying to do these large resolution files before and although if I try to open too big of a file in Gif Movie Gear, I will run out of memory. At least it will open the files if there aren't too many frames and I can cut the psd files in half and make multiple avi which I can append in Virtualdub and use the external encoder to encode the final file if I have to.


The same HEVC encoder set (or any other encoder set for that matter) in Virtualdub will accept any supported resolution using the "-" stdin which is why I'm confused that convert.exe and ffmpeg.exe are not allowing me to do my higher resolution files since they both accept stdin and why it's making me give it an output resolution since it sees the input resolution through the pipe.

[poisondeathray]

I've still been trying to get convert.exe and ffmpeg to work but although ffmpeg claims to support a bunch of ultra high definition files, I'm not getting any encodes higher that 1920x1200 to work. I guess that Wilbert's Imagemagick program is just way too old to support very high resolutions. I know there were large Tiff files back then but nobody was using them in video files since videos larger 128x96 - 352x288 were hard to find.

MY PC isn't fast enough and doesn't have enough memory to do 8K anyway but it does 4K fast enough. x264 was slow also trying to do these large resolution files before and although if I try to open too big of a file in Gif Movie Gear, I will run out of memory. At least it will open the files if there aren't too many frames and I can cut the psd files in half and make multiple avi which I can append in Virtualdub and use the external encoder to encode the final file if I have to.


The same HEVC encoder set (or any other encoder set for that matter) in Virtualdub will accept any supported resolution using the "-" stdin which is why I'm confused that convert.exe and ffmpeg.exe are not allowing me to do my higher resolution files since they both accept stdin and why it's making me give it an output resolution since it sees the input resolution through the pipe.

What do you mean "back then ?" . ffmpeg and convert definitely work with UHD, 4K, and higher. Post your console log, what error messages are you getting? Run taskmanage while you are debugging this and monitor your memory usage

(BTW - It's not "Wilbert's Imagemagick" program - he just made the avisynth adaptation of it. But you're not using that, you 're using the original convert.exe )

If something works with the vdub external encoder through stdin - it will definitely work directly without vdub.

You need to specify the resolution, because it's a RAW pipe. The benefit of a raw pipe is it's the most compatible with everything - it "looks" like raw data. If you used a yuv4mpegpipe, there is header information, and thus no need to enter those characteristics like framerate, resolution etc... because those are taken from the input file characteristics and passed along. AFAIK you can't use a yuv4mpegpipe with convert anyways

If you're running out of memory - it should be possible to pipe subsampled raw YUV 4:2:0 from convert, instead of RGB .This should take less memory. The final encoder might gobble up lots of memory depending on the settings. If you have long lookahead etc.. those frames are cached in memory. So using faster settings might help if you have a memory problem