Native Avisynth support in ffmpeg

[Inc]

After watching some interesting exchanges in the mailinglist of ffmpeg-dev in the last days ... now they did apply native avisynth script support:

http://svn.mplayerhq.hu/ffmpeg/trunk/?sortby=date#dirlist
(Last log entry of for instance "Configure")

http://svn.mplayerhq.hu/ffmpeg/trunk/configure?view=markup&rev=6122&sortby=date
(look under --enable-avisynth ;) )

http://svn.mplayerhq.hu/ffmpeg/trunk/Changelog?view=markup&rev=6122&sortby=date
(last item of the "version <next>" listing)


When looking more deeply within the avisynth.c interface in the libavformat directory I can see they use the Avifil32 API to obtain A/V data from scripts:


Thus .... Sound will be limited by an Unsigned Long 'virtual' 4GB Barrier?
(Would be bad for 5.1 Avisynth PCM DATA outputs :( )

Moment ... how does AviStreamRead() gets Audiodata? in Samples or Blocks?? Cant remember right now ....


I recommended in the mailinglist the usage of the avisnyth_c interface but there was no reaction.

[bond]

great stuff! thanks a lot robux4!

[IanB]

@Inc,

Thanks for the super-wide-cinemascope post. NOT! (please fix it)

And yes AVIStream read has a very annoying 4GB cliff. Squid was looking into ways and means of dealing with it. I don't know if he got anywhere.

[Inc]

Thanks for the super-wide-cinemascope post. NOT! (please fix it)Cant follow you, whats wrong? Do you mean the code part?
On my TFT screen it results in a normal posting-proportion.

Ill remove the code part as I cant affect its wide-appearing

[IanB]

Thanks! Yes it was the very wide code block (Damn vBulletin), it cause all the other text to be that wide as well and imposible to read.

What they really want is to support the IAvisynthClipInfo interface. GUID={E6D6B708-124D-11D4-86F3-DB80AFD98778} VirtualDub is a good example of how to use it.

[squid_80]

@And yes AVIStream read has a very annoying 4GB cliff. Squid was looking into ways and means of dealing with it. I don't know if he got anywhere.
I shelved the whole thing when Avery starting teasing with glimpses of virtualdub 1.7.0.

[Inc]

Couldn't the 4GB Cliff problen get solved if in ffmpeg they do acces scripts using the avisynth_c interface and its commands as audio sample count is defined as INT64?