On 2/7/2025 5:39 PM, James Almer wrote:
> The existing code should be able
> to handle 10bit streams for both base and second layers
Thank you, James! I just went through verification with a 10bit encoded
MV-HEVC and it seems to be decoding as expected. I compared the ffmpeg
decoded with the HTM
On Fri, Feb 7, 2025 at 5:52 PM Vittorio Giovara
wrote:
> As far as I know, 10bit bitdepth is not specified in the MV profile for
> HEVC, therefore, any 10 bit support would be out of standard.
Thanks for the reply. You are right that the initial versions of the
standard did not specify a 10bit
Hello, is there any plan to add 10bit support to MV-HEVC decoding?
Thank you
Danny Hong
___
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
Quoting Anton Khirnov (2024-09-14 11:01:27)
> It is, but mainly as a testing/development aid, I do not expect it to be
> generally useful. Or is there a particular reason you need to
> interleave the views into one stream?
Understood. Since we can extract both views synchronized with the view
spe
Quoting James Almer (2024-09-13 22:57:44)
> It's probably not misplaced but mistagged as nuh_layer_id == 0 when it
> should be 1 (Can SEI NALUs be in anything other than the base layer?).
> The SEI is User Data Unregistered, and its contents are different than
> the one preceding the base layer VCL
Quoting James Almer (2024-09-13 22:19:35)
> Are you talking about decoding the resulting raw bitstream created from
> doing stream copy from the source mov? If so, what's happening is
> probably that the parser is splitting AUs when the second SEI with
> layer_id == 0 shows up in those non-conforma
Quoting Anton Khirnov (2024-09-13 12:44:55)
> Note that -view_ids is a decoder option and does nothing with
> streamcopy.
> Also, that option is intended for API users, with ffmpeg CLI you should
> be using view specifiers instead.
Thanks! Tried with "-map 0:v:view:all" and the result is the sam
Thanks for the patch set! Ran some initial tests and here are some
findings:
1. Tested using the HTM ref SW encoded bitstreams; the HTM encoded 2 layer
MV-HEVC elementary streams are decoded by both the HTM decoder and ffmpeg,
and both resulted in the same decoded pixels for both views.
2. Teste
Quoting Anton Khirnov (2024-08-16 09:32:28)
> The way this will work is that different views will be output by decoder
> as separate frames with side data indicating their view ID.
Thanks for the info again! Wouldn't it be easier for the user/consumer of
the decoded frames to simply have the sid
Quoting Anton Khirnov (2024-08-15 19:36:47)
> Yes, it should be submitted to ML within a few months.
Thank you for the info! This is great! We have experience with HEVC
implementation and also with the layered use case. If there is anything we
can help out with the development please let us kn
has been recently added.
Thank you
Danny Hong
___
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".
11 matches
Mail list logo
