Video colour issue

[dapper sonnet]

try pass yuva420p to -pix_fmt

[native harbor]

huh why

do you want to parse ffprobe output or change the actual video?

[dapper sonnet]

problem is that pix fmt is yuv420p(tv,progressive)

they just want progressive

[native harbor]

yep, so why are you putting an alpha channel in?

[dapper sonnet]

didn't realize

[native harbor]

this is a matter of colour range and not pixfmt as far as I'm aware

sorry that was to aetopia

[native harbor]

this is the actual question

what for? seems like a case of the xy problem (https://xyproblem.info)

well, but, why? the "tv" is just indicating it's limited colour range

[native harbor]

well, that's what you should've asked in the first place

Video colour issue

anyways, describe how the colours are weird (ideally 2 screenshots - source and video), and how you're processing the video and where in the stage the colours get weird

[native harbor]

Is that the file from the editor or the actual anime?

I assume it's the anime?

and the issue happens after exporting from the editor or after encoding?

[native harbor]

Could you run ffprobe on the editor output file?

[native harbor]

You'll have better luck using libx264 and converting to yuv420p (or yuv444p10le to preserve the rgb colour format, but since the source isn't rgb you'll be fine with yuv420p)

[native harbor]

Try -c:v ffv1 -t 5, output to mkv and see if the issue persists (without any pixfmt args)

(as a troubleshooting step)

[native harbor]

Send the entire command if possible

literally just ffmpeg -i input.avi -c:v ffv1 -t 1 out.mkv

[native harbor]

hmm?

yeah that's fine, but do the colours look like the edited output?

should be enough to compare

you can run ffmpeg -i video1 -i video2 -filter_complex "[0:v:0][1:v:0]ssim" -t 2 -f null - to see if they're actually identical or not

Are you comparing source with final output?

You need to compare editor output to final output

That just shouldn't happen, odd

Well, one easy fix is to export in H264 from your editor which should fix this

Leave it as is

Like handbrake? yes, nmkoder. But handbrake itself is quite far behind and has confusing options.

[native harbor]

it isn't possible and if it were, you'd only have the ability to "edit" at points where P-frames are and absolutely no replacement of anything

[native harbor]

nope, also, open a new thread for that issue

[native harbor]

again, your attempted solution vs your actual problem kind of deal