> On Nov 7, 2022, at 6:32 AM, Paul B Mahol wrote:
>
> On 11/7/22, Tobias Rapp wrote:
>>> On 07/11/2022 10:56, Paul B Mahol wrote:
>>> On 11/7/22, Tobias Rapp wrote:
Hi,
recently when testing I stumbled over the situation that a specific
10-bit YUV input file was encoded
On 07/11/2022 12:31, Paul B Mahol wrote:
On 11/7/22, Tobias Rapp wrote:
On 07/11/2022 10:56, Paul B Mahol wrote:
On 11/7/22, Tobias Rapp wrote:
Hi,
recently when testing I stumbled over the situation that a specific
10-bit YUV input file was encoded separately using two different
loss-less
On 11/7/22, Tobias Rapp wrote:
> On 07/11/2022 10:56, Paul B Mahol wrote:
>> On 11/7/22, Tobias Rapp wrote:
>>> Hi,
>>>
>>> recently when testing I stumbled over the situation that a specific
>>> 10-bit YUV input file was encoded separately using two different
>>> loss-less encoders V210 and FFV1
On 07/11/2022 10:56, Paul B Mahol wrote:
On 11/7/22, Tobias Rapp wrote:
Hi,
recently when testing I stumbled over the situation that a specific
10-bit YUV input file was encoded separately using two different
loss-less encoders V210 and FFV1. When comparing the FrameMD5 checksum
of both output
On 11/7/22, Tobias Rapp wrote:
> Hi,
>
> recently when testing I stumbled over the situation that a specific
> 10-bit YUV input file was encoded separately using two different
> loss-less encoders V210 and FFV1. When comparing the FrameMD5 checksum
> of both output files most of the checksums did
Hi,
recently when testing I stumbled over the situation that a specific
10-bit YUV input file was encoded separately using two different
loss-less encoders V210 and FFV1. When comparing the FrameMD5 checksum
of both output files most of the checksums did match, but some of them
where differen
