[FFmpeg-user] slow encoding from raw rgb

[Daniel Oberhoff]

Hello,


So we are trying to encode raw rgb data from a pipe with ffmpeg. We
found that ffmpeg implicitly converts the data to tv range bt601, which
is suboptimal. Especially tv range loses more information than
neccessary, also bt709 seems to be the better color space.


We know we can fix this by adding -vf
scale=out_color_matrix=bt709:out_range=pc. Unfortuntately thi makes
encoding a lot slower (40 vs 60 fps) which effectively makes this
approach too slow for us. Do yiz have any idea why this is the case?


Best


Daniel

[Paul B Mahol]

Post by Daniel Oberhoff
Hello,
So we are trying to encode raw rgb data from a pipe with ffmpeg. We
found that ffmpeg implicitly converts the data to tv range bt601, which
is suboptimal. Especially tv range loses more information than
neccessary, also bt709 seems to be the better color space.
We know we can fix this by adding -vf
scale=out_color_matrix=bt709:out_range=pc. Unfortuntately thi makes
encoding a lot slower (40 vs 60 fps) which effectively makes this
approach too slow for us. Do yiz have any idea why this is the case?

That approach does not use slice threading.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-***@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-request

[Daniel Oberhoff]

Post by Paul B Mahol

Post by Daniel Oberhoff
Hello,
So we are trying to encode raw rgb data from a pipe with ffmpeg. We
found that ffmpeg implicitly converts the data to tv range bt601, which
is suboptimal. Especially tv range loses more information than
neccessary, also bt709 seems to be the better color space.
We know we can fix this by adding -vf
scale=out_color_matrix=bt709:out_range=pc. Unfortuntately thi makes
encoding a lot slower (40 vs 60 fps) which effectively makes this
approach too slow for us. Do yiz have any idea why this is the case?

That approach does not use slice threading.

So what is the suggested way to do this? Or should we just accept that
rgb encoding is either slow or suboptimal? Is this such a rare use-case?

Best


Daniel

[Paul B Mahol]

Post by Daniel Oberhoff

Post by Paul B Mahol

Post by Daniel Oberhoff
Hello,
So we are trying to encode raw rgb data from a pipe with ffmpeg. We
found that ffmpeg implicitly converts the data to tv range bt601, which
is suboptimal. Especially tv range loses more information than
neccessary, also bt709 seems to be the better color space.
We know we can fix this by adding -vf
scale=out_color_matrix=bt709:out_range=pc. Unfortuntately thi makes
encoding a lot slower (40 vs 60 fps) which effectively makes this
approach too slow for us. Do yiz have any idea why this is the case?

That approach does not use slice threading.

So what is the suggested way to do this? Or should we just accept that
rgb encoding is either slow or suboptimal? Is this such a rare use-case?

I suggest to raise bounty to further improve swscale library.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-***@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpe