TagLib 1.6 RC1

Hi,

I'm happy to finally announce TagLib 1.6 RC1. I apologize it took a
little longer than I expected. There have been a number of bug fixes
since the last release. TagLib 1.6 also brings support for four new
file formats (MP4, ASF, AIFF and WAV) and a few new ID3v2 frames.
Thanks to everybody who contributed patches! See below for detailed
change log.

I'd like to ask you to test this version and report any problem you
encounter. If things will go well, I'm hoping to release TagLib 1.6
next weekend. Also check the API documentation and let us know about
any new classes/methods with missing or unclear documentation. Thank
you.

TagLib 1.6 will be the last release in 1.x series. The next release
will be 2.0, which will be both source code and binary incompatible
with previous versions.

Source code
=========
http://ftp.musicbrainz.org/pub/musicbrainz/users/luks/taglib/taglib-1.6rc1.tar.gz

API documentation
==============
http://ftp.musicbrainz.org/pub/musicbrainz/users/luks/taglib/api/

Changes since version 1.5
===================

 * Split Ogg packets larger than 64k into multiple pages. (BUG:171957)
 * TagLib can now use FLAC padding block. (BUG:107659)
 * ID3v2.2 frames are now not incorrectly saved. (BUG:176373)
 * Support for ID3v2.2 PIC frames. (BUG:167786)
 * Fixed a bug in ByteVectorList::split().
 * XiphComment::year() now falls back to YEAR if DATE doesn't exist
and XiphComment::year() falls back to TRACKNUM if TRACKNUMBER doesn't
exist. (BUG:144396)
 * Improved ID3v2.3 genre parsing. (BUG:188578)
 * Better checking of corrupted ID3v2 APIC data. (BUG:168382)
 * Bitrate calculating using the Xing header now uses floating point
numbers. (BUG:172556)
 * New TagLib::String method rfind().
 * Added support for MP4 file format with iTunes-style metadata [optional].
 * Added support for ASF (WMA) file format [optional].
 * Fixed crash when saving a Locator APEv2 tag. (BUG:169810)
 * Fixed a possible crash in the non-const version of
String::operator[] and in String::operator+=. (BUG:169389)
 * Added support for PRIV ID3v2 frames.
 * Empty ID3v2 genres are no longer treated as numeric ID3v1 genres.
 * Added support for the POPM (rating/playcount) ID3v2 frame.
 * Generic RIFF file format support:
   * Support for AIFF files with ID3v2 tags.
   * Support for WAV files with ID3v2 tags.
 * Fixed crash on handling unsupported ID3v2 frames, e.g. on encrypted
frames. (BUG:161721)
 * Fixed overflow while calculating bitrate of FLAC files with a very
high bitrate.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Sander Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Great to see another release. Regarding the MP4/ASF support in 1.6, is
there a way to detect for a program using taglib to detect whether
support is buildin or not (runtime and compiletime)? Since I access the
mp4 tag to check for disc numbers, I guess my program depends on some of
the mp4 dependent header files. Will those be installed when mp4/asf is
disabled?

How much does the ASF/MP4 support differ from taglib-extras ?

Cheers,

Sander


Lukáš Lalinský wrote:

> Hi,
>
> I'm happy to finally announce TagLib 1.6 RC1. I apologize it took a
> little longer than I expected. There have been a number of bug fixes
> since the last release. TagLib 1.6 also brings support for four new
> file formats (MP4, ASF, AIFF and WAV) and a few new ID3v2 frames.
> Thanks to everybody who contributed patches! See below for detailed
> change log.
>
> I'd like to ask you to test this version and report any problem you
> encounter. If things will go well, I'm hoping to release TagLib 1.6
> next weekend. Also check the API documentation and let us know about
> any new classes/methods with missing or unclear documentation. Thank
> you.
>
> TagLib 1.6 will be the last release in 1.x series. The next release
> will be 2.0, which will be both source code and binary incompatible
> with previous versions.
>
> Source code
> =========
> http://ftp.musicbrainz.org/pub/musicbrainz/users/luks/taglib/taglib-1.6rc1.tar.gz
>
> API documentation
> ==============
> http://ftp.musicbrainz.org/pub/musicbrainz/users/luks/taglib/api/
>
> Changes since version 1.5
> ===================
>
>  * Split Ogg packets larger than 64k into multiple pages. (BUG:171957)
>  * TagLib can now use FLAC padding block. (BUG:107659)
>  * ID3v2.2 frames are now not incorrectly saved. (BUG:176373)
>  * Support for ID3v2.2 PIC frames. (BUG:167786)
>  * Fixed a bug in ByteVectorList::split().
>  * XiphComment::year() now falls back to YEAR if DATE doesn't exist
> and XiphComment::year() falls back to TRACKNUM if TRACKNUMBER doesn't
> exist. (BUG:144396)
>  * Improved ID3v2.3 genre parsing. (BUG:188578)
>  * Better checking of corrupted ID3v2 APIC data. (BUG:168382)
>  * Bitrate calculating using the Xing header now uses floating point
> numbers. (BUG:172556)
>  * New TagLib::String method rfind().
>  * Added support for MP4 file format with iTunes-style metadata [optional].
>  * Added support for ASF (WMA) file format [optional].
>  * Fixed crash when saving a Locator APEv2 tag. (BUG:169810)
>  * Fixed a possible crash in the non-const version of
> String::operator[] and in String::operator+=. (BUG:169389)
>  * Added support for PRIV ID3v2 frames.
>  * Empty ID3v2 genres are no longer treated as numeric ID3v1 genres.
>  * Added support for the POPM (rating/playcount) ID3v2 frame.
>  * Generic RIFF file format support:
>    * Support for AIFF files with ID3v2 tags.
>    * Support for WAV files with ID3v2 tags.
>  * Fixed crash on handling unsupported ID3v2 frames, e.g. on encrypted
> frames. (BUG:161721)
>  * Fixed overflow while calculating bitrate of FLAC files with a very
> high bitrate.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqgKewACgkQhygVDb8DRqzCbQCfbcM9GQwoQuQgZzCCholKi4OX
9bgAn1n2105B9kdDCCYAxrk3US0BlD1L
=2u4l
-----END PGP SIGNATURE-----
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

On Thu, Sep 3, 2009 at 10:41 PM, Sander Jansen<s.jansen@...> wrote:
> Great to see another release. Regarding the MP4/ASF support in 1.6, is
> there a way to detect for a program using taglib to detect whether
> support is buildin or not (runtime and compiletime)? Since I access the
> mp4 tag to check for disc numbers, I guess my program depends on some of
> the mp4 dependent header files. Will those be installed when mp4/asf is
> disabled?

If you are using FileRef, you can just check if it has a file opened.
The header files should not be installed without enabling those
options, so at compile time you can look e.g. for mp4file.h to
determine whether you have TagLib with MP4 support or not.

> How much does the ASF/MP4 support differ from taglib-extras ?

taglib-extras is mostly a copy of post-1.5 code from taglib trunk (ie,
the ASF and MP4 classes are identical).

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Sander Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lukáš Lalinský wrote:

> On Thu, Sep 3, 2009 at 10:41 PM, Sander Jansen<s.jansen@...> wrote:
>> Great to see another release. Regarding the MP4/ASF support in 1.6, is
>> there a way to detect for a program using taglib to detect whether
>> support is buildin or not (runtime and compiletime)? Since I access the
>> mp4 tag to check for disc numbers, I guess my program depends on some of
>> the mp4 dependent header files. Will those be installed when mp4/asf is
>> disabled?
>
> If you are using FileRef, you can just check if it has a file opened.
> The header files should not be installed without enabling those
> options, so at compile time you can look e.g. for mp4file.h to
> determine whether you have TagLib with MP4 support or not.

How about adding an extra define to the pkg-config file when those are
enabled. Then I can use pkg-config directly and use the extra define in
my code without having to check for the right header files?

Cheers,

Sander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqgLf8ACgkQhygVDb8DRqwEIgCdE2CqbsELGFN+U7IeMrlDayQP
ezIAmgI28++29YPwouAYcLSadTYv7/kE
=cwtJ
-----END PGP SIGNATURE-----
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

2009/9/3 Sander Jansen <s.jansen@...>:
> How about adding an extra define to the pkg-config file when those are
> enabled. Then I can use pkg-config directly and use the extra define in
> my code without having to check for the right header files?

Good idea, that would work. I'll add that before releasing 1.6.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Lukáš Lalinský wrote:
>> How much does the ASF/MP4 support differ from taglib-extras ?
>
> taglib-extras is mostly a copy of post-1.5 code from taglib trunk (ie,
> the ASF and MP4 classes are identical).

Yes...those formats that are shared between the two are identical and
have regularly been synced (except for any tiny changes necessary for
compilation). Once distributions package 1.6, taglib-extras will have
another release that drops those formats.

--Jeff



_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Michael Schwendt]

On Thu, 03 Sep 2009 21:11:26 -0400, Jeff wrote:

> Lukáš Lalinský wrote:
> >> How much does the ASF/MP4 support differ from taglib-extras ?
> >
> > taglib-extras is mostly a copy of post-1.5 code from taglib trunk (ie,
> > the ASF and MP4 classes are identical).
>
> Yes...those formats that are shared between the two are identical and
> have regularly been synced (except for any tiny changes necessary for
> compilation). Once distributions package 1.6, taglib-extras will have
> another release that drops those formats.

Do you encourage packagers to enable the _optional_ (!) ASF/WMA and MP4
format support?
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

On Fri, Sep 4, 2009 at 11:17 AM, Michael Schwendt<mschwendt@...> wrote:

> On Thu, 03 Sep 2009 21:11:26 -0400, Jeff wrote:
>
>> Lukáš Lalinský wrote:
>> >> How much does the ASF/MP4 support differ from taglib-extras ?
>> >
>> > taglib-extras is mostly a copy of post-1.5 code from taglib trunk (ie,
>> > the ASF and MP4 classes are identical).
>>
>> Yes...those formats that are shared between the two are identical and
>> have regularly been synced (except for any tiny changes necessary for
>> compilation). Once distributions package 1.6, taglib-extras will have
>> another release that drops those formats.
>
> Do you encourage packagers to enable the _optional_ (!) ASF/WMA and MP4
> format support?

I don't encourage or discourage it. From technical point of view they
are fine. You might be concerned about patent issues, but I'm sure you
have worse code in your distribution (and most likely even the same
code, either with Amarok1 or taglib-extras). Nice situation is for
example:

http://marc.info/?l=taglib-devel&m=120767061907191&w=2

which says Fedora would rather not distribute the ASF code and yet there is:

https://admin.fedoraproject.org/pkgdb/packages/name/taglib-extras (same code)
https://admin.fedoraproject.org/pkgdb/packages/name/libtunepimp (the
implementation in TagLib 1.6 is based on this code)
https://admin.fedoraproject.org/pkgdb/packages/name/python-mutagen
(ASF part is again based on the code from libtunepimp)
https://admin.fedoraproject.org/pkgdb/packages/name/bmpx (copy of WMA
code from libtunepimp)

I'm sure I can find more. So, do your own decision. :)

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Michael Schwendt]

On Fri, 4 Sep 2009 11:42:55 +0200, Lukáš wrote:

> > Do you encourage packagers to enable the _optional_ (!) ASF/WMA and MP4
> > format support?
>
> I don't encourage or discourage it. From technical point of view they
> are fine.

Thanks. I was mostly interested in the run-time readiness of these
new features for now.
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Michael Schwendt wrote:
> On Fri, 4 Sep 2009 11:42:55 +0200, Lukáš wrote:
>
>>> Do you encourage packagers to enable the _optional_ (!) ASF/WMA and MP4
>>> format support?
>> I don't encourage or discourage it. From technical point of view they
>> are fine.
>
> Thanks. I was mostly interested in the run-time readiness of these
> new features for now.

Michael,

Before Amarok split out taglib-extras, the ASF code in-tree was
identical as the code here, so it's been given a workout for years.

The MP4 code is different -- the code in Amarok used libmp4v2, and this
does not -- but since it got put into taglib-extras (which is a required
dependency of Amarok) it's been getting a workout, and several bugs have
already been fixed (and the majority of these were workarounds for
corrupted files). I should note that Lukas maintains it based on his
pre-existing code for mutagen, so the only real new part is not the how,
but the specifics of it being on C++.

--Jeff



_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Tony Pombo]

I currently have several projects on Windows that use TagLib 1.5 as a static library.  I like the convenience of distributing a single executable file.

However, I understand that TagLib 1.6 doesn't support compiling to a static LIB file on Windows.  I am disappointed to hear this.

Having to distribute, install, and support another (unnecessary DLL) file should not be required.  I would like to suggest that support for compiling to a static LIB be added to 1.6.

This feature was available in v1.5, and I see no reason to remove it from v1.6

Thank you.

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

On Tue, Sep 8, 2009 at 5:57 AM, Tony Pombo<mcp@...> wrote:
> I currently have several projects on Windows that use TagLib 1.5 as a static library.  I like the convenience of distributing a single executable file.
>
> However, I understand that TagLib 1.6 doesn't support compiling to a static LIB file on Windows.  I am disappointed to hear this.
>
> Having to distribute, install, and support another (unnecessary DLL) file should not be required.  I would like to suggest that support for compiling to a static LIB be added to 1.6.
>
> This feature was available in v1.5, and I see no reason to remove it from v1.6

This feature was not removed in 1.6, it was not supported in 1.5
either. If you can tell me how did you build static library with 1.5
and what doesn't work with 1.6, I can try to fix it.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Tony Pombo]

In March 2009, I created a Visual Studio 2008 project that would create a
DLL and/or a LIB file.  I honestly haven't tried to compile version 1.6 yet.
As long as nothing has been done to explicitly prevent compiling as a static
library, it should still work.  I will try to find time this week to test
the current build.

I'd be happy to share the VS2008 project with whomever wants it.

Thanks

-----Original Message-----
From: Lukáš Lalinský [mailto:lalinsky@...]
Sent: Tuesday, September 08, 2009 3:09 AM
To: Tony Pombo
Cc: taglib-devel@...
Subject: Re: TagLib 1.6 RC1 - Windows Static LIB

On Tue, Sep 8, 2009 at 5:57 AM, Tony Pombo<mcp@...> wrote:
> I currently have several projects on Windows that use TagLib 1.5 as a
static library.  I like the convenience of distributing a single executable
file.
>
> However, I understand that TagLib 1.6 doesn't support compiling to a
static LIB file on Windows.  I am disappointed to hear this.
>
> Having to distribute, install, and support another (unnecessary DLL) file
should not be required.  I would like to suggest that support for compiling
to a static LIB be added to 1.6.
>
> This feature was available in v1.5, and I see no reason to remove it from
v1.6

This feature was not removed in 1.6, it was not supported in 1.5
either. If you can tell me how did you build static library with 1.5
and what doesn't work with 1.6, I can try to fix it.

--
Lukas Lalinsky
lalinsky@...

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.83/2353 - Release Date: 09/08/09
06:48:00

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

2009/9/9 Tony Pombo <mcp@...>:
> In March 2009, I created a Visual Studio 2008 project that would create a
> DLL and/or a LIB file.  I honestly haven't tried to compile version 1.6 yet.
> As long as nothing has been done to explicitly prevent compiling as a static
> library, it should still work.  I will try to find time this week to test
> the current build.

Well, I don't know how have you managed that, since the
taglib_export.h file with dllimport/dllexport was there in 1.5 as
well. But if it worked, it will work again. But I'd also added
explicit support for building a static version of the library in CMake
a few days ago. The only difference is that you need to define
TAGLIB_STATIC in your project if you want to use such library. This
will stop taglib_export.h from trying to dllimport the classes.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[NightStrike]

2009/9/8 Lukáš Lalinský <lalinsky@...>:

> On Tue, Sep 8, 2009 at 5:57 AM, Tony Pombo<mcp@...> wrote:
>> I currently have several projects on Windows that use TagLib 1.5 as a static library.  I like the convenience of distributing a single executable file.
>>
>> However, I understand that TagLib 1.6 doesn't support compiling to a static LIB file on Windows.  I am disappointed to hear this.
>>
>> Having to distribute, install, and support another (unnecessary DLL) file should not be required.  I would like to suggest that support for compiling to a static LIB be added to 1.6.
>>
>> This feature was available in v1.5, and I see no reason to remove it from v1.6
>
> This feature was not removed in 1.6, it was not supported in 1.5
> either. If you can tell me how did you build static library with 1.5
> and what doesn't work with 1.6, I can try to fix it.

Since you use libtool and autotools, doing --enable-static and
--disable-shared, along with a patch to dll_export, builds static
libs.
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Lukáš Lalinský wrote:

> On Fri, Sep 4, 2009 at 11:17 AM, Michael Schwendt<mschwendt@...>
> wrote:
>> On Thu, 03 Sep 2009 21:11:26 -0400, Jeff wrote:
>>
>>> Lukáš Lalinský wrote:
>>> >> How much does the ASF/MP4 support differ from taglib-extras ?
>>> >
>>> > taglib-extras is mostly a copy of post-1.5 code from taglib trunk (ie,
>>> > the ASF and MP4 classes are identical).
>>>
>>> Yes...those formats that are shared between the two are identical and
>>> have regularly been synced (except for any tiny changes necessary for
>>> compilation). Once distributions package 1.6, taglib-extras will have
>>> another release that drops those formats.
>>
>> Do you encourage packagers to enable the _optional_ (!) ASF/WMA and MP4
>> format support?
>
> I don't encourage or discourage it. From technical point of view they
> are fine. You might be concerned about patent issues, but I'm sure you
> have worse code in your distribution (and most likely even the same
> code, either with Amarok1 or taglib-extras). Nice situation is for
> example:
>
> http://marc.info/?l=taglib-devel&m=120767061907191&w=2
>
> which says Fedora would rather not distribute the ASF code and yet there
> is:

legal had a change of heart, fwiw,
https://bugzilla.redhat.com/show_bug.cgi?id=taglib-extras

-- Rex


_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel