Jérôme Martinez
Jérôme Martinez
Just some administrative stuff: even if [we don't move](https://github.com/FFmpeg/FFV1/issues/161) to [IETF CELLAR working group](https://github.com/ietf-wg-cellar), it may make more sense to mimic the names of the repositories, i.e. `ffv1-specification` for being...
This pull request expands FFV1 to provide lossless compression to additional pixel formats by adding floating-point values support, and permits the lossless encoding and decoding of the following FFmpeg currently...
Work in progress, I would like to be sure there is an agreement about the path to use before adapting more things (quant_table_set_index_count...) Since this is a new `colorspace_type` value,...
As we can add content at the end of `Parameters()` in version 3, we don't need to wait for version 4 for adding metadata not impacting the frame bitstream. I...
WebVTT and DivXTrickTrack are listed in the Matroska core doc. IMO an element should not be specific to a format, so the core doc should not contain such names, but...
Based on: - no rec date/time - synthetic gray video - silence (between -7 and 7)
As `BlockAddIDValue` of 4 may be interpreted as ITU T.35 without checking `BlockAddIDType` (reason we mandate `BlockAddIDValue` when `BlockAddIDType` is 4, right?), I suggest to recommend to avoid `BlockAddIDValue` of...
Checking both [RFC 5484](https://www.rfc-editor.org/rfc/rfc5484.html) and a copy of it in the Matroska doc on one side and SMPTE ST 12-1 on another side, I see that MKV and RFC 5484...
I try to understand the example in https://github.com/ietf-wg-cellar/matroska-specification/blob/master/block_additional_mappings/smpte-st12-1-timecode.md. I have split the example and manually decoded it, here is my outcome (lower case for units, upper case for tens, B...
Several container formats, e.g. MXF or QuickTime, don't have SMPTE ST 12 Timecode values per frame, they have a start time code and a frame rate, then other time codes...