similar to: WAV Header and Tagging

So, I saw a form of wav header I didn;t know about today. It's not in my (admittedly aging) copy of the RIFF spec from M$, but it's pretty clear how to handle it (mostly in the context of OggEnc). Here's a dump with od -c: 0000000 R I F F 370 357 l 002 W A V E f m t 0000020 020 \0 \0 \0 001 \0 002 \0 D 254 \0 \0 020 261 002 \0 0000040 004 \0

this is a little off-topic, but i want to get a sense of "best practices" for tagging flac files. i want to archive my entire cd collection as flac files (onto a few of those new western digital 120GB drives). as part of encoding the flac files, i'd like to add 1. id3v2 tags (preferably automatically gotten from freedb) 2. timed lyrics a la lyrics3 v2 (is there a freedb-like

-------------- next part -------------- An embedded message was scrubbed... From: Stefan Weilhartner <whylee@whylee.at> Subject: Info-Tags in ogg, flac, mp3, wav Date: Sun, 10 Oct 2004 20:38:58 +0200 Size: 1526 Url: http://lists.xiph.org/pipermail/vorbis-dev/attachments/20041010/1611e14f/Info-Tagsinoggflacmp3wav.mht

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! :-) Thanks! Chris benny k. wrote: >hi chris, > >On Thu, Mar 14, 2002 at 09:22:06AM -0700, Chris Hirsch wrote: > >>Hey all..I'm brand new to FLAC and learning to use it. Can somebody tell >>me how

A friend of mine recently had a problem with a "broken" .WAV file (as you call them) because oggenc first printed out a warning and then didn't accept the file because of a "unexpected EOF error". Because I was interested in the issue, I decided to take a look at the oggenc source, and in fact, it is your .WAV reader that's wrong. More precisely: there are two version

Hello, I know my question has been asked before because I spent the last week searching the web for how to use Speex in combination with WaveIn/WaveOut and I ran into a few posts, but none of them answer the question. There is still a lot of confusion how to use WaveIn/WaveOut and Speex by junior developers such as myself. Even after examining code for SpeexDec and SpeexEnc, I cannot get clear

Thank you for such a quick response. The only reason I started with Char buffers is because WaveIn and WaveOut on Windows XP accept/emit WAVEHDR structures, which store audio data in LPSTR, which is Char*. typedef struct { LPSTR lpData; DWORD dwBufferLength; ... } WAVEHDR; When I was going from Char to float and back looked very wrong to me as well, but I was just not

Ok so I can use any ID3v2 or v1 tagger (say the perl one) for FLAC files and things will be kosher? I'd LOVE to be able roll my own tagging scheme like you can in Vorbis and I don't mind doing some code either..I wasn't aware that FLAC was able to do that..or at least I didn't userstand how to do that. I guess that is where you register for your own developer ID eh? Josh

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.

Alright. So, the tag proposal that has been labored over for some months has now been reclassified a bit. There new URL is now here: http://reactor-core.org/ogg-tag-recommendations.html And is prefaced by the following statement: "The following recommendations were developed by a community of Ogg/Vorbis users for their own use." I believe the implication is that this document

Hi, I just had a problem that is not described in the faq and it was quite hard to find the right fix so I 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.

We're experiencing a problem where one of our users is unable to authenticate to Samba some times (1 - 2 times/week out of 5). Typically when it happens, it's when she first attempts to access it in the morning. Regardless of how many times she tries again, she is unable to authenticate. However, if she tries later in the day, it works fine. She is the only user this has happened to.

I have a CD collection of about 20 discs that I currently archive on my hard disk in MP3 format. No, I do not like lossy compression. No, I do not like closed standards. No, I do not like software patents (Fraunhofer). In fact, I do not even need compression at this point, as my hard disk capacity is greater than the sum total of the CDs' WAV-format sizes. However, I need its ID3

Hi, I wrote a quite useful perl script (and I am still working on it) that does all the renaming and tagging of my MP3 files automatically (which is very useful because I am an order fanatic and everything has to have MY format). I'm not quite done with ID3v2 support but that will probably work soon. As I am planning to start using Ogg Vorbis instead of MP3 in the future I am already now

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 metadata, and if you would

Hi, I'm writing a tag-editor for ogg files. What tags, besides ogg-tags, are allowed in ogg files (if any). I'm thinking of id3v1, id3v2, ape tags and so on. I have a (probably small) problem with writing a new "comment header". I have tried opening a file with a valid header, and then simply moved some of the comment tags position, so that the total size and the count still

> 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 problem persists. > > What version of linux? glibc? > > RH 7.2

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 this. Move place of 'include "config.h"' to the top. I

I've been with FLAC since 0.7, and I've loved the FLAC files I've ripped with grip, converted from FLAC 0.8 to 0.9, and played constantly on my desktop. And then 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

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