Changes to write ID3v2.3 tags and unsynchronization

[Scott Wheeler]

Hi Jonathan --

Your mail got flagged by the KDE mail server as spam, so perhaps that  
was what was causing problems.  Occasionally it's a bit trigger happy.

I recently handed off maintainership to Lukas, but I'm sure if you  
send the patches along they'll at least be looked at.  Out of  
curiosity, which programs specifically still have problems reading  
ID3v2.4 tags?  I thought that was mostly a solved problem at this point.

-Scott

On Oct 23, 2009, at 8:12 AM, Jonathan Potter wrote:

> Hi Scott,
>
> (I tried to post this message to the list twice but it never showed  
> up, even though I am subscribed and getting emails. Figured I'd send  
> it to you directly in case you were interested)
>
> I've been working with taglib for a little while, integrating it  
> into our product (Directory Opus, a Windows file manager). I'd like  
> to say I think you've all done a great job – it's a really nicely  
> designed library and seems to work very well from what little we've  
> seen of it so far.
>
> After working with it for a while we came to the realisation that we  
> really needed to be able to write ID3v2.3 tags, as it seems like  
> most Windows-based software (including Windows Media Player) still  
> doesn't support ID3v2.4. Therefore I've made a number of changes to  
> taglib to support this (it didn't actually end up being very  
> difficult).
>
> I've also added support for unsynchronisation (both on a per-frame  
> level for 2.4 as well as a whole tag level for 2.3) – although it  
> seems like so few programs properly support unsynchronisation (at  
> least with ID3v2.3) that I'm not sure how useful this is.
>
> I'm just wondering now if anyone is interested in seeing these  
> changes – so far in in-house testing it seems to work ok but I'm  
> obviously not 100% sure it hasn't caused any problems as we're not  
> THAT familiar with the taglib code. So if anyone who is more  
> familiar with taglib would be interested in having a look, please  
> let me know as we'd love any feedback you may have.
>
> Cheers,
> Jonathan Potter
>
>