similar to: Proposal for Discussion: LICENSE and COPYRIGHT tags on Vorbis Comments

Hi, I'm wondering: If you have audio files like foo1.ogg and foo1.mp3, and the Vorbis file has nice comments (title, tracknumber, artist, album, date, etc), is there a tool to copy the information to an MP3 file on a "best effort" strategy? I know that MP3 TAGs are quite limited regarding lengths. Regards, Ulrich

Hi I am developing a free MP3 & Ogg encoder for Cakewalk music production software (see http://cwenc.sourceforge.net for details). I use the binary 1.0 Ogg Vorbis release for Windows for the actual encoding, but for handling of tags I have started to use the library. This became necessary as I wanted to reuse any tags (or "comments" as the correct Ogg term is, AFAIK) which might

In one of the last monthly meetings it was decided that OggPCM is ready and all it needs is an implementation (for instance, in ogg123). The problem is that nobody seems available to do it. If either Martin or Sampo would like to work on it, I believe nobody will oppose. CMML and Skeleton implementations are far more urgent right now, though. I have changed the main page in the XiphWiki to

Hi, there. --- mike dillon <mdillon@standmed.com> wrote: > good luck getting a list of genres that will satisfy everyone. Simply, it is impossible. I just put the list completely the same context with the MP3 tag editor with Winamp. ...Some people seem to mix ID3 tag of MP3 with comment of Ogg Vorbis. As long as it is category-information string, you can add any thing you like to Ogg

Hi, I've written some code to validate comments passed to libkate, which happens to use the Vorbis comments format (apart from the framing bit, which I dumped rather early). While coding this, I wondered if I should allow empty tags (eg, '=foo'). I had a look at liboggz and vorbiscomment, and they both allow it (I didn't test vorbiscomment, just looked at the source). However,

List, A recent discussion over on XiphWiki is trying to decide if OggPCM should support only little-endianness or the usual combo of big and little. It started with the following statement by an user (Qqq): "Portable players are usually ARM, which is usually little-endian. The Macintosh is now little-endian. Obviously the PC is little-endian. Clearly there is a winner. It's long past

Erik de Castro Lopo <mle+xiph@mega-nerd.com> wrote: > Martin Leese wrote: > > So what is "OggPCM"? I started this thread > > because I was puzzled why someone was > > changing a draft instead of the document > > itself. > > The original OggPCM was started by a person who really didn't > lnow what they were doing and wouldn't listen to

hi, is there an official or semiofficial way to store gps location in vorbis comments or any ogg file. mp4 and exif store at least: - location name (e.g. London, UK) - longitude (degree as double), latitude (degree as double), elevation (meters) (these three according to WGS84) Stefan

thx oddsock for your detailed reply, I think I now understand the problem :) I'm currently using a php-script (mp3 toolbox - http://www.radiotoolbox.com/downloads/) to stream static mp3's on-demand, and this script obviously sends the icy-headers (which are the shoutcast metadata protocol, right?). however, I think that it would be a nice feature for icecast to support these

Ivo Emanuel Gon?alves wrote: > List, > > A recent discussion over on XiphWiki is trying to decide if OggPCM > should support only little-endianness or the usual combo of big and > little. > > It started with the following statement by an user (Qqq): > > "Portable players are usually ARM, which is usually little-endian. The > Macintosh is now little-endian.

Hello, I'd like to ask about the possibility of embedding pictures like an album cover artwork into a vorbis comment header. Since the data in a comment string after the separating "=" has a defined length, this could theoretically also be binary picture data. For example "PICTURE=[...any binary data...]" It only would be a problem for existing software which isn't

Hi, I just copied 15 GB of Music from my Slackware install over to my laptop running CentOS. Everything's running fine, except a few minor quirks. About 10 to 15% of the 4.000 songs in my collection seem to have broken ID3 tags in XMMS. In the playlist window, there are only truncated fields of a few random letters appearing. But when I right-click on one of these songs, the ID3 info is

Hi, having inspected one of the files found at music.ibiblio.org, I realized that the comments are quite poor or misformatted in the files. I'm telling you, because: 1) I think it's great to have some free music 2) I think the performers deserve to be recognized Generally, I'd put as much as possible into the Vorbis comments. Then you could skip creating these index.html manually:

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

On Thu, Mar 14, 2002 at 10:26:45AM -0700, Chris Hirsch wrote: > So there are no command line options like in oggenc to do artist and > misc tags? Sure if you've got a solution that I don't have to do from > scratch then post away! :-) the patch is located below. i have already submitted it to the author. http://www.bagu.org/flac.html i have also made a utility to calculate

Hello. I would like to know if there are any developments planned for Vorbis comment specifications. I am generally content with the variety of field names, but I would really appreciate having a standard GUESTARTIST field (or something in the vicinity) to be able to better describe collaborations. This is helpful in cases where there is a main artist for the track/album, and there are also guest

Just finally getting around to this :-) I've never used abcde...looks like it'll be a winner in my book....just to understand...your patch (which does tagging) is against the original and only FLAC patch that enables abcde to do flac which is v1.9.9 and the newest is 2.0.3? or do I just patch your new patch against 2.03? Yeah I know I should just try it (and I'm sure I will) I

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

--- Chris Hirsch <chris@base2technology.com> wrote: > So there are no command line options like in oggenc to do artist and > misc tags? Sure if you've got a solution that I don't have to do from > scratch then post away! :-) I think that uses vorbis tags. FLAC doesn't specify a tagging system. You have three choices: 1) use id3v1 or v2 (preferably v1 since that has

I note that LICENSES and README state LGPL v2.1 but there are other files with other licenses, most obviously many shell script files such as: regedit/hivexregedit sh/example* Also some Makefiles: perl/Makefile.am sh/Makefile.am ...etc... find . -type f | while read filename; \ do if grep -iqs 'general public license' $filename; then \ if grep -viqs 'lesser' $filename; then