Output various from avs to stdout has stopped working

[unix]

Hey guys!

Suddenly and first time I got this issue. Actually I'm encoding movie and at the middle of encoding I got this error message.

" Output various from avs to stdout has stopped wroking "

https://i.imgur.com/4zPrFej.jpg

any help?!

[Groucho2004]

Hey guys!

Suddenly and first time I got this issue. Actually I'm encoding movie and at the middle of encoding I got this error message.

" Output various from avs to stdout has stopped wroking "

https://i.imgur.com/4zPrFej.jpg

any help?!
This means that avs2pipemod crashed. There are many potential reasons for that, I'd start with the script. So, run your script with AVSMeter and check if it crashes and/or runs out of memory. Also, post your script.



If anyone is wondering about this odd error message - Look at the .rc file:
BEGIN
VALUE "FileDescription", "output various data from avs to stdout"
VALUE "FileVersion", "1.1.1.0"
VALUE "InternalName", "avs2pipemod"
VALUE "LegalCopyright", "Copyright (C) 2016 OKA Motofumi"
VALUE "OriginalFilename", "avs2pipemod.exe"
VALUE "ProductName", "avs2pipemod"
VALUE "ProductVersion", "1.1.1.0"
END

The "FileDescription" would usually hold the application name, the "output various data from avs to stdout" should be under "Comments" in the "StringFileInfo" block.

[unix]

AVSMeter 22.avs -o
Pause

When I run the avs script with AM it crashed.

post your script.

which script?

[asarian]

Not to get into the middle of things, but whatever happened to the good old avs2yuv.exe? When I was still doing AviSynth (I migrated to VS later on), avs2yuv never failed me.

[Groucho2004]

When I run the avs script with AM it crashed.No error message?

which script?The .avs script.

[qyot27]

Not to get into the middle of things, but whatever happened to the good old avs2yuv.exe? When I was still doing AviSynth (I migrated to VS later on), avs2yuv never failed me.
avs2yuv's y4m capabilities are limited to 8-bit? Don't pick at the logic there too much.

I dunno, it's almost never* necessary to use one of these AviSynth piping utilities anyway. Have people forgotten that x264 has natively supported AviSynth scripts as input since 2005 (http://git.videolan.org/?p=x264%2Fx264-sandbox.git&a=search&h=HEAD&st=commit&s=avisynth)? Piping just introduces needless overhead.

*the exceptions being crossing the Wine-to-native barrier on Linux, mixing 32-bit AviSynth with 64-bit x264 (only; there's no point in piping 64-bit AviSynth to 32-bit x264 - just use a 64-bit x264), or for apps that don't have AviSynth input support (like x265 builds lacking the LAVF input patch). And even then, in most cases you could do the exact same thing - encoding right from the script with [libx265 and friends] or piping out to an external program - just by using FFmpeg.

[asarian]

avs2yuv's y4m capabilities are limited to 8-bit? Don't pick at the logic there too much.

I dunno, it's almost never* necessary to use one of these AviSynth piping utilities anyway. Have people forgotten that x264 has natively supported AviSynth scripts as input since 2005 (http://git.videolan.org/?p=x264%2Fx264-sandbox.git&a=search&h=HEAD&st=commit&s=avisynth)? Piping just introduces needless overhead.

Back in the day, I had to run 32-bit AviSynth, because most of the relevant filters (to me) were 32-bit only, and 64-bit stuff was largely experimental/absent. So, I used avs2yuv to pipe things to 64-bit x264. And avs2yuv never crashed on me, ever.

[Groucho2004]

And avs2yuv never crashed on me, ever.Since AVSMeter also crashed in this case it's fair to assume that there's something wrong with the script and/or associated plugins.

[asarian]

Since AVSMeter also crashed in this case it's fair to assume that there's something wrong with the script and/or associated plugins.

Indeed. Outside the 'feeder' crashing itself, there's normally no reason why a simple pipe program should crash on its own. I was simply surprised to see someone use something else than avs2yuv, is all. :)

[StvG]

avs2yuv's y4m capabilities are limited to 8-bit? Don't pick at the logic there too much...

mod 4+ has support for AviSynth+ high bit-depth pixel formats (https://github.com/MasterNobody/avs2yuv/releases)

[unix]

Thank you very much everyone for the information, I decide to encode directly by x264 without piping and everything goes well.

thanks again.

[asarian]

Thank you very much everyone for the information, I decide to encode directly by x264 without piping and everything goes well.

thanks again.


It can't use .vpy input files yet, right?

[unix]

It can't use .vpy input files yet, right?

If u mean it can't use .vpy without piping then yes you're right, but I used avs to encode the final file (not for filtering).