Shit, sorry...I can see the replies now.
-steinar
fre. 16. des. 2022, 10:55 skrev Nicolas George :
> Steinar Apalnes (12022-12-16):
> > Did not get any response in the user list so trying here...
>
> Yes, you did.
>
> And even if you did not, that would not be an excus
me light on this.
Thanks,
Steinar Apalnes
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
tor. 25. aug. 2022 kl. 02:11 skrev Stephen Hutchinson :
> On 8/24/22 1:04 PM, Steinar Apalnes wrote:
> > tir. 8. feb. 2022 kl. 12:03 skrev Stephen Hutchinson :
> >
> >> * Field Order
> >> * Chroma Location
> >> * Color Transfer Characteristics
tir. 8. feb. 2022 kl. 12:03 skrev Stephen Hutchinson :
> * Field Order
> * Chroma Location
> * Color Transfer Characteristics
> * Color Range
> * Color Primaries
> * Matrix Coefficients
>
> The existing TFF/BFF detection is retained as a fallback for
> older versions of AviSynth that can't access
Hi,
It seems to be a bug (maybe by design) when trying to control how the
video/color ranges are treated in the "scale" filter.
Basically what I need to specify is that the range should NOT be converted
when input range == output range, for example:
in_range=pc:out_range=pc or
in_range=tv:out_range
Hi,
I tried posting a similar question to the ffmpeg user list but got no
response. So I'm trying my luck here now. The thing is I need to be able to
control how the sws dither behaves.
Using a build from master (26.06.2021) I would expect to see different
frame hash on the these two commands:
ff
> >
> > I used the devel list because I considered, and still consider this as
> > a bug, and not a user "how-to" question.
> >
>
> My general rule of thumb I use whenever someone asks if they should post in
> #ffmpeg or #ffmpeg-devel (irc) etc is to only ask on devel if you are
> specifically hack
> >>> Hi,
> >> > It looks like the -f concat options has a problem when mixingUNC paths in
> >> > the concat file and local concat file path in command line:
> >> >
> >> >
> >> > Concat file:
> >> >
> >> > ffconcat version 1.0
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400201.MXF'
> >
ample 3. 8.100 / 3. 8.100
> > libpostproc55. 8.100 / 55. 8.100
> > [concat @ 01fa3b087f80] Impossible to open
> > 'd:\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400201.MXF'
> > d:\temp\AA4002.mxf.concat: No such file or directory
> >
> >
..", which of course will not work. There's
nothing else wrong with the command or concat files cause if I change the
content of the concat file to the local representation of the
\\server\CanonXF share E: it works just fine. Same if the concat file is on
the \\s
Gyan Doshi :
> On 06-12-2018 02:26 PM, Steinar Apalnes wrote:
> > This patch adds the new "avcintra-flavor" to the -x264opts. The
> > avcintra-flavor option in x264 adds the possibility to create the Sony
> XAVC
> > flavor of avcintra. Default is Panasonic.
> &g
This patch adds the new "avcintra-flavor" to the -x264opts. The
avcintra-flavor option in x264 adds the possibility to create the Sony XAVC
flavor of avcintra. Default is Panasonic.
Tested OK.
-steinar
0001-add avcintra-flavor option.patch
Description: Binary data
__
12 matches
Mail list logo