similar to: comments+tags CD data

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

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

Hi we run a util at work called 'bounds checker' and it came up with this little beauty: void oggpack_readinit(oggpack_buffer *b,unsigned char *buf,int bytes){ memset(b,0,sizeof(oggpack_buffer)); b->buffer=b->ptr=buf; b->storage=bytes; } Stack memory overrun: Copying 20 bytes to opb; Starting offset 0, destination size 4 bytes. This is in RC1 code base. Any ideas?

I have read some posts about using FLAC to archive CD collections and would like to get some feedback. I am torn between creating a bin and cue file with CDDB info and compressing that down with FLAC as a single file or the second method of ripping all the files out to wav and converting to FLAC and maybe saving the cue file in attempt to use it later. The first method I believe will pretty much

I see that this was the right place to fire off this question. Thanks for your feedback. It has given me a base to start some trials. I used to use EAC on Windows, but I tend to only use open source software as much as possible and I don't use Windows any more. I gave a brief look at abcde, but it is clear I need to look at this some more. It looks like it has the potential to do everything I

I just uploaded a new FLAC FAQ: http://flac.sourceforge.net/faq.html Let me know if I forgot any common questions. Josh __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

Hi there, is there any specific reason for ignoring TITLE and PERFORMER info when importing CD-TEXT cuesheets into flac files? (These two fields have not always been used but they have become widely supported by now). One may answer that the preferred method for getting this kind of info for a cuesheet-flac would be CDDB, but CDDB info is not always reliable. In my opinion the goal "Now a CD

I wanted to post publicly my problem with Jonathan's proposed album requirements. Although I do apologize, since this thread is too big already. The idea that as a requirement one should be able to identify the exact CD a track was ripped from is not a valid requirement in my book (not for the tags at least), and I hope I can explain why. Without knowing the exact way Jonathan wishes to

--- smoerk <smoerk@gmx.de> wrote: > good idea, i'm always putting *.cue files to the directory with the > ripped audio files. but it would prefer one file per song and not one > big file for the whole cd. My vision of how the players should work is this: - make one album.flac with CUESHEET - player loads album.flac, sees CUESHEET, calculates CDDB id (or CDindex, or custom

On Thu, 2003-12-25 at 21:35, Josh Coalson wrote: > --- jason <jason@doomba.com> wrote: > > is there a cuesheet syntax document someplace? > it's not really standardized that well. there are some links > here: http://flac.sourceforge.net/documentation.html (search > for --cuesheet) hmmmm.... i just reread the faq and your right... i'm kind of losing interest in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, as I said before on this list I use the vorbiscomment utility in my music file management perl script and I've just noticed that it has huge problems with German umlauts. "ö", for example, becomes "ö", which is QUITE annoying. In xmms, the tags are displayed correctly, though. I'm using the newest libraries and

I've just started to archive my CD collection (about 800 CDs), and my criteria are pretty much the same as the original message under this subject, except that I'm doing one file per CD. One file per song is just too much of a pain, and there's really no need, given FLAC's ability to have metadata in the file. The first thing I do is run cd-discid against the cd, and store that

Email eller vedhæftet fil afsendt fra din adresse (eller med din adresse som afsender) er blevet afvist fra Allerød Kommune. Spam og virus bliver typisk sendt under dække af andre afsendere og den blokerede email behøver derfor ikke oprinde direkte fra dig. (Husk dog altid at have et opdateret antivirusprogram på din computer.) Du kan evt. scanne din computer med det gratis' værktøj

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to use flac to make backups of my CD collection, and am running into problems with disks that contain a pregap (or lead-in) before the start of track one. cdrdao rips these disks *WITHOUT* the pregap, and puts a PREGAP entry into the cue file. For my test CD (Police, Synchronicity, catalog# 0082839373524) I get (in part): TRACK 01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I made these nifty pythonscripts to make my ripping+encoding+sorting easier. They are designed to use in Grip. w_oggenc: Call this instead of oggenc in Grip with the command-line: "%A" "%d" "%t" "%a" "%n" "%y" "%G" "%i" Now you can put additional info in the

Hey 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. Thanks, Chris -- Only in America do banks leave both doors open and then chain the pens to the counters

oggenc -b 128 cdda.wav cdda.ogg lame -h cdda.wav cdda.mp3 ogg123 -d null cdda.ogg mpg123 -t cdda.mp3 Here we can see that the mp3 tools are clearly superior in terms of the numbers of characters saved on the command line. mp3 users enjoy a 20% saving. Real-life results may narrow this gap. Rik p.s. ;) --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

I'm trying to install the exaile package on my newly upgraded CentOS 6.4 machine. It fails (see below) with missing dependencies on python-cddb and gnome-python2-gtkmozembed. I found this thread but there does not seem to be any resolution. \ Has anyone got this installed? Am I missing a repo? Thanks, Steve # yum install exaile Loaded plugins: fastestmirror, refresh-packagekit, security

All this talk about vorbis comments has made me think. Would it be possible to create backups of the Vorbis comments for my vorbis collection (currently about 1850 files) ? Instead of having to make sure I enter the correct details into CDex (saving in to cdplayer.ini & backing up that), or if I have comments in the Vorbis files that aren't stored in cdplayer.ini, such as the tags