From lllcubed at gmail.com  Mon May 21 14:01:22 2007
From: lllcubed at gmail.com (L Cubed)
Date: Mon, 21 May 2007 16:01:22 -0500
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <52c121940705211401h558c1b71i4ae272471d66f924@mail.gmail.com>

On 5/21/07, Chris Morton <chris at ca-dreaming.com> wrote:
> Can anyone recommend a *free* command-line driven MP3 tagger for batch
> processing? As a requisite, the tagger should accept parameters.

Besides the OS, what batch operations are critical for you?

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From fiji at ayup.limey.net  Tue May 29 06:48:49 2007
From: fiji at ayup.limey.net (Ben Bennett)
Date: Tue, 29 May 2007 09:48:49 -0400
Subject: [ID3 Dev] patents
In-Reply-To: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net>
References: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net>
Message-ID: <20070529134849.GA22498@ayup.limey.net>

It is better not to know.  Really.

You get nailed for the serious money for wilful infringement.

However, tagging doesn't know (or at least need to know) about any of
the internal details of mp3 tags.  You could theoretically apply ID3v2
tags to a word doc, a jpeg, or whatever you wanted.  Now... the target
app probably couldn't read it with the leading "junk", but that's a
different story.

		 -ben

On Tue, May 29, 2007 at 02:25:11PM +0100, Mark Smith wrote:
> Does anyone know, or have a view about, whether the recent courtroom  
> shenanigans regarding mp3 patents have any bearing on the creation  
> and use of ID3 tags? Particularly whether or not we, as developers of  
> tagging software, have anything to be concerned about.
> 
> It seems that maybe doing anything even vaguely connected with mp3  
> could be seen as swimming in shark-infested waters.
> 
> best,
> 
> Mark Smith
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From support at mp3tag.de  Tue May 29 06:50:09 2007
From: support at mp3tag.de (Florian Heidenreich)
Date: Tue, 29 May 2007 15:50:09 +0200
Subject: [ID3 Dev] patents
In-Reply-To: <20070529134849.GA22498@ayup.limey.net>
References: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net> <20070529134849.GA22498@ayup.limey.net>
Message-ID: <465C2F91.1080707@mp3tag.de>

In addition to what Ben said, ID3 tags (neither ID3v1 nor ID3v2) are 
part of the MP3 spec so we should be on the safe side.

Kind regards,
Florian


Ben Bennett schrieb:
> It is better not to know.  Really.
> 
> You get nailed for the serious money for wilful infringement.
> 
> However, tagging doesn't know (or at least need to know) about any of
> the internal details of mp3 tags.  You could theoretically apply ID3v2
> tags to a word doc, a jpeg, or whatever you wanted.  Now... the target
> app probably couldn't read it with the leading "junk", but that's a
> different story.
> 
> 		 -ben
> 
> On Tue, May 29, 2007 at 02:25:11PM +0100, Mark Smith wrote:
>> Does anyone know, or have a view about, whether the recent courtroom  
>> shenanigans regarding mp3 patents have any bearing on the creation  
>> and use of ID3 tags? Particularly whether or not we, as developers of  
>> tagging software, have anything to be concerned about.
>>
>> It seems that maybe doing anything even vaguely connected with mp3  
>> could be seen as swimming in shark-infested waters.
>>
>> best,
>>
>> Mark Smith

-- 
Mp3tag - the universal Tag editor
http://www.mp3tag.de/en/

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From paul_t100 at fastmail.fm  Tue May 29 07:29:27 2007
From: paul_t100 at fastmail.fm (Paul Taylor)
Date: Tue, 29 May 2007 15:29:27 +0100
Subject: [ID3 Dev] patents
In-Reply-To: <09C1E299-8880-48EA-BBF4-7260BB2878A4@maseurope.net>
References: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net> <20070529134849.GA22498@ayup.limey.net> <465C2F91.1080707@mp3tag.de> <09C1E299-8880-48EA-BBF4-7260BB2878A4@maseurope.net>
Message-ID: <465C38C7.70607@fastmail.fm>

What has happened with MP3 patents ?

Mark Smith wrote:
> That is pretty much my reading of things, but I thought it might be 
> interesting raise it here, since it came up on another list.
>
> best,
>
> Mark
>
> On 29 May 2007, at 14:50, Florian Heidenreich wrote:
>
>> In addition to what Ben said, ID3 tags (neither ID3v1 nor ID3v2) are 
>> part of the MP3 spec so we should be on the safe side.
>>
>> Kind regards,
>> Florian
>>
>>
>> Ben Bennett schrieb:
>>> It is better not to know.  Really.
>>> You get nailed for the serious money for wilful infringement.
>>> However, tagging doesn't know (or at least need to know) about any of
>>> the internal details of mp3 tags.  You could theoretically apply ID3v2
>>> tags to a word doc, a jpeg, or whatever you wanted.  Now... the target
>>> app probably couldn't read it with the leading "junk", but that's a
>>> different story.
>>>          -ben
>>> On Tue, May 29, 2007 at 02:25:11PM +0100, Mark Smith wrote:
>>>> Does anyone know, or have a view about, whether the recent 
>>>> courtroom  shenanigans regarding mp3 patents have any bearing on 
>>>> the creation  and use of ID3 tags? Particularly whether or not we, 
>>>> as developers of  tagging software, have anything to be concerned 
>>>> about.
>>>>
>>>> It seems that maybe doing anything even vaguely connected with mp3  
>>>> could be seen as swimming in shark-infested waters.
>>>>
>>>> best,
>>>>
>>>> Mark Smith
>>
>> --Mp3tag - the universal Tag editor
>> http://www.mp3tag.de/en/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
>> For additional commands, e-mail: id3v2-help at id3.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>
>
> --Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.0.0/756 - Release Date: 
> 06/04/2007 00:00
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From jwhite at cdtag.com  Mon May 21 12:26:19 2007
From: jwhite at cdtag.com (Jud White)
Date: Mon, 21 May 2007 14:26:19 -0500
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <4651F25B.5030007@cdtag.com>

case's tag is the only one that comes to mind. or you could roll your 
own with one of the free libs out there

Chris Morton wrote:
> Can anyone recommend a *free* command-line driven MP3 tagger for batch 
> processing? As a requisite, the tagger should accept parameters. 



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From lllcubed at gmail.com  Mon May 21 14:41:46 2007
From: lllcubed at gmail.com (L Cubed)
Date: Mon, 21 May 2007 16:41:46 -0500
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <52c121940705211416i11044d5au61e34b2666501bb1@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
	 <52c121940705211416i11044d5au61e34b2666501bb1@mail.gmail.com>
Message-ID: <52c121940705211441qf3f4f0eqcb002e7d11d199af@mail.gmail.com>

On 5/21/07, L Cubed <lllcubed at gmail.com> wrote:
> On 5/21/07, Chris Morton <chris at ca-dreaming.com> wrote:
> > Can anyone recommend a *free* command-line driven MP3 tagger for batch
> > processing? As a requisite, the tagger should accept parameters.
>
>
> Before I found this, I was using id3.exe (attached as a renamed zip
> file).  I don't know what the origin of this program is.
>
> HTH,
>
> LCubed
>

Apologizes to the list, intended to send this to Chris...

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From benski at winamp.com  Wed May 16 21:32:07 2007
From: benski at winamp.com (Ben Allison)
Date: Thu, 17 May 2007 00:32:07 -0400 (EDT)
Subject: [ID3 Dev] Sync-safe sizes?
In-Reply-To: <000f01c7983a$73b33d00$3c00a8c0@fluke>
References: <003b01c79838$741fcc60$3c00a8c0@fluke>
    <037501c79839$ecbb3c80$6501a8c0@xp1800desk>
    <000f01c7983a$73b33d00$3c00a8c0@fluke>
Message-ID: <1901.10.180.190.36.1179376327.squirrel@mail.winamp.com>

Applications not writing syncsafe frame sizes in ID3v2.4 has been a major
issue for widespread adoption of 2.4.  I'm sure the mailing list archives
have more to say - unfortunately there's not an easy answer.

-Ben Allison

> Hi Jim,
>
> Thanks for the quick response! OK, that's good - that's exactly what my
> code
> does now. I thought I must be missing something obvious; I thought I'd
> checked the frame size specs too, but obviously not! I'll have a read, and
> update as required.
>
> Mike.


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From smacfarl at gmail.com  Sat May 12 14:52:54 2007
From: smacfarl at gmail.com (Shawn MacFarland)
Date: Sat, 12 May 2007 17:52:54 -0400
Subject: [ID3 Dev] Introductory question
Message-ID: <32cccae20705121452n488a24c9oeb40f985c8bb6e85@mail.gmail.com>

Hello,

I was wondering about how broadcast (podcast) streams should be tagged. ID3
does an excellent job of providing song recording information, and the basic
structure of the tag or something very compatible with it would seem to be
useful to tag podcast streams.

Consider for example the NPR Radio show "This American Life". It's got
multiple distinct audio segments each show, as well as introductory,
transitional, and conclusion audio segments. It would be nice if within the
mp3 tag we could mark the offsets into the mp3 where these parts of the
broadcast exist, so that a program that reads the tag could provide a link
into the mp3 to the point where the segment begins or ends.

As another example consider a sports event. The final broadcast might
provide links to an outline of a game, in American football, maybe the
beginning and ending of downs, particular penalty or injury breaks, points
scored - key plays. etc.

Further it would be nice for the end user of a broadcast to be able to
highlight the segments he/she particular likes by adding labels and markers
within the header of the stream's tag, to provide a more customized index of
the broadcast.

I apology to the mailing list since this question is slightly off topic, but
I was hoping someone on the list subscribers could point me in the right
direction toward people who are working on this kind of thing.

Thank you for you time,
Shawn MacFarland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070512/b26a44d8/attachment.html>

From tsorensen at gmail.com  Mon May 21 12:44:40 2007
From: tsorensen at gmail.com (Tom Sorensen)
Date: Mon, 21 May 2007 15:44:40 -0400
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <4da424620705211244s1cc50d6dk7e37b5f4dd2cc14a@mail.gmail.com>

On what OS?

I've used both id3v2 and id3tag (and prefer the former) on a variety
of Linux systems. Both are only V2.3 though.

On 5/21/07, Chris Morton <chris at ca-dreaming.com> wrote:
> Can anyone recommend a *free* command-line driven MP3 tagger for batch
> processing? As a requisite, the tagger should accept parameters.

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From mike at ambientdesign.com  Wed May 16 21:18:41 2007
From: mike at ambientdesign.com (Mike van Bokhoven)
Date: Thu, 17 May 2007 16:18:41 +1200
Subject: [ID3 Dev] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke> <037501c79839$ecbb3c80$6501a8c0@xp1800desk>
Message-ID: <000f01c7983a$73b33d00$3c00a8c0@fluke>

Hi Jim,

Thanks for the quick response! OK, that's good - that's exactly what my code
does now. I thought I must be missing something obvious; I thought I'd
checked the frame size specs too, but obviously not! I'll have a read, and
update as required.

Mike.


----- Original Message ----- 
From: "Jim" <jmartin92 at comcast.net>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 4:14 PM
Subject: Re: [ID3 Dev] Sync-safe sizes?


> Hi Mike.
>
> Welcome to the list.  I think you are confusing the ID3 tag size,
contained
> in the tag header, with the frame size, which is contained in the frame
> header.
>
> In ID3v2.3 and ID3v2.4, the tag size contained in the tag header was
always
> a 32 bit syncsafe integer.  No change there.
>
>
> In ID3v2.3 and before, the frame size was NOT a syncsafe integer.  It was
> just a regular 32 bit integer.  In ID3v2.4, the frame size was changed to
a
> 32 bit syncsafe integer.  So you have to read the frame size differently
for
> ID3v2.4 and later.
>
> Check the frame overview section in the ID3v2.3 and ID3v2.4 specs.
>
> Jim
>
> ----- Original Message ----- 
> From: "Mike van Bokhoven" <mike at ambientdesign.com>
> To: <id3v2 at id3.org>
> Sent: Thursday, May 17, 2007 12:04 AM
> Subject: [ID3 Dev] Sync-safe sizes?
>
>
> > Hi! New list member here.
> >
> > I'm just writing in the hope of a bit of clarification regarding
sync-safe
> > words, mainly the sizes of the tag and frames. The 2.3 spec says:
> >
> > -------------------------------------------------------
> > ID3v2 size              4 * %0xxxxxxx
> > The ID3v2 tag size is encoded with four bytes where the most significant
> bit
> > (bit 7) is set to zero in every byte, making a total of 28 bits. The
> zeroed
> > bits are ignored, so a 257 bytes long tag is represented as $00 00 02
01.
> > -------------------------------------------------------
> >
> > The 2.4 spec says:
> >
> > -------------------------------------------------------
> > ID3v2 size             4 * %0xxxxxxx
> > The ID3v2 tag size is stored as a 32 bit synchsafe integer (section
6.2),
> > making a total of 28 effective bits (representing up to 256MB).
> >
> > -------------------------------------------------------
> >
> > As far as I can see, these two specs are identical with regards to these
> > fields. When I'm reading frames, I read in a word for the size.
Originally
> I
> > was compressing that value to ignore the missing bit. I found that that
> > didn't seem to work for any APIC frame (and I expect any frame with size
> > >127 bytes). On a little investigation, I discovered that the raw value
I
> > read in already represented the correct size, before the adjustment! But
> the
> > specs seem clear - both tag and frame sizes are represented by expanded,
> > sync-safe words.
> >
> > All the tags I'm looking at are version 3 (2.3). Doing some research, I
> > found one person claiming that 2.3 and earlier don't use sync-safe
words,
> > which disagrees with the spec, but agrees with my observations. I
haven't
> > been able to find out much more.
> >
> > My question is - what am I missing here? I can't believe that pretty
much
> > everyone who writes APIC frames is getting the encoding wrong...
> >
> > Thanks,
> >
> > Mike.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> > For additional commands, e-mail: id3v2-help at id3.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From chris at ca-dreaming.com  Tue May 22 10:09:17 2007
From: chris at ca-dreaming.com (Chris Morton)
Date: Tue, 22 May 2007 10:09:17 -0700
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <46524A14.9090900@gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
	 <46524A14.9090900@gmail.com>
Message-ID: <746d910c0705221009u29a0bed8o68b067217ba5f499@mail.gmail.com>

Hi Aaron,

I've installed Python and have uncompressed the eyeD3 gz. But I'm running
Windows, so have forgotten how to make an EXE I can use with this OS. Can
you jog my memory?

Thanks

> Chris


On 5/21/07, Aaron VonderHaar <gruen0aermel at gmail.com> wrote:
>
> eyeD3 is the most complete command-line tagger that I have found.  It
> supports v2.3 and v2.4 tags (and v1 tags).  It supports all text frames,
> images (APIC frames) and UFID frames.  It requires python.
>
> http://eyed3.nicfit.net/
>
>
> Chris Morton wrote:
> > Can anyone recommend a *free* command-line driven MP3 tagger for batch
> > processing? As a requisite, the tagger should accept parameters.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>


-- 
View my LinkedIn profile:
http://www.linkedin.com/in/ChrisMorton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070522/38f7731b/attachment.html>

From mkm6 at makuch.org  Mon May 21 15:18:59 2007
From: mkm6 at makuch.org (Michael Makuch)
Date: Mon, 21 May 2007 17:18:59 -0500
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <52c121940705211416i11044d5au61e34b2666501bb1@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com> <52c121940705211416i11044d5au61e34b2666501bb1@mail.gmail.com>
Message-ID: <002001c79bf6$07c77240$2b02a8c0@mesquite>

id3.exe, that appears to be my old command line id3 tagger utility. I put
that together several years ago from the id3lib examples.  See usage
below.

This zip http://www.muzikbrowzer.com/dl/id3.zip contains 

id3.cpp - source for id3 command line util (builds against id3lib
linux/win32)
id3 - linux binary
id3.exe - win32 binary
mbtag.exe - adds wma, ogg and flac support

Regards,

Mike

$ id3
id3 [options] <file> # w/out options display tag info.  options:
     -v      <value> # id3 version (1 or 2)
     -dt             # delete tag (version 1 or 2 if specified else both
     -df     <value> # delete tag field
     -getart <value> # getart, writes to <file>
     -TCON   <value> # genre
     -TPE1   <value> # artist
     -TALB   <value> # album
     -TIT2   <value> # title
     -TRCK   <value> # track
     -TLEN   <value> # length
     -TYER   <value> # year
     -TPOS   <value> # part in set
     -TPUB   <value> # publisher
     -UFID   <value> # ufid
     -TMED   <value> # dig...
     -COMM   <value> # comment
     -APIC   <value> # art file, reads from <file>



> -----Original Message-----
> From: L Cubed [mailto:lllcubed at gmail.com]
> Sent: Monday, May 21, 2007 4:17 PM
> To: id3v2 at id3.org
> Subject: Re: [ID3 Dev] Command-Line Batch Tagger
> 
> On 5/21/07, Chris Morton <chris at ca-dreaming.com> wrote:
> > Can anyone recommend a *free* command-line driven MP3 tagger for batch
> > processing? As a requisite, the tagger should accept parameters.
> 
> If you are looking tools to do old skool batch files, with conditional
> logic based on what is/isn't in the tags already...
> 
> There really isn't much available for Win32, but metamp3 *might* be
> helpful.
> 
> http://www.hydrogenaudio.org/forums/index.php?showtopic=49751
> 
> 
> Before I found this, I was using id3.exe (attached as a renamed zip
> file).  I don't know what the origin of this program is.
> 
> HTH,
> 
> LCubed


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From jmartin92 at comcast.net  Thu May 17 05:29:02 2007
From: jmartin92 at comcast.net (Jim)
Date: Thu, 17 May 2007 08:29:02 -0400
Subject: [ID3 Dev] [OT] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke> <039901c7983e$f245e650$6501a8c0@xp1800desk> <003301c79841$8e892fc0$3c00a8c0@fluke>
Message-ID: <001901c7987e$f531c790$6501a8c0@xp1800desk>

Ok.  I figured that might be the case but just wanted to make sure you
weren't reading only half of it.

Jim

----- Original Message ----- 
From: "Mike van Bokhoven" <mike at ambientdesign.com>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 1:09 AM
Subject: Re: [ID3 Dev] [OT] Sync-safe sizes?


> I mean word in this sense:
>
> http://www.webopedia.com/TERM/w/word2.html
> http://www.computeruser.com/resources/dictionary/dictionary.html
>
> In this case, as I'm writing for 32-bit platforms only, I mean 32 bits,
but
> I guess it could mean pretty much any size that could be argued to be
native
> to a given platform in some way. e.g. if I were writing for a PDP8, I'd
mean
> 12 bits. So, I should have been more specific!
>
> Mike.
>
>
>
>
> ----- Original Message ----- 
> From: "Jim" <jmartin92 at comcast.net>
> To: <id3v2 at id3.org>
> Sent: Thursday, May 17, 2007 4:50 PM
> Subject: Re: [ID3 Dev] Sync-safe sizes?
>
>
> > This is a little off-topic, but why are you reading in a word for the
> frame
> > size?  (Does word in this context mean 16 bits or 32 bits?)
> >
> > ----- Original Message ----- 
> > From: "Mike van Bokhoven" <mike at ambientdesign.com>
> > To: <id3v2 at id3.org>
> > Sent: Thursday, May 17, 2007 12:04 AM
> > Subject: [ID3 Dev] Sync-safe sizes?
> >
> >
> > > Hi! New list member here.
> > >
> > > I'm just writing in the hope of a bit of clarification regarding
> sync-safe
> > > words, mainly the sizes of the tag and frames. The 2.3 spec says:
> > >
> > > -------------------------------------------------------
> > > ID3v2 size              4 * %0xxxxxxx
> > > The ID3v2 tag size is encoded with four bytes where the most
significant
> > bit
> > > (bit 7) is set to zero in every byte, making a total of 28 bits. The
> > zeroed
> > > bits are ignored, so a 257 bytes long tag is represented as $00 00 02
> 01.
> > > -------------------------------------------------------
> > >
> > > The 2.4 spec says:
> > >
> > > -------------------------------------------------------
> > > ID3v2 size             4 * %0xxxxxxx
> > > The ID3v2 tag size is stored as a 32 bit synchsafe integer (section
> 6.2),
> > > making a total of 28 effective bits (representing up to 256MB).
> > >
> > > -------------------------------------------------------
> > >
> > > As far as I can see, these two specs are identical with regards to
these
> > > fields. When I'm reading frames, I read in a word for the size.
> Originally
> > I
> > > was compressing that value to ignore the missing bit. I found that
that
> > > didn't seem to work for any APIC frame (and I expect any frame with
size
> > > >127 bytes). On a little investigation, I discovered that the raw
value
> I
> > > read in already represented the correct size, before the adjustment!
But
> > the
> > > specs seem clear - both tag and frame sizes are represented by
expanded,
> > > sync-safe words.
> > >
> > > All the tags I'm looking at are version 3 (2.3). Doing some research,
I
> > > found one person claiming that 2.3 and earlier don't use sync-safe
> words,
> > > which disagrees with the spec, but agrees with my observations. I
> haven't
> > > been able to find out much more.
> > >
> > > My question is - what am I missing here? I can't believe that pretty
> much
> > > everyone who writes APIC frames is getting the encoding wrong...
> > >
> > > Thanks,
> > >
> > > Mike.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> > > For additional commands, e-mail: id3v2-help at id3.org
> > >
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> > For additional commands, e-mail: id3v2-help at id3.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From jmartin92 at comcast.net  Wed May 16 21:14:52 2007
From: jmartin92 at comcast.net (Jim)
Date: Thu, 17 May 2007 00:14:52 -0400
Subject: [ID3 Dev] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke>
Message-ID: <037501c79839$ecbb3c80$6501a8c0@xp1800desk>

Hi Mike.

Welcome to the list.  I think you are confusing the ID3 tag size, contained
in the tag header, with the frame size, which is contained in the frame
header.

In ID3v2.3 and ID3v2.4, the tag size contained in the tag header was always
a 32 bit syncsafe integer.  No change there.


In ID3v2.3 and before, the frame size was NOT a syncsafe integer.  It was
just a regular 32 bit integer.  In ID3v2.4, the frame size was changed to a
32 bit syncsafe integer.  So you have to read the frame size differently for
ID3v2.4 and later.

Check the frame overview section in the ID3v2.3 and ID3v2.4 specs.

Jim

----- Original Message ----- 
From: "Mike van Bokhoven" <mike at ambientdesign.com>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 12:04 AM
Subject: [ID3 Dev] Sync-safe sizes?


> Hi! New list member here.
>
> I'm just writing in the hope of a bit of clarification regarding sync-safe
> words, mainly the sizes of the tag and frames. The 2.3 spec says:
>
> -------------------------------------------------------
> ID3v2 size              4 * %0xxxxxxx
> The ID3v2 tag size is encoded with four bytes where the most significant
bit
> (bit 7) is set to zero in every byte, making a total of 28 bits. The
zeroed
> bits are ignored, so a 257 bytes long tag is represented as $00 00 02 01.
> -------------------------------------------------------
>
> The 2.4 spec says:
>
> -------------------------------------------------------
> ID3v2 size             4 * %0xxxxxxx
> The ID3v2 tag size is stored as a 32 bit synchsafe integer (section 6.2),
> making a total of 28 effective bits (representing up to 256MB).
>
> -------------------------------------------------------
>
> As far as I can see, these two specs are identical with regards to these
> fields. When I'm reading frames, I read in a word for the size. Originally
I
> was compressing that value to ignore the missing bit. I found that that
> didn't seem to work for any APIC frame (and I expect any frame with size
> >127 bytes). On a little investigation, I discovered that the raw value I
> read in already represented the correct size, before the adjustment! But
the
> specs seem clear - both tag and frame sizes are represented by expanded,
> sync-safe words.
>
> All the tags I'm looking at are version 3 (2.3). Doing some research, I
> found one person claiming that 2.3 and earlier don't use sync-safe words,
> which disagrees with the spec, but agrees with my observations. I haven't
> been able to find out much more.
>
> My question is - what am I missing here? I can't believe that pretty much
> everyone who writes APIC frames is getting the encoding wrong...
>
> Thanks,
>
> Mike.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From gruen0aermel at gmail.com  Mon May 21 18:40:36 2007
From: gruen0aermel at gmail.com (Aaron VonderHaar)
Date: Mon, 21 May 2007 18:40:36 -0700
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <46524A14.9090900@gmail.com>

eyeD3 is the most complete command-line tagger that I have found.  It 
supports v2.3 and v2.4 tags (and v1 tags).  It supports all text frames, 
images (APIC frames) and UFID frames.  It requires python.

http://eyed3.nicfit.net/


Chris Morton wrote:
> Can anyone recommend a *free* command-line driven MP3 tagger for batch 
> processing? As a requisite, the tagger should accept parameters.


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From chris.newell at rd.bbc.co.uk  Mon May 14 01:48:39 2007
From: chris.newell at rd.bbc.co.uk (Chris Newell)
Date: Mon, 14 May 2007 09:48:39 +0100
Subject: [ID3 Dev] Introductory question
In-Reply-To: <32cccae20705121452n488a24c9oeb40f985c8bb6e85@mail.gmail.co
 m>
References: <32cccae20705121452n488a24c9oeb40f985c8bb6e85@mail.gmail.com>
Message-ID: <6.2.0.14.2.20070514093742.02b21528@pop3>

At 22:52 12/05/2007, Shawn MacFarland wrote:
>I was wondering about how broadcast (podcast) streams should be tagged. ID3 does an excellent job of providing song recording information, and the basic structure of the tag or something very compatible with it would seem to be useful to tag podcast streams. 
>
>Consider for example the NPR Radio show "This American Life". It's got multiple distinct audio segments each show, as well as introductory, transitional, and conclusion audio segments. It would be nice if within the mp3 tag we could mark the offsets into the mp3 where these parts of the broadcast exist, so that a program that reads the tag could provide a link into the mp3 to the point where the segment begins or ends. 
>
>As another example consider a sports event. The final broadcast might provide links to an outline of a game, in American football, maybe the beginning and ending of downs, particular penalty or injury breaks, points scored - key plays. etc. 
>
>Further it would be nice for the end user of a broadcast to be able to highlight the segments he/she particular likes by adding labels and markers within the header of the stream's tag, to provide a more customized index of the broadcast. 

Shawn,

The new ID3v2 Chapter Addendum can do all of these things. It's available here:

   http://www.id3.org/id3v2-chapters-1.0

Unfortunately. it's not widely supported by authoring systems or media players as yet.

>I was hoping someone on the list subscribers could point me in the right direction toward people who are working on this kind of thing.

There is a Sourceforge project which provides an authoring tool for ID3v2 Chapters here:

   http://id3v2-chap-tool.sourceforge.net/

There is a commercial media player (for Pocket PCs and Smart Phones) which supports ID3v2 Chapters here:

   <http://www.conduits.com/news/pr20060925.html>http://www.conduits.com/news/pr20060925.html  

The BBC produces a weekly podcast which includes ID3v2 Chapters signalling here:

   <http://www.bbc.co.uk/rd/navigate/podcast/rss.xml>http://www.bbc.co.uk/rd/navigate/podcast/rss2.xml  

This is all the activity I'm currently aware of. If you want any help to get started with ID3v2 Chapters please let me know.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070514/76f6a75d/attachment.html>

From chris at ca-dreaming.com  Tue May 15 15:33:50 2007
From: chris at ca-dreaming.com (Chris Morton)
Date: Tue, 15 May 2007 15:33:50 -0700
Subject: [ID3 Dev] Free Command-Line ID3v2 Tagger
Message-ID: <746d910c0705151533g71810629x6974beee24850697@mail.gmail.com>

Hi All,

I'm looking for a free command-line ID3v2 tagger that I can add to an
automated routine I'm writing. The tagger should be able to accept variables
for input, and if a suitable JPG is in the source folder, it should know to
use that as the album art.

Any recommendations?

Thanks!

-- 
View my LinkedIn profile:
http://www.linkedin.com/in/ChrisMorton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070515/1fb9a1dc/attachment.html>

From jmartin92 at comcast.net  Wed May 16 21:50:46 2007
From: jmartin92 at comcast.net (Jim)
Date: Thu, 17 May 2007 00:50:46 -0400
Subject: [ID3 Dev] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke>
Message-ID: <039901c7983e$f245e650$6501a8c0@xp1800desk>

This is a little off-topic, but why are you reading in a word for the frame
size?  (Does word in this context mean 16 bits or 32 bits?)

----- Original Message ----- 
From: "Mike van Bokhoven" <mike at ambientdesign.com>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 12:04 AM
Subject: [ID3 Dev] Sync-safe sizes?


> Hi! New list member here.
>
> I'm just writing in the hope of a bit of clarification regarding sync-safe
> words, mainly the sizes of the tag and frames. The 2.3 spec says:
>
> -------------------------------------------------------
> ID3v2 size              4 * %0xxxxxxx
> The ID3v2 tag size is encoded with four bytes where the most significant
bit
> (bit 7) is set to zero in every byte, making a total of 28 bits. The
zeroed
> bits are ignored, so a 257 bytes long tag is represented as $00 00 02 01.
> -------------------------------------------------------
>
> The 2.4 spec says:
>
> -------------------------------------------------------
> ID3v2 size             4 * %0xxxxxxx
> The ID3v2 tag size is stored as a 32 bit synchsafe integer (section 6.2),
> making a total of 28 effective bits (representing up to 256MB).
>
> -------------------------------------------------------
>
> As far as I can see, these two specs are identical with regards to these
> fields. When I'm reading frames, I read in a word for the size. Originally
I
> was compressing that value to ignore the missing bit. I found that that
> didn't seem to work for any APIC frame (and I expect any frame with size
> >127 bytes). On a little investigation, I discovered that the raw value I
> read in already represented the correct size, before the adjustment! But
the
> specs seem clear - both tag and frame sizes are represented by expanded,
> sync-safe words.
>
> All the tags I'm looking at are version 3 (2.3). Doing some research, I
> found one person claiming that 2.3 and earlier don't use sync-safe words,
> which disagrees with the spec, but agrees with my observations. I haven't
> been able to find out much more.
>
> My question is - what am I missing here? I can't believe that pretty much
> everyone who writes APIC frames is getting the encoding wrong...
>
> Thanks,
>
> Mike.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From mike at ambientdesign.com  Wed May 16 22:09:33 2007
From: mike at ambientdesign.com (Mike van Bokhoven)
Date: Thu, 17 May 2007 17:09:33 +1200
Subject: [ID3 Dev] [OT] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke> <039901c7983e$f245e650$6501a8c0@xp1800desk>
Message-ID: <003301c79841$8e892fc0$3c00a8c0@fluke>

I mean word in this sense:

http://www.webopedia.com/TERM/w/word2.html
http://www.computeruser.com/resources/dictionary/dictionary.html

In this case, as I'm writing for 32-bit platforms only, I mean 32 bits, but
I guess it could mean pretty much any size that could be argued to be native
to a given platform in some way. e.g. if I were writing for a PDP8, I'd mean
12 bits. So, I should have been more specific!

Mike.




----- Original Message ----- 
From: "Jim" <jmartin92 at comcast.net>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 4:50 PM
Subject: Re: [ID3 Dev] Sync-safe sizes?


> This is a little off-topic, but why are you reading in a word for the
frame
> size?  (Does word in this context mean 16 bits or 32 bits?)
>
> ----- Original Message ----- 
> From: "Mike van Bokhoven" <mike at ambientdesign.com>
> To: <id3v2 at id3.org>
> Sent: Thursday, May 17, 2007 12:04 AM
> Subject: [ID3 Dev] Sync-safe sizes?
>
>
> > Hi! New list member here.
> >
> > I'm just writing in the hope of a bit of clarification regarding
sync-safe
> > words, mainly the sizes of the tag and frames. The 2.3 spec says:
> >
> > -------------------------------------------------------
> > ID3v2 size              4 * %0xxxxxxx
> > The ID3v2 tag size is encoded with four bytes where the most significant
> bit
> > (bit 7) is set to zero in every byte, making a total of 28 bits. The
> zeroed
> > bits are ignored, so a 257 bytes long tag is represented as $00 00 02
01.
> > -------------------------------------------------------
> >
> > The 2.4 spec says:
> >
> > -------------------------------------------------------
> > ID3v2 size             4 * %0xxxxxxx
> > The ID3v2 tag size is stored as a 32 bit synchsafe integer (section
6.2),
> > making a total of 28 effective bits (representing up to 256MB).
> >
> > -------------------------------------------------------
> >
> > As far as I can see, these two specs are identical with regards to these
> > fields. When I'm reading frames, I read in a word for the size.
Originally
> I
> > was compressing that value to ignore the missing bit. I found that that
> > didn't seem to work for any APIC frame (and I expect any frame with size
> > >127 bytes). On a little investigation, I discovered that the raw value
I
> > read in already represented the correct size, before the adjustment! But
> the
> > specs seem clear - both tag and frame sizes are represented by expanded,
> > sync-safe words.
> >
> > All the tags I'm looking at are version 3 (2.3). Doing some research, I
> > found one person claiming that 2.3 and earlier don't use sync-safe
words,
> > which disagrees with the spec, but agrees with my observations. I
haven't
> > been able to find out much more.
> >
> > My question is - what am I missing here? I can't believe that pretty
much
> > everyone who writes APIC frames is getting the encoding wrong...
> >
> > Thanks,
> >
> > Mike.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> > For additional commands, e-mail: id3v2-help at id3.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From mike at ambientdesign.com  Wed May 16 21:04:20 2007
From: mike at ambientdesign.com (Mike van Bokhoven)
Date: Thu, 17 May 2007 16:04:20 +1200
Subject: [ID3 Dev] Sync-safe sizes?
Message-ID: <003b01c79838$741fcc60$3c00a8c0@fluke>

Hi! New list member here.

I'm just writing in the hope of a bit of clarification regarding sync-safe
words, mainly the sizes of the tag and frames. The 2.3 spec says:

-------------------------------------------------------
ID3v2 size              4 * %0xxxxxxx
The ID3v2 tag size is encoded with four bytes where the most significant bit
(bit 7) is set to zero in every byte, making a total of 28 bits. The zeroed
bits are ignored, so a 257 bytes long tag is represented as $00 00 02 01.
-------------------------------------------------------

The 2.4 spec says:

-------------------------------------------------------
ID3v2 size             4 * %0xxxxxxx
The ID3v2 tag size is stored as a 32 bit synchsafe integer (section 6.2),
making a total of 28 effective bits (representing up to 256MB).

-------------------------------------------------------

As far as I can see, these two specs are identical with regards to these
fields. When I'm reading frames, I read in a word for the size. Originally I
was compressing that value to ignore the missing bit. I found that that
didn't seem to work for any APIC frame (and I expect any frame with size
>127 bytes). On a little investigation, I discovered that the raw value I
read in already represented the correct size, before the adjustment! But the
specs seem clear - both tag and frame sizes are represented by expanded,
sync-safe words.

All the tags I'm looking at are version 3 (2.3). Doing some research, I
found one person claiming that 2.3 and earlier don't use sync-safe words,
which disagrees with the spec, but agrees with my observations. I haven't
been able to find out much more.

My question is - what am I missing here? I can't believe that pretty much
everyone who writes APIC frames is getting the encoding wrong...

Thanks,

Mike.


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From jmartin92 at comcast.net  Tue May 29 07:41:23 2007
From: jmartin92 at comcast.net (Jim)
Date: Tue, 29 May 2007 10:41:23 -0400
Subject: [ID3 Dev] patents
References: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net> <20070529134849.GA22498@ayup.limey.net> <465C2F91.1080707@mp3tag.de> <09C1E299-8880-48EA-BBF4-7260BB2878A4@maseurope.net> <465C38C7.70607@fastmail.fm>
Message-ID: <001901c7a1ff$72e34d60$6501a8c0@xp1800desk>

I'm guessing he's talking about Microsoft getting nailed with a 1.5 billion
judgment for violating an Alcatel-Lucent patent.

----- Original Message ----- 
From: "Paul Taylor" <paul_t100 at fastmail.fm>
To: <id3v2 at id3.org>
Sent: Tuesday, May 29, 2007 10:29 AM
Subject: Re: [ID3 Dev] patents


> What has happened with MP3 patents ?
>
> Mark Smith wrote:
> > That is pretty much my reading of things, but I thought it might be
> > interesting raise it here, since it came up on another list.
> >
> > best,
> >
> > Mark
> >
> > On 29 May 2007, at 14:50, Florian Heidenreich wrote:
> >
> >> In addition to what Ben said, ID3 tags (neither ID3v1 nor ID3v2) are
> >> part of the MP3 spec so we should be on the safe side.
> >>
> >> Kind regards,
> >> Florian
> >>
> >>
> >> Ben Bennett schrieb:
> >>> It is better not to know.  Really.
> >>> You get nailed for the serious money for wilful infringement.
> >>> However, tagging doesn't know (or at least need to know) about any of
> >>> the internal details of mp3 tags.  You could theoretically apply ID3v2
> >>> tags to a word doc, a jpeg, or whatever you wanted.  Now... the target
> >>> app probably couldn't read it with the leading "junk", but that's a
> >>> different story.
> >>>          -ben
> >>> On Tue, May 29, 2007 at 02:25:11PM +0100, Mark Smith wrote:
> >>>> Does anyone know, or have a view about, whether the recent
> >>>> courtroom  shenanigans regarding mp3 patents have any bearing on
> >>>> the creation  and use of ID3 tags? Particularly whether or not we,
> >>>> as developers of  tagging software, have anything to be concerned
> >>>> about.
> >>>>
> >>>> It seems that maybe doing anything even vaguely connected with mp3
> >>>> could be seen as swimming in shark-infested waters.
> >>>>
> >>>> best,
> >>>>
> >>>> Mark Smith
> >>
> >> --Mp3tag - the universal Tag editor
> >> http://www.mp3tag.de/en/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> >> For additional commands, e-mail: id3v2-help at id3.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> > For additional commands, e-mail: id3v2-help at id3.org
> >
> >
> >
> > --Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.446 / Virus Database: 269.0.0/756 - Release Date:
> > 06/04/2007 00:00
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From gruen0aermel at gmail.com  Wed May 23 11:44:53 2007
From: gruen0aermel at gmail.com (Aaron VonderHaar)
Date: Wed, 23 May 2007 11:44:53 -0700
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705221009u29a0bed8o68b067217ba5f499@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>	 <46524A14.9090900@gmail.com> <746d910c0705221009u29a0bed8o68b067217ba5f499@mail.gmail.com>
Message-ID: <46548BA5.5030108@gmail.com>

Chris, I haven't been using Windows recently, but there are some tips 
here, http://www.thescripts.com/forum/thread642594.html

It looks like basically to install, you will need to go into the 
unzipped folder from the command line and run `python setup.py install` 
to install the python modules into the correct location.

Then to use eyeD3, you will need to run `python /path/to/eyeD3`, and if 
that works, you could possibly create an eyeD3.bat file and put it in 
your $PATH.

REM Sample eyeD3.bat
python /path/to/eyeD3 %*
REM end of Sample eyeD3.bat

Good luck,
--Aaron V.

Chris Morton wrote:
> Hi Aaron,
>  
> I've installed Python and have uncompressed the eyeD3 gz. But I'm 
> running Windows, so have forgotten how to make an EXE I can use with 
> this OS. Can you jog my memory?
>  
> Thanks
>  
>  > Chris
> 
>  
> On 5/21/07, *Aaron VonderHaar* <gruen0aermel at gmail.com 
> <mailto:gruen0aermel at gmail.com>> wrote:
> 
>     eyeD3 is the most complete command-line tagger that I have found.  It
>     supports v2.3 and v2.4 tags (and v1 tags).  It supports all text
>     frames,
>     images (APIC frames) and UFID frames.  It requires python.
> 
>     http://eyed3.nicfit.net/
> 
> 
>     Chris Morton wrote:
>      > Can anyone recommend a *free* command-line driven MP3 tagger for
>     batch
>      > processing? As a requisite, the tagger should accept parameters.
> 
> 
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
>     <mailto:id3v2-unsubscribe at id3.org>
>     For additional commands, e-mail: id3v2-help at id3.org
>     <mailto:id3v2-help at id3.org>
> 
> 
> 
> 
> -- 
> View my LinkedIn profile:
> http://www.linkedin.com/in/ChrisMorton


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From babak.sayyid at gmail.com  Mon May 28 05:58:28 2007
From: babak.sayyid at gmail.com (Babak S. Hosseini)
Date: Mon, 28 May 2007 14:58:28 +0200
Subject: [ID3 Dev] Measuring the length of an id3v2 tag inside an mp3
Message-ID: <6efe9a9b0705280558rb518e0bse9896ac9ed3125ab@mail.gmail.com>

Hello,
I'm trying to measure the length of the ID3v2 block inside an mp3 file.
In the specification a 257 bytes long tag is represented as $00 00 02 01.
How is that mapped? Can someone explain it in detail ?


Header:
ID3v2/file identifier   "ID3"
ID3v2 version           $03 00
ID3v2 flags             %abc00000
ID3v2 size              4 * %0xxxxxxx

The first 10 Bytes of my mp3 file have the following content:
0x49 0x44 0x33 0x03 0x00 0x00 0x00 0x04 0x3F 0x23

According to the specification, the length of the id3 block size is
encoded in:
0x00 0x04 0x3F 0x23

How many bytes does this encode?

Thanks.

-- 
ttyl.

Babak Sayyid Hosseini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070528/f5e50b42/attachment.html>

From id3v2 at northpb.com  Tue May 15 12:17:30 2007
From: id3v2 at northpb.com (Dan O'Neill)
Date: Tue, 15 May 2007 12:17:30 -0700
Subject: [ID3 Dev] Someone is looking for Eric Kemp
Message-ID: <464A074A.4050503@northpb.com>

Is Eric Kemp on this list?  If you know him, please forward this note.

Thanks,

dano


-------- Original Message --------
Date: 	Tue, 15 May 2007 15:06:03 -0400
From: 	<david.schlitz at bakerbotts.com>
To: 	<dano at id3.org>



I am trying to reach Eric Kemp.  I need to ask him a question about a
project.  Do you have contact information for him.

David Schlitz

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From mike at ambientdesign.com  Wed May 16 21:41:55 2007
From: mike at ambientdesign.com (Mike van Bokhoven)
Date: Thu, 17 May 2007 16:41:55 +1200
Subject: [ID3 Dev] Sync-safe sizes?
References: <003b01c79838$741fcc60$3c00a8c0@fluke>    <037501c79839$ecbb3c80$6501a8c0@xp1800desk>    <000f01c7983a$73b33d00$3c00a8c0@fluke> <1901.10.180.190.36.1179376327.squirrel@mail.winamp.com>
Message-ID: <002501c7983d$b25fd380$3c00a8c0@fluke>

I was wondering about that - I was beginning to think about really awful
ways to verify the frame size, such as checking for an apparently valid
frame header following each frame before the last one. Wrong for several
reasons, but when reading a 2.4 frame with obviously invalid sizes, what
else can be done?

For now, my app will continue to write 2.3 by default I think, it seems
safer. Once I get to grips with ID3 better (have been working with it for
the grand total of a day or so) I might look at going to 2.4, if the support
is out there. 2.3's been quite co-operative in general; I'm reading, parsing
and updating the basic standard frames, and writing all frames out again.
Working on APIC support now, hence the size problem!

Thanks again for the info,

Mike.



----- Original Message ----- 
From: "Ben Allison" <benski at winamp.com>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 4:32 PM
Subject: Re: [ID3 Dev] Sync-safe sizes?


> Applications not writing syncsafe frame sizes in ID3v2.4 has been a major
> issue for widespread adoption of 2.4.  I'm sure the mailing list archives
> have more to say - unfortunately there's not an easy answer.
>
> -Ben Allison
>
> > Hi Jim,
> >
> > Thanks for the quick response! OK, that's good - that's exactly what my
> > code
> > does now. I thought I must be missing something obvious; I thought I'd
> > checked the frame size specs too, but obviously not! I'll have a read,
and
> > update as required.
> >
> > Mike.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From lllcubed at gmail.com  Mon May 21 14:16:54 2007
From: lllcubed at gmail.com (L Cubed)
Date: Mon, 21 May 2007 16:16:54 -0500
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <52c121940705211416i11044d5au61e34b2666501bb1@mail.gmail.com>

On 5/21/07, Chris Morton <chris at ca-dreaming.com> wrote:
> Can anyone recommend a *free* command-line driven MP3 tagger for batch
> processing? As a requisite, the tagger should accept parameters.

If you are looking tools to do old skool batch files, with conditional
logic based on what is/isn't in the tags already...

There really isn't much available for Win32, but metamp3 *might* be helpful.

http://www.hydrogenaudio.org/forums/index.php?showtopic=49751


Before I found this, I was using id3.exe (attached as a renamed zip
file).  I don't know what the origin of this program is.

HTH,

LCubed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: id3.z__
Type: application/octet-stream
Size: 296009 bytes
Desc: not available
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070521/6fa3a151/attachment.obj>
-------------- next part --------------
---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org

From mark at maseurope.net  Tue May 29 06:25:11 2007
From: mark at maseurope.net (Mark Smith)
Date: Tue, 29 May 2007 14:25:11 +0100
Subject: [ID3 Dev] patents
Message-ID: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net>

Does anyone know, or have a view about, whether the recent courtroom  
shenanigans regarding mp3 patents have any bearing on the creation  
and use of ID3 tags? Particularly whether or not we, as developers of  
tagging software, have anything to be concerned about.

It seems that maybe doing anything even vaguely connected with mp3  
could be seen as swimming in shark-infested waters.

best,

Mark Smith



---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From chris at ca-dreaming.com  Mon May 21 11:59:35 2007
From: chris at ca-dreaming.com (Chris Morton)
Date: Mon, 21 May 2007 11:59:35 -0700
Subject: [ID3 Dev] Command-Line Batch Tagger
Message-ID: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>

Can anyone recommend a *free* command-line driven MP3 tagger for batch
processing? As a requisite, the tagger should accept parameters.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20070521/fa79c408/attachment.html>

From fiji at ayup.limey.net  Thu May 17 05:58:36 2007
From: fiji at ayup.limey.net (Ben Bennett)
Date: Thu, 17 May 2007 08:58:36 -0400
Subject: [ID3 Dev] Sync-safe sizes?
In-Reply-To: <002501c7983d$b25fd380$3c00a8c0@fluke>
References: <003b01c79838$741fcc60$3c00a8c0@fluke> <037501c79839$ecbb3c80$6501a8c0@xp1800desk> <000f01c7983a$73b33d00$3c00a8c0@fluke> <1901.10.180.190.36.1179376327.squirrel@mail.winamp.com> <002501c7983d$b25fd380$3c00a8c0@fluke>
Message-ID: <20070517125836.GA25612@ayup.limey.net>

On Thu, May 17, 2007 at 04:41:55PM +1200, Mike van Bokhoven wrote:
> I was wondering about that - I was beginning to think about really awful
> ways to verify the frame size, such as checking for an apparently valid
> frame header following each frame before the last one. Wrong for several
> reasons, but when reading a 2.4 frame with obviously invalid sizes, what
> else can be done?

Unfortunately that is all we can recommend.
 
> For now, my app will continue to write 2.3 by default I think, it seems
> safer. Once I get to grips with ID3 better (have been working with it for
> the grand total of a day or so) I might look at going to 2.4, if the support
> is out there. 2.3's been quite co-operative in general; I'm reading, parsing
> and updating the basic standard frames, and writing all frames out again.
> Working on APIC support now, hence the size problem!

2.3 support is far more consistent and writing 2.3 frames is the best
you can do if you want wide interoperability.  Unfortunately taglib
gets the meaning of some 2.3 stuff wrong and only writes (valid) 2.4.
But 2.3 is still a better choice 'cause it at least can be read.

As noted by others, there are a couple of threads about this in the
archives.  Someone from Apple was paying attention for a while and
there were noises about getting the 2.4 frame sizes fixed... but I am
not holding my breath.

		   -ben

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From jid3 at blinkenlights.org  Mon May 21 15:45:21 2007
From: jid3 at blinkenlights.org (Paul Grebenc)
Date: Mon, 21 May 2007 18:45:21 -0400 (EDT)
Subject: [ID3 Dev] Command-Line Batch Tagger
In-Reply-To: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
References: <746d910c0705211159i71a14faah19898abc112c8f5@mail.gmail.com>
Message-ID: <Pine.LNX.4.63.0705211843030.3164@localhost.localdomain>


JID3 comes with a limited command-line mode.  It's just an executable jar, 
but you can run it from the command line, passing parameters.  Adding new 
options for features not available via command line would be very simple.

http://jid3.blinkenlights.org

Paul


On Mon, 21 May 2007, Chris Morton wrote:

> Can anyone recommend a *free* command-line driven MP3 tagger for batch
> processing? As a requisite, the tagger should accept parameters.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org


From mark at maseurope.net  Tue May 29 07:03:30 2007
From: mark at maseurope.net (Mark Smith)
Date: Tue, 29 May 2007 15:03:30 +0100
Subject: [ID3 Dev] patents
In-Reply-To: <465C2F91.1080707@mp3tag.de>
References: <D8365F3E-AB97-47DA-8CAE-20427DAFF2B9@maseurope.net> <20070529134849.GA22498@ayup.limey.net> <465C2F91.1080707@mp3tag.de>
Message-ID: <09C1E299-8880-48EA-BBF4-7260BB2878A4@maseurope.net>

That is pretty much my reading of things, but I thought it might be  
interesting raise it here, since it came up on another list.

best,

Mark

On 29 May 2007, at 14:50, Florian Heidenreich wrote:

> In addition to what Ben said, ID3 tags (neither ID3v1 nor ID3v2)  
> are part of the MP3 spec so we should be on the safe side.
>
> Kind regards,
> Florian
>
>
> Ben Bennett schrieb:
>> It is better not to know.  Really.
>> You get nailed for the serious money for wilful infringement.
>> However, tagging doesn't know (or at least need to know) about any of
>> the internal details of mp3 tags.  You could theoretically apply  
>> ID3v2
>> tags to a word doc, a jpeg, or whatever you wanted.  Now... the  
>> target
>> app probably couldn't read it with the leading "junk", but that's a
>> different story.
>> 		 -ben
>> On Tue, May 29, 2007 at 02:25:11PM +0100, Mark Smith wrote:
>>> Does anyone know, or have a view about, whether the recent  
>>> courtroom  shenanigans regarding mp3 patents have any bearing on  
>>> the creation  and use of ID3 tags? Particularly whether or not  
>>> we, as developers of  tagging software, have anything to be  
>>> concerned about.
>>>
>>> It seems that maybe doing anything even vaguely connected with  
>>> mp3  could be seen as swimming in shark-infested waters.
>>>
>>> best,
>>>
>>> Mark Smith
>
> -- 
> Mp3tag - the universal Tag editor
> http://www.mp3tag.de/en/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org