avs2pipe

[Atak_Snajpera]

you can always add optional --show-audio-progress switch.

besides most of audio encoders have --quiet switch (opusenc,fhg aac,aften ac3, vorbis,flac)

btw thanks for quick response. i wil test it as soon as i can.

[SamKook]

I'm having a little problem when converting wav that would be over 4GB.
I'm piping audio from an avs script to neroaacencoder, but if I leave the default -wav setting and the audio is too long, it will say the following thing:

avs2pipemod[info]: writing 14504.948 seconds of 44100 Hz, 2 channel audio.
avs2pipemod[warning]: audio size over 32bit limit (4GB), clients may truncate audio.
ERROR: could not parse WAV file
avs2pipemod[info]: finished, wrote 0.011 seconds [0%].
avs2pipemod[info]: total elapsed time is 0.000 sec.
avs2pipemod[error]: only wrote 506 of 639668224 samples.

I know I can fix it by lowering the bitrate, but I'd like to keep the default setting when that's not necessary in my batch files.

Now my problem is that even if avs2pipemod gives an error message, the return value is still 0 meaning there was no errors for DOS so I can't check the %ERRORLEVEL% variable for errors and try again with a lower bitrate. Is there any chance that this could be fixed?

Unless it's me who does something wrong when I test it with the following:

"C:\Program Files (x86)\avs2pipemod-0.4.1\avs2pipemod.exe" -wav test.avs | "C:\Program Files (x86)\NeroAACCodec-1.5.1\neroAacEnc.exe" -q 0.42 -if - -of test.aac & ECHO %ERRORLEVEL%

[tebasuna51]

To allow than NeroAacEnc.exe accept wav files greater than 4 GB you need add the parameter -ignorelength:

...neroAacEnc.exe" -ignorelength -q 0.42 -if - -of test.aac ...

Edit:
BTW the correct extension for output is test.m4a
NeroAacEnc can only output audio AAC in mp4 container.

[SamKook]

Thanks, that make things a lot simpler. I'm not sure how I haven't tried it before since it seem so obvious now that I re-read the help for it.
A different errorlevel in case of errors would still be nice, but much less important now.

Thanks for letting me know about the extension. It doesn't change much since it get muxed right after, but it's always better to do things right.

[_argos]

@Chikuzen (or doobry?, i am confused)
First, let me thank you for your great effort. Nice tool.

I encountered a strange behaviour while trying to capture output of "avs2pipemod.exe -info somescript.avs" in Python. When the script had audio (via DirectShowSource( ... audio=true)) the output could be captured, but without audio (via DirectShowSource( ... audio=false)) thge cpatured output was always empty. Using the command from commandline showed output everytime. So my question ist:

Do you do something to stdout when audio is absent or use different output for info?

Update: Well I looked into the source code. And I don't get it. There is nothing done differently, just an additional if-block for audio, put to sdtout the same way as video. Okay, my new crazy theory: The program exits to fast for Python to capture the output somehow if audio is not present, which then would be a problem of Python not your program. This is weird.

Greetings
Malte

PS I do use -info to probe with different scripts to find out which scripts can be used to render a file.

[feos]

I'm using avs2pipemod to put the video info to file:

avs2pipemod -info encode.avs > info.txt

and right after creating the info file, it freezes. I also did it from the command line without output to file, and it prints the file info in the cmd and then freezes.

Extracting the audio works well. Using the latest version from the above.

[Groucho2004]

Originally Posted by feos

I'm using avs2pipemod to put the video info to file:

avs2pipemod -info encode.avs > info.txt

and right after creating the info file, it freezes. I also did it from the command line without output to file, and it prints the file info in the cmd and then freezes.

Extracting the audio works well. Using the latest version from the above.

Post your script and/or try using avsmeter (with "-i" switch).

[feos]

Originally Posted by Groucho2004

Post your script and/or try using avsmeter (with "-i" switch).

A note before I do so:
The script alone loads very well into virtualdub, and audio/video processing works from the normal x264 command line. Also, what's notable is that the same batch and the same avs worked together very well for years. Then it stopped working. I installed another OS and it works on neither.

EDIT:

F:\Encode\TASEncodingPackage>AVSMeter encode.avs -i
AVSMeter 1.7.7 (AVS 2.6, x86) by Groucho2004
AviSynth 2.60, build:Sep 18 2013 [17:36:36]
Number of frames:               235326
Length (hhh:mm:ss.ms):   001:05:22.100
Frame width:                       320
Frame height:                      224
Framerate:                      60.000 (60/1)
Interlaced:                         No
Colorspace:                       YV12

Then it also froze :/
Here's the script: http://pastebin.com/CNAzMuxj

[Groucho2004]

Originally Posted by feos

Also, what's notable is that the same batch and the same avs worked together very well for years. Then it stopped working.

You have to figure out what change causes the script to freeze. Since you mentioned that the script worked for years, you at least changed the avisynth version. It might be a incompatibility between Avisynth and one of the plug-ins.

[feos]

Reverting to older Avisynth version (2010) doesn't help. But It seems the problem may be in using pass=1. The batch sets that before taking info. And when I set pass=1, the script won't load into virtualdub, telling "ExactDedup: failed to open dupinfo file". However the file is where the script reads it, and it looks ok. So the problem is with ExactDedup plugin. But I backupped the dll too, and it doesn't work, while it did (with whatever avisynth version).

[Groucho2004]

Originally Posted by feos

"ExactDedup: failed to open dupinfo file".

Try fully qualified paths for the (txt) files.

[feos]

It got loaded into virtualdub at pass=1 now, but avs2pipemod still freezes at the same line.

EDIT: It appears even when I do pass=0 (no ExactDedup used), avs2pipemod still freezes after creating the info file...

EDIT: Using "info" instead of "-info" prints info into cmd window, but creates only the blank file. Which isn't what I need, because that file is read from, to set SAR according to clip parameters.

EDIT: Had to solve it by dropping the FreeSub plugin use. avs2pipemod+freesub+ffmpeg were hanging. Here's some gdb trace: http://pastebin.com/QbPWLqwG.

The issue got its workaround.

[Chikuzen]

new version released

avs2pipemod-1.0.0
- change avisynth_c.h to Avisynth+MT's avisynth.h.
- change C99 to C++11.
- change mingw-w64 to VisualC++2015.
- drop Avisynth2.5x support.
- drop WindowsXP support.
- drop x264bd and x264raw options.
- add Avisynth+MT's new 16/32bit formats support.
- add FFmpeg's extended Y4M formats output support.
- add '-dll' option.

now, avs2pipemod requires VC++2015 runtime (because I decided to avoid avisynth_c.h).

[Chikuzen]

updated.

avs2pipemod-1.0.1
- fix video output when avs has no audio (reported by stax76).

[Chikuzen]

updated.

avs2pipemod-1.0.2
- fix calculating video duration of -info.
- show avisynth's VersionString() on -info.

[Chikuzen]

updated.

avs2pipemod-1.0.3
- fix memory leak possibility.
- add version resource.

[ultim]

Originally Posted by Chikuzen

updated.

avs2pipemod-1.0.3
- fix memory leak possibility.
- add version resource.

Just being curious: Did you find the memory leak by chance, or were you made aware of it by Avs+'s new warning logs?

[Chikuzen]

Originally Posted by ultim

Just being curious: Did you find the memory leak by chance, or were you made aware of it by Avs+'s new warning logs?

by Avs+'s warning.

[yup]

Hi all!
Please advice how use avs2pipe with x265.
I can write command for rawvideo:

avs2pipemod64  -rawvideo test.avs | x265_64 --input - --input-res 960x720 --fps 50.0 --output video.h265

How can write for y4m, script output progressive video.
yup.

[Chikuzen]

avs2pipemod64 -y4mp test.avs | x265_64 --input - --y4m --output video.h265