Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: wav/cue -> FB2k/LAME... proper ID3 (year, genre?) (Read 2664 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

wav/cue -> FB2k/LAME... proper ID3 (year, genre?)

Hi,

I've been ripping my CDs with EAC to wav/cue (using CD-text from FreeDB), and then transcoding to mp3 with Foobar2k +ID3V2 +foo_clienc using LAME (--alt-preset medium).  This provides an easy way to get most of the info to the ID3 tags, but not the year and genre!  I know you could easily do it by hand with the masstagger, but when you're talking about a few hundred CDs, that quickly becomes massively tedious.

Any ideas or suggestions?

Thanks!

wav/cue -> FB2k/LAME... proper ID3 (year, genre?)

Reply #1 –
Year and genre cannot be saved in the .cue files.

Why don't you use EAC to encode the tracks to mp3 when ripping?

wav/cue -> FB2k/LAME... proper ID3 (year, genre?)

Reply #2 –
I'm trying to put my CDs in storage, so for archiving I'm ripping to wav/cue. The machine I'm ripping with only has a 500MHz CPU--but it has a Plextor 40max, which I can always rely on to provide bit-for-bit perfect copies.  I've been ripping to image, then transporting the files to work, where I have a brand new 2.8GHz machine for encoding to APE, then taking transcoding to mp3.

wav/cue -> FB2k/LAME... proper ID3 (year, genre?)

Reply #3 –
Why don't you store the genre and year in the cue/wav filename then?
after that, passing the info to foobars masstagger should be piece of cake