Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[USMAN AAMER]

Hi,

following is the output:

D:\new downloads\video dataset\30sec nature>ffmpeg -re -i v1.mp4 -c:v
libx265 -an -pix_fmt yuv420p -preset slow -crf 30 -rtsp_transport tcp -f
rtsp rtsp://localhost:554/live
ffmpeg version git-2020-08-31-4a11a6f Copyright (c) 2000-2020 the FFmpeg
developers
  built with gcc 10.2.1 (GCC) 20200805
  configuration: --enable-gpl --enable-version3 --enable-sdl2
--enable-fontconfig --enable-gnutls --enable-iconv --enable-libass
--enable-libdav1d --enable-libbluray --enable-libfreetype
--enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy
--enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame
--enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264
--enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma
--enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf
--enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa
--enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm
--enable-librav1e --enable-libsvtav1 --disable-w32threads --enable-libmfx
--enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va
--enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
--enable-libopenmpt --enable-amf
  libavutil  56. 58.100 / 56. 58.100
  libavcodec 58.101.101 / 58.101.101
  libavformat58. 51.101 / 58. 51.101
  libavdevice58. 11.101 / 58. 11.101
  libavfilter 7. 87.100 /  7. 87.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'v1.mp4':
  Metadata:
major_brand : mp42
minor_version   : 0
compatible_brands: isommp42
creation_time   : 2018-03-08T14:28:45.00Z
  Duration: 00:00:30.00, start: 0.00, bitrate: 1210 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv,
bt709), 1280x720 [SAR 1:1 DAR 16:9], 1080 kb/s, 29.97 fps, 29.97 tbr, 90k
tbn, 59.94 tbc (default)
Metadata:
  creation_time   : 2018-03-08T14:28:45.00Z
  handler_name: ISO Media file produced by Google Inc. Created on:
03/08/2018.
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz,
stereo, fltp, 125 kb/s (default)
Metadata:
  creation_time   : 2018-03-08T14:28:45.00Z
  handler_name: ISO Media file produced by Google Inc. Created on:
03/08/2018.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
Press [q] to stop, [?] for help
x265 [info]: HEVC encoder version 3.4+2-73ca1d7be377
x265 [info]: build info [Windows][GCC 10.2.1][64 bit] 8bit+10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX
FMA3 BMI2 AVX2
x265 [info]: Main profile, Level-3.1 (Main tier)
x265 [info]: Thread pool created using 4 threads
x265 [info]: Slices  : 1
x265 [info]: frame threads / pool features   : 2 / wpp(12 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3
x265 [info]: Keyframe min / max / scenecut / bias  : 25 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt: 25 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb   : 1 / 1 / 0
x265 [info]: References / ref-limit  cu / depth  : 4 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress: CRF-30.0 / 0.60
x265 [info]: tools: rect limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
x265 [info]: tools: rskip mode=1 signhide tmvp strong-intra-smoothing
lslices=4
x265 [info]: tools: deblock sao

and here CMD starts waiting and when I cancel the command using 'Ctrl + C'
it shows the following:

Could not write header for output file #0 (incorrect codec parameters ?):
Immediate exit requested
Error initializing output stream 0:0 --

encoded 0 frames
Exiting normally, received signal 2.

On Thu, Oct 29, 2020 at 9:20 PM Carl Zwanzig  wrote:

> On 10/29/2020 1:50 AM, USMAN AAMER wrote:
> > How can I resolve the issue?
>
> Start by posting the entire command output that fails.  (and remember not
> to
> top-post on this list)
>
> z!
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Zwanzig]

On 10/29/2020 1:50 AM, USMAN AAMER wrote:

How can I resolve the issue?


Start by posting the entire command output that fails.  (and remember not to 
top-post on this list)


z!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[USMAN AAMER]

Hi,
I am trying to stream videos with RTSP using the following command:

>ffmpeg -re -i v1.mp4 -c:v libx265 -an -preset slow -crf 30 -rtsp_transport
tcp -f rtsp rtsp://localhost:554/live.sdp

Streaming does not start and the following error occurred:
Could not write header for output file #0 (incorrect codec parameters ?):
Immediate exit requested
Error initializing output stream 0:0 --

How can I resolve the issue?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Reuben Martin]

On Thu, Jun 23, 2016 at 4:00 PM, juan carlos Rebate 
wrote:

> according to the standard, html5 the mp4 format is ideal for this purpose,
> many companies that previously used flash html5 technology now used in mp4
> format, so again I say that is because ffmpeg
>


You need to understand that live streaming video, and pre-encoded
play-on-demand video are very different things. mp4 is indeed great for
html5, but it is not streamed live. You can use mp4 for live streaming IF
THE VIDEO IS IN CHUNKED FORMAT. This means the video is chopped up into
small little mp4 files that are maybe a few seconds long each. You can't
just load this into an html5 video tag, you have to use the javascript
Media Source Extensions API in order to manage downloading and chaining all
these little mp4 chunks together into a continuous video feed. You can't
stream mp4 format in the same sense as RTP, MPEG-TS, or RTMP. MP4 files
require an "moov atom" that gives info about the file, including how long
it is. Well, you have no way to know how long it is till the video is
finished encoding, so you can't use it live. This is also why "web
optimized" mp4 files move the "moov atom" to the front of the file, so that
it is the first atom that is read when downloading an on-demand-video, so
that it can start decoding before the file is finished downloading.
Otherwise if has to download the whole thing before it can play it because
by default the moov atom is placed at the end of the file. Hopefully you
understand why the moov atom creates an problem with live video that is not
done encoding. The chunked videos get around this by the short little mp4
videos being self-contained with each including it's moov atom.

This is the second time I've told you about Media Source Extensions.
Seriously, do some reading.
https://www.smashingmagazine.com/2016/04/html5-media-source-extensions-bringing-production-video-web/

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

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-23 21:40 GMT+02:00 Phil Turmel :

> On 06/23/2016 11:31 AM, juan carlos Rebate wrote:
>
> > Does anyone know how I can do to write the header?
>
> You've been told over and over, pointing at the error messages, that mp4
> won't work for streaming.  It is *not* ffmpeg's problem.  MP4 needs
> information in it's header that isn't available until *after* encoding,
> which is why the encoder needs to *seek* back to the beginning of the
> output file to fill it in.  That's not possible with realtime streams.
> ffmpeg would need to look into the future and provide data describing
> frames that haven't yet been created by your camera to satisfy you.  Let
> us know when you've invented a time machine.
>
> You've received recommendations for other formats that don't require
> such a header and are therefore real-time streamable.  Pick one.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
according to the standard, html5 the mp4 format is ideal for this purpose,
many companies that previously used flash html5 technology now used in mp4
format, so again I say that is because ffmpeg
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Phil Turmel]

On 06/23/2016 11:31 AM, juan carlos Rebate wrote:

> Does anyone know how I can do to write the header?

You've been told over and over, pointing at the error messages, that mp4
won't work for streaming.  It is *not* ffmpeg's problem.  MP4 needs
information in it's header that isn't available until *after* encoding,
which is why the encoder needs to *seek* back to the beginning of the
output file to fill it in.  That's not possible with realtime streams.
ffmpeg would need to look into the future and provide data describing
frames that haven't yet been created by your camera to satisfy you.  Let
us know when you've invented a time machine.

You've received recommendations for other formats that don't require
such a header and are therefore real-time streamable.  Pick one.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-22 21:33 GMT+02:00 juan carlos Rebate :

>
>
> 2016-06-22 21:16 GMT+02:00 Cley Faye :
>
>> 2016-06-22 19:45 GMT+02:00 juan carlos Rebate :
>>
>> > the problem is in ffmpeg not know what else wants me to say, I have
>> > indicated the error, as I indicated all screen output with the error,
>> have
>> > not received any solution, if you want something specific let me know
>> >
>>
>> ​I, and other, pointed out that your command line was incorrect *and* that
>> your choice of codec/container was invalid for what you're trying to do.
>> Some provided *working* example.
>>
>> There is no detailed explanation on the error code because it spells out
>> what's wrong:
>> > [mp4 @ 028d5840] muxer does not support non seekable output
>> > Could not write header for output file #0 (incorrect codec parameters
>> ?):
>>
>> It plain say "mp4 muxer does not support non seekable output". If you
>> insist on using a container that "does NOT support NON SEEKABLE output"
>> with a *non seekable* output such as a stream obviously you'll keep
>> getting
>> an error.
>> What I learned is that if google don't give anything useful with an error
>> message, there is two possibilities: you've discovered a new problem, or
>> you're doing something wrong. Seeing that ffmpeg is used in that exact
>> scenario by a lot of people, well... I'm not saying there is no bug in
>> ffmpeg but "take input X, output to Y" is one of the feature that works
>> fine.
>>
>> Granted, I don't have the whole picture, but to fix what you posted in
>> this
>> thread, just changing the mp4 container to anything that support streaming
>> works fine, as said by others, as said by me, and as *showned* in a video.
>> I'm baffled why you keep saying "oh no there is no solution this program
>> is
>> clearly not working" when you've got many already.
>>
>> As far as I'm concerned, this thread is done: you've given a bogus
>> command,
>> you've got answers as to what was wrong with it, and a working example.
>> I'm
>> afraid there's nothing more that can be done by random people there.
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>
> then makes no sense to use ffmpeg, I tried to use flash and I can not do
> so, I tried to do it with webm and you can not do so
> Adobe has told me in an email that flash if it supports what I want using
> swf as container, but ffmpeg sends me the same error
>
I'm desperate, I have found that the order of commands does not matter, but
if I have come to the conclusion that there are two possibilities.
1 ffmpeg can not do what I need.
2 is missing some command syntax, I purchased a book which says that the order
of commands does not matter that the syntax is correct, I consulted with
adobe and tells me that flash can make streaming using RTMP protocol and
prococolo http, this book only has about streamin with webcam example thus
serves no purpose for me
Does anyone know how I can do to write the header?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-22 21:16 GMT+02:00 Cley Faye :

> 2016-06-22 19:45 GMT+02:00 juan carlos Rebate :
>
> > the problem is in ffmpeg not know what else wants me to say, I have
> > indicated the error, as I indicated all screen output with the error,
> have
> > not received any solution, if you want something specific let me know
> >
>
> ​I, and other, pointed out that your command line was incorrect *and* that
> your choice of codec/container was invalid for what you're trying to do.
> Some provided *working* example.
>
> There is no detailed explanation on the error code because it spells out
> what's wrong:
> > [mp4 @ 028d5840] muxer does not support non seekable output
> > Could not write header for output file #0 (incorrect codec parameters ?):
>
> It plain say "mp4 muxer does not support non seekable output". If you
> insist on using a container that "does NOT support NON SEEKABLE output"
> with a *non seekable* output such as a stream obviously you'll keep getting
> an error.
> What I learned is that if google don't give anything useful with an error
> message, there is two possibilities: you've discovered a new problem, or
> you're doing something wrong. Seeing that ffmpeg is used in that exact
> scenario by a lot of people, well... I'm not saying there is no bug in
> ffmpeg but "take input X, output to Y" is one of the feature that works
> fine.
>
> Granted, I don't have the whole picture, but to fix what you posted in this
> thread, just changing the mp4 container to anything that support streaming
> works fine, as said by others, as said by me, and as *showned* in a video.
> I'm baffled why you keep saying "oh no there is no solution this program is
> clearly not working" when you've got many already.
>
> As far as I'm concerned, this thread is done: you've given a bogus command,
> you've got answers as to what was wrong with it, and a working example. I'm
> afraid there's nothing more that can be done by random people there.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
then makes no sense to use ffmpeg, I tried to use flash and I can not do so,
I tried to do it with webm and you can not do so
Adobe has told me in an email that flash if it supports what I want using
swf as container, but ffmpeg sends me the same error
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-22 19:45 GMT+02:00 juan carlos Rebate :

> the problem is in ffmpeg not know what else wants me to say, I have
> indicated the error, as I indicated all screen output with the error, have
> not received any solution, if you want something specific let me know
>

​I, and other, pointed out that your command line was incorrect *and* that
your choice of codec/container was invalid for what you're trying to do.
Some provided *working* example.

There is no detailed explanation on the error code because it spells out
what's wrong:
> [mp4 @ 028d5840] muxer does not support non seekable output
> Could not write header for output file #0 (incorrect codec parameters ?):

It plain say "mp4 muxer does not support non seekable output". If you
insist on using a container that "does NOT support NON SEEKABLE output"
with a *non seekable* output such as a stream obviously you'll keep getting
an error.
What I learned is that if google don't give anything useful with an error
message, there is two possibilities: you've discovered a new problem, or
you're doing something wrong. Seeing that ffmpeg is used in that exact
scenario by a lot of people, well... I'm not saying there is no bug in
ffmpeg but "take input X, output to Y" is one of the feature that works
fine.

Granted, I don't have the whole picture, but to fix what you posted in this
thread, just changing the mp4 container to anything that support streaming
works fine, as said by others, as said by me, and as *showned* in a video.
I'm baffled why you keep saying "oh no there is no solution this program is
clearly not working" when you've got many already.

As far as I'm concerned, this thread is done: you've given a bogus command,
you've got answers as to what was wrong with it, and a working example. I'm
afraid there's nothing more that can be done by random people there.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-22 19:38 GMT+02:00 Cley Faye :

> 2016-06-22 18:36 GMT+02:00 juan carlos Rebate :
>
> > ¿I can send photos or capture video ?, so'll see that does not work
>
>
> Since you've been very uncooperative to *any* kind of help and always
> filled every replies with attacks toward ffmpeg, and since this command
> line have something like four arguments and you can't test it, I doubt
> you'll believe a video showing it simply work. Anyway, it took mere seconds
> to record, so here it is.
> ​
> https://www.youtube.com/watch?v=JLz-0zMqlhM
>
> Now, if you still believe that ffmpeg is completely unusable and can't do
> the simplest task despite every attempt to help you (and show you!) on this
> list (from people that have more patience than me), you'll have to wonder
> if the problem really lies in ffmpeg.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
the problem is in ffmpeg not know what else wants me to say, I have
indicated the error, as I indicated all screen output with the error, have
not received any solution, if you want something specific let me know
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-22 18:36 GMT+02:00 juan carlos Rebate :

> ¿I can send photos or capture video ?, so'll see that does not work


Since you've been very uncooperative to *any* kind of help and always
filled every replies with attacks toward ffmpeg, and since this command
line have something like four arguments and you can't test it, I doubt
you'll believe a video showing it simply work. Anyway, it took mere seconds
to record, so here it is.
​
https://www.youtube.com/watch?v=JLz-0zMqlhM

Now, if you still believe that ffmpeg is completely unusable and can't do
the simplest task despite every attempt to help you (and show you!) on this
list (from people that have more patience than me), you'll have to wonder
if the problem really lies in ffmpeg.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-22 18:13 GMT+02:00 Cley Faye :

> 2016-06-22 17:51 GMT+02:00 juan carlos Rebate :
>
> ​​
> > The same command line you provided, with matroska replacing mp4 works
> fine
> > ​ ​
> > for a standard input file:​
> > >ffmpeg -i lp_e1m3_a.mkv -f matroska -c:v mpeg4 -listen 1
> > ​ ​
> > http://0.0.0.0:80
>
>
> >
>
>
> >
> >
> with this command vlc can not see the flow when you try to connect gives
> the
> > error message I have indicated before, there is no way to make it work
>
>
> ​How do you try to connect with VLC? This command works fine with my
> version of ffmpeg, which is already quite old:
> > ffmpeg version N-78990-g689211d Copyright (c) 2000-2016 the FFmpeg
> developers
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
¿I can send photos or capture video ?, so'll see that does not work
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-22 17:51 GMT+02:00 juan carlos Rebate :

​​
> The same command line you provided, with matroska replacing mp4 works fine
> ​ ​
> for a standard input file:​
> >ffmpeg -i lp_e1m3_a.mkv -f matroska -c:v mpeg4 -listen 1
> ​ ​
> http://0.0.0.0:80


>


>
>
with this command vlc can not see the flow when you try to connect gives the
> error message I have indicated before, there is no way to make it work


​How do you try to connect with VLC? This command works fine with my
version of ffmpeg, which is already quite old:
> ffmpeg version N-78990-g689211d Copyright (c) 2000-2016 the FFmpeg
developers
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-22 4:08 GMT+02:00 Cley Faye :

> 2016-06-22 0:05 GMT+02:00 juan carlos Rebate :
>
> > I've tried all combinations for codecs mpeg4 libx264 also webm libvpx
> > with the same negative results
> >
>
> The same command line you provided, with matroska replacing mp4 works fine
> for a standard input file:​
> >ffmpeg -i lp_e1m3_a.mkv -f matroska -c:v mpeg4 -listen 1
> http://0.0.0.0:80
>
> ​Only differences here:
>  - I'm using an input file, as setting an rtp server just to test this is
> silly
>  - I'm not providing an address to listen from
>  - Using mp4 as a container gives the exact same error you have anyway
>
> Using the above command, I was able to see the stream from VLC with no
> issue.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
with this command vlc can not see the flow when you try to connect gives the
error message I have indicated before, there is no way to make it work
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-22 0:05 GMT+02:00 juan carlos Rebate :

> I've tried all combinations for codecs mpeg4 libx264 also webm libvpx
> with the same negative results
>

The same command line you provided, with matroska replacing mp4 works fine
for a standard input file:​
>ffmpeg -i lp_e1m3_a.mkv -f matroska -c:v mpeg4 -listen 1 http://0.0.0.0:80

​Only differences here:
 - I'm using an input file, as setting an rtp server just to test this is
silly
 - I'm not providing an address to listen from
 - Using mp4 as a container gives the exact same error you have anyway

Using the above command, I was able to see the stream from VLC with no
issue.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-21 23:54 GMT+02:00 Cley Faye :

> 2016-06-21 23:35 GMT+02:00 juan carlos Rebate :
>
> > Could not write header for output file #0 (incorrect codec parameters ?):
> > Invalid argument
>
>
> ​That's relatively clear to me. Have you tried *any* other combination of
> codec/containers? As far as I can tell, ffmpeg won't stream mp4 containers.
> Note that using network addresses does not mean "simply pipe the file on
> the socket"...
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
I've tried all combinations for codecs mpeg4 libx264 also webm libvpx
with the same negative results
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Lou]

On Tue, 21 Jun 2016 23:35:47 +0200
juan carlos Rebate  wrote:

> [mp4 @ 028811e0] muxer does not support non seekable output

The answer is in your console output.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-21 23:35 GMT+02:00 juan carlos Rebate :

> Could not write header for output file #0 (incorrect codec parameters ?):
> Invalid argument


​That's relatively clear to me. Have you tried *any* other combination of
codec/containers? As far as I can tell, ffmpeg won't stream mp4 containers.
Note that using network addresses does not mean "simply pipe the file on
the socket"...
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-21 21:43 GMT+02:00 juan carlos Rebate :

>
>
> 2016-06-21 21:27 GMT+02:00 Cley Faye :
>
>> 2016-06-21 21:06 GMT+02:00 juan carlos Rebate :
>>
>> > I keep looking but not quite find anything to help me solve the problem
>>
>>
>> ​> ffmpeg -y -i rtp://239.0.0.107:8208
>>
>>  -map 0 -f mp4 -c:v mpeg4 -listen 1
>> http://localhost:80  -multiple_requests 1 -seekable 1
>> -bufsize 200k -r 299
>> -re -b:v 982k​
>>
>> ​What was told in the previous message is that some of your arguments are
>> misplaced. In the quoted command line, everything after localhost:80 is
>> ignored because it is misplaced. Maybe fixing that first will help.​
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>
> that is not the reason, ffmpeg command ignores any order, there is no
> place to indicate how have correctamete
>
Now if you are inside, it is assumed that this is the right place but you
still see the same error,
>ffmpeg -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
http://192.168.1.41:80
ffmpeg version N-80117-gdac030d Copyright (c) 2000-2016 the FFmpeg
developers
  built with gcc 5.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig
--enable-frei0r --enable-gnutls --enable-iconv --enable-libass
--enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype
--enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug
--enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus
--enable-librtmp --enable-libschroedinger --enable-libsnappy
--enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame
--enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis
--enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264
--enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg
--enable-lzma --enable-decklink --enable-zlib
  libavutil  55. 24.100 / 55. 24.100
  libavcodec 57. 43.100 / 57. 43.100
  libavformat57. 37.101 / 57. 37.101
  libavdevice57.  0.101 / 57.  0.101
  libavfilter 6. 46.100 /  6. 46.100
  libswscale  4.  1.100 /  4.  1.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc54.  0.100 / 54.  0.100
[NULL @ 00913b20] non-existing SPS 0 referenced in buffering period
[NULL @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] decode_slice_header error
[h264 @ 00913b20] no frame!
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] non-existing SPS 0 referenced in buffering period
[h264 @ 00913b20] non-existing PPS 0 referenced
[h264 @ 00913b20] 

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-21 21:27 GMT+02:00 Cley Faye :

> 2016-06-21 21:06 GMT+02:00 juan carlos Rebate :
>
> > I keep looking but not quite find anything to help me solve the problem
>
>
> ​> ffmpeg -y -i rtp://239.0.0.107:8208
>
>  -map 0 -f mp4 -c:v mpeg4 -listen 1
> http://localhost:80  -multiple_requests 1 -seekable 1
> -bufsize 200k -r 299
> -re -b:v 982k​
>
> ​What was told in the previous message is that some of your arguments are
> misplaced. In the quoted command line, everything after localhost:80 is
> ignored because it is misplaced. Maybe fixing that first will help.​
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
that is not the reason, ffmpeg command ignores any order, there is no place to
indicate how have correctamete
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Cley Faye]

2016-06-21 21:06 GMT+02:00 juan carlos Rebate :

> I keep looking but not quite find anything to help me solve the problem


​> ffmpeg -y -i rtp://239.0.0.107:8208

 -map 0 -f mp4 -c:v mpeg4 -listen 1
http://localhost:80  -multiple_requests 1 -seekable 1
-bufsize 200k -r 299
-re -b:v 982k​

​What was told in the previous message is that some of your arguments are
misplaced. In the quoted command line, everything after localhost:80 is
ignored because it is misplaced. Maybe fixing that first will help.​
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

I keep looking but not quite find anything to help me solve the problem

2016-06-21 1:07 GMT+02:00 juan carlos Rebate :

>
>
> 2016-06-21 1:00 GMT+02:00 Phil Turmel :
>
>> Hi Juan,
>>
>> On 06/20/2016 06:15 PM, juan carlos Rebate wrote:
>>
>> >> ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
>> > http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r
>> 299
>> > -re -b:v 982k
>>
>> [trim /]
>>
>> > Trailing options were found on the commandline.
>>
>> You seem to have missed this.  The order of options matters.  The
>> general requirement is:
>>
>> ffmpeg in-options -i inputfile out-options outputfile
>>
>> { I know nothing about the rest of your problem, but this is documented. }
>>
>> Phil
>>
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>
> is so poorly documented request help in forums Tapoco are able to know
> because
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-21 1:00 GMT+02:00 Phil Turmel :

> Hi Juan,
>
> On 06/20/2016 06:15 PM, juan carlos Rebate wrote:
>
> >> ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
> > http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r
> 299
> > -re -b:v 982k
>
> [trim /]
>
> > Trailing options were found on the commandline.
>
> You seem to have missed this.  The order of options matters.  The
> general requirement is:
>
> ffmpeg in-options -i inputfile out-options outputfile
>
> { I know nothing about the rest of your problem, but this is documented. }
>
> Phil
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
is so poorly documented request help in forums Tapoco are able to know
because
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Phil Turmel]

Hi Juan,

On 06/20/2016 06:15 PM, juan carlos Rebate wrote:

>> ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
> http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r 299
> -re -b:v 982k

[trim /]

> Trailing options were found on the commandline.

You seem to have missed this.  The order of options matters.  The
general requirement is:

ffmpeg in-options -i inputfile out-options outputfile

{ I know nothing about the rest of your problem, but this is documented. }

Phil

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

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

2016-06-21 0:07 GMT+02:00 Kieran O Leary :

> Hi
> On 20 Jun 2016 10:41 p.m., "juan carlos Rebate" 
> wrote:
> >
> > in all results of google there is no page that explains how to resolve
> this
> > error, commands only explain but not the solution, nor is there
> > documentation solution
> >
>
> https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A_rd=cr
> >
> Sounds like the solution would depend on the combination of
> codec/container/settings? Can you post the full uncut console output?
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

>ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r 299
-re -b:v 982k
ffmpeg version N-80117-gdac030d Copyright (c) 2000-2016 the FFmpeg
developers
  built with gcc 5.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig
--enable-frei0r --enable-gnutls --enable-iconv --enable-libass
--enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype
--enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug
--enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus
--enable-librtmp --enable-libschroedinger --enable-libsnappy
--enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame
--enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis
--enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264
--enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg
--enable-lzma --enable-decklink --enable-zlib
  libavutil  55. 24.100 / 55. 24.100
  libavcodec 57. 43.100 / 57. 43.100
  libavformat57. 37.101 / 57. 37.101
  libavdevice57.  0.101 / 57.  0.101
  libavfilter 6. 46.100 /  6. 46.100
  libswscale  4.  1.100 /  4.  1.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc54.  0.100 / 54.  0.100
Trailing options were found on the commandline.
[NULL @ 02084460] non-existing SPS 0 referenced in buffering period
[NULL @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] non-existing SPS 0 referenced in buffering period
[h264 @ 02084460] non-existing PPS 0 referenced
[h264 @ 02084460] decode_slice_header error
[h264 @ 02084460] no frame!
[h264 @ 02084460] mmco: unref short failure
[h264 @ 02084460] Increasing reorder buffer to 2
[h264 @ 02084460] Increasing reorder 

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[Kieran O Leary]

Hi
On 20 Jun 2016 10:41 p.m., "juan carlos Rebate"  wrote:
>
> in all results of google there is no page that explains how to resolve
this
> error, commands only explain but not the solution, nor is there
> documentation solution
>
https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A_rd=cr
>
Sounds like the solution would depend on the combination of
codec/container/settings? Can you post the full uncut console output?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):

[juan carlos Rebate]

in all results of google there is no page that explains how to resolve this
error, commands only explain but not the solution, nor is there
documentation solution
https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A_rd=cr
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

On 26/07/15 11:27, Carl Eugen Hoyos wrote:
 MrNice wxcvbn2006 at iol.ie writes:
 
 I tried -ts abs then -ts mono2abs, (wallclock is the same as abs)

 Duration: N/A, start: 1437900701.356327
 Duration: N/A, start: 1437900702.504357
 
 This looks correct to me...
 
 Carl Eugen
 

But the error messages are still here:
Past duration 0.802895 too large
*** dropping frame 10 from stream 0 at ts 8
Cliping frame in rate conversion by


./ffmpeg -debug 1 -f pulse -ar 44100 -ac 2 -channel_layout stereo
-thread_queue_size 512 -i alsa_input.pci-_00_14.2.analog-stereo -f
v4l2 -ts mono2abs -channel 1 -pix_fmt yuyv422 -thread_queue_size 512 -i
/dev/video0 -c:v ffv1 -pix_fmt yuv422p -c:a pcm_s16le
/Store3/Test/t_`date +%Y%m%d_%H%M`.mkv
ffmpeg version N-73832-g736a386 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse --enable-gpl --enable-libx264
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 49.101 / 56. 49.101
  libavformat56. 40.101 / 56. 40.101
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 25.100 /  5. 25.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc53.  3.100 / 53.  3.100
 matched as AVOption 'debug' with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'pulse'.
Reading option '-ar' ... matched as option 'ar' (set audio sampling rate
(in Hz)) with argument '44100'.
Reading option '-ac' ... matched as option 'ac' (set number of audio
channels) with argument '2'.
Reading option '-channel_layout' ... matched as option 'channel_layout'
(set channel layout) with argument 'stereo'.
Reading option '-thread_queue_size' ... matched as option
'thread_queue_size' (set the maximum number of queued packets from the
demuxer) with argument '512'.
Reading option '-i' ... matched as input file with argument
'alsa_input.pci-_00_14.2.analog-stereo'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'v4l2'.
Reading option '-ts' ... matched as AVOption 'ts' with argument 'mono2abs'.
Reading option '-channel' ... matched as AVOption 'channel' with
argument '1'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel
format) with argument 'yuyv422'.
Reading option '-thread_queue_size' ... matched as option
'thread_queue_size' (set the maximum number of queued packets from the
demuxer) with argument '512'.
Reading option '-i' ... matched as input file with argument '/dev/video0'.
Reading option '-c:v' ... matched as option 'c' (codec name) with
argument 'ffv1'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel
format) with argument 'yuv422p'.
Reading option '-c:a' ... matched as option 'c' (codec name) with
argument 'pcm_s16le'.
Reading option '/Store3/Test/t_20150726_0953.mkv' ... matched as output
file.
Finished splitting the commandline.
Parsing a group of options: global .
Successfully parsed a group of options.
Parsing a group of options: input file
alsa_input.pci-_00_14.2.analog-stereo.
Applying option f (force format) with argument pulse.
Applying option ar (set audio sampling rate (in Hz)) with argument 44100.
Applying option ac (set number of audio channels) with argument 2.
Applying option channel_layout (set channel layout) with argument stereo.
Applying option thread_queue_size (set the maximum number of queued
packets from the demuxer) with argument 512.
Successfully parsed a group of options.
Opening an input file: alsa_input.pci-_00_14.2.analog-stereo.
[pulse @ 0x34d3200] All info found
Input #0, pulse, from 'alsa_input.pci-_00_14.2.analog-stereo':
  Duration: N/A, start: 1437900797.180740, bitrate: 1411 kb/s
Stream #0:0, 1, 1/100: Audio: pcm_s16le, 44100 Hz, stereo, s16,
1411 kb/s
Successfully opened the file.
Parsing a group of options: input file /dev/video0.
Applying option f (force format) with argument v4l2.
Applying option pix_fmt (set pixel format) with argument yuyv422.
Applying option thread_queue_size (set the maximum number of queued
packets from the demuxer) with argument 512.
Successfully parsed a group of options.
Opening an input file: /dev/video0.
[video4linux2,v4l2 @ 0x34ebfc0] fd:6 capabilities:85220001
[video4linux2,v4l2 @ 0x34ebfc0] Selecting input_channel: 1
[video4linux2,v4l2 @ 0x34ebfc0] Current input_channel: 1, input_name:
S-Video, input_std: ff
[video4linux2,v4l2 @ 0x34ebfc0] Querying the device for the current
frame size
[video4linux2,v4l2 @ 0x34ebfc0] Setting frame size to 720x576
[video4linux2,v4l2 @ 0x34ebfc0] The V4L2 driver is using the interlaced mode
[video4linux2,v4l2 @ 0x34ebfc0] Current standard: PAL, id: ff,
frameperiod: 1/25
[video4linux2,v4l2 @ 0x34ebfc0] Detected monotonic timestamps, converting
[video4linux2,v4l2 @ 0x34ebfc0] All info found
Input #1, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, start: 1437900798.315291, bitrate: 165888 kb/s
Stream #1:0, 1, 

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Eugen Hoyos]

MrNice wxcvbn2006 at iol.ie writes:

 I tried -ts abs then -ts mono2abs, (wallclock is the same as abs)
 
 Duration: N/A, start: 1437900701.356327
 Duration: N/A, start: 1437900702.504357

This looks correct to me...

Carl Eugen

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

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

On 25/07/15 16:21, Carl Eugen Hoyos wrote:
 MrNice wxcvbn2006 at iol.ie writes:
 
 Input #0, pulse, from 'alsa_input.pci-_00_14.2.analog-stereo':
   Duration: N/A, start: 1437724175.042321
 
 Input #1, video4linux2,v4l2, from '/dev/video0':
   Duration: N/A, start: 1349.084272
 
 This is a major issue, you may try options like 
 the following that may fix it:
 -ts abs
 -ts mono2abs
 
 -wallclock 0
 
 (And it is of course possible that this issue 
 disappears with alsa, I don't know...)
 
 
 Carl Eugen
 

Really I have no luck: For months I try to find fix for ffmpeg with
alsa, as I got statics in the audio. Ubuntu, Ubuntu studio, Mint,
Centos, Stella, Fedora, have the same issue (New OS install on a spare
HD for each of them).

This month, I found out that with pulse, audio is good. I was happy.

Now I have an error with Duration...
I tried -ts abs then -ts mono2abs, (wallclock is the same as abs)

Duration: N/A, start: 1437900701.356327
Duration: N/A, start: 1437900702.504357
...
Cliping frame in rate conversion by 0.08
Cliping frame in rate conversion by 0.199486
...
Past duration 0.600685 too large


I even tried -force_key_frames 00:00:00.000 (found in another forum),
same issue.
Same issue with alsa (+ statics)

So, I am a bit hopeless, and it's raining again outside. :-(
I am sorry, I don't want to take advantage of your kindness, Carl,
Moritz, but I'll need your help again.

So, what do you want I do?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Eugen Hoyos]

MrNice wxcvbn2006 at iol.ie writes:

 Input #0, pulse, from 'alsa_input.pci-_00_14.2.analog-stereo':
   Duration: N/A, start: 1437724175.042321

 Input #1, video4linux2,v4l2, from '/dev/video0':
   Duration: N/A, start: 1349.084272

This is a major issue, you may try options like 
the following that may fix it:
-ts abs
-ts mono2abs

-wallclock 0

(And it is of course possible that this issue 
disappears with alsa, I don't know...)


Carl Eugen

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

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

 0-
 The objective is to get lossless audio and video

 Just to make sure: Do you mean video and
 lossless audio?
 Yes of course. This was a short way (in a wrong order indeed) to say
 ...to get and keep the best Dazzle can provide without adding artefacts.
 
 1- I read the video stream with -pix_fmt yuyv422 then write with
 -pix_fmt yuv422p. No choice, as you wrote,
 “As said, you cannot use PIX_FMT_YUYV422 because no encoder supports it.”
 I think there is no lost but only a different way to organise. Do you agree?
 
 2- There are clipping and drops (Highlighted by ). I
 don't know why. Could you help?
 
 3- With libx264 are there some options I could add to improve the
 quality? (libx264 has a lot of options hard for me to understand)
 ___

@Carl

In another thread you wrote:

 I.e. either use a codec designed for lossless encoding
 such as HuffYUV, or use something like x264 with
 lossless settings.

 FFv1 should be superior in (nearly) every regard, for
 example you would need several different x264 libraries
 to support all possible colour spaces and they are not
 supported by Huffyuv at all.

 Carl Eugen


I am confused. What should be the best codec for my usage: FFV1, x264,
Huffyuv, other?
Could you tell me the good options for this codec?

JP

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

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Eugen Hoyos]

MrNice wxcvbn2006 at iol.ie writes:

 I am confused. What should be the best codec for 
 my usage: FFV1, x264, Huffyuv, other?

I believe I suggested -vcodec mpeg2video -mbd 2 -qscale 2 
and I didn't change my opinion;-)

ffv1 is lossless, mpeg2video is not and x264 is not 
lossless unless you tell it to be.

Both regarding quality and filesize, I would not suggest 
a lossless encoding from your low-quality source, but a 
high-quality lossy encoding.

(x264 of course allows smaller filesizes than mpeg2video 
for the same quality, so you can safely choose it instead.)

Carl Eugen

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

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

On 20/07/15 16:02, Carl Eugen Hoyos wrote:
 MrNice wxcvbn2006 at iol.ie writes:
 
 [video4linux2,v4l2  at  0x1d33fa0] Thread 
 message queue blocking; consider raising the 
 thread_queue_size option (current value: 8)
 
 Thread message queue blocking;
 What does this warning mean? 
 
 How to remove it?
 
 Are you sure that you read the message?
 
 The objective is to get lossless audio and video 
 
 Just to make sure: Do you mean video and 
 lossless audio?
 
 from what the Dazzle DVC100 provide.
 
 AFAIK, yuyv422 is better than yuv420p. I tried to 
 use yuyv422 but I have the error:
 Incompatible pixel format 'yuyv422' for codec 
 'mpeg4', auto-selecting format 'yuv420p'

 What is the codec I could use the get 422?
 
 -vcodec mpeg2video supports 4:2:2 subsampling.
 
 Is my ffmpeg command good to get the best quality?
 
 No, it is missing -qscale 2 -mbd 2
 (if you don't want to use libx264).
 
 Carl Eugen


 Thread message queue blocking;
 What does this warning mean?
With some trails, I found the limit at 20. On site forums, they set at
512 or 1024. So I try at 512 but I don't know the up limit. What do you
think?

 (if you don't want to use libx264).
I installed libx264.
So here my new command, unfortunately with errors.

**
./ffmpeg -debug 1 -f pulse -ar 44100 -ac 2 -channel_layout stereo
-thread_queue_size 512 -i alsa_input.pci-_00_14.2.analog-stereo -f
v4l2 -channel 1 -pix_fmt yuyv422 -thread_queue_size 512 -i /dev/video0
-c:v libx264 -pix_fmt yuv422p -c:a pcm_s16le /Store3/Test/t_`date
+%Y%m%d_%H%M`.mkv
ffmpeg version N-73832-g736a386 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse --enable-gpl --enable-libx264
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 49.101 / 56. 49.101
  libavformat56. 40.101 / 56. 40.101
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 25.100 /  5. 25.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc53.  3.100 / 53.  3.100
 matched as AVOption 'debug' with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'pulse'.
Reading option '-ar' ... matched as option 'ar' (set audio sampling rate
(in Hz)) with argument '44100'.
Reading option '-ac' ... matched as option 'ac' (set number of audio
channels) with argument '2'.
Reading option '-channel_layout' ... matched as option 'channel_layout'
(set channel layout) with argument 'stereo'.
Reading option '-thread_queue_size' ... matched as option
'thread_queue_size' (set the maximum number of queued packets from the
demuxer) with argument '512'.
Reading option '-i' ... matched as input file with argument
'alsa_input.pci-_00_14.2.analog-stereo'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'v4l2'.
Reading option '-channel' ... matched as AVOption 'channel' with
argument '1'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel
format) with argument 'yuyv422'.
Reading option '-thread_queue_size' ... matched as option
'thread_queue_size' (set the maximum number of queued packets from the
demuxer) with argument '512'.
Reading option '-i' ... matched as input file with argument '/dev/video0'.
Reading option '-c:v' ... matched as option 'c' (codec name) with
argument 'libx264'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel
format) with argument 'yuv422p'.
Reading option '-c:a' ... matched as option 'c' (codec name) with
argument 'pcm_s16le'.
Reading option '/Store3/Test/t_20150724_0849.mkv' ... matched as output
file.
Finished splitting the commandline.
Parsing a group of options: global .
Successfully parsed a group of options.
Parsing a group of options: input file
alsa_input.pci-_00_14.2.analog-stereo.
Applying option f (force format) with argument pulse.
Applying option ar (set audio sampling rate (in Hz)) with argument 44100.
Applying option ac (set number of audio channels) with argument 2.
Applying option channel_layout (set channel layout) with argument stereo.
Applying option thread_queue_size (set the maximum number of queued
packets from the demuxer) with argument 512.
Successfully parsed a group of options.
Opening an input file: alsa_input.pci-_00_14.2.analog-stereo.
[pulse @ 0x2db1200] All info found
Input #0, pulse, from 'alsa_input.pci-_00_14.2.analog-stereo':
  Duration: N/A, start: 1437724175.042321, bitrate: 1411 kb/s
Stream #0:0, 1, 1/100: Audio: pcm_s16le, 44100 Hz, stereo, s16,
1411 kb/s
Successfully opened the file.
Parsing a group of options: input file /dev/video0.
Applying option f (force format) with argument v4l2.
Applying option pix_fmt (set pixel format) with argument yuyv422.
Applying option thread_queue_size (set the maximum number of queued
packets from the demuxer) with argument 512.
Successfully parsed a group of options.
Opening an input file: 

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

On 19/07/15 19:59, Carl Eugen Hoyos wrote:
 ffmpeg -i /dev/video0 out.avi

Boot my desktop this morning and first try:

 ./ffmpeg -i /dev/video0 out.avi
ffmpeg version N-73517-g47d0773 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 47.100 / 56. 47.100
  libavformat56. 40.100 / 56. 40.100
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 21.100 /  5. 21.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.100 /  1.  2.100
Input #0, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, start: 2338.288325, bitrate: 165888 kb/s
Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 720x576,
165888 kb/s, 25 fps, 25 tbr, 1000k tbn, 1000k tbc
Output #0, avi, to 'out.avi':
  Metadata:
ISFT: Lavf56.40.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 720x576,
q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
  encoder : Lavc56.47.100 mpeg4
Stream mapping:
  Stream #0:0 - #0:0 (rawvideo (native) - mpeg4 (native))
Press [q] to stop, [?] for help
frame=  214 fps= 25 q=2.0 Lsize= 183kB time=00:00:08.56 bitrate=
175.4kbits/s
video:173kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
muxing overhead: 6.181012%
***

Record started, the file has no video (black screen), I think it's OK.
I tried with other recording commands to be sure but didn't change any
set-up then I did a second try:

 ./ffmpeg -i /dev/video0 out.avi
ffmpeg version N-73517-g47d0773 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 47.100 / 56. 47.100
  libavformat56. 40.100 / 56. 40.100
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 21.100 /  5. 21.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.100 /  1.  2.100
Input #0, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, bitrate: 165888 kb/s
Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 720x576,
165888 kb/s, 25 fps, 25 tbr, 1000k tbn, 1000k tbc
Output #0, avi, to 'out.avi':
  Metadata:
ISFT: Lavf56.40.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 720x576,
q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
  encoder : Lavc56.47.100 mpeg4
Stream mapping:
  Stream #0:0 - #0:0 (rawvideo (native) - mpeg4 (native))
Could not write header for output file #0 (incorrect codec parameters
?): Immediate exit requested
Exiting normally, received signal 2.
**

I tried few times I got the same error.
I don't know what has done the issue.
I reboot the desktop then try again.
Now no error. Any idea what has caused the issue? Where I could have a
look if it happen again?

So I try my original command and I have some questions at the very bottom:

 ./ffmpeg -debug 1 -f pulse -ar 44100 -ac 2 -channel_layout stereo -i
alsa_input.pci-_00_14.2.analog-stereo -f v4l2 -channel 1 -i
/dev/video0 -c:a copy /Store3/Test/t_`date +%Y%m%d_%H%M`.mkv
ffmpeg version N-73517-g47d0773 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 47.100 / 56. 47.100
  libavformat56. 40.100 / 56. 40.100
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 21.100 /  5. 21.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.100 /  1.  2.100
 matched as AVOption 'debug' with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'pulse'.
Reading option '-ar' ... matched as option 'ar' (set audio sampling rate
(in Hz)) with argument '44100'.
Reading option '-ac' ... matched as option 'ac' (set number of audio
channels) with argument '2'.
Reading option '-channel_layout' ... matched as option 'channel_layout'
(set channel layout) with argument 'stereo'.
Reading option '-i' ... matched as input file with argument
'alsa_input.pci-_00_14.2.analog-stereo'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'v4l2'.
Reading option '-channel' ... matched as AVOption 'channel' with
argument '1'.
Reading option '-i' ... matched as input file with argument '/dev/video0'.
Reading option '-c:a' ... matched as option 'c' (codec name) with
argument 'copy'.
Reading option '/Store3/Test/t_20150720_1419.mkv' ... matched as output
file.
Finished splitting the commandline.
Parsing a group of options: global .
Successfully parsed a group of options.
Parsing a group of options: input file
alsa_input.pci-_00_14.2.analog-stereo.
Applying option f (force format) with argument pulse.
Applying option ar (set 

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Eugen Hoyos]

MrNice wxcvbn2006 at iol.ie writes:

 [video4linux2,v4l2  at  0x1d33fa0] Thread 
 message queue blocking; consider raising the 
 thread_queue_size option (current value: 8)

 Thread message queue blocking;
 What does this warning mean? 

 How to remove it?

Are you sure that you read the message?

 The objective is to get lossless audio and video 

Just to make sure: Do you mean video and 
lossless audio?

 from what the Dazzle DVC100 provide.

 AFAIK, yuyv422 is better than yuv420p. I tried to 
 use yuyv422 but I have the error:
 Incompatible pixel format 'yuyv422' for codec 
 'mpeg4', auto-selecting format 'yuv420p'
 
 What is the codec I could use the get 422?

-vcodec mpeg2video supports 4:2:2 subsampling.

 Is my ffmpeg command good to get the best quality?

No, it is missing -qscale 2 -mbd 2
(if you don't want to use libx264).

Carl Eugen

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

Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[Carl Eugen Hoyos]

MrNice wxcvbn2006 at iol.ie writes:

 [video4linux2,v4l2  at  0x2770c40] interrupted

Please test the following:
$ ffmpeg -i /dev/video0 out.avi

 Moreover with alsa, this command was working few 
 months ago and not working now :

Then please run git bisect to find the change 
introducing the issue.

Carl Eugen

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

[FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?)

[MrNice]

Hello everybody,

I want to record audio and video from a analogue to digital converter
Pinnacle Dazzle DVC100.

Command :
 ./ffmpeg -debug 1 -f pulse -i alsa_input.pci-_00_14.2.analog-stereo
-f v4l2 -i /dev/video0 /Store3/Test/copy_`date +%m%d_%H%M`.avi
ffmpeg version N-73517-g47d0773 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4)
  configuration: --enable-libpulse
  libavutil  54. 28.100 / 54. 28.100
  libavcodec 56. 47.100 / 56. 47.100
  libavformat56. 40.100 / 56. 40.100
  libavdevice56.  4.100 / 56.  4.100
  libavfilter 5. 21.100 /  5. 21.100
  libswscale  3.  1.101 /  3.  1.101
  libswresample   1.  2.100 /  1.  2.100
 matched as AVOption 'debug' with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'pulse'.
Reading option '-i' ... matched as input file with argument
'alsa_input.pci-_00_14.2.analog-stereo'.
Reading option '-f' ... matched as option 'f' (force format) with
argument 'v4l2'.
Reading option '-i' ... matched as input file with argument '/dev/video0'.
Reading option '/Store3/Test/copy_0719_1905.avi' ... matched as output file.
Finished splitting the commandline.
Parsing a group of options: global .
Successfully parsed a group of options.
Parsing a group of options: input file
alsa_input.pci-_00_14.2.analog-stereo.
Applying option f (force format) with argument pulse.
Successfully parsed a group of options.
Opening an input file: alsa_input.pci-_00_14.2.analog-stereo.
[pulse @ 0x2757ba0] All info found
Guessed Channel Layout for  Input Stream #0.0 : stereo
Input #0, pulse, from 'alsa_input.pci-_00_14.2.analog-stereo':
  Duration: N/A, start: 1437329119.928277, bitrate: 1536 kb/s
Stream #0:0, 1, 1/100: Audio: pcm_s16le, 48000 Hz, 2 channels,
s16, 1536 kb/s
Successfully opened the file.
Parsing a group of options: input file /dev/video0.
Applying option f (force format) with argument v4l2.
Successfully parsed a group of options.
Opening an input file: /dev/video0.
[video4linux2,v4l2 @ 0x2770c40] fd:6 capabilities:85220001
[video4linux2,v4l2 @ 0x2770c40] Current input_channel: 1, input_name:
S-Video, input_std: ff
[video4linux2,v4l2 @ 0x2770c40] Querying the device for the current
frame size
[video4linux2,v4l2 @ 0x2770c40] Setting frame size to 720x576
[video4linux2,v4l2 @ 0x2770c40] Trying to set codec:rawvideo pix_fmt:yuv420p
Last message repeated 1 times
[video4linux2,v4l2 @ 0x2770c40] Trying to set codec:rawvideo pix_fmt:yuv422p
[video4linux2,v4l2 @ 0x2770c40] Trying to set codec:rawvideo pix_fmt:yuyv422
[video4linux2,v4l2 @ 0x2770c40] The V4L2 driver is using the interlaced mode
[video4linux2,v4l2 @ 0x2770c40] Current standard: PAL, id: ff,
frameperiod: 1/25
[video4linux2,v4l2 @ 0x2770c40] interrupted
Input #1, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, bitrate: 165888 kb/s
Stream #1:0, 0, 1/100: Video: rawvideo, 1 reference frame (YUY2
/ 0x32595559), yuyv422, 720x576 (0x0), 1/100, 165888 kb/s, 25 fps,
25 tbr, 1000k tbn, 1000k tbc
Successfully opened the file.
Parsing a group of options: output file /Store3/Test/copy_0719_1905.avi.
Successfully parsed a group of options.
Opening an output file: /Store3/Test/copy_0719_1905.avi.
Successfully opened the file.
detected 8 logical cores
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'video_size' to
value '720x576'
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'pix_fmt' to value '1'
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'time_base' to value
'1/100'
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'pixel_aspect' to
value '0/1'
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'sws_param' to value
'flags=2'
[graph 0 input from stream 1:0 @ 0x2743dc0] Setting 'frame_rate' to
value '25/1'
[graph 0 input from stream 1:0 @ 0x2743dc0] w:720 h:576 pixfmt:yuyv422
tb:1/100 fr:25/1 sar:0/1 sws_param:flags=2
[format @ 0x274df00] compat: called with args=[yuv420p]
[format @ 0x274df00] Setting 'pix_fmts' to value 'yuv420p'
[auto-inserted scaler 0 @ 0x27324c0] Setting 'flags' to value '0x4'
[auto-inserted scaler 0 @ 0x27324c0] w:iw h:ih flags:'0x4' interl:0
[format @ 0x274df00] auto-inserting filter 'auto-inserted scaler 0'
between the filter 'Parsed_null_0' and the filter 'format'
[AVFilterGraph @ 0x2739a40] query_formats: 4 queried, 2 merged, 1
already done, 0 delayed
[auto-inserted scaler 0 @ 0x27324c0] w:720 h:576 fmt:yuyv422 sar:0/1 -
w:720 h:576 fmt:yuv420p sar:0/1 flags:0x4
[graph 1 input from stream 0:0 @ 0x274d6e0] Setting 'time_base' to value
'1/48000'
[graph 1 input from stream 0:0 @ 0x274d6e0] Setting 'sample_rate' to
value '48000'
[graph 1 input from stream 0:0 @ 0x274d6e0] Setting 'sample_fmt' to
value 's16'
[graph 1 input from stream 0:0 @ 0x274d6e0] Setting 'channel_layout' to
value '0x3'
[graph 1 input from stream 0:0 @ 0x274d6e0] tb:1/48000 samplefmt:s16
samplerate:48000 chlayout:0x3
[audio format for output stream 0:1 @