[FFmpeg-devel] [PATCH 4/5] aptx: implement the aptX HD bluetooth codec
aurel at gnuage.org
Sun Feb 4 17:07:26 EET 2018
On Sat, Jan 20, 2018 at 11:20:22PM +0000, Rostislav Pehlivanov wrote:
> On 20 January 2018 at 17:26, Aurelien Jacobs <aurel at gnuage.org> wrote:
> > On Sun, Jan 14, 2018 at 10:54:34PM +0100, Carl Eugen Hoyos wrote:
> > > 2018-01-14 14:06 GMT+01:00 Aurelien Jacobs <aurel at gnuage.org>:
> > >
> > > > Well, here is an updated patch which uses codec tags for the decoder
> > and
> > > > profile for the encoder.
> > >
> > > Sorry but I object to this patch:
> > > We should not invent codec_tags.
> > OK, I understand, and I agree.
> > But now we are in an interlocking situation.
> > We have 2 solutions to handle aptX vs. aptX HD but those 2 solutions have
> > been rejected by 2 different person.
> > Do anybody have a 3rd solution, that everyone would accept ?
> > And if not, how do we resolve this ?
> > Is there any policy nowadays to handle this kind of interlocking ?
> Fine, I see no choice but to use multiple codec IDs for aptxhd since the
> format really provides you with nothing bitstream wise to determine what it
> is. Even game codecs have a bit or two for version.
Now, will someone push the original patchset ?
Or should I rebase it and submt it again ?
More information about the ffmpeg-devel