On Mon, Feb 05, 2018 at 12:27:20AM +0100, Michael Niedermayer wrote: > On Sun, Feb 04, 2018 at 04:07:26PM +0100, Aurelien Jacobs wrote: > > On Sat, Jan 20, 2018 at 11:20:22PM +0000, Rostislav Pehlivanov wrote: > > > On 20 January 2018 at 17:26, Aurelien Jacobs <au...@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 <au...@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. > > > > OK. Good. > > > Now, will someone push the original patchset ? > > I think you should be able to push it yourself if there are no review > comments remaining > you are listed in MAINTAINERS for some parts and i see a "ajacobs" for ffmpeg > so you should have git write access
OK. Well I digged out my ssh key from old laptop, an I pushed it myself. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel