On 9/28/2016 8:26 PM, Michael Niedermayer wrote:
> On Wed, Sep 28, 2016 at 08:18:20PM -0300, James Almer wrote:
>> On 9/28/2016 8:09 PM, James Almer wrote:
>>> On 9/28/2016 7:35 PM, Michael Niedermayer wrote:
On Wed, Sep 28, 2016 at 07:23:37PM -0300, James Almer wrote:
> Numerical values
On Wed, Sep 28, 2016 at 08:18:20PM -0300, James Almer wrote:
> On 9/28/2016 8:09 PM, James Almer wrote:
> > On 9/28/2016 7:35 PM, Michael Niedermayer wrote:
> >> On Wed, Sep 28, 2016 at 07:23:37PM -0300, James Almer wrote:
> >>> Numerical values for channel layout can be confusing and unintuitive,
On 9/28/2016 8:09 PM, James Almer wrote:
> On 9/28/2016 7:35 PM, Michael Niedermayer wrote:
>> On Wed, Sep 28, 2016 at 07:23:37PM -0300, James Almer wrote:
>>> Numerical values for channel layout can be confusing and unintuitive,
>>> especially
>>> when no channel count is printed.
>>
>> doesnt
On 9/28/2016 7:35 PM, Michael Niedermayer wrote:
> On Wed, Sep 28, 2016 at 07:23:37PM -0300, James Almer wrote:
>> Numerical values for channel layout can be confusing and unintuitive,
>> especially
>> when no channel count is printed.
>
> doesnt this break the format in libavformat/hashenc.c
>
On Wed, Sep 28, 2016 at 07:23:37PM -0300, James Almer wrote:
> Numerical values for channel layout can be confusing and unintuitive,
> especially
> when no channel count is printed.
doesnt this break the format in libavformat/hashenc.c
for format_version=2 ?
[...]
--
Michael GnuPG
Numerical values for channel layout can be confusing and unintuitive, especially
when no channel count is printed.
Signed-off-by: James Almer
---
libavformat/framehash.c | 5 -
tests/ref/fate/8bps | 2 +-