The Pioneer DVR-104 CD-RW/DVD-RW fails to
accept any cue sheet variants using the generic-mmc driver.
Is there any particular documentation I should be requesting
from Pioneer for trying to fix this?
2,0,0: PIONEER DVD-RW DVR-104 Rev: 1.20
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)
Starting write simulation at speed 8...
Process can be aborted with QUIT signal (usually CTRL-\).
Turning BURN-Proof on
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Simulation failed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SCSI: max DMA: 64512
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
Using libscg transport code version 'schily-scsi-linux-sg.c-1.68'
0,0,0: PIONEER DVD-RW DVR-104 Rev: 1.20
Reading driver table from file "/usr/local/share/cdrdao/drivers".
Found 312 valid driver table entries.
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)
Starting write at speed 4...
Pausing 10 seconds - hit CTRL-C to abort.
Process can be aborted with QUIT signal (usually CTRL-\).
Lead-in start: 97:26:66 length: 11484
Lead-out length: 6750
Using pthread POSIX real time scheduling.
Memory locked
Waiting for reader process
Using pthread POSIX real time scheduling.
Swap: 1
Buffer filled
Awaken, will start writing
Turning BURN-Proof on
Multi session mode: 0
Data block type: 0
Session format: 20
Toc type: 0x20
Drive accepted write parameter mode page variant 0.
Executing power calibration...
Power calibration successful.
Track is Blank, Next Writable Address is valid
NWA: -150
Hm. I wonder if I could use Nero under Windows to try
and burn something and observe what it was sending as
the cue sheet? I've tried sending various variations
of the cue sheet, but I haven't found one that works yet.
Alas, I don't have a Windows box handy to try...
Pioneer has a firmware upgrade available.
I wonder if that will help... (It also requires
Windows to install it.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-14
I have the same problem with my DVR-103. Even with the newest firmwar :-(
Gerd
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-28
Same problem with Sony CRX140E.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the DVR-104, and I actually got cdrdao to write *once*. I am running a stock 2.4.19 kernel, with everything compiled as modules (used redhat's .config file).
I got that same error all the time - no cue sheet variant accepted. Then, I went to modules.conf and commented out the line that preloads ide-cd whenever ide-scsi is loaded, so that *only* ide-scsi and the scsi subsystem modules load when I do cdrdao scanbus.
The one time it worked was immediately after rebooting, so that all the modules were loaded into a fresh kernel instance. Since that one time, I get a new error - a variant of "device not ready", and then timeouts waiting for the device to respond - rather than the "no cue sheet variant" error. I haven't had the chance to reboot again to see it I can make it work with another cd-r.
Oh, and yes.. I did upgrade my DVR-104 to the 1.32 firmware a while back. The successful run happened yesterday.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can repeatedly get the following cue sheet to work with this drive, using the setup I described above:
FILE "cdrdao_works.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
Any cue sheet which looks like that will write, with any .bin .
From what I can tell, all others fail. I don't know if this will work with other cd-writing drives, but here's an example of one that doesn't work, and gives the "no cue sheet variants accepted" error:
FILE "ent-2x10.bin" BINARY
TRACK 01 MODE2/2336
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2336
FLAGS DCP
INDEX 00 00:04:00
INDEX 01 00:06:00
That's the cue file vcdeasy generated, no manual edits..
Are these features not supported by any drive with cdrdao at the moment, or is there an actual problem with non-vanilla cue sheets on this drive?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since I last posted, I've learned that the DVR-A04/104 drives actually don't support DAO in RAW mode. I don't know what all the possible options and modes are, but my own conclusion is that it's just not going to work. Supposedly, the DVR-A05/105 has DAO RAW, so that makes me wonder: is it something missing from the drive's firmware, or some specific hardware capability?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also have this problem running Mac OS X 10.2.3 with a A05 drive. Sometimes it can send the cue sheet, sometimes it can't. My old drive an Sony CRX 140e had no problems ever.
The built in CD burner software can still burn CD's as well as Toast so I think it must be something with cdrdao.
Anyone have any solutions to this yet?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-07-21
Posted on Burnatonce and SourceForge
I also had the problem of "ERROR: Drive does not accept any cue sheet variant - please report." My configuration is running Windows 98 Special Edition (V 4.10.2222 A). The drive I'm using is an HP CD-Writer+ 9300 with V1.0b firmware. I installed "burnatonce" so that I could create VCDs from cue/bin files. I purchased the application Photo2VCD Professional and it has the ability to burn CDs directly. I did this successfully using the "disc-at-once" burning procedure. But when I tried to create a disc using the "session-at-once" procedure and I tried to add another session, it failed to do so, saying the disc was unwriteable. I looked at the disc with the software that came with the drive - Easy CD Creator V3.5c - and the Disc Information said the disc was "Non-recordable". The Photo2VCD application creates a cue/bin file pair and it said that you could use "Golden Hawk CDRWin", "Nero Burning ROM" or "burnatonce" to burn a disc. I opted for "burnatonce". I had no problems until it got to the point of writing the disc. Here is the log file from "burnatonce":
0,1,0: HP CD-Writer+ 9300 Rev: 1.0b
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0010)
Starting write at speed 4...
Using multi session mode.
Executing power calibration...
Power calibration successful.
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Writing failed.
At this point I started looking for a description of the "cue" file format, but I haven't yet stumbled upon a specification for this file format. Does anyone know where you can find a specification for the "cue" file format? I experimented with modifying the cue file and was able to produce other error messages, but no variation I tried worked successfully. The original cue file follows:
FILE "RALLY.BIN" BINARY
TRACK 01 MODE2/2352
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2352
FLAGS DCP
INDEX 00 01:11:59
INDEX 01 01:13:59
INDEX 02 01:14:16
When I installed "burnatonce" it said I should also install ASPI layer version 4.60 (1021) (ASPI32.EXE). However, the description of this file on the Adaptec website (http://www.adaptec.com/worldwide/support/driverdetail.html?filekey=aspi32.exe) lists several programs that you shouldn't install 4.60 with, including "Windows Media Plyer 7.0", which I have on my system. Thus, I didn't install the ASPI 4.60 layer. According to the Microsoft System Information app, I have the Adaptec APIX 4.60 (1021) driver installed on the system, which is part of the Adaptec ASPI 4.60 layer.
I checked the "burnatonce" website and found an entry on this topic (http://www.burnatonce.com/forums/index.php?showtopic=528&st=0&) and it pointed me at the SourceForge (http://sourceforge.net/forum/forum.php?thread_id=746464&forum_id=6284) website. What I see tells me several people have had this problem and there is no apparent resolution. Anything new to add to this discussion?
Regards,
Mike Augeri
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Pioneer DVR-104 CD-RW/DVD-RW fails to
accept any cue sheet variants using the generic-mmc driver.
Is there any particular documentation I should be requesting
from Pioneer for trying to fix this?
(See bug 607103 filed to track this.)
Output when trying to burn a demo svcd:
# /usr/local/bin/cdrdao simulate --device 2,0,0 --driver generic-mmc --speed 8 -n test_svcd_ntsc.cue
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
2,0,0: PIONEER DVD-RW DVR-104 Rev: 1.20
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)
Starting write simulation at speed 8...
Process can be aborted with QUIT signal (usually CTRL-\).
Turning BURN-Proof on
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Simulation failed.
Same problem here with an OEM'd Pioneer DVR-104 that is packaged as a Cendyne DVR-A04.
I'd also like to figure out a fix for this.
As an addendum, here's the output from cdrdao 1.1.7 for the Cendyne DVR-A04 (in reality a Pioneer DVR 104):
[root@dn103 testsvcd]# /usr/local/bin/cdrdao write --device 0,0,0 --speed 4 -v 5 test_svcd_ntsc.cue
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.
SCSI: max DMA: 64512
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
Using libscg transport code version 'schily-scsi-linux-sg.c-1.68'
0,0,0: PIONEER DVD-RW DVR-104 Rev: 1.20
Reading driver table from file "/usr/local/share/cdrdao/drivers".
Found 312 valid driver table entries.
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)
Starting write at speed 4...
Pausing 10 seconds - hit CTRL-C to abort.
Process can be aborted with QUIT signal (usually CTRL-\).
Lead-in start: 97:26:66 length: 11484
Lead-out length: 6750
Using pthread POSIX real time scheduling.
Memory locked
Waiting for reader process
Using pthread POSIX real time scheduling.
Swap: 1
Buffer filled
Awaken, will start writing
Turning BURN-Proof on
Multi session mode: 0
Data block type: 0
Session format: 20
Toc type: 0x20
Drive accepted write parameter mode page variant 0.
Executing power calibration...
Power calibration successful.
Track is Blank, Next Writable Address is valid
NWA: -150
Cue Sheet (variant 0):
CTL/ TNO INDEX DATA SCMS MIN SEC FRAME
ADR FORM
41 00 00 24 00 00 00 00
61 01 00 20 00 00 00 00
61 01 01 20 00 00 02 00
61 02 00 20 00 00 21 01
61 02 01 20 00 00 23 01
61 02 02 20 00 00 30 28
61 02 03 20 00 00 42 29
61 02 04 20 00 00 55 10
61 02 05 20 00 01 05 74
41 aa 01 24 00 01 28 46
Cue Sheet (variant 1):
CTL/ TNO INDEX DATA SCMS MIN SEC FRAME
ADR FORM
41 00 00 24 00 00 00 00
61 01 00 20 00 00 00 00
61 01 01 20 00 00 02 00
61 02 00 20 00 00 21 01
61 02 01 20 00 00 23 01
61 02 02 20 00 00 30 28
61 02 03 20 00 00 42 29
61 02 04 20 00 00 55 10
61 02 05 20 00 01 05 74
41 aa 01 24 00 01 28 46
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Writing failed.
Hm. I wonder if I could use Nero under Windows to try
and burn something and observe what it was sending as
the cue sheet? I've tried sending various variations
of the cue sheet, but I haven't found one that works yet.
Alas, I don't have a Windows box handy to try...
Pioneer has a firmware upgrade available.
I wonder if that will help... (It also requires
Windows to install it.)
I have the same problem with my DVR-103. Even with the newest firmwar :-(
Gerd
Same problem with Sony CRX140E.
I have the DVR-104, and I actually got cdrdao to write *once*. I am running a stock 2.4.19 kernel, with everything compiled as modules (used redhat's .config file).
I got that same error all the time - no cue sheet variant accepted. Then, I went to modules.conf and commented out the line that preloads ide-cd whenever ide-scsi is loaded, so that *only* ide-scsi and the scsi subsystem modules load when I do cdrdao scanbus.
The one time it worked was immediately after rebooting, so that all the modules were loaded into a fresh kernel instance. Since that one time, I get a new error - a variant of "device not ready", and then timeouts waiting for the device to respond - rather than the "no cue sheet variant" error. I haven't had the chance to reboot again to see it I can make it work with another cd-r.
Oh, and yes.. I did upgrade my DVR-104 to the 1.32 firmware a while back. The successful run happened yesterday.
More detail:
I can repeatedly get the following cue sheet to work with this drive, using the setup I described above:
FILE "cdrdao_works.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
Any cue sheet which looks like that will write, with any .bin .
From what I can tell, all others fail. I don't know if this will work with other cd-writing drives, but here's an example of one that doesn't work, and gives the "no cue sheet variants accepted" error:
FILE "ent-2x10.bin" BINARY
TRACK 01 MODE2/2336
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2336
FLAGS DCP
INDEX 00 00:04:00
INDEX 01 00:06:00
That's the cue file vcdeasy generated, no manual edits..
Are these features not supported by any drive with cdrdao at the moment, or is there an actual problem with non-vanilla cue sheets on this drive?
Upgrading the firmware didn't help.
I was also unable to burn a VCD/cue using Nero under Windows with this drive. This seems to imply that the drive may just not support this?
Since I last posted, I've learned that the DVR-A04/104 drives actually don't support DAO in RAW mode. I don't know what all the possible options and modes are, but my own conclusion is that it's just not going to work. Supposedly, the DVR-A05/105 has DAO RAW, so that makes me wonder: is it something missing from the drive's firmware, or some specific hardware capability?
I also have this problem running Mac OS X 10.2.3 with a A05 drive. Sometimes it can send the cue sheet, sometimes it can't. My old drive an Sony CRX 140e had no problems ever.
The built in CD burner software can still burn CD's as well as Toast so I think it must be something with cdrdao.
Anyone have any solutions to this yet?
Posted on Burnatonce and SourceForge
I also had the problem of "ERROR: Drive does not accept any cue sheet variant - please report." My configuration is running Windows 98 Special Edition (V 4.10.2222 A). The drive I'm using is an HP CD-Writer+ 9300 with V1.0b firmware. I installed "burnatonce" so that I could create VCDs from cue/bin files. I purchased the application Photo2VCD Professional and it has the ability to burn CDs directly. I did this successfully using the "disc-at-once" burning procedure. But when I tried to create a disc using the "session-at-once" procedure and I tried to add another session, it failed to do so, saying the disc was unwriteable. I looked at the disc with the software that came with the drive - Easy CD Creator V3.5c - and the Disc Information said the disc was "Non-recordable". The Photo2VCD application creates a cue/bin file pair and it said that you could use "Golden Hawk CDRWin", "Nero Burning ROM" or "burnatonce" to burn a disc. I opted for "burnatonce". I had no problems until it got to the point of writing the disc. Here is the log file from "burnatonce":
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
0,1,0: HP CD-Writer+ 9300 Rev: 1.0b
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0010)
Starting write at speed 4...
Using multi session mode.
Executing power calibration...
Power calibration successful.
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Writing failed.
At this point I started looking for a description of the "cue" file format, but I haven't yet stumbled upon a specification for this file format. Does anyone know where you can find a specification for the "cue" file format? I experimented with modifying the cue file and was able to produce other error messages, but no variation I tried worked successfully. The original cue file follows:
FILE "RALLY.BIN" BINARY
TRACK 01 MODE2/2352
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2352
FLAGS DCP
INDEX 00 01:11:59
INDEX 01 01:13:59
INDEX 02 01:14:16
When I installed "burnatonce" it said I should also install ASPI layer version 4.60 (1021) (ASPI32.EXE). However, the description of this file on the Adaptec website (http://www.adaptec.com/worldwide/support/driverdetail.html?filekey=aspi32.exe) lists several programs that you shouldn't install 4.60 with, including "Windows Media Plyer 7.0", which I have on my system. Thus, I didn't install the ASPI 4.60 layer. According to the Microsoft System Information app, I have the Adaptec APIX 4.60 (1021) driver installed on the system, which is part of the Adaptec ASPI 4.60 layer.
I checked the "burnatonce" website and found an entry on this topic (http://www.burnatonce.com/forums/index.php?showtopic=528&st=0&) and it pointed me at the SourceForge (http://sourceforge.net/forum/forum.php?thread_id=746464&forum_id=6284) website. What I see tells me several people have had this problem and there is no apparent resolution. Anything new to add to this discussion?
Regards,
Mike Augeri