Re: [FFmpeg-user] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Carl Eugen Hoyos]

Am Mi., 11. Sept. 2019 um 14:08 Uhr schrieb Gyan :

>  ffmpeg -i input_file -i watermark.png -filter_complex 
> "[0]yadif=0:-1:1[v];[v][1]overlay"
> -c:v libx264 -pix_fmt yuv420p -c:a aac
> -metadata copyright=“blah” -metadata comment=“contact blah” 
> -report output_file
>
>
> The yadif filter will only deinterlace if the frame is marked as interlaced.

The metadata that marks frames as interlaced is typically wrong:
It will mark progressive frames as interlaced and the de-interlacer
will permanently damage the frames.

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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Reto Kromer]

digitensions via ffmpeg-user wrote:

>I was having issues with the ‘ and “ options,

In any case, do not use the typographically correct punctuation,
but do use ' and ".

Best regards, Reto

___
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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Gyan]

On 11-09-2019 06:52 PM, digitensions via ffmpeg-user wrote:

Gyan, I am pleased to read yadif only works if interlacing is sensed. I see it has 
an auto mode, but will it differentiate between upper and lower if sensed also? The 
"[0]yadif=0:-1:1[v];[v][1]overlay” suggestion seems to have worked. I was 
having issues with the ‘ and “ options, but it functions perfectly this way:


In my answer, it is set to auto-detect parity. Manual parity can be 
forced by changing the 2nd arg, so


yadif=0:0:1  for top-field first.
yadif=0:1:1  for bottom-field first.


Gyan

___
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] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

[Michael Kohne via ffmpeg-user]

On Tue, Mar 5, 2019 at 11:25 AM Carl Eugen Hoyos  wrote:

> 2019-03-05 16:45 GMT+01:00, Michael Kohne :
> > On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne 
> wrote:
> >
> >> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos 
> >> wrote:
> >>
> >>> 2019-02-21 15:24 GMT+01:00, Michael Kohne :
> >>> > ./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
> >>> > 192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100
> >>> -map 0
> >>> > -f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
> >>> > /data/vidtmp/out.txt 2>&1
> >>>
> >>> You do realize that by separating the command line
> >>> from the console output, you make it harder to
> >>> understand the issue?
> >>>
> >> I'll try to not do that in the future.
> >>
> >>
> >>> Does it work with "-re"?
> >>>
> >>> No, -re has no effect. Here's a run with -re set - same issue as the
> >> original run.
> >>
> >> 
> >
> > Given that -re didn't work, is there something else I should be doing to
> > try to understand this?
> > I'd prefer to not double my CPU usage by avoiding the 'tee' muxer.
> > I guess the first question is: Is this a bug in some way? Is it supposed
> to
> > do this for some reason that's unclear to me?
>
> The tee muxer is very special, I hoped that somebody
> else who has used (or better: implemented) it would comment.
>
> You could test the delay and adelay filter, I don't know the exact options
> out
> of my head but I am curious if they at least can delay the issue you see.
>
> Carl Eugen
>
>
Dredging up this question again - I have not had the time to play with the
delay and adelay filters, hopefully soon.

To refresh the memory, I'm trying to transcode a stream two to avi files by
using the tee muxer, and the errors are:
[avi @ 0x9873ba0] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 1104 >= 1104
[avi @ 0x987d2a0] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 1104 >= 1104

I got around the issue for the moment by simply double-encoding, but I want
to try to understand what's going on.

My question of the moment is:
Does the muxer (specifically the AVI muxer) push any kind of information
back upstream to the encoder?
Because if it does, then that might explain the problem - the tee muxer
might not be quite up to merging that info from two instances of the muxer,
and things go to hell from there.

Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
mhko...@moberg.com

-- 






Celebrating 20 Years

Transforming Neurocritical Care

Moberg 
Research, Inc.

224 S Maple Street, Ambler, PA 19002

24/7 Customer 
Support: 888.662.7246

www.moberg.com 


___
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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[digitensions via ffmpeg-user]

Gyan, Moritz, Kieran,

Thank you so much for the answers. The script is designed to take a mezzanine 
file of ProRes or H264 mov origin and allow trimming, deinterlacing (of just 
the mov, not the watermark), overlay of watermark png, and make copyright 
metadata additions for supply to clients as viewing copies for computer review 
etc.  Our archives have progressive and interlaced (upper and lower) mezzanine 
files reserved for supply to production houses etc, which aren’t appropriate to 
issue as viewing copies. Instead of keeping two sets of mezzanine files per 
digitised file - viewing and production supply - we’re looking to generate a 
script so that anyone can produce an mp4 on demand from one higher level 
mezzanine.

Gyan, I am pleased to read yadif only works if interlacing is sensed. I see it 
has an auto mode, but will it differentiate between upper and lower if sensed 
also? The "[0]yadif=0:-1:1[v];[v][1]overlay” suggestion seems to have worked. I 
was having issues with the ‘ and “ options, but it functions perfectly this way:

'-filter_complex', "[0]yadif=0:-1:1[v];[v][1]overlay”,

I need to test this more broadly when I get some more video samples, or 
generate some with FFmpeg.

Thanks Moritz for the reminder that I must take better notice of the failed 
approaches I’ve tried already. I always rush through things without doing this. 
I’ll make sure my next FFmpeg-user submission is better prepared :)

Awesome help, thank you!

Joanna



> On 11 Sep 2019, at 12:59, Gyan  wrote:
> 
> 
> 
> On 11-09-2019 04:48 PM, digitensions via ffmpeg-user wrote:
>> Hello!
>> 
>> Thanks for admitting me to FFmpeg-user, and thanks to all those who maintain 
>> this list. The information I’ve been receiving since joining is outstanding.
>> 
>> This is a bit of a basic question I fear, but searching online hasn’t 
>> helped.  I am just co-writing a Python script which uses subprocess calls to 
>> run an FFmpeg command. I’ve been try to combine a watermark overlay with a 
>> command that uses yadif.  As a command it would run like so:
>> 
>> ffmpeg -i input_file -i watermark.png -filter_complex overlay -c:v libx263 
>> -pix_fmt yuv420p -vf yadif -metadata copyright=“blah” -metadata 
>> comment=“contact blah” -c:a aaa -report output_file
>> 
>> For reference, the script is here: 
>> https://github.com/digitensions/MACEscripts/blob/master/main.py
>> 
>> My error message:
>> ffmpeg started on 2019-09-11 at 11:12:45
>> Report written to "ffmpeg-20190911-111245.log"
>> ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers
>>   built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
>>   configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3_1 --enable-shared 
>> --enable-pthreads --enable-version3 --enable-hardcoded-tables 
>> --enable-avresample --cc=clang 
>> --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include
>>  
>> -I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include/darwin'
>>  --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl 
>> --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus 
>> --enable-librubberband --enable-libsnappy --enable-libtesseract 
>> --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 
>> --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig 
>> --enable-libfreetype --enable-frei0r --enable-libass 
>> --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg 
>> --enable-librtmp --enable-libspeex --enable-videotoolbox --disable-libjack 
>> --disable-indev=jack --enable-libaom --enable-libsoxr
>>   libavutil  56. 22.100 / 56. 22.100
>>   libavcodec 58. 35.100 / 58. 35.100
>>   libavformat58. 20.100 / 58. 20.100
>>   libavdevice58.  5.100 / 58.  5.100
>>   libavfilter 7. 40.101 /  7. 40.101
>>   libavresample   4.  0.  0 /  4.  0.  0
>>   libswscale  5.  3.100 /  5.  3.100
>>   libswresample   3.  3.100 /  3.  3.100
>>   libpostproc55.  3.100 / 55.  3.100
>> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
>> '/Users/Joanna/Desktop/new(ScriptTest)/[Chimney].mov':
>>   Metadata:
>> major_brand : qt
>> minor_version   : 512
>> compatible_brands: qt
>> encoder : Lavf58.20.100
>>   Duration: 00:00:26.32, start: 0.00, bitrate: 163608 kb/s
>> Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le(tv, 
>> bt709, progressive), 1920x1080, 162452 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 
>> tbr, 12800 tbn, 12800 tbc (default)
>> Metadata:
>>   handler_name: VideoHandle

Re: [FFmpeg-user] V360 filter

[Paul B Mahol]

On 9/11/19, Michael Koch  wrote:
> Am 11.09.2019 um 14:23 schrieb Michael Koch:
>> Am 11.09.2019 um 13:13 schrieb Michael Koch:
>>> Paul,
>>>
> I think the field of view isn't correct in the stereographic output.
>
> Here is a script for making really nice test images, for measuring
> field
> of view:
 Well spotted, thanks, should be fixed.
>>>
>>> The field of view of the stereographic output isn't correct. Here are
>>> a few examples:
>>> set in command line / measured in output image
>>> 60° / 74°
>>> 120° / 135°
>>> 180° / 180°
>>> 240° / 212°
>>> 300° / 236°
>>> 360° / 274°
>>
>> Make this correction:
>>
>> new_fov = 180 * tan(fov/4)
>>
>> where fov the the field of view you get from the command line, and
>> fov_new is the value that you use for the filter.
>> You must exclude values too close to 360°, because 360° stereographic
>> projection is impossible.
>>
>
> P.S. of course fov must be converted to radians before using tan():
>
> new_fov = 180 * tan(fov * pi / 720)

Thanks, that cleared some stuff.
Should be fixed.

> 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".
___
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] V360 filter

[Michael Koch]

Am 11.09.2019 um 14:23 schrieb Michael Koch:

Am 11.09.2019 um 13:13 schrieb Michael Koch:

Paul,


I think the field of view isn't correct in the stereographic output.

Here is a script for making really nice test images, for measuring 
field

of view:

Well spotted, thanks, should be fixed.


The field of view of the stereographic output isn't correct. Here are 
a few examples:

set in command line / measured in output image
60° / 74°
120° / 135°
180° / 180°
240° / 212°
300° / 236°
360° / 274°


Make this correction:

new_fov = 180 * tan(fov/4)

where fov the the field of view you get from the command line, and 
fov_new is the value that you use for the filter.
You must exclude values too close to 360°, because 360° stereographic 
projection is impossible.




P.S. of course fov must be converted to radians before using tan():

new_fov = 180 * tan(fov * pi / 720)

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] V360 filter

[Michael Koch]

Am 11.09.2019 um 13:13 schrieb Michael Koch:

Paul,


I think the field of view isn't correct in the stereographic output.

Here is a script for making really nice test images, for measuring 
field

of view:

Well spotted, thanks, should be fixed.


The field of view of the stereographic output isn't correct. Here are 
a few examples:

set in command line / measured in output image
60° / 74°
120° / 135°
180° / 180°
240° / 212°
300° / 236°
360° / 274°


Make this correction:

new_fov = 180 * tan(fov/4)

where fov the the field of view you get from the command line, and 
fov_new is the value that you use for the filter.
You must exclude values too close to 360°, because 360° stereographic 
projection is impossible.


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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Gyan]

On 11-09-2019 04:48 PM, digitensions via ffmpeg-user wrote:

Hello!

Thanks for admitting me to FFmpeg-user, and thanks to all those who maintain 
this list. The information I’ve been receiving since joining is outstanding.

This is a bit of a basic question I fear, but searching online hasn’t helped.  
I am just co-writing a Python script which uses subprocess calls to run an 
FFmpeg command. I’ve been try to combine a watermark overlay with a command 
that uses yadif.  As a command it would run like so:

ffmpeg -i input_file -i watermark.png -filter_complex overlay -c:v libx263 
-pix_fmt yuv420p -vf yadif -metadata copyright=“blah” -metadata 
comment=“contact blah” -c:a aaa -report output_file

For reference, the script is here: 
https://github.com/digitensions/MACEscripts/blob/master/main.py

My error message:
ffmpeg started on 2019-09-11 at 11:12:45
Report written to "ffmpeg-20190911-111245.log"
ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers
   built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
   configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3_1 --enable-shared 
--enable-pthreads --enable-version3 --enable-hardcoded-tables 
--enable-avresample --cc=clang 
--host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include
 
-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include/darwin'
 --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom 
--enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband 
--enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvorbis 
--enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid 
--enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r 
--enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb 
--enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-videotoolbox 
--disable-libjack --disable-indev=jack --enable-libaom --enable-libsoxr
   libavutil  56. 22.100 / 56. 22.100
   libavcodec 58. 35.100 / 58. 35.100
   libavformat58. 20.100 / 58. 20.100
   libavdevice58.  5.100 / 58.  5.100
   libavfilter 7. 40.101 /  7. 40.101
   libavresample   4.  0.  0 /  4.  0.  0
   libswscale  5.  3.100 /  5.  3.100
   libswresample   3.  3.100 /  3.  3.100
   libpostproc55.  3.100 / 55.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
'/Users/Joanna/Desktop/new(ScriptTest)/[Chimney].mov':
   Metadata:
 major_brand : qt
 minor_version   : 512
 compatible_brands: qt
 encoder : Lavf58.20.100
   Duration: 00:00:26.32, start: 0.00, bitrate: 163608 kb/s
 Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le(tv, 
bt709, progressive), 1920x1080, 162452 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 
12800 tbn, 12800 tbc (default)
 Metadata:
   handler_name: VideoHandler
   encoder : Lavc58.35.100 prores_ks
   timecode: 01:00:00:00
 Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, mono, 
s32 (24 bit), 1152 kb/s (default)
 Metadata:
   handler_name: SoundHandler
 Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
 Metadata:
   handler_name: TimeCodeHandler
   timecode: 01:00:00:00
Input #1, png_pipe, from 
'/Users/Joanna/Desktop/new(ScriptTest)/bitc/venv/watermarks/FHD.png':
   Duration: N/A, bitrate: N/A
 Stream #1:0: Video: png, rgba(pc), 1920x1080 [SAR 2835:2835 DAR 16:9], 25 
tbr, 25 tbn, 25 tbc
Filtergraph 'yadif' was specified through the -vf/-af/-filter option for output 
stream 0:0, which is fed from a complex filtergraph.
-vf/-af/-filter and -filter_complex cannot be used together for the same stream.
(venv) Joanna:venv Joanna$

I’m aware my source is progressive, my only available test file at present. I 
tried a few options combining yadif with the -filter_complex and had no 
success, but I wonder if those more knowledgeable would have an effective work 
around, or could point me to one?


The deinterlacing should be performed before overlay within the same 
filtergraph, so


ffmpeg -i input_file -i watermark.png -filter_complex 
"[0]yadif=0:-1:1[v];[v][1]overlay"
   -c:v libx264 -pix_fmt yuv420p -c:a aac
   -metadata copyright=“blah” -metadata comment=“contact blah” -report 
output_file


The yadif filter will only deinterlace if the frame is marked as interlaced.


Gyan

___
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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Moritz Barsnick]

Hi Joanna,

On Wed, Sep 11, 2019 at 12:18:57 +0100, digitensions via ffmpeg-user wrote:
> Thanks for admitting me to FFmpeg-user, and thanks to all those who
> maintain this list. The information I’ve been receiving since joining
> is outstanding.

Thanks, welcome here.

> ffmpeg -i input_file -i watermark.png -filter_complex overlay -c:v libx263 
> -pix_fmt yuv420p -vf yadif -metadata copyright=“blah” -metadata 
> comment=“contact blah” -c:a aaa -report output_file

What's the intent? To first do an overlay, then to deinterlace? You
need to specify your intent correctly (to yourself and use ;-)) first,
before designing your command (and for helping us assist you with it).

Assuming your watermark.png isn't interlaced, you probably want to
deinterlace the input_file first, then overlay a watermark, correct?

> For reference, the script is here: 
> https://github.com/digitensions/MACEscripts/blob/master/main.py

Probably not necessary, you actually provided all the relevant
information. ("Media Archive for Central England" sounds important.
;-))

> Filtergraph 'yadif' was specified through the -vf/-af/-filter option for 
> output stream 0:0, which is fed from a complex filtergraph.
> -vf/-af/-filter and -filter_complex cannot be used together for the same 
> stream.

This message is pretty clear. You need to use one or the other, and
combine your filters to so-called chains. There's some explanation
here:

https://ffmpeg.org/ffmpeg-filters.html#Filtergraph-syntax-1

but probably even better in ffmpeg's wiki.

Anyway, I suggest the following:

$ ffmpeg -i input_file -i watermark.png -filter_complex "[0:v]yadif[deint]; 
[deint][1:v]overlay[out]" -map "[out]" -map 0:a [...]
(untested)

Note how the input can be named, as well as the outputs of each chain.
My syntax here is two separate "chains" (with only one filter each),
which are assembled with "[]" inputs and outputs, and separated by ";".
Within each filter chain, you can connect one filter's output with the
next filter's input with a ",", e.g.

  -filter_complex "[0:v]yadif,scale=w=iw/2:h=-2[out]"

or

  -vf "yadif,scale=w=iw/2:h=-2"

(Just as a syntax example, not for your use case.)

> combining yadif with the -filter_complex and had no success

It's often helpful to also point out what else you tried and what the
result was (and what you were expecting), but my hints should help you
forward.

> The alternative is to write an if statement that checks for
> interlacing and activates the yadif call separately, which I’m happy
> to attempt if needed.

That's a different topic, deinterlacing conditionally.

Cheers,
Moritz
___
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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[Kieran O Leary]

Hi

On Wed, 11 Sep 2019, 12:27 digitensions via ffmpeg-user, <
ffmpeg-user@ffmpeg.org> wrote:

> Hello!
>
> Thanks for admitting me to FFmpeg-user, and thanks to all those who
> maintain this list. The information I’ve been receiving since joining is
> outstanding.
>
> This is a bit of a basic question I fear, but searching online hasn’t
> helped.  I am just co-writing a Python script which uses subprocess calls
> to run an FFmpeg command. I’ve been try to combine a watermark overlay with
> a command that uses yadif.  As a command it would run like so:
>
> ffmpeg -i input_file -i watermark.png -filter_complex overlay -c:v libx263
> -pix_fmt yuv420p -vf yadif -metadata copyright=“blah” -metadata
> comment=“contact blah” -c:a aaa -report output_file


> For reference, the script is here:
> https://github.com/digitensions/MACEscripts/blob/master/main.py
>
> My error message:
> ffmpeg started on 2019-09-11 at 11:12:45
> Report written to "ffmpeg-20190911-111245.log"
> ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers
>   built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
>   configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3_1 --enable-shared
> --enable-pthreads --enable-version3 --enable-hardcoded-tables
> --enable-avresample --cc=clang
> --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include
> -I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include/darwin'
> --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl
> --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus
> --enable-librubberband --enable-libsnappy --enable-libtesseract
> --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264
> --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig
> --enable-libfreetype --enable-frei0r --enable-libass
> --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg
> --enable-librtmp --enable-libspeex --enable-videotoolbox --disable-libjack
> --disable-indev=jack --enable-libaom --enable-libsoxr
>   libavutil  56. 22.100 / 56. 22.100
>   libavcodec 58. 35.100 / 58. 35.100
>   libavformat58. 20.100 / 58. 20.100
>   libavdevice58.  5.100 / 58.  5.100
>   libavfilter 7. 40.101 /  7. 40.101
>   libavresample   4.  0.  0 /  4.  0.  0
>   libswscale  5.  3.100 /  5.  3.100
>   libswresample   3.  3.100 /  3.  3.100
>   libpostproc55.  3.100 / 55.  3.100
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from
> '/Users/Joanna/Desktop/new(ScriptTest)/[Chimney].mov':
>   Metadata:
> major_brand : qt
> minor_version   : 512
> compatible_brands: qt
> encoder : Lavf58.20.100
>   Duration: 00:00:26.32, start: 0.00, bitrate: 163608 kb/s
> Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le(tv,
> bt709, progressive), 1920x1080, 162452 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25
> tbr, 12800 tbn, 12800 tbc (default)
> Metadata:
>   handler_name: VideoHandler
>   encoder : Lavc58.35.100 prores_ks
>   timecode: 01:00:00:00
> Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz,
> mono, s32 (24 bit), 1152 kb/s (default)
> Metadata:
>   handler_name: SoundHandler
> Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
> Metadata:
>   handler_name: TimeCodeHandler
>   timecode: 01:00:00:00
> Input #1, png_pipe, from
> '/Users/Joanna/Desktop/new(ScriptTest)/bitc/venv/watermarks/FHD.png':
>   Duration: N/A, bitrate: N/A
> Stream #1:0: Video: png, rgba(pc), 1920x1080 [SAR 2835:2835 DAR 16:9],
> 25 tbr, 25 tbn, 25 tbc
> Filtergraph 'yadif' was specified through the -vf/-af/-filter option for
> output stream 0:0, which is fed from a complex filtergraph.
> -vf/-af/-filter and -filter_complex cannot be used together for the same
> stream.
> (venv) Joanna:venv Joanna$
>
> I’m aware my source is progressive, my only available test file at
> present. I tried a few options combining yadif with the -filter_complex and
> had no success, but I wonder if those more knowledgeable would have an
> effective work around, or could point me to one?
>
> The alternative is to write an if statement that checks for interlacing
> and activates the yadif call separately, which I’m happy to attempt if
> needed.
>
> Any advice gratefully received.
>

You can chain multiple filters with commas, so -filter_complex
overlay,yadif should work?

Best,

Kieran O'Leary
___
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] Resolving -filter_complex overlay / -vf yadif conflicts in subprocess call Python script

[digitensions via ffmpeg-user]

Hello!

Thanks for admitting me to FFmpeg-user, and thanks to all those who maintain 
this list. The information I’ve been receiving since joining is outstanding.

This is a bit of a basic question I fear, but searching online hasn’t helped.  
I am just co-writing a Python script which uses subprocess calls to run an 
FFmpeg command. I’ve been try to combine a watermark overlay with a command 
that uses yadif.  As a command it would run like so:

ffmpeg -i input_file -i watermark.png -filter_complex overlay -c:v libx263 
-pix_fmt yuv420p -vf yadif -metadata copyright=“blah” -metadata 
comment=“contact blah” -c:a aaa -report output_file

For reference, the script is here: 
https://github.com/digitensions/MACEscripts/blob/master/main.py

My error message:
ffmpeg started on 2019-09-11 at 11:12:45
Report written to "ffmpeg-20190911-111245.log"
ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers
  built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3_1 --enable-shared 
--enable-pthreads --enable-version3 --enable-hardcoded-tables 
--enable-avresample --cc=clang 
--host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include
 
-I/Library/Java/JavaVirtualMachines/adoptopenjdk-11.0.2.jdk/Contents/Home/include/darwin'
 --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom 
--enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband 
--enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvorbis 
--enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid 
--enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r 
--enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb 
--enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-videotoolbox 
--disable-libjack --disable-indev=jack --enable-libaom --enable-libsoxr
  libavutil  56. 22.100 / 56. 22.100
  libavcodec 58. 35.100 / 58. 35.100
  libavformat58. 20.100 / 58. 20.100
  libavdevice58.  5.100 / 58.  5.100
  libavfilter 7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale  5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc55.  3.100 / 55.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
'/Users/Joanna/Desktop/new(ScriptTest)/[Chimney].mov':
  Metadata:
major_brand : qt  
minor_version   : 512
compatible_brands: qt  
encoder : Lavf58.20.100
  Duration: 00:00:26.32, start: 0.00, bitrate: 163608 kb/s
Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le(tv, bt709, 
progressive), 1920x1080, 162452 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 12800 
tbn, 12800 tbc (default)
Metadata:
  handler_name: VideoHandler
  encoder : Lavc58.35.100 prores_ks
  timecode: 01:00:00:00
Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, mono, s32 
(24 bit), 1152 kb/s (default)
Metadata:
  handler_name: SoundHandler
Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
Metadata:
  handler_name: TimeCodeHandler
  timecode: 01:00:00:00
Input #1, png_pipe, from 
'/Users/Joanna/Desktop/new(ScriptTest)/bitc/venv/watermarks/FHD.png':
  Duration: N/A, bitrate: N/A
Stream #1:0: Video: png, rgba(pc), 1920x1080 [SAR 2835:2835 DAR 16:9], 25 
tbr, 25 tbn, 25 tbc
Filtergraph 'yadif' was specified through the -vf/-af/-filter option for output 
stream 0:0, which is fed from a complex filtergraph.
-vf/-af/-filter and -filter_complex cannot be used together for the same stream.
(venv) Joanna:venv Joanna$ 

I’m aware my source is progressive, my only available test file at present. I 
tried a few options combining yadif with the -filter_complex and had no 
success, but I wonder if those more knowledgeable would have an effective work 
around, or could point me to one?

The alternative is to write an if statement that checks for interlacing and 
activates the yadif call separately, which I’m happy to attempt if needed.

Any advice gratefully received.

Joanna White

___
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] V360 filter

[Michael Koch]

Paul,


I think the field of view isn't correct in the stereographic output.

Here is a script for making really nice test images, for measuring field
of view:

Well spotted, thanks, should be fixed.


The field of view of the stereographic output isn't correct. Here are a 
few examples:

set in command line / measured in output image
60° / 74°
120° / 135°
180° / 180°
240° / 212°
300° / 236°
360° / 274°

Vertical field of view is limited to 180°, which makes "little planet" 
impossible..


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".