Re: [id3lib-devel] New version of id3lib features

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi, Severino,

The version of id3lib that we will be releasing is more-or-less the next
version of the id3lib found on www.id3lib.org.  To make a long story short, I
wanted to get id3lib to work with linux, so I started hacking on it last
November, about a year after development on the original id3lib.  Musicmatch
had taken over development, but hadn't made any of their changes public.  After
much discussion with MusicMatch, they have agreed to relinquish control of
development to this branch.  It will be relicensed under the LGPL (see
http://www.opensource.org/licenses/lgpl-license.html) to ensure that the
library, and any modifications made to it, will remain freely available for
everyone.  The license does allow proprietary, close-source applications to
link to it, so long as any changes to the library itself are made available.

I have made many modifications to the library since I started working on it,
although the basic interface has remained intact.  The biggest change that
you'll notice is the directory layout has been altered so that it is more
conducive for building in a unix environment, although others have written
dev studio projects so it can compile in windows with Visual C++.  See the prj/
directory in the current download given in the last email.  My goal is to keep
the library as functional on as many platforms as possible, but I'm much more
confortable developing for unix/linux than windows.

I am hoping to wrap up the last details so that I can make an official release
by tomorrow.  In the meantime, feel free to peruse the changes I've made.  I
put up a quick little webpage at http://id3lib.sourceforge.net.  It links to
the project page, which has a lot of resources that we can use to assist in
development.  Hopefully once a release is ready, we can get MusicMatch to
update http://id3lib.org so that there will be no confusion like this in the
future. 

If you have any further questions, please don't be afraid to ask.  I don't know
how much others know about the current situation, so I'm not sure how much I
need to explain.  I doubt you're the only one who has these questions, so
please ask away.

-Scott

On Thu, Apr 06, 2000 at 06:08:59PM +0200, Severino (id3lib) wrote:
> Hi Scott,
> 
> ActiveX controls are a special kind of DLLs mainly used in Windows OS by
> Visual Basic (but not only) developers in order to incorporate features that
> the development environment language does not support.
> In our case we want to make these developers able to incorporate MP3
> capabilities into their application through one of these ActiveX controls.
> One of the tasks of our ActiveX control, that incorporates the source code
> of the ID3LIB we have downloaded from http://www.id3lib.org/files/id3lib.zip
> , is to make quite easy for one of these programmers to develop applications
> that read and write ID3v2 tags.
> 
> The version of ID3lib we are using is for use with Windows and is now
> coordinated by Music Match and was initially written by Dirk Mahoney and
> Andreas Sigfridsson: is the version You are releasing in some way related to
> this one?
> 
> Kind Regards
> 
>  Severino Delaurenti
>  Castlemount Soft (http://www.castlems.com)
>  Italy
> 
> 
> 
> 
> -----Original Message-----
> From: Scott Haug [mailto:st...@cs...]
> Sent: 06 April 2000 17:35
> To: Severino (id3lib)
> Cc: id3...@li...
> Subject: Re: [id3lib-devel] New version of id3lib features
> 
> 
> Hi, Severino,
> 
> On Thu, Apr 06, 2000 at 10:31:43AM +0200, Severino (id3lib) wrote:
> > Hi all,
> >
> > I subscribed today to this list, on suggestion of Scott Haug, because we
> are
> > developing an Mp3 management ActiveX control that should incorporate the
> > id3lib functionalities.
> 
> Good to hear.  I don't know anything about ActiveX controls, but I'm
> interested
> to learn how id3lib can be used in this manner.
> 
> >
> > Due to the fact that id3lib currently does not manage all the frames
> > available in the id3v2 standard (for example AENC, SYLT, COMR, etc.) I
> would
> > like to know which new features will be available on the next library
> > release and also the planned release date.
> 
> As for the planned release date, it should be Any Day Now.  The library
> interface/implementation isn't going to change much between now and then.  I
> just need to evaluate some minor issues like versioning and making sure all
> files are properly noted with the licensing/copyright information.
> 
> Now the issue of supported frames.  In one way, all frames will be
> supported,
> though just to varying degrees.  The following is a list of frames that will
> have minimal support in the library upon release:
> 
> // AENC  CRA  ID3FID_AUDIOCRYPTO       Audio encryption
> // COMR       ID3FID_COMMERCIAL        Commercial frame
> // EQUA  EQU  ID3FID_EQUALIZATION      Equalization
> // ETCO  ETC  ID3FID_EVENTTIMING       Event timing codes
> // MCDI  MCI  ID3FID_CDID              Music CD identifier
> // MLLT  MLL  ID3FID_MPEGLOOKUP        MPEG location lookup table
> // OWNE       ID3FID_OWNERSHIP         Ownership frame
> // POSS       ID3FID_POSITIONSYNC      Position synchronisation frame
> // PRIV       ID3FID_PRIVATE           Private frame
> // RBUF  BUF  ID3FID_BUFFERSIZE        Recommended buffer size
> // RVAD  RVA  ID3FID_VOLUMEADJ         Relative volume adjustment
> // RVRB  REV  ID3FID_REVERB            Reverb
> // SYLT  SLT  ID3FID_SYNCEDLYRICS      Synchronized lyric/text
> // SYTC  STC  ID3FID_SYNCEDTEMPO       Synchronized tempo codes
> //       CRM  ID3FID_METACRYPTO        Encrypted meta frame
> 
> This is taken from field.cpp.  The first column is the 4 character id, the
> second is the 3 char id, the third is the constant representing this frame
> in
> di3lib, and the third is the id3v2 description of the frame.  All of these
> frames will be successfully parsed from a file/stream, and can be rewritten
> to
> a file/stream.  But manual creation of these frames will be limited.
> Basically, all of these frames will be treated as a single block of binary
> data.  You can set this data as one block, and retrieve it as a single
> block.
> But the creation and parsing of that block will not be assisted by the
> library.  If someone wants to help extend the interface to improve the
> handling
> of these frames, by all means.  But that's the extent of the support for
> these
> frames at this time.
> 
> >
> > Hope that I will be able to contribute to the list actively.
> 
> I'm looking forward to it.
> 
> >
> > Kind Regards
> >
> > Severino Delaurenti
> > Castlemount Soft (http://www.castlems.com)
> > Italy
> >
> 
> -Scott
> 
> 
> 
> 
> _______________________________________________
> id3lib-devel mailing list
> id3...@li...
> http://lists.sourceforge.net/mailman/listinfo/id3lib-devel

-- 