search for: id3v2

Hi, I've been working writing some tools that deal with id3v2 tags on mp3 files. id3v2 is this really, really long specification with places for all kinds of metadata for media. I've looking at the sample vorbis encoder and a file I made from it I noted that you have some a comment field, and I was wondering if you had any plans to support more...

...hen I noticed the truncated ID3 tags in my FLAC files. I at first thought the problem lied in FLAC; I posted to this list, hoping for a solution. But then I realized my trusty GRIP was the flawed program. Now re-ripping my CDs, I want to do it right. I need either a program that either adds the ID3V2 tags directly to the files (a better ripper), or a program that takes ID3V1 truncat- tags, queries FreeDB, gets the whole track name, and puts it into an ID3V2 tag. Has anyone used a free ripper that supports FLAC and ID3V2 tags? If so, let me know! Thanks everyone, especially Josh for this code...

I tagged some FLAC files with ID3V2 information (by the id3v2 program), but their metadata does not show up in XMMS. Anyone else have this problem? Anyone have a solution? (I tested the tags using the --list option of id3v2; they are there. XMMS and the FLAC plugin just don't seem to respect them.) -- Asheesh.

Hi Josh, I found id3v2 didn't work on v1.1.0. I checked source codes, macros- (in such cases as FLAC_HAVE_ID3LIB) ware moved to config.h. That is good. But the place to do include is the after of #ifdef FLAC_HAVE_ID3LIB. The result of configure script isn't reflected. And it doesn't always have id3lib with th...

> A good number have id3v2 tags... say 20-30%. Do you find that it's stuttering on id3v2 files? Since those contain data that is counted by the timing code, but not played the the player, that seems a likely suspect. Ie, you'll get _playable_ data too slow. Try a stream with _no_ id3v2 files and see if the proble...

...%s as a command line option to FLAC (eac variable for the wav filename). Checking or unchecking "Using CRC check" doesn't seem to do anything as far as I can tell. However, checking "Add ID3 tags" breaks FLAC. EAC is using the default options of "Additionally write ID3V2 tags, using a padding of 4kB". After ripping and encoding, metaflac reports: ERROR: not a FLAC file (no 'fLaC' header) I don't know how to troubleshoot this further, so any suggestions would be great. On the files that do get created correctly (either using flac as an extern...

...tell. this probably a left-over from MP3 encoder usage. leave it off to be safe so it doesn't pollute the command line. flac'c crc checking is always on. > However, checking "Add ID3 tags" breaks FLAC. EAC is using the > default > options of "Additionally write ID3V2 tags, using a padding of 4kB". > After > ripping and encoding, metaflac reports: > ERROR: not a FLAC file (no 'fLaC' header) > I don't know how to troubleshoot this further, so any suggestions > would be > great. ID3V2 tags go at the front of the file and s...

Lo and behold, the new version of grip (http://www.nostatic.org/grip) has ID3V2 support. I want to be able to rip from grip, extract the data from the FLACs into WAVs, normalize the WAVs, then re-encode them into FLACs. How can I make sure the ID3V1 and ID3V2 tags stored by grip are saved in between the FLACs? What shell commands can I use to store the tags in a temp file?...

Its file name is plugin_common/id3v2.c. I forgot to write. Sorry. On Sat, 29 Mar 2003 02:34:30 +0900 Daisuke Shimamura <Daisuke_Shimamura@nifty.com> wrote: > Hi Josh, > > I found id3v2 didn't work on v1.1.0. I checked source codes, macros- (in > such cases as FLAC_HAVE_ID3LIB) ware moved to config.h. That is go...

hey, as far as ogg option goes, am i correct to assume that it is only usefull so that you can use anything that supports ogg to play the files on another note, how can i add id3v2 tags to native flac files? is there are command line player for flac? thanx for the help. ben

...e: > > > > maybe tagging. i think that id3 tag isn't enough 'cause it > supports only 30 > > > character strings and don't fulfil a requirement of > internationalization i > > > mentioned before. > > > > > The decoder properly ignores id3v2 tags. Unless you mean that the > plugins > > should read id3v2... that I can look into. > > This should be pretty easy to do with libid3, but is ID3 really the > right > choice for FLAC? Since FLAC is intended to support streaming, and > ID3v2 lives > at the beginning...

...e: > > > > maybe tagging. i think that id3 tag isn't enough 'cause it > supports only 30 > > > character strings and don't fulfil a requirement of > internationalization i > > > mentioned before. > > > > > The decoder properly ignores id3v2 tags. Unless you mean that the > plugins > > should read id3v2... that I can look into. > > This should be pretty easy to do with libid3, but is ID3 really the > right > choice for FLAC? Since FLAC is intended to support streaming, and > ID3v2 lives > at the beginning...

> > What kidn of files are you streaming? > > MP3s and nothing but. Are they high bitrate? VBR? Do they have id3v2 tags? We could all guess they were mp3s :) <p>What version of linux? glibc? Icecast 1.3.11? jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org...

...wanted to send it here, hoping it will be added to the faq. The error message is the same as in: http://www.xiph.org/archives/vorbis/200210/0073.html Warning: Hole in data found at approximate offset 5238000 bytes. Corrupted ogg. In this case it was caused by id3tags added by grip. Using id3v2 (http://id3v2.sf.net) to remove the tags fixed this problem. id3v2 -d *.ogg id3v3 -s *.ogg <p><p># Han -- FreeBSD: The Power (__) I'm changing the CHANNEL ... But all I get is To Serve. \\\'',) commercials for RONCO MIRACLE BAMBOO RELENG_4...

Hi. Seeing as the topic appeared a while ago I was wondering: How do people feel about adopting ID3v2 for Vorbis aswell. This would, of course, mean it's given a stream of its own and even allow interleaving. It could be usefull, seeing as it would cut down on both initial development and software support, since a lot (most?) audio players already support it. It could also allow for code sharin...

...'t have ANY details on what that means, and was wondering what has changed. The only thing I see (in the changelog) is that plugins have removed support for ID3 tags. I'm curious because I have been using ID3 tags with FLAC (I store extra data such as album art with my media files, and ID3v2 tags allow me to do so). Will this continue to be OK, or is 1.1.1 breaking that compatibility? Not that I like ID3v2 or anything, it's not very pleasant to work with. Thanks in advance, Ron

...y all..I'm brand new to FLAC and learning to use it. Can somebody tell >>me how to insert things such as Artist, album etc. into the FLAC file? >>I'd like to do this at encode time via the command line. >> > >as far as i know you can't. you have to use id3v1 or id3v2 tags. if you >using linux i have made a patch for abcde, a command line ripper/encoder w/ >cddb and id3 support. if you want it, i can make it available. its just a >shell script so it may work with other unix as well. > >let me know and i'll put it on my web page. > >ben &...

...ant comment tags. Let's see - it won't be in XML; that's about all I can recall from the discussion. In other words, it hasn't come along very far. 3) The inadequacy of the id3 system is well-known. In particular, classical music is not given fair treatment. And so, we have id3v2, a conflicting and/or supplemental standard. While id3v1 support is widespread, id3v2 support is still spotty. Some applications which *can* use id3v2 prefer id3v1 when given both! *cough*winamp*cough* It's a mess. 4) The need for a concrete standard is very real. The average user ne...

On Wed, 6 Feb 2002, Jack Moffitt wrote: > > A good number have id3v2 tags... say 20-30%. > > Do you find that it's stuttering on id3v2 files? Since those contain > data that is counted by the timing code, but not played the the player, > that seems a likely suspect. Ie, you'll get _playable_ data too slow. I replaced my normal playlist with a...

The protocol of sending of metadata over a stream (which is HTTP) does not allow for this type of thing. The problem is not necessarily the fact that the id3 tags are at the end of the files, as id3v2 does not have this restriction, but rather just the "agreed" upon protocol for handling metadata for streamed mp3s (and I'm only going to talk about mp3s here, since it's different for other media). For mp3 streaming, there is only ONE metadata protocol that is adopted by the...