Sep 25, 2022, 23:17 by andreas.rheinha...@outlook.com:
> Lynne:
>
>> Sep 25, 2022, 14:34 by andreas.rheinha...@outlook.com:
>>
>>> Lynne:
>>>
Sep 24, 2022, 23:57 by d...@lynne.ee:
> Sep 24, 2022, 21:40 by mar...@martin.st:
>
>> What about ac3dsp then - that one seems like it'
Lynne:
> Sep 25, 2022, 14:34 by andreas.rheinha...@outlook.com:
>
>> Lynne:
>>
>>> Sep 24, 2022, 23:57 by d...@lynne.ee:
>>>
Sep 24, 2022, 21:40 by mar...@martin.st:
> What about ac3dsp then - that one seems like it's fairly optimized for
> arm?
>
Haven't touched them,
Sep 25, 2022, 14:34 by andreas.rheinha...@outlook.com:
> Lynne:
>
>> Sep 24, 2022, 23:57 by d...@lynne.ee:
>>
>>> Sep 24, 2022, 21:40 by mar...@martin.st:
>>>
What about ac3dsp then - that one seems like it's fairly optimized for arm?
>>> Haven't touched them, they're still being used. U
Sep 25, 2022, 21:55 by mar...@martin.st:
> On Sat, 24 Sep 2022, Lynne wrote:
>
>>> What about ac3dsp then - that one seems like it's fairly optimized for arm?
>>>
>>
>> Haven't touched them, they're still being used. Unfortunately, for AC3,
>> the full MDCT optimizations in lavc do make a differen
On Sat, 24 Sep 2022, Lynne wrote:
What about ac3dsp then - that one seems like it's fairly optimized for arm?
Haven't touched them, they're still being used. Unfortunately, for AC3,
the full MDCT optimizations in lavc do make a difference and the overall
decoder becomes 15% slower with this p
Lynne:
> Sep 24, 2022, 23:57 by d...@lynne.ee:
>
>> Sep 24, 2022, 21:40 by mar...@martin.st:
>>
>>> What about ac3dsp then - that one seems like it's fairly optimized for arm?
>>>
>> Haven't touched them, they're still being used. Unfortunately, for AC3,
>> the full MDCT optimizations in lavc do m
Sep 24, 2022, 23:57 by d...@lynne.ee:
> Sep 24, 2022, 21:40 by mar...@martin.st:
>
>> What about ac3dsp then - that one seems like it's fairly optimized for arm?
>>
> Haven't touched them, they're still being used. Unfortunately, for AC3,
> the full MDCT optimizations in lavc do make a difference
Sep 24, 2022, 21:40 by mar...@martin.st:
> On Sat, 24 Sep 2022, Hendrik Leppkes wrote:
>
>> On Sat, Sep 24, 2022 at 9:26 PM Hendrik Leppkes wrote:
>>
>>>
>>> On Sat, Sep 24, 2022 at 8:43 PM Martin Storsjö wrote:
>>> >
>>> > On Sat, 24 Sep 2022, Lynne wrote:
>>> >
>>> > > This commit changes both
On Sat, 24 Sep 2022, Hendrik Leppkes wrote:
On Sat, Sep 24, 2022 at 9:26 PM Hendrik Leppkes wrote:
On Sat, Sep 24, 2022 at 8:43 PM Martin Storsjö wrote:
>
> On Sat, 24 Sep 2022, Lynne wrote:
>
> > This commit changes both the encoder and decoder to use the new lavu/tx
code,
> > which has fa
On Sat, Sep 24, 2022 at 9:26 PM Hendrik Leppkes wrote:
>
> On Sat, Sep 24, 2022 at 8:43 PM Martin Storsjö wrote:
> >
> > On Sat, 24 Sep 2022, Lynne wrote:
> >
> > > This commit changes both the encoder and decoder to use the new lavu/tx
> > > code,
> > > which has faster C transforms and more as
On Sat, Sep 24, 2022 at 8:43 PM Martin Storsjö wrote:
>
> On Sat, 24 Sep 2022, Lynne wrote:
>
> > This commit changes both the encoder and decoder to use the new lavu/tx
> > code,
> > which has faster C transforms and more assembly optimizations.
>
> What's the case of e.g. 32 bit arm - that does
On Sat, 24 Sep 2022, Lynne wrote:
This commit changes both the encoder and decoder to use the new lavu/tx code,
which has faster C transforms and more assembly optimizations.
What's the case of e.g. 32 bit arm - that does have a bunch of fft and
mdct assembly, but is that something that ends
12 matches
Mail list logo
