From: Brian B. <br...@pi...> - 2012-04-05 16:52:00
|
I am using GWC 0.21-16, which is currently shipped with the ubuntu studio 12.04 precise pangolin beta 2. It is also the current version with my production ubuntu studio 11.10 system. It isn't strictly relevant, but I convert vinyl to digital using an Edirol FA-66 firewire device controlled by jackd and captured by Ardour. I use Ardour to export a single wav file for the entire vinyl album and then use gwc to clean up the recording. When I have a wav file that I like, I then manually mark the boundary of each track with "Markers -> Add Song Marker". Finally, I "View -> SelectAll" and then "File -> Create cdrdao toc file As...". I manually fill in the album and track names on the toc dialogue and save the file. I write a new CD with "cdrdao --speed 4 export.toc". This is a procedure I've been following for several years without any problems. However, since I upgraded gwc to 0.21-16, cdrdao has complained about the toc files and refused to write the cd as follows: brian@schizo:~/WeatherReport-sportinLife/export$ cdrdao write --speed 4 export.toc Cdrdao version 1.2.3 - (C) Andreas Mueller <an...@da...> ERROR: Track 7: Requested length (89737555 + 12992447 samples) exceeds length of audio file "/home/brian/WeatherReport-sportinLife/export/export.wav" (102729733 samples at offset 0). ERROR: The toc check function detected at least one warning. ERROR: If you record this toc the resulting CD might be unusable ERROR: or the recording process might abort with error. ERROR: Use option --force to ignore the warnings. ERROR: Toc file "export.toc" is inconsistent. The toc file is fairly badly wrong - the first track does not even start with sample number zero! I took a copy of the bad toc file and manually edited all the track start and length sample counters. I took the actual boundaries by displaying the sample counters for each of the song markers displayed by gwc, so we were working off the same wav file and analysis. My manual sample counters were very different to those automatically generated by gwc. I've googled, but not found anything relevant. Am I using the appropriate dialogue to create my toc file on this release of gwc (i.e. this is a user error), or does this sound like a bug? (I notice you've added new toc file features in recent releases, so perhaps this is collateral damage.) I don't know whether your mailing list strips attachments, so I won't send the two files at this time. I'm happy to send them in-line if anyone feels they would help in diagnosis. Obviously this isn't urgent for me because I have a tedious but viable bypass for the problem. However, this version of gwc is being pushed out as 0.21.16~dfsg-3build (precise) and 0.21.16~dfsg-3 (oneiric) from the ubuntu repositories, so it has a wide exposure! Regards, Brian Burch |