| 1 |
Joerg Schilling wrote: |
| 2 |
|
| 3 |
> Jörg Schaible <joerg.schaible@×××.de> wrote: |
| 4 |
> |
| 5 |
>> > There is a set of red-book deviations that is called "cactus |
| 6 |
>> > datashield" |
| 7 |
>> > |
| 8 |
>> > cdparanoia will not extract more than 40 seconds from such a "CD" |
| 9 |
>> > regardless of the drive you are using. |
| 10 |
>> > |
| 11 |
>> > With cdda2wav you will be able to extract the whole "CD" as long as the |
| 12 |
>> > drive is not cunfused by the media and as long as you don't run hostile |
| 13 |
>> > software like "hald" or similar that helps to confuse the drive. |
| 14 |
>> |
| 15 |
>> At least from konsole I can use cdda2wav with normal speed, while the |
| 16 |
>> ripping KDE apps all seem to fail. Since KDE is still based on hald, |
| 17 |
>> about what kind of effects you're talking? |
| 18 |
> |
| 19 |
> The defects seen in "cactus datashield" will cause many drives to go into |
| 20 |
> an endless loop in firmware in case you send the READ TOC command to the |
| 21 |
> drive. |
| 22 |
> |
| 23 |
> Hald was written by people who know too few about CD-ROM handling and as |
| 24 |
> hald and other programs (e.g. libGStreamer and cdparanoia) send a READ TOC |
| 25 |
> to the drive, they may trigger this problem. The only way out of this |
| 26 |
> problem is to mechanically reload the media and not to let any other |
| 27 |
> program access the drive except for cdda2wav. |
| 28 |
|
| 29 |
Thanks for taking the time. |
| 30 |
|
| 31 |
- Jörg |
Archives