Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Roger Pack]

On 9/12/15, Francois Visagie  wrote:
> Hi,
>
>
>
> I hope to reach an expert familiar with both ffmpeg and Avisynth! I’m
> looking to perform some processing in ffmpeg, and then to continue in
> Avisynth. For a number of reasons, including disk space, I’d like to avoid
> intermediate files. Which, if any, of the ffmpeg server protocols are
> compatible with Avisynth’s TCPSource() filter, i.e.
>
>
>
> TCPSource (string hostname, int "port", string "compression")

ffmpeg can output to tcp
https://www.ffmpeg.org/ffmpeg-protocols.html#tcp
or to a named pipe.
You can probably use practically any container (mpeg2ts, mp4).
GL!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Francois Visagie]

> -Original Message-
> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
> Frank Tetzel
> Sent: 14 September 2015 21:40
> To: ffmpeg-user@ffmpeg.org
> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> 
> > > What processing do you want to do with ffmpeg?
> >
> > At a minimum I foresee concatenating input files with it. My current
> > project has 350+ video files. Avisynth cannot work with more than 25
> > - 35 without crashing. I have not found an Avisynth mechanism for
> > concatenating files that preserves audio.
> 
> There are multiple ways to concatenate files depending on the input codecs
> and what other processing you want to do with it [4]. Not sure if it handles
> hundreds of input files well enough.

In my testing it does, except that the current version is broken for M2TS input.

> 
> > > And why do you want to
> > > send it over tcp, if that's what TCPSource reads (not an avisynth
> > > user)?
> >
> > To avoid intermediate storage. Workspace for this project is 2TB.
> > Each additional version of the project is currently ~700GB. Some form
> > of inter-process communication is required to avoid intermediate
> > storage. TCPSource() seems the only type of built-in IPC input
> > Avisynth supports.
> 
> I don't know which data layout they expect in TCPSource and if it is in any
> way compatible with the tcp output protocol in ffmpeg, or any other
> protocol. I know this was your question in the first place but i can't help 
> you
> there. You could play around and just try to connect [1][2].

No luck so far, unfortunately.

> 
> There's also some avisynth support in ffmpeg [3]. As i never used it i don't
> know about its capabilities.

ffmpeg supports Avisynth input. I'm unsure whether its support extends beyond 
that.

> 
> What are you doing after processing with avisynth? Do you pipe it back into
> ffmpeg for encoding? Can't you use built-in filters [5] instead of an avisynth
> script?

Most of the non-linear editing will happen within Avisynth, including timeline 
editing, effects, contrast enhancement (effectively median unsharp masking with 
higher radius and lower strength), resizing for PAL DVD, motion-compensated 
denoising, sharpening and interlacing - a bit too complex for my ffmpeg 
knowledge!

> 
> 
> [1] http://avisynth.nl/index.php/TCPServer
> [2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
> [3] http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
> [4] http://trac.ffmpeg.org/wiki/Concatenate
> [5] http://ffmpeg.org/ffmpeg-filters.html#Description

Thanks for such a thoughtful and thorough contribution.

> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Francois Visagie]

> -Original Message-
> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
> Frank Tetzel
> Sent: 14 September 2015 21:40
> To: ffmpeg-user@ffmpeg.org
> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> 
> > > What processing do you want to do with ffmpeg?
> >
> > At a minimum I foresee concatenating input files with it. My current
> > project has 350+ video files. Avisynth cannot work with more than 25
> > - 35 without crashing. I have not found an Avisynth mechanism for
> > concatenating files that preserves audio.
> 
> There are multiple ways to concatenate files depending on the input codecs
> and what other processing you want to do with it [4]. Not sure if it handles
> hundreds of input files well enough.
> 
> > > And why do you want to
> > > send it over tcp, if that's what TCPSource reads (not an avisynth
> > > user)?
> >
> > To avoid intermediate storage. Workspace for this project is 2TB.
> > Each additional version of the project is currently ~700GB. Some form
> > of inter-process communication is required to avoid intermediate
> > storage. TCPSource() seems the only type of built-in IPC input
> > Avisynth supports.
> 
> I don't know which data layout they expect in TCPSource and if it is in any
> way compatible with the tcp output protocol in ffmpeg, or any other
> protocol. I know this was your question in the first place but i can't help 
> you
> there. You could play around and just try to connect [1][2].

On the premise that Avisynth would expect similar input via TCPSource() than it 
produces via frame-serving, I noted its video and audio formats when serving to 
ffmpeg and specified those codecs for the most likely-looking protocol, tcp.

Then came the issue of which format to specify for the tcp protocol. ffmpeg 
reports Avisynth's input format as 'avisynth', which the former does not 
support as an output format. I tried a couple of likely-looking candidates, 
mostly the 'raw' ones. With some, e.g. 'rawvideo':

ffmpeg -y -i 0.MTS -c:v rawvideo -c:a pcm_s16le -f rawvideo 
tcp://127.0.0.1:22050?listen

ffmpeg and Avisynth would connect and ffmpeg would in fact start serving. After 
a short while, however, Avisynth would crash out and ffmpeg would terminate with

av_interleaved_write_frame(): Unknown error

This seems to indicate at least format incompatibility, and perhaps initial 
connection set-up also.

> 
> There's also some avisynth support in ffmpeg [3]. As i never used it i don't
> know about its capabilities.
> 
> What are you doing after processing with avisynth? Do you pipe it back into
> ffmpeg for encoding? Can't you use built-in filters [5] instead of an avisynth
> script?
> 
> 
> [1] http://avisynth.nl/index.php/TCPServer
> [2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
> [3] http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
> [4] http://trac.ffmpeg.org/wiki/Concatenate
> [5] http://ffmpeg.org/ffmpeg-filters.html#Description
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Paul B Mahol]

On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
>> -Original Message-
>> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
>> Frank Tetzel
>> Sent: 14 September 2015 21:40
>> To: ffmpeg-user@ffmpeg.org
>> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
>>
>> > > What processing do you want to do with ffmpeg?
>> >
>> > At a minimum I foresee concatenating input files with it. My current
>> > project has 350+ video files. Avisynth cannot work with more than 25
>> > - 35 without crashing. I have not found an Avisynth mechanism for
>> > concatenating files that preserves audio.
>>
>> There are multiple ways to concatenate files depending on the input codecs
>> and what other processing you want to do with it [4]. Not sure if it
>> handles
>> hundreds of input files well enough.
>>
>> > > And why do you want to
>> > > send it over tcp, if that's what TCPSource reads (not an avisynth
>> > > user)?
>> >
>> > To avoid intermediate storage. Workspace for this project is 2TB.
>> > Each additional version of the project is currently ~700GB. Some form
>> > of inter-process communication is required to avoid intermediate
>> > storage. TCPSource() seems the only type of built-in IPC input
>> > Avisynth supports.
>>
>> I don't know which data layout they expect in TCPSource and if it is in
>> any
>> way compatible with the tcp output protocol in ffmpeg, or any other
>> protocol. I know this was your question in the first place but i can't
>> help you
>> there. You could play around and just try to connect [1][2].
>
> On the premise that Avisynth would expect similar input via TCPSource() than
> it produces via frame-serving, I noted its video and audio formats when
> serving to ffmpeg and specified those codecs for the most likely-looking
> protocol, tcp.
>
> Then came the issue of which format to specify for the tcp protocol. ffmpeg
> reports Avisynth's input format as 'avisynth', which the former does not
> support as an output format. I tried a couple of likely-looking candidates,
> mostly the 'raw' ones. With some, e.g. 'rawvideo':
>
> ffmpeg -y -i 0.MTS -c:v rawvideo -c:a pcm_s16le -f rawvideo
> tcp://127.0.0.1:22050?listen

How is rawvideo format supposed to handle audio frames?

>
> ffmpeg and Avisynth would connect and ffmpeg would in fact start serving.
> After a short while, however, Avisynth would crash out and ffmpeg would
> terminate with
>
> av_interleaved_write_frame(): Unknown error
>
> This seems to indicate at least format incompatibility, and perhaps initial
> connection set-up also.
>
>>
>> There's also some avisynth support in ffmpeg [3]. As i never used it i
>> don't
>> know about its capabilities.
>>
>> What are you doing after processing with avisynth? Do you pipe it back
>> into
>> ffmpeg for encoding? Can't you use built-in filters [5] instead of an
>> avisynth
>> script?
>>
>>
>> [1] http://avisynth.nl/index.php/TCPServer
>> [2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
>> [3] http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
>> [4] http://trac.ffmpeg.org/wiki/Concatenate
>> [5] http://ffmpeg.org/ffmpeg-filters.html#Description
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Francois Visagie]

> -Original Message-
> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
> Paul B Mahol
> Sent: 15 September 2015 12:55
> To: FFmpeg user questions
> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> 
> On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
> >> -Original Message-
> >> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf
> >> Of Paul B Mahol
> >> Sent: 15 September 2015 12:46
> >> To: FFmpeg user questions
> >> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> >>
> >> On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
> >> >> -Original Message-
> >> >> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On
> >> >> Behalf Of Frank Tetzel
> >> >> Sent: 14 September 2015 21:40
> >> >> To: ffmpeg-user@ffmpeg.org
> >> >> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> >> >>
> >> >> > > What processing do you want to do with ffmpeg?
> >> >> >
> >> >> > At a minimum I foresee concatenating input files with it. My
> >> >> > current project has 350+ video files. Avisynth cannot work with
> >> >> > more than 25
> >> >> > - 35 without crashing. I have not found an Avisynth mechanism
> >> >> > for concatenating files that preserves audio.
> >> >>
> >> >> There are multiple ways to concatenate files depending on the
> >> >> input codecs and what other processing you want to do with it [4].
> >> >> Not sure if it handles hundreds of input files well enough.
> >> >>
> >> >> > > And why do you want to
> >> >> > > send it over tcp, if that's what TCPSource reads (not an
> >> >> > > avisynth user)?
> >> >> >
> >> >> > To avoid intermediate storage. Workspace for this project is 2TB.
> >> >> > Each additional version of the project is currently ~700GB. Some
> >> >> > form of inter-process communication is required to avoid
> >> >> > intermediate storage. TCPSource() seems the only type of
> >> >> > built-in IPC input Avisynth supports.
> >> >>
> >> >> I don't know which data layout they expect in TCPSource and if it
> >> >> is in any way compatible with the tcp output protocol in ffmpeg,
> >> >> or any other protocol. I know this was your question in the first
> >> >> place but i can't help you there. You could play around and just
> >> >> try to connect [1][2].
> >> >
> >> > On the premise that Avisynth would expect similar input via
> >> > TCPSource() than it produces via frame-serving, I noted its video
> >> > and audio formats when serving to ffmpeg and specified those codecs
> >> > for the most likely-looking protocol, tcp.
> >> >
> >> > Then came the issue of which format to specify for the tcp protocol.
> >> > ffmpeg reports Avisynth's input format as 'avisynth', which the
> >> > former does not support as an output format. I tried a couple of
> >> > likely-looking candidates, mostly the 'raw' ones. With some, e.g.
> >> > 'rawvideo':
> >> >
> >> > ffmpeg -y -i 0.MTS -c:v rawvideo -c:a pcm_s16le -f rawvideo
> >> > tcp://127.0.0.1:22050?listen
> >>
> >> How is rawvideo format supposed to handle audio frames?
> >
> > Not, granted. Although rawvideo was simply the one picked (not very
> > cleverly) for the example.
> 
> And others like avi also do not work?

avi specifically was tried, and also did not work.

> 
> >
> >>
> >> >
> >> > ffmpeg and Avisynth would connect and ffmpeg would in fact start
> >> > serving.
> >> > After a short while, however, Avisynth would crash out and ffmpeg
> >> > would terminate with
> >> >
> >> > av_interleaved_write_frame(): Unknown error
> >> >
> >> > This seems to indicate at least format incompatibility, and perhaps
> >> > initial connection set-up also.
> >> >
> >> >>
> >> >> There's also some avisynth support in ffmpeg [3]. As i never used
> >> >> it i don't know about its capabilities.
> >> >>
> >> >> What are you doing after processing with avisynth? 

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Francois Visagie]

> -Original Message-
> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
> Paul B Mahol
> Sent: 15 September 2015 12:46
> To: FFmpeg user questions
> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> 
> On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
> >> -Original Message-
> >> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf
> >> Of Frank Tetzel
> >> Sent: 14 September 2015 21:40
> >> To: ffmpeg-user@ffmpeg.org
> >> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
> >>
> >> > > What processing do you want to do with ffmpeg?
> >> >
> >> > At a minimum I foresee concatenating input files with it. My
> >> > current project has 350+ video files. Avisynth cannot work with
> >> > more than 25
> >> > - 35 without crashing. I have not found an Avisynth mechanism for
> >> > concatenating files that preserves audio.
> >>
> >> There are multiple ways to concatenate files depending on the input
> >> codecs and what other processing you want to do with it [4]. Not sure
> >> if it handles hundreds of input files well enough.
> >>
> >> > > And why do you want to
> >> > > send it over tcp, if that's what TCPSource reads (not an avisynth
> >> > > user)?
> >> >
> >> > To avoid intermediate storage. Workspace for this project is 2TB.
> >> > Each additional version of the project is currently ~700GB. Some
> >> > form of inter-process communication is required to avoid
> >> > intermediate storage. TCPSource() seems the only type of built-in
> >> > IPC input Avisynth supports.
> >>
> >> I don't know which data layout they expect in TCPSource and if it is
> >> in any way compatible with the tcp output protocol in ffmpeg, or any
> >> other protocol. I know this was your question in the first place but
> >> i can't help you there. You could play around and just try to connect
> >> [1][2].
> >
> > On the premise that Avisynth would expect similar input via
> > TCPSource() than it produces via frame-serving, I noted its video and
> > audio formats when serving to ffmpeg and specified those codecs for
> > the most likely-looking protocol, tcp.
> >
> > Then came the issue of which format to specify for the tcp protocol.
> > ffmpeg reports Avisynth's input format as 'avisynth', which the former
> > does not support as an output format. I tried a couple of
> > likely-looking candidates, mostly the 'raw' ones. With some, e.g. 
> > 'rawvideo':
> >
> > ffmpeg -y -i 0.MTS -c:v rawvideo -c:a pcm_s16le -f rawvideo
> > tcp://127.0.0.1:22050?listen
> 
> How is rawvideo format supposed to handle audio frames?

Not, granted. Although rawvideo was simply the one picked (not very cleverly) 
for the example.

> 
> >
> > ffmpeg and Avisynth would connect and ffmpeg would in fact start serving.
> > After a short while, however, Avisynth would crash out and ffmpeg
> > would terminate with
> >
> > av_interleaved_write_frame(): Unknown error
> >
> > This seems to indicate at least format incompatibility, and perhaps
> > initial connection set-up also.
> >
> >>
> >> There's also some avisynth support in ffmpeg [3]. As i never used it
> >> i don't know about its capabilities.
> >>
> >> What are you doing after processing with avisynth? Do you pipe it
> >> back into ffmpeg for encoding? Can't you use built-in filters [5]
> >> instead of an avisynth script?
> >>
> >>
> >> [1] http://avisynth.nl/index.php/TCPServer
> >> [2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
> >> [3]
> >> http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
> >> [4] http://trac.ffmpeg.org/wiki/Concatenate
> >> [5] http://ffmpeg.org/ffmpeg-filters.html#Description
> >> ___
> >> ffmpeg-user mailing list
> >> ffmpeg-user@ffmpeg.org
> >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> > ___
> > ffmpeg-user mailing list
> > ffmpeg-user@ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Paul B Mahol]

On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
>> -Original Message-
>> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of
>> Paul B Mahol
>> Sent: 15 September 2015 12:46
>> To: FFmpeg user questions
>> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
>>
>> On 9/15/15, Francois Visagie <francois.visa...@gmail.com> wrote:
>> >> -Original Message-
>> >> From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf
>> >> Of Frank Tetzel
>> >> Sent: 14 September 2015 21:40
>> >> To: ffmpeg-user@ffmpeg.org
>> >> Subject: Re: [FFmpeg-user] ffmpeg serving to Avisynth
>> >>
>> >> > > What processing do you want to do with ffmpeg?
>> >> >
>> >> > At a minimum I foresee concatenating input files with it. My
>> >> > current project has 350+ video files. Avisynth cannot work with
>> >> > more than 25
>> >> > - 35 without crashing. I have not found an Avisynth mechanism for
>> >> > concatenating files that preserves audio.
>> >>
>> >> There are multiple ways to concatenate files depending on the input
>> >> codecs and what other processing you want to do with it [4]. Not sure
>> >> if it handles hundreds of input files well enough.
>> >>
>> >> > > And why do you want to
>> >> > > send it over tcp, if that's what TCPSource reads (not an avisynth
>> >> > > user)?
>> >> >
>> >> > To avoid intermediate storage. Workspace for this project is 2TB.
>> >> > Each additional version of the project is currently ~700GB. Some
>> >> > form of inter-process communication is required to avoid
>> >> > intermediate storage. TCPSource() seems the only type of built-in
>> >> > IPC input Avisynth supports.
>> >>
>> >> I don't know which data layout they expect in TCPSource and if it is
>> >> in any way compatible with the tcp output protocol in ffmpeg, or any
>> >> other protocol. I know this was your question in the first place but
>> >> i can't help you there. You could play around and just try to connect
>> >> [1][2].
>> >
>> > On the premise that Avisynth would expect similar input via
>> > TCPSource() than it produces via frame-serving, I noted its video and
>> > audio formats when serving to ffmpeg and specified those codecs for
>> > the most likely-looking protocol, tcp.
>> >
>> > Then came the issue of which format to specify for the tcp protocol.
>> > ffmpeg reports Avisynth's input format as 'avisynth', which the former
>> > does not support as an output format. I tried a couple of
>> > likely-looking candidates, mostly the 'raw' ones. With some, e.g.
>> > 'rawvideo':
>> >
>> > ffmpeg -y -i 0.MTS -c:v rawvideo -c:a pcm_s16le -f rawvideo
>> > tcp://127.0.0.1:22050?listen
>>
>> How is rawvideo format supposed to handle audio frames?
>
> Not, granted. Although rawvideo was simply the one picked (not very
> cleverly) for the example.

And others like avi also do not work?

>
>>
>> >
>> > ffmpeg and Avisynth would connect and ffmpeg would in fact start
>> > serving.
>> > After a short while, however, Avisynth would crash out and ffmpeg
>> > would terminate with
>> >
>> > av_interleaved_write_frame(): Unknown error
>> >
>> > This seems to indicate at least format incompatibility, and perhaps
>> > initial connection set-up also.
>> >
>> >>
>> >> There's also some avisynth support in ffmpeg [3]. As i never used it
>> >> i don't know about its capabilities.
>> >>
>> >> What are you doing after processing with avisynth? Do you pipe it
>> >> back into ffmpeg for encoding? Can't you use built-in filters [5]
>> >> instead of an avisynth script?
>> >>
>> >>
>> >> [1] http://avisynth.nl/index.php/TCPServer
>> >> [2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
>> >> [3]
>> >> http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
>> >> [4] http://trac.ffmpeg.org/wiki/Concatenate
>> >> [5] http://ffmpeg.org/ffmpeg-filters.html#Description
>> >> ___
>> >> ffmpeg-user mailing list
>> >> ffmpeg-user@ffmpeg.org
>> >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>> >
>> > ___
>> > ffmpeg-user mailing list
>> > ffmpeg-user@ffmpeg.org
>> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>> >
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Frank Tetzel]

> > What processing do you want to do with ffmpeg?
> 
> At a minimum I foresee concatenating input files with it. My current
> project has 350+ video files. Avisynth cannot work with more than 25
> - 35 without crashing. I have not found an Avisynth mechanism for
> concatenating files that preserves audio.

There are multiple ways to concatenate files depending on the input
codecs and what other processing you want to do with it [4]. Not sure
if it handles hundreds of input files well enough.

> > And why do you want to
> > send it over tcp, if that's what TCPSource reads (not an avisynth
> > user)?
> 
> To avoid intermediate storage. Workspace for this project is 2TB.
> Each additional version of the project is currently ~700GB. Some form
> of inter-process communication is required to avoid intermediate
> storage. TCPSource() seems the only type of built-in IPC input
> Avisynth supports.

I don't know which data layout they expect in TCPSource and if it is in
any way compatible with the tcp output protocol in ffmpeg, or any other
protocol. I know this was your question in the first place but i can't
help you there. You could play around and just try to connect [1][2].

There's also some avisynth support in ffmpeg [3]. As i never used it i
don't know about its capabilities.

What are you doing after processing with avisynth? Do you pipe it back
into ffmpeg for encoding? Can't you use built-in filters [5] instead of
an avisynth script?


[1] http://avisynth.nl/index.php/TCPServer
[2] http://ffmpeg.org/ffmpeg-protocols.html#tcp
[3] http://www.ffmpeg.org/faq.html#How-can-I-read-DirectShow-files_003f
[4] http://trac.ffmpeg.org/wiki/Concatenate
[5] http://ffmpeg.org/ffmpeg-filters.html#Description
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Carl Eugen Hoyos]

Francois Visagie  gmail.com> writes:

> I hope to reach an expert familiar with both 
> ffmpeg and Avisynth!

I have never used avisynth and unfortunately cannot 
help you.

> I’m looking to perform some processing in ffmpeg, 
> and then to continue in Avisynth.

Which feature of Avisynth is missing in FFmpeg?

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] ffmpeg serving to Avisynth

[Frank Tetzel]

> I hope to reach an expert familiar with both ffmpeg and Avisynth! I’m
> looking to perform some processing in ffmpeg, and then to continue in
> Avisynth. For a number of reasons, including disk space, I’d like to
> avoid intermediate files. Which, if any, of the ffmpeg server
> protocols are compatible with Avisynth’s TCPSource() filter, i.e.

What processing do you want to do with ffmpeg? And why do you want
to send it over tcp, if that's what TCPSource reads (not an avisynth
user)? If it's just decoding then have a look at ffms2 [1]. It has an
avisynth plugin.

[1] https://github.com/FFMS/ffms2
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

[FFmpeg-user] ffmpeg serving to Avisynth

[Francois Visagie]

Hi,

 

I hope to reach an expert familiar with both ffmpeg and Avisynth! I’m
looking to perform some processing in ffmpeg, and then to continue in
Avisynth. For a number of reasons, including disk space, I’d like to avoid
intermediate files. Which, if any, of the ffmpeg server protocols are
compatible with Avisynth’s TCPSource() filter, i.e.

 

TCPSource (string hostname, int "port", string "compression")

Compression can be disabled.

 

If a suitable ffmpeg server protocol is available, please also indicate what
format to use.

 

Thanks,

François

 

François Visagie

 

 

T: +27 (83) 326-4358

F: +27 (86) 542-2133

E: francois.visa...@gmail.com

 

 

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user