Re: [FFmpeg-user] ffprobe timeout is not working
Am Sa., 19. Sept. 2020 um 19:14 Uhr schrieb gilmotta
:
>
> Hello Everybody,
>
> I'm afraid this is a recurring subject but -timeout and -stimeout is not
> working for me. I look at older posts but no luck.
>
> I tried seconds, milliseconds and micro seconds but no matter what I do
> ffprobe returns immediately when I type the command with -timeout or
> -stimeout
>
> /var/www/ffmpeg-4.3/ffprobe -timeout 3000 -v error -i
> rtmp://localhost/streams/stream1
> [rtmp @ 0x587f5c0] Cannot open connection
> tcp://localhost:1935?listen&listen_timeout=-64771072
> rtmp://localhost/fds/stream1: Address already in use
Complete, uncut console output missing.
Does the patch below (inlined) help?
Carl Eugen
diff --git a/libavformat/rtmpproto.c b/libavformat/rtmpproto.c
index d9741bc622..c4975097a0 100644
--- a/libavformat/rtmpproto.c
+++ b/libavformat/rtmpproto.c
@@ -120,7 +120,7 @@ typedef struct RTMPContext {
int nb_tracked_methods; ///< number of tracked methods
int tracked_methods_size; ///< size of the
tracked methods buffer
int listen; ///< listen mode flag
-int listen_timeout; ///< listen timeout to
wait for new connections
+uint64_t listen_timeout; ///< listen timeout to
wait for new connections
int nb_streamid;///< The next stream id
to return on createStream calls
doubleduration; ///< Duration of the
stream in seconds as returned by the server (only valid if non-zero)
char username[50];
@@ -2653,7 +2653,7 @@ static int rtmp_open(URLContext *s, const char
*uri, int flags, AVDictionary **o
port = RTMP_DEFAULT_PORT;
if (rt->listen)
ff_url_join(buf, sizeof(buf), "tcp", NULL, hostname, port,
-"?listen&listen_timeout=%d",
+"?listen&listen_timeout=%"PRId64,
rt->listen_timeout * 1000);
else
ff_url_join(buf, sizeof(buf), "tcp", NULL, hostname, port, NULL);
___
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] bwdif filter question
On 09/20/2020 05:44 PM, Carl Eugen Hoyos wrote:
Am So., 20. Sept. 2020 um 06:59 Uhr schrieb Mark Filipak (ffmpeg)
:
On 09/18/2020 03:01 PM, Carl Eugen Hoyos wrote:
Am 16.09.2020 um 15:58 schrieb Mark Himsley :
On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg) wrote:
Is the input to the bwdif filter fields or frames?
The input to every filter in a filter chain is a raster of pixels.
That raster may contain one frame or two fields.
That may not be wrong (apart from Paul’s comment) but I wonder how useful it is:
No matter if the raster contains one field, two interlaced fields or a
progressive
frame, the filter will always see an input frame.
"...if the raster contains *one field*...the filter will always see an input
*frame*."
How is that possible? How can a frame contain just one field?
The following makes little sense, it is just meant as an example:
$ ffmpeg -f lavfi -i testsrc2,field -vf bwdif -f null -
Here, the input to the bwdif consists of frames that contain one field
(of the original input).
Thanks, Carl Eugen. Kindly forgive my ignorance -- I can't read 'C' code and probably couldn't find
the relevant code section if my life depended on it.
If bwdif is the *only* filter, then, from previous discussions, I understand that its input (i.e.
the decoder's output) is raw frames (e.g. 720x576)? If raw frames, then I can understand the above
to mean that the filter is 'fed' only one field (e.g. 720x288). Logically, to me, that would be a
frame (i.e. a 720x288 frame), but no matter (let's forget that). However, even then, the filter is
receiving only one field. How can it 'deinterlace' a single field? I'm mystified. Does it line
double in such a circumstance? Or does it deinterlace the current single field with the next single
field one frame later?
The fact that there is metadata that may signal the content is also not
necessarily
helpful as this metadata is typically wrong (often signalling fields when a
frame is provided).
Can you provide an example (or a link to an example)? I've examined a
great number of DSM mpeg presentation streams ('VOB's & 'm2ts's) and
I've not seen a single case. What metadata are you looking at?
sequence_extension: 'progressive_sequence'?
picture_coding_extension: 'picture_structure'?
picture_coding_extension: 'top_field_first'?
picture_coding_extension: 'repeat_first_field'?
I would expect that most commercial encodings you have uses
one of the above, independently of the content...
Based on my experience, and to the best of my knowledge, every MPEG PS & TS have all 5 metadata
values. Certainly, every MPEG stream *I've* parsed have all 5.
picture_coding_extension: 'progressive_frame'?
... while this is unusual, even for movies in PAL streams.
For what it's worth, I have only one PAL movie, "The Man Who Would Be King", from Australia. It has
all 5 metadata values and appears to be a regular MPEG PS.
Regarding 'progressive_frame', ffmpeg has 'interlaced_frame' in lieu of 'progressive_frame'. I think
that 'interlaced_frame' = !'progressive_frame' but I'm not sure. Confirming it as a fact is a side
project that I work on only occasionally. H.242 defines "interlace" as solely the condition of PAL &
NTSC scan-fields (i.e. field period == (1/2)(1/FPS)), but I don't want to pursue that further
because I don't want to be perceived as a troll. :-)
- Mark.
___
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] bwdif filter question
Am So., 20. Sept. 2020 um 06:59 Uhr schrieb Mark Filipak (ffmpeg)
:
>
> On 09/18/2020 03:01 PM, Carl Eugen Hoyos wrote:
> >> Am 16.09.2020 um 15:58 schrieb Mark Himsley :
> >>> On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg)
> >>> wrote:
> >>> Is the input to the bwdif filter fields or frames?
> >> The input to every filter in a filter chain is a raster of pixels.
> >> That raster may contain one frame or two fields.
> >
> > That may not be wrong (apart from Paul’s comment) but I wonder how useful
> > it is:
> > No matter if the raster contains one field, two interlaced fields or a
> > progressive
> > frame, the filter will always see an input frame.
>
> "...if the raster contains *one field*...the filter will always see an input
> *frame*."
> How is that possible? How can a frame contain just one field?
The following makes little sense, it is just meant as an example:
$ ffmpeg -f lavfi -i testsrc2,field -vf bwdif -f null -
Here, the input to the bwdif consists of frames that contain one field
(of the original input).
> > The fact that there is metadata that may signal the content is also not
> > necessarily
> > helpful as this metadata is typically wrong (often signalling fields when a
> > frame is provided).
>
> Can you provide an example (or a link to an example)? I've examined a
> great number of DSM mpeg presentation streams ('VOB's & 'm2ts's) and
> I've not seen a single case. What metadata are you looking at?
> sequence_extension: 'progressive_sequence'?
> picture_coding_extension: 'picture_structure'?
> picture_coding_extension: 'top_field_first'?
> picture_coding_extension: 'repeat_first_field'?
I would expect that most commercial encodings you have uses
one of the above, independently of the content...
> picture_coding_extension: 'progressive_frame'?
... while this is unusual, even for movies in PAL streams.
Otoh, I typically saw pal dvb streams, maybe my claim is
only true for them.
Carl Eugen
___
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] Transcoding mpeg2video in mpegts to h264 in mpegts has fast playback
Am So., 20. Sept. 2020 um 03:13 Uhr schrieb Patrick Double : > > > On Sep 18, 2020, at 1:37 PM, Carl Eugen Hoyos wrote: > > > >> Am 18.09.2020 um 18:51 schrieb Pat Double : > >> > >> Here is my sample: > >> > >> https://www.dropbox.com/s/7s7itvj1uy2nov7/RobotMaker-short.ts > > > > Please provide an input sample, never provide output files unless > > specifically requested. > > This is an input sample. The file claims to be written by FFmpeg. You cannot put ass into mpegts. Your input file is NOT interlaced, it is telecined, use an inverse telecine filter. Every deinterlacer permanently damages your video, in theory an inverse telecine filter creates perfect output. Both pullup and fieldmatch seem to work ok for your sample. The following works and keeps the Closed Captions, it may not work correctly with the inverse telecine filter though: $ ffmpeg -i input -acodec copy -vcodec lib264 out.ts Carl Eugen ___ 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] Create a 10-bit VLog test video
Am 20.09.2020 um 15:19 schrieb Michael Koch: Am 19.09.2020 um 17:01 schrieb Paul B Mahol: On Sat, Sep 19, 2020 at 12:10 PM Michael Koch wrote: Hello all, I want to create a 10-bit VLog test video which contains 18 levels of gray, according to Panasonic's VLog curve. The curve is documented here: https://pro-av.panasonic.net/en/cinema_camera_varicam_eva/support/pdf/VARICAM_V-Log_V-Gamut.pdf I want the leftmost bar to be black (128) and the other 17 bars are for -8 to +8 stops, so that the rightmost bar is at level 1023. I'm using this command line and the console output is copied below: ffmpeg -f lavfi -i nullsrc=s=svga,format=gray16 -lavfi geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))' -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 5 -y VLog_10bit.mov The video looks perfect when played with FFplay. The leftmost bars are indistinguishable on a 8-bit monitor because the levels are too close together, but the rightmost bars look as expected. However when I play the same video with VLC, the two brightest bars at the right side have the same shade of gray. I don't understand why. Is this a problem in my video, or is it a problem in VLC? When I extraxt a 16-bit PNG image from the video, this looks as expected with 18 levels of gray. ffmpeg -i VLog_10bit.mov -frames 1 -y out.png Unrelated: I did try to add the oscilloscope filter at the end of the filter chain, but it seems it doesn't work with 16-bit data. There should be a warning or an error message. oscilloscope=tw=1:s=1 That happened only with gray>8 formats and have been fixed already. Thanks, oscilloscope works fine now. Do you have any idea why the brightest bar looks correct in FFplay and wrong in VLC? Is the problem reproducible on other computers? I've solved the problem. If "-color_range pc" is added to the command line, the video plays fine in FFplay and also in VLC. Michael ___ 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] how to convert *.cin into *.avi?
Here is the demo.cin example: https://www.dropbox.com/s/dta1swkn2ohl91l/demo.cin?dl=0 -Original Message- From: ffmpeg-user On Behalf Of Carl Eugen Hoyos Sent: Sunday, September 20, 2020 3:36 PM To: FFmpeg user questions Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi? > Am 20.09.2020 um 08:10 schrieb Reto Kromer : > > Paul B Mahol wrote: > >> FFmpeg currently does not have any support for Cineon (.cin file >> extension with magic bytes 0x802a5fd7 at start) at all. > > If you force their lecture as DPX, then in my experience you can use > them in FFmpeg. Could you provide such a sample? Carl Eugen ___ 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] how to convert *.cin into *.avi?
> Am 20.09.2020 um 08:10 schrieb Reto Kromer : > > Paul B Mahol wrote: > >> FFmpeg currently does not have any support for Cineon (.cin >> file extension with magic bytes 0x802a5fd7 at start) at all. > > If you force their lecture as DPX, then in my experience you can > use them in FFmpeg. Could you provide such a sample? Carl Eugen ___ 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] Create a 10-bit VLog test video
Am 19.09.2020 um 15:06 schrieb Mick Finn: Does vlc even support 10 bit playback on supported monitors? I have 10 bit calibrated monitor and don’t notice the same difference with vlc as with say resolve I don't have a 10-bit monitor. I'm assuming that FFplay or VLC do automatically convert 10-bit videos to 8-bit. The question is: Why do the two brightest bars look correct when played with FFplay, but wrong when played with VLC? Michael ___ 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] Create a 10-bit VLog test video
Am 19.09.2020 um 17:01 schrieb Paul B Mahol: On Sat, Sep 19, 2020 at 12:10 PM Michael Koch wrote: Hello all, I want to create a 10-bit VLog test video which contains 18 levels of gray, according to Panasonic's VLog curve. The curve is documented here: https://pro-av.panasonic.net/en/cinema_camera_varicam_eva/support/pdf/VARICAM_V-Log_V-Gamut.pdf I want the leftmost bar to be black (128) and the other 17 bars are for -8 to +8 stops, so that the rightmost bar is at level 1023. I'm using this command line and the console output is copied below: ffmpeg -f lavfi -i nullsrc=s=svga,format=gray16 -lavfi geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))' -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 5 -y VLog_10bit.mov The video looks perfect when played with FFplay. The leftmost bars are indistinguishable on a 8-bit monitor because the levels are too close together, but the rightmost bars look as expected. However when I play the same video with VLC, the two brightest bars at the right side have the same shade of gray. I don't understand why. Is this a problem in my video, or is it a problem in VLC? When I extraxt a 16-bit PNG image from the video, this looks as expected with 18 levels of gray. ffmpeg -i VLog_10bit.mov -frames 1 -y out.png Unrelated: I did try to add the oscilloscope filter at the end of the filter chain, but it seems it doesn't work with 16-bit data. There should be a warning or an error message. oscilloscope=tw=1:s=1 That happened only with gray>8 formats and have been fixed already. Thanks, oscilloscope works fine now. Do you have any idea why the brightest bar looks correct in FFplay and wrong in VLC? Is the problem reproducible on other computers? Michael ___ 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] how to convert *.cin into *.avi?
Thank you, Peter -Original Message- From: ffmpeg-user On Behalf Of Reto Kromer Sent: Sunday, September 20, 2020 2:14 PM To: FFmpeg user questions Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi? peter.lysyan...@gmail.com wrote: >Did you succeed to see any image from this file? This is a ULS scan of >the elbow of an arm. No, not the actual image. I could retrieve only a little shadows by using what I know about medical imaging. >What would you recommend instead of FFmpeg? I am afraid, I don't have any recommendation at all. This is a proprietary format which I don't know. It is *NOT* the Cineon (.cin) format used when the digital intermediate was introduced in movie film postproduction by Kodak. That's for sure. ___ 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] how to convert *.cin into *.avi?
peter.lysyan...@gmail.com wrote: >Did you succeed to see any image from this file? This is a ULS >scan of the elbow of an arm. No, not the actual image. I could retrieve only a little shadows by using what I know about medical imaging. >What would you recommend instead of FFmpeg? I am afraid, I don't have any recommendation at all. This is a proprietary format which I don't know. It is *NOT* the Cineon (.cin) format used when the digital intermediate was introduced in movie film postproduction by Kodak. That's for sure. ___ 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] how to convert *.cin into *.avi?
Did you succeed to see any image from this file? This is a ULS scan of the elbow of an arm. What would you recommend instead of FFmpeg? -Original Message- From: ffmpeg-user On Behalf Of Reto Kromer Sent: Sunday, September 20, 2020 1:02 PM To: FFmpeg user questions Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi? peter.lysyan...@gmail.com wrote: >Yes, this file is exported from SonoTouch ultrasound scanner. >Is there a chance to open this movie? Possibly. Yet, in my personal opinion, not with FFmpeg. (I probably misinterpreted as showing a liver cancer, therefore my question, but this device seems to be a much more elementar one.) ___ 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] how to convert *.cin into *.avi?
peter.lysyan...@gmail.com wrote: >Yes, this file is exported from SonoTouch ultrasound scanner. >Is there a chance to open this movie? Possibly. Yet, in my personal opinion, not with FFmpeg. (I probably misinterpreted as showing a liver cancer, therefore my question, but this device seems to be a much more elementar one.) ___ 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] how to convert *.cin into *.avi?
Jim, I understand your point. Unfortunately I don't know too much. Due to this, I have posted a link to the file in the hopes of helping extract the images. Peter -Original Message- From: ffmpeg-user On Behalf Of Jim DeLaHunt Sent: Sunday, September 20, 2020 11:41 AM To: ffmpeg-user@ffmpeg.org Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi? On 2020-09-19 01:24, peter.lysyan...@gmail.com wrote: > I was unable to use FFmpeg to convert the * .cin file to * .avi. On 2020-09-20 01:00, peter.lysyan...@gmail.com wrote: > Yes, this file is exported from SonoTouch ultrasound scanner. Is there a > chance to open this movie? Peter: For future reference, the next time you ask for help converting a file, you might find it helpful to volunteer in the first message the relevant information you have about the source file. The information that the file comes from a particular ultrasound scanner is very important. You only give this list just the filename extension (*.cin) and not what you know about the source. You might want to think about what else you know about this content, and its format, and its source. What else have you not yet shared? The more (relevant) information you give, the more likely it is that someone on the list will recognise the situation and offer an answer. Best regards, —Jim DeLaHunt ___ 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] how to convert *.cin into *.avi?
On 2020-09-19 01:24, peter.lysyan...@gmail.com wrote: I was unable to use FFmpeg to convert the * .cin file to * .avi. On 2020-09-20 01:00, peter.lysyan...@gmail.com wrote: Yes, this file is exported from SonoTouch ultrasound scanner. Is there a chance to open this movie? Peter: For future reference, the next time you ask for help converting a file, you might find it helpful to volunteer in the first message the relevant information you have about the source file. The information that the file comes from a particular ultrasound scanner is very important. You only give this list just the filename extension (*.cin) and not what you know about the source. You might want to think about what else you know about this content, and its format, and its source. What else have you not yet shared? The more (relevant) information you give, the more likely it is that someone on the list will recognise the situation and offer an answer. Best regards, —Jim DeLaHunt ___ 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] how to convert *.cin into *.avi?
Yes, this file is exported from SonoTouch ultrasound scanner. Is there a chance to open this movie? -Original Message- From: ffmpeg-user On Behalf Of Reto Kromer Sent: Sunday, September 20, 2020 9:40 AM To: FFmpeg user questions Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi? Paul B Mahol wrote: >> Below is the link to demo.cin file in my Dropbox: >> >> https://www.dropbox.com/s/dta1swkn2ohl91l/demo.cin?dl=0 > >This file is not Cineon for sure. I agree. Is this image any related to medical imaging? ___ 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".
