bob_walton Posted February 13, 2006 Report Share Posted February 13, 2006 When checking a freshly burned audio CD, the Roxio Audio Player displays incorrect artist and album information for a couple of tracks, even though the track tags appeared correct at the time of burning. I've encountered this before, but this time there seems to be no way of fixing it. Apparently, the same artist and album initially got incorrectly set for the two tracks. (They were ripped in as mp3s from vinyl records.) I thought the fix would be to delete the playlist and build a new one (same name), making sure the audio files were in their correct artist and album sub-directories. No change. Incidentally, the original mp3s were converted to wav files during processing. I wonder if any of you out there might have a solution? Link to comment Share on other sites More sharing options...
bob_walton Posted February 13, 2006 Author Report Share Posted February 13, 2006 When checking a freshly burned audio CD, the Roxio Audio Player displays incorrect artist and album information for a couple of tracks, even though the track tags appeared correct at the time of burning. I've encountered this before, but this time there seems to be no way of fixing it. Apparently, the same artist and album initially got incorrectly set for the two tracks. (They were ripped in as mp3s from vinyl records.) I thought the fix would be to delete the playlist and build a new one (same name), making sure the audio files were in their correct artist and album sub-directories. No change. Incidentally, the original mp3s were converted to wav files during processing. I wonder if any of you out there might have a solution? An update to the above: The HACP freeware program indicates the burned CD track information is actually correct. Assuming this is true, and there is no reason to believe that it isn't true, it would then seem there is a bug in the Roxio Audio Player itself: For computer display purposes at disk play, the Player must be picking up the original track information from somewhere, right or wrong, created when the tracks were first ripped to disk. It is good to know, however, that you can at least trust the tag editor for the data written to disk. I hope someone who knows can comment on this! Link to comment Share on other sites More sharing options...
james_hardin Posted February 14, 2006 Report Share Posted February 14, 2006 An update to the above: The HACP freeware program indicates the burned CD track information is actually correct. Assuming this is true, and there is no reason to believe that it isn't true, it would then seem there is a bug in the Roxio Audio Player itself: For computer display purposes at disk play, the Player must be picking up the original track information from somewhere, right or wrong, created when the tracks were first ripped to disk. It is good to know, however, that you can at least trust the tag editor for the data written to disk. I hope someone who knows can comment on this! I do very little audio work so I cannot be of any real help. If you are correct I doubt there will be any fix as this program is 2 versions behind the current version and Roxio Player was eliminated along the way. Link to comment Share on other sites More sharing options...
lynn98109 Posted February 14, 2006 Report Share Posted February 14, 2006 An update to the above: The HACP freeware program indicates the burned CD track information is actually correct. Assuming this is true, and there is no reason to believe that it isn't true, it would then seem there is a bug in the Roxio Audio Player itself: For computer display purposes at disk play, the Player must be picking up the original track information from somewhere, right or wrong, created when the tracks were first ripped to disk. It is good to know, however, that you can at least trust the tag editor for the data written to disk. I hope someone who knows can comment on this! The way CDDB identifies a track is to look at the entire disc and match up the times of each of the tracks within the discs. If you take that track away from the original disc and put it into something else, CDDB hasn't got the foggiest. If the information is incorrect (I don't use CDDB, but I did once get a CD that had all the tracks listed in the tracklist on the printwork but not in the same order), then about all you can do is create a new file - say, .wav - and when you are creating it put the alternate info in - and if that won't work, I think you may be stuck. Lynn Link to comment Share on other sites More sharing options...
bob_walton Posted February 17, 2006 Author Report Share Posted February 17, 2006 The way CDDB identifies a track is to look at the entire disc and match up the times of each of the tracks within the discs. If you take that track away from the original disc and put it into something else, CDDB hasn't got the foggiest. If the information is incorrect (I don't use CDDB, but I did once get a CD that had all the tracks listed in the tracklist on the printwork but not in the same order), then about all you can do is create a new file - say, .wav - and when you are creating it put the alternate info in - and if that won't work, I think you may be stuck. Lynn Even if ver. 6 is an old version, the topic is relevant. It seems to me that even through the different ownership (Symantec, Roxio, etc.) and the different versions, the programmers tended to repeat software 'oddities" from version to version. Read 'oddities' as bugs. I go back to the classic versions prior to ver. 4. You do have a chance to alter CDDB data after a disk search, but that doesn't include the file name. If there happens to be a delimiter in the file name, Audio Central will truncate the string in the playback display. I suppose the bottom line is the Tag Editor enters the correct data on the CD at burn time, no matter what Audio Central pumps out on the screen during CD playback. <Big Sigh> Hells bells, it wouldn't be Easy CD Creator if it worked perfectly. :-) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.