I just tried a CD rip again in dbPowerAmp. >>Does it queue up ripped tracks to be encoded. > >Yes, but you will not really notice with FLAC, as it is so fast at >encoding. > It ripped the first track. Didn't find the CD in AccurateRip DB, so it seemed to do two secure rip passes. It then started to encode the first track to FLAC. However, the next track wasn't ripped until the first had been encoded.
Encoding does take time, especially for long tracks. A lot of my music consists of long tracks, not short pop tracks. A queue of songs for ripping and a queue of songs for encoding would seem more sensible. I can see in the settings that I can choose tags to be disabled. However, I don't want to permanently disable disc number tags. I only want to write them if total disks is greater than 1. i.e. I don't want disk 1/1. So instead, I keep the writing of the disk tag enabled, and have to remember to delete Disc "1/1" before ripping. Similarly, I don't store album artist tags for normal albums; only if there are guest artists. I may disable the writing of that tag, and just add it in the Metadata panel for the small number of cases where it's needed. Another minor point. The year can be set as a property of the album. If I choose to display the year for each track (as a column in the grid), it isn't displayed unless I choose to tick "Compilation". There are non-compilation albums that have tracks in different years. If I select a single track and change the tags for that track in the metadata panel (eg. it will say "Metadata for track 1"), it changes the year for all tracks. I'd only expect it to do that if I choose "Meta Data for All Tracks". _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
