Re: [FFmpeg-devel] avcodec/aacenc: Compatibility with Bluetooth A2DP headsets

2020-01-03 Thread Hendrik Leppkes
On Fri, Jan 3, 2020 at 9:24 AM Andrey Semashev
 wrote:
>
> On 2020-01-03 09:14, Kieran Kunhya wrote:
> >>
> >>> Thanks.
> >>
> >> Ping?
> >>
> >
> > Have you tried using our LATM mux?
>
> No, I'm trying to avoid libavformat dependency. I'm sure my LATM code is
> fine because it works with libfdk-aac.

No harm in testing to confirm.

- Hendrik
___
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".

Re: [FFmpeg-devel] avcodec/aacenc: Compatibility with Bluetooth A2DP headsets

2020-01-03 Thread Andrey Semashev

On 2020-01-03 09:14, Kieran Kunhya wrote:



Thanks.


Ping?



Have you tried using our LATM mux?


No, I'm trying to avoid libavformat dependency. I'm sure my LATM code is 
fine because it works with libfdk-aac.

___
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".

Re: [FFmpeg-devel] avcodec/aacenc: Compatibility with Bluetooth A2DP headsets

2020-01-02 Thread Kieran Kunhya
>
> > Thanks.
>
> Ping?
>

Have you tried using our LATM mux?

Kieran
___
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".

Re: [FFmpeg-devel] avcodec/aacenc: Compatibility with Bluetooth A2DP headsets

2020-01-02 Thread Andrey Semashev

On 2019-12-24 01:57, Andrey Semashev wrote:

Hi,

I'm trying to add support for AAC to PulseAudio with regard to Bluetooth 
A2DP. I'm using libavcodec to encode AAC content and then packetize it 
into RTP MP4-LATM packets, as required by A2DP spec. My current 
implementation allows to switch between libfdk-aac and built-in AAC 
encoder backends.


With libfdk-aac, everything's working well, the encoded audio is 
correctly played by the BT headset (EOZ Air). But with the built-in 
encoder I can hear occasional audio drop outs and artefacts like clicks 
and weird stereo effects. I'm assuming this is because some decoding 
errors on the headset, but obviously I don't have any kind of debug info 
from it. When the same content is played (e.g. the same song) on 
different runs, the artefacts appear at roughly the same places, so I'm 
assuming that the problem is input content-related.


Given that libfdk-aac output is played without artefacts by the device, 
I'm assuming my packetization code is correct. I also tried to debug and 
analyze its output and didn't find anything out of order. This makes me 
believe the problem is in the built-in encoder.


How should I proceed about this problem? What kind of information would 
be useful to the aacenc developer(s) to debug this? Is there any 
information as to how conforming aacenc is to the AAC spec and other, 
especially hardware implementations?


For a start, here is my code:

https://gitlab.freedesktop.org/andrey.semashev/pulseaudio/blob/a2dp-codecs-aac/src/modules/bluetooth/a2dp-codec-aac.c 



libavcodec encoder context initialization is at:

https://gitlab.freedesktop.org/andrey.semashev/pulseaudio/blob/a2dp-codecs-aac/src/modules/bluetooth/a2dp-codec-aac.c#L685 



Thanks.


Ping?
___
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".

[FFmpeg-devel] avcodec/aacenc: Compatibility with Bluetooth A2DP headsets

2019-12-23 Thread Andrey Semashev

Hi,

I'm trying to add support for AAC to PulseAudio with regard to Bluetooth 
A2DP. I'm using libavcodec to encode AAC content and then packetize it 
into RTP MP4-LATM packets, as required by A2DP spec. My current 
implementation allows to switch between libfdk-aac and built-in AAC 
encoder backends.


With libfdk-aac, everything's working well, the encoded audio is 
correctly played by the BT headset (EOZ Air). But with the built-in 
encoder I can hear occasional audio drop outs and artefacts like clicks 
and weird stereo effects. I'm assuming this is because some decoding 
errors on the headset, but obviously I don't have any kind of debug info 
from it. When the same content is played (e.g. the same song) on 
different runs, the artefacts appear at roughly the same places, so I'm 
assuming that the problem is input content-related.


Given that libfdk-aac output is played without artefacts by the device, 
I'm assuming my packetization code is correct. I also tried to debug and 
analyze its output and didn't find anything out of order. This makes me 
believe the problem is in the built-in encoder.


How should I proceed about this problem? What kind of information would 
be useful to the aacenc developer(s) to debug this? Is there any 
information as to how conforming aacenc is to the AAC spec and other, 
especially hardware implementations?


For a start, here is my code:

https://gitlab.freedesktop.org/andrey.semashev/pulseaudio/blob/a2dp-codecs-aac/src/modules/bluetooth/a2dp-codec-aac.c

libavcodec encoder context initialization is at:

https://gitlab.freedesktop.org/andrey.semashev/pulseaudio/blob/a2dp-codecs-aac/src/modules/bluetooth/a2dp-codec-aac.c#L685

Thanks.
___
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".