Re: [mpg123-devel] Heads up

[JonY <jo...@us...>]

On 9/16/2013 10:37, Thomas Orgis wrote:
> Hi,
> 
> just wanting to say that I'm not entirely dead and still intend to get
> mpg132 1.16.0 out. I wanted to hack in the build system switch to allow
> K6 users to skip on suboptimal dxt36 (runtime switching is perhaps just
> to much needless work and testing), but stumbled over an old patch for
> APIC support instead. So, you can extract album art via libmpg123 now
> (see MPG123_PICTURE and the list of
> http://mpg123.orgis.org/api/structmpg123__picture.shtml in
> http://mpg123.orgis.org/api/structmpg123__id3v2.shtml).
> 
> That might be interesting for fancy jukebox applications that are too
> lazy to use proper tag libraries. Since clearly not every one needs
> this, the picture parsing must be enabled explicitly. There is
> mpg123-id3dump now, which is an extension of
> http://mpg123.orgis.org/api/id3dump_8c.shtml and also can write album
> art to files.
> 
> This new program is not part of the Windows builds (the packages
> created by the build script); it needs adaption to support unicode file
> names, at least, on that platform. JonY: you feel like fixing it up and
> at the same time collect the code you would duplicate from mpg123.c in
> a common spot? All those define checks really have gotten ugly, no need
> to have them twice:-/
> 

Sure, will take a look at it, does it have to go in for the 1.16 release?

> Any other last words befor 1.16.0? I really want this performance boost
> out there.
> 

Btw, ffmp3float clocked in at 7.6s average while mpg123 at 7.2 average
on a 20+ minute mp3. Tested on an Core-i7 Windows machine with the mpv
player.