On Tue, Nov 7, 2023 at 3:09 PM <markfilipak.i...@gmail.com> wrote: > On 11/7/23 08:39, Paul B Mahol wrote: > > On Tue, Nov 7, 2023 at 2:22 PM <markfilipak.i...@gmail.com> wrote: > > > >> On 11/7/23 06:55, Phil Rhodes via ffmpeg-user wrote: > >>> On Tuesday, 7 November 2023 at 11:48:24 GMT, < > >> markfilipak.i...@gmail.com> wrote: > >>> > >>>> I think it sets the color tags on the _input_ > >>> I'm not so sure ... > >> > >> I tried it. The saturation was still there. > >> > >> What exactly you tried? > > set ARGS=-map 0:v -map 0:a:1 -map 0:a:0 -vf > setparams=range=tv:color_primaries=smpte170m:color_trc=smpte170m:colorspace=smpte170m,separatefields,setdar=16/9 > > -c:v libx265 -x265-params crf=18 -c:a copy > ffmpeg -ss 10:37.846 -to 11:09.335 -i "%SOURCE%" %ARGS% "%TARGET%" > > It seems to me that if 'setparams' is marking tags in the SOURCE instead > of the encoder, it would > not be in '-vf' and would not require transcoding. It would be a '-bsf:v'. > So, I don't know what > 'setparams' does. Apparently nothing. >
That is a bug. Workaround is to use: -colorspace -color_range etc output options directly. > > _______________________________________________ > 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".