Re: lame main branch

Haha I agree! I suppose the best strategy for 3.100 would be a patch
simply replacing hip with mpg123 in the lame executable. That should
be fast, since it has been said that the encoder doesn't grab any
special information from the decoder.

Later, whenever you get the time, you can work on replacing hip in
the frame analyzer. Since the vast majority of people don't use mp3x

anyway, there should be no hurry at all.
-- 

Roberto José de Amorim
MSc in Computer Science
Columbia University - New York


________________________________
De: Thomas Orgis <[email protected]>
Para: [email protected] 
Cc: Roberto José de Amorim <[email protected]>
Enviadas: Terça-feira, 22 de Agosto de 2017 13:43
Assunto: Re: [Lame-dev] lame main branch


In any case, worst case is another lame release with the mpg123 patch
in a rather short time after the one being prepared now. This counts as
project activity;-)


Alrighty then,


Thomas
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev