Joining to videos, trimming unwanted footage Cropping & AddBorders

[Sharc]

Try with
LWLibavVideoSource(........) instead of AviSource(.............)

[SkyBlues2021]

Thanks Sharc. I will try that .Thanks.

[SkyBlues2021]

I've tried the LWLibavVideoSource . But I still get the same error. I also tried it on virtualdub2 and got this error message. Thanks.

[davexnet]

I don't think avs scripts open in Avidemux; there used to be a proxy that worked, but haven't seen it in a while
Vdub2 shouldn't have any issues though

[Sharc]

But both AviSource and LWLibavVideoSource seem to work in the OP's AvsPmod. Strange.....

Does the simple script

version()

open in Vdub and/or Avidemux?

Edit: Yes, it seems like Avidemux cannot dierctly open avs scripts. I probably have something installed on my PC which I don't even remember what it is, in order to make it work. But VirtualDub2 should be working in any case. I just retested on my small notebook here.

[SkyBlues2021]

Thanks davexnet & Sharc. I tried version() and get the same error message with Avidemux. Virtualdub2 loads the script however when I select file>save & open as AVI I get an error message also. Thanks.

[davexnet]

You're doing something wrong. Just drag the avs script into vdub2.
Regarding version(), you can't save it, it's not a video

[Sharc]

^ this,
or Save & Refresh..... (F5), rather than Save & Open as avi (F7)

[jagabo]

Regarding version(), you can't save it, it's not a video

It creates an RGB24 video and you can save it. No point though.

By the say, I can't open AVS script in AviDemux. Though, if you look through its settings there are references to AviSynth.

[SkyBlues2021]

Thanks. Does that mean that with Avidemux an avs. must be converted to an AVI file before it can only be opened? meaning I will have to save a intermediate file? I will try the vdub2 suggestions when I get home from work. Thanks.

[Sharc]

Does that mean that with Avidemux an avs. must be converted to an AVI file before it can only be opened? meaning I will have to save a intermediate file?

I made a few more tests but I didn't find the conditions when Avidemux succeeds in opening .avs scripts and when it fails. Weird.

So maybe better forget Avidemux for now and focus on VirtualDub2, which always worked here.

[jagabo]

With VirtualDub2 be sure to use File -> Open Video File (or drag/drop an AVS script), not File -> Run Script. The latter is for VirtualDub2's own scripting language, not AviSynth scripts. And when using 32 bit AviSynth you must use 32 bit VirtualDub2; when using 64 bit AviSynth you must use 64 bit VirtualDub2.

[lollo]

So maybe better forget Avidemux for now and focus on VirtualDub2, which always worked here.

Even better, forget all these useless GUIs and encode the AviSynth script with a simple command line:

ffmpeg.exe -i script.avs -c:v libx264 -crf 17 -preset slow -aspect 4:3 -c:a aac -b:a output.mp4

It would have saved lot of energy, time and discussion

[Sharc]

So maybe better forget Avidemux for now and focus on VirtualDub2, which always worked here.

Even better, forget all these useless GUIs and encode the AviSynth script with a simple command line:

ffmpeg.exe -i script.avs -c:v libx264 -crf 17 -preset slow -aspect 4:3 -c:a aac -b:a output.mp4

It would have saved lot of energy, time and discussion

Yes, provided we don't forget to specify the bitrate for the audio .....

ffmpeg.exe -i script.avs -c:v libx264 -crf 17 -preset slow -aspect 4:3 -c:a aac -b:a 128k output.mp4

or delete the -b:a to leave it at its default

[lollo]

Correct, bad editing on my side

[Sharc]

Also, your commandline encodes and flags the interlaced output as progressive which is probably not quite what we want, no?

For interlaced encoding and flagging:

ffmpeg.exe -i script.avs -c:v libx264 -crf 17 -preset slow -flags +ilme+ildct -aspect 4:3 -c:a aac -b:a 128k "output.mp4"

[lollo]

Also, your commandline encodes and flags the interlaced output as progressive which is probably not quite what we want, no?
For interlaced encoding:

Originally, OP wanted to deinterlace his video. We helped him n the past with QTGMC on the same footage (he had a QTGMC() command in his script)!

[Sharc]

Also, your commandline encodes and flags the interlaced output as progressive which is probably not quite what we want, no?
For interlaced encoding:

Originally, OP wanted to deinterlace its video. We helped him n the past with QTGMC on the same footage (he had a QTGMC() command in his script)!

Maybe, but neither the script nor your commandline deinterlaces.
Anyway, discussions go on with or without GUI, it seems

[lollo]

Anyway, discussions go on with or without GUI, it seems

Yes

BTW, OP had some help 1 year ago for his (same) capture. including deinterlacing: https://www.digitalfaq.com/forum/video-capture/12805-first-video-capture.html, and also about encoding: https://www.digitalfaq.com/forum/video-capture/12805-first-video-capture.html#post85085

the same some months later: https://www.digitalfaq.com/forum/video-restore/12856-avisynth-plugin-virtualdub.html

Apparently now he's is in your clan of no-deinterlace , I thought it was still using initial approach. In any case you're right, with his script in this thread my command line encoding is wrong.

[SkyBlues2021]

Thanks Sharc, jagabo & lollo. I've finally been able to open a script in vdub2! I've installed vdub2 32-bit. I can open them with file> open video file or Tools > script editor and also drag/drop method which is fantastic. I've installed Avidemux 2.7.4 32-bit (they don't seem to have version 2.8.1 in 32-bit) but it gives an error message see attached.

I have attached the new virtualdub2 encoded video and hopefully there aren't any chroma issues? Thanks.

[Sharc]

Yes, chroma motion is correct now IMO. It is in synchronism with the luma motion.

Glad it works now for you with VirtualDub2, and you can process and encode Avisynth scripts via VirtualDub. You have now the full potential of Avisynth available for processing your videos.

As I wrote, after some tests I gave up trying to open Avisynth scripts in Avidemux. Sometimes it worked, sometimes it failed for no obvious reason.

[SkyBlues2021]

Thanks Sharc. I'm so relieved and grateful for everyone's help. I will try again with the Avidemux encoder but I also need to try and read and cross reference the chroma/luma to better understand it as I'm clueless. Thanks.

[davexnet]

I couldn't get Avidemux to open Avisynth scripts at all, but it kind of works if you run Avsproxy from the command line,
then in Avidemux file/connect to avsproxy.

[SkyBlues2021]

Thanks davexnet. I wonder if frequent Avidemux users have to save the script as an AVI before opening. Thanks.

[Sharc]

I bet the typical Avidemux user does not use Avisynth scripts at all. He opens his sources directly in Avidemux and does the rest with the tools which are provided by the GUI. And eventually lives with what the GUI offers to him. That's the purpose of such GUIs.

[Sharc]

I couldn't get Avidemux to open Avisynth scripts at all, .....

It seems to work here for YV12() 4:2:0 sources only. It fails however for the 4:2:2 YUY2 (huffyuv) captures. Hence these must be converted with ConvertToYV12(.....) in the script.
No warranty though, but this seems to be the rule here to let Avidemux open .avs scripts.

[jagabo]

AviDemux doesn't work for YV12 scripts here. I also tried YV24, YV16, YUY2, RGB24 and RGB32. All give the same "Cannot find a demuxer..." error that SkyBlues2021 is reporting. It may be because I use it as a portable application (it's never been "installed" on this computer). Maybe there's something in the installation procedure that is needed to enable AviSynth import.

[SkyBlues2021]

Thanks Sharc & jagabo. I will stick with the Virtualdub2 encoded, which seems to have done a good job. Thank you for researching the Avidemux encoder for me, I had hoped to use it as a just in case, however it seems a bit temperamental. Thanks.