| 1 |
On Thu, Nov 5, 2009 at 1:32 PM, Joerg Schilling |
| 2 |
<Joerg.Schilling@××××××××××××××××.de> wrote: |
| 3 |
> Mark Knecht <markknecht@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> On Thu, Nov 5, 2009 at 12:55 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 6 |
>> <SNIP> |
| 7 |
>> > |
| 8 |
>> > The *.inf files look fairly consistent from song to song: |
| 9 |
>> > |
| 10 |
>> |
| 11 |
>> Actually, Track 6 looks strange: |
| 12 |
> |
| 13 |
>> > Tracknumber= 6 |
| 14 |
>> |
| 15 |
>> > Index= 0 -1 -1 -1 -1 -1 29076 |
| 16 |
>> > Index0= 33231 |
| 17 |
> |
| 18 |
> this cannot work! |
| 19 |
> |
| 20 |
> cdda2wav uses a binary interval search algorithm that usually works correctly. |
| 21 |
> |
| 22 |
> It seems that the drive used for reading has reead and/or seek problems. |
| 23 |
> remove the list of -1's and make sure that |
| 24 |
> |
| 25 |
> A song tape starts with 2m red tape folowed by magnetic tape followed by 2 |
| 26 |
> seconds of white tape. |
| 27 |
> |
| 28 |
> If you mount a disk, you cut off the red tape and glue the magnetic tape |
| 29 |
> behind the 2s white tape of the previous track. |
| 30 |
> |
| 31 |
> A song starts with Index1, Index0 is somewhere to the end of the tack and is |
| 32 |
> a logical part of the current track although it carries the next rack number. |
| 33 |
> A RedBook and Reichsrundfunggesellschaft ;-) compliant track uses Index0 that |
| 34 |
> is equal to tracksize -150 (2 seconds). |
| 35 |
> |
| 36 |
> Opera disks contain further indices as index into the libretto. In this case, |
| 37 |
> you have index numbers > 1. |
| 38 |
> |
| 39 |
> Cdda2wav is the only DAE program that is compliant to the standard and therefore |
| 40 |
> it is the only known program where you may rearrange the order of tracks |
| 41 |
> without the need to edit the audio channel data. |
| 42 |
> |
| 43 |
> In case you do not have an opera disk from Deutsche Grammophon, it is most |
| 44 |
> unlikely that you have a index list. |
| 45 |
> |
| 46 |
> Cdda2wav should never write negative numbers to the index list. As you did not |
| 47 |
> send the cdda2wav output, I cannot comment the reason. |
| 48 |
> |
| 49 |
> Jörg |
| 50 |
> |
| 51 |
|
| 52 |
In this case I will investigate doing the cdda2wav portion on a |
| 53 |
different machine and then writing it on the machine I have been using |
| 54 |
as that drive seems to be the only one that will still generate CDs |
| 55 |
playable in my car. |
| 56 |
|
| 57 |
I'm not completely convinced this is a drive problem but it won't hurt |
| 58 |
to be careful about where each step is done and do some comparisons of |
| 59 |
the files. |
| 60 |
|
| 61 |
Thanks a lot for your help. I'm traveling for the next few days and |
| 62 |
won't look at this again until Monday orTuesday. Have a great weekend. |
| 63 |
|
| 64 |
cheers, |
| 65 |
Mark |
Archives