Menu
▾
▴
cdrdao-devel
|
From: Christ v. W. <cvw...@gm...> - 2005-07-22 21:14:09
|
Hello, my first posting here, hope I get most of the info right :-) I'm on a Mac, using OS-10.4. My cdrdao version is 1.2.0. I downloaded a compiled binary off a web site. I could compile it myself, but I'd only get 1.1.9... I have a few .wav files, and a .cue file that goes with it. Unfortunately, cdrdao says: ERROR: example.cue:22: Index beyond track end. ERROR: example.cue:23: Index beyond track end. ERROR: example.cue:24: Index beyond track end. ERROR: example.cue:25: Index beyond track end. ERROR: example.cue:26: Index beyond track end. ERROR: example.cue:27: Index beyond track end. ERROR: example.cue:28: Index beyond track end. ERROR: example.cue:29: Index beyond track end. ERROR: example.cue:30: Index beyond track end. Here's the .cue file. Names changed to protect the innocent... PERFORMER "Some Artist" TITLE "Some CD with 3 tracks" FILE "XXXXXX1.wav" WAVE TRACK 01 AUDIO PERFORMER "Some Artist" TITLE "Track name 1" INDEX 01 00:00:00 INDEX 02 05:53:38 INDEX 03 07:42:19 INDEX 04 09:39:61 INDEX 05 11:29:58 INDEX 06 13:48:16 INDEX 07 14:16:35 INDEX 08 16:23:04 INDEX 09 17:27:54 INDEX 10 24:56:65 FILE "XXXXXX2.wav" WAVE TRACK 02 AUDIO PERFORMER "Some artist" TITLE "Track name 2" INDEX 01 00:00:00 INDEX 02 01:18:49 INDEX 03 05:25:52 INDEX 04 08:47:71 INDEX 05 11:41:20 INDEX 06 16:29:06 TRACK 03 AUDIO PERFORMER "Some artist" TITLE "Track name 3" INDEX 01 21:44:24 Can anybody shed some light on how to do this? Regards, Christ van Willegen |
|
From: Denis L. <den...@ya...> - 2005-07-22 21:38:05
|
Hi, Could you provide the length (in bytes) of the 3 wav files that we're talking about here ? The error seems to imply that at least one of them is simply too short for the specified indices... -denis --- Christ van Willegen <cvw...@gm...> wrote: > Hello, > > my first posting here, hope I get most of the info right :-) > > I'm on a Mac, using OS-10.4. My cdrdao version is 1.2.0. I downloaded > a compiled binary off a web site. I could compile it myself, but I'd > only get 1.1.9... > > I have a few .wav files, and a .cue file that goes with it. > > Unfortunately, cdrdao says: > ERROR: example.cue:22: Index beyond track end. > > ERROR: example.cue:23: Index beyond track end. > > ERROR: example.cue:24: Index beyond track end. > > ERROR: example.cue:25: Index beyond track end. > > ERROR: example.cue:26: Index beyond track end. > > ERROR: example.cue:27: Index beyond track end. > > ERROR: example.cue:28: Index beyond track end. > > ERROR: example.cue:29: Index beyond track end. > > ERROR: example.cue:30: Index beyond track end. > > > Here's the .cue file. Names changed to protect the innocent... > > PERFORMER "Some Artist" > TITLE "Some CD with 3 tracks" > > FILE "XXXXXX1.wav" WAVE > TRACK 01 AUDIO > PERFORMER "Some Artist" > TITLE "Track name 1" > INDEX 01 00:00:00 > INDEX 02 05:53:38 > INDEX 03 07:42:19 > INDEX 04 09:39:61 > INDEX 05 11:29:58 > INDEX 06 13:48:16 > INDEX 07 14:16:35 > INDEX 08 16:23:04 > INDEX 09 17:27:54 > INDEX 10 24:56:65 > > FILE "XXXXXX2.wav" WAVE > TRACK 02 AUDIO > PERFORMER "Some artist" > TITLE "Track name 2" > INDEX 01 00:00:00 > INDEX 02 01:18:49 > INDEX 03 05:25:52 > INDEX 04 08:47:71 > INDEX 05 11:41:20 > INDEX 06 16:29:06 > > TRACK 03 AUDIO > PERFORMER "Some artist" > TITLE "Track name 3" > INDEX 01 21:44:24 > > Can anybody shed some light on how to do this? > > Regards, > > Christ van Willegen > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click > _______________________________________________ > Cdrdao-devel mailing list > Cdr...@li... > https://lists.sourceforge.net/lists/listinfo/cdrdao-devel > |
|
From: Christ v. W. <cvw...@gm...> - 2005-07-22 21:57:25
|
Hi Denis, list, I mis-replied, and took if off-list... Here it is on the list as well. > Could you provide the length (in bytes) of the 3 wav files that we're > talking about here ? The error seems to imply that at least one of them > is simply too short for the specified indices... Interestingly enough, cdrdao complains at the first empty line after the specification for track 1... Anyway, here goes... There are only 2 wav files, by the way! Track 3 is a subset of track 2. I've burned another Audio CD with only 1 track of data, but with multiple track definitions in the .cue file. 274251820 xxx1.wav 271294508 xxx2.wav Hope this helps! Christ van Willegen |
|
From: Matthias C. <der...@gm...> - 2005-07-23 11:25:49
|
Hi! Does cdrdao now support AUDIO tracks in CUE files? That would render cue2toc useless. Otherwise I'd like to incorporate the latest cue2toc version into the cdrdao package since it seems to do its job and I'm not planning to work on it anymore. Regards Matthias |
|
From: Denis L. <den...@ya...> - 2005-07-23 18:08:56
|
--- Matthias Czapla <der...@gm...> wrote: > Hi! > > Does cdrdao now support AUDIO tracks in CUE files? That would render > cue2toc useless. Otherwise I'd like to incorporate the latest > cue2toc > version into the cdrdao package since it seems to do its job and I'm > not > planning to work on it anymore. > > Regards > Matthias Hey Matthias, Yes, i replaced the old pccts cue parser with yours, so in theory yes it does render cue2toc useless. Though i'm sure there are bugs to track down (see previous email) and i had a pretty limited set of cue file examples to work with... I've been busy those past few months, but i'll have some time in the next few weeks to iron out some bugs and release 1.2.1. -denis |
|
From: Matthias C. <der...@gm...> - 2005-07-23 18:29:18
|
Hi Denis! On Sat, Jul 23, 2005 at 11:08:48AM -0700, Denis Leroy wrote: > --- Matthias Czapla <der...@gm...> wrote: > > Does cdrdao now support AUDIO tracks in CUE files? That would render > > cue2toc useless. > > Yes, i replaced the old pccts cue parser with yours, so in theory yes > it does render cue2toc useless. Okay. It was a stupid idea to make it a separate "project" anyway. Regards Matthias |
|
From: Denis L. <den...@ya...> - 2005-07-23 18:35:21
|
--- Matthias Czapla <der...@gm...> wrote: > Okay. It was a stupid idea to make it a separate "project" anyway. > > Regards > Matthias I beg to differ. It was an excellent idea. To merge your parser, i had to go through the PCCTS parser in details to understand the differences. And that was quite a pain in the behind... -denis |
Thanks for helping keep SourceForge clean.
X