Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Giulio Orsero
On Thu, Apr 10, 2008 at 10:53 PM, Thomas Schmitt [EMAIL PROTECTED] wrote:

 Your operating system seems to be a kernel 2.4.
2.4.33 kernel.org
 On modern 2.6 it is supposed that one can write to the
 formatted area of BD-RE via the plain block device.
  dd if=test.iso of=/dev/sr0 bs=32K
 On kernel 2.4 this would work with DVD-RAM. No idea
 whether your kernel will accept BD-RE.

On BD-RE it fails with
$ dd if=/dev/zero of=/dev/scd0 bs=32k
dd: opening `/dev/scd0': Read-only file system
$

it works ok on DVD-RAM media.

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Giulio Orsero
On Thu, Apr 10, 2008 at 11:42 PM, Thomas Schmitt [EMAIL PROTECTED] wrote:

  http://scdbackup.sourceforge.net/cdrskin-0.4.5.tar.gz
  MD5: 2ae5d8f06d4847f5436bb99441dfc5cd
 After compilation and install it should report on
  $ cdrskin -version
  Version timestamp :  2008.04.10.211529

$ cdrskin -version
cdrskin 0.4.5 : limited cdrecord compatibility wrapper for libburn
Cdrecord 2.01-Emulation Copyright (C) 2006-2008, see libburnia-project.org
libburn interface :  0.4.5
libburn in use:  0.4.5
cdrskin version   :  0.4.5
Version timestamp :  2008.04.10.211926
Build timestamp   :  -none-given-


it now works ok

cdrskin 0.4.5 : limited cdrecord compatibility wrapper for libburn
cdrskin: verbosity level : 1
cdrskin: NOTE : greying out all drives besides given dev='/dev/sg1'
cdrskin: scanning for devices ...
cdrskin: ... scanning for devices done
cdrskin: beginning to burn disc
cdrskin: status 1 burn_disc_blank The drive holds a blank disc
Current: BD-RE
Track 01: data  5259 MB padsize:  1024 KB
Total size: 5260 MB (598:33.38) = 2693354 sectors
Lout start: 5260 MB (598:35/38) = 2693354 sectors
Starting to write CD/DVD at speed MAX in real SAO mode for single session.
Last chance to quit, starting real write in   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
cdrskin: thank you for being patient since 1 seconds
Starting new track at sector: 0
...
...
cdrskin: thank you for being patient since 1278 seconds
Track 01: Total bytes read/written: 5514940416/5515988992 (2693354 sectors).
Writing  time:  1278.935s
Cdrskin: fifo had 2692842 puts and 2692842 gets.
Cdrskin: fifo was 0 times empty and 323524 times full, min fill was 99%.
Min drive buffer fill was 20%
cdrskin: burning done


Speed is the same as with cdrecord and growisofs, 1x instead of 2x, I
think this is due to verification/defect detection.

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Thomas Schmitt
Hi,

i wrote:
  Your operating system seems to be a kernel 2.4.
Giulio Orsero wrote:
 2.4.33 kernel.org
 $ dd if=/dev/zero of=/dev/scd0 bs=32k
 dd: opening `/dev/scd0': Read-only file system
 It works ok on DVD-RAM media.

I think it is less intrusive to work with a
burn program than to upgrade the kernel
which probably regards BD-RE as fat data CD-ROM.

So let's see whether we can get cdrskin-0.4.5
to success.


I read MMC-5 for disabling write error detection
in order to get full speed.
That topic is scattered all over the document.

Two possible paths of exploration appear for now:

- Format the media with certification and use
  WRITE12 with streaming bit.
  This would give the drive chances to skip the
  error detection reading and it would give it a
  hint that speed is critical.

- Format the media with no spare area.
  This would take away the chance to correct errors
  and maybe disable the costly detection of errors.
  That would be format 31h.

Did you already post the format capacities
section from the output of  dvd+rw-mediainfo ?
With a DVD-RAM that looks like:
  READ FORMAT CAPACITIES:
formatted: 2236704*2048=4580769792
00h(800):  2236704*2048=4580769792
00h(800):  2295072*2048=4700307456
01h(800):  2226976*2048=4560846848
01h(800):  2217248*2048=4540923904

I would be interested in the availability of formats
30h(...) and 31h(...)

The path with streaming bit on certified media can
possibly be explored with DVD-RAM. Formatting without
spare area is not described for DVD-RAM but might hide
behind this format descriptor
00h(800):  2295072*2048=4700307456
which offers a suspiciously large payload capacity.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Thomas Schmitt
Hi,

Giulio Orsero:
 I formatted the media using dvd+rw-format with default/standard
 options (ie: didn't use any command line option)

Did you have technical indications that freshly purchased
media need to be formatted prior to first usage ?
I.e. did you ever test to write them out of the box ?
Did that fail ?

(DVD-RAM are sold formatted. They work immediately.)


 READ FORMAT CAPACITIES:
  formatted: 11826176*2048=24220008448
  00h(3000): 11826176*2048=24220008448
  30h(3000): 11826176*2048=24220008448
  30h(5000): 11564032*2048=23683137536
  30h(1000): 12088320*2048=24756879360
  31h(800):  12219392*2048=25025314816

This gives room for both my ideas.


 it [cdrskin] now works ok

Great. This gives the foundation for more experiments.


 Speed is the same as with cdrecord and growisofs, 1x instead of 2x, I
 think this is due to verification/defect detection.

4314915 bytes per second.
With 24220008448 bytes this would make more than
one and a half hour. :(


I'll begin with an experiment on WRITE12 and streaming bit.
Later we can explore formatting stunts.
I'll test with my DVD-RAM first and will inform you when
a development tarball is uploaded.

To Andy and Joerg:
Do you have any other ideas how to circumvent the hardware
error detection with DVD-RAM and BD-RE ?
Or do you have any other theory what makes both types
so slow ?


Have a nice day :)

Thomas
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Giulio Orsero
On Fri, Apr 11, 2008 at 11:50 AM, Thomas Schmitt [EMAIL PROTECTED] wrote:

 Did you already post the format capacities
 section from the output of  dvd+rw-mediainfo ?

I formatted the media using dvd+rw-format with default/standard
options (ie: didn't use any command line option)

INQUIRY:[HL-DT-ST][BD-RE  BE06LU10 ][YE03]
GET [CURRENT] CONFIGURATION:
 Mounted Media: 43h, BD-RE
 Media ID:  LGEBRE/S01
 Current Write Speed:   2.0x4495=8992KB/s
 Write Speed #0:2.0x4495=8992KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance: 2.0x4495=8992KB/[EMAIL PROTECTED] - 11826175]
 Speed Descriptor#0:02/11826175 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
BD SPARE AREA INFORMATION:
 Spare Area:393216/393216=100.0% free
READ DISC INFORMATION:
 Disc status:   complete
 Number of Sessions:1
 State of Last Session: complete
 Number of Tracks:  1
READ FORMAT CAPACITIES:
 formatted: 11826176*2048=24220008448
 00h(3000): 11826176*2048=24220008448
 30h(3000): 11826176*2048=24220008448
 30h(5000): 11564032*2048=23683137536
 30h(1000): 12088320*2048=24756879360
 31h(800):  12219392*2048=25025314816
READ TRACK INFORMATION[#1]:
 Track State:   complete
 Track Start Address:   0*2KB
 Free Blocks:   0*2KB
 Track Size:11826176*2KB
FABRICATED TOC:
 Track#1  : [EMAIL PROTECTED]
 Track#AA : [EMAIL PROTECTED]
 Multi-session Info:[EMAIL PROTECTED]
READ CAPACITY:  11826176*2048=24220008448


-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Giulio Orsero
On Fri, Apr 11, 2008 at 1:07 PM, Thomas Schmitt [EMAIL PROTECTED] wrote:
 Hi,

 Giulio Orsero:
  I formatted the media using dvd+rw-format with default/standard
  options (ie: didn't use any command line option)

 Did you have technical indications that freshly purchased
 media need to be formatted prior to first usage ?
 I.e. did you ever test to write them out of the box ?
 Did that fail ?

I tried using cdrecord and it basically errored out sayng this need
to be formatted. I'm going to do it but then it failed (on the list I
read cdrecord will be updated to be able to format BD-RE media soon).
So I formatted with dvd+rw-format and then cdrecord started writing to
it.
dvd+rw-format formatted it without complaining, if I retry now it says
it's already formatted and I need to use lengthly complete formatting
using -format=full (which I didn't use the 1st time)

The media is the one included with the burner; I will receive
different media in a few days.

This is the diff between output of dvd+rw-mediainfo with new media and
after I formatted it:

--- dvd+mediainfo.blank 2008-03-31 18:18:43.0 +0200
+++ dvd+mediainfo.formattato2008-04-01 15:48:55.0 +0200
@@ -5,23 +5,29 @@
  Current Write Speed:   2.0x4495=8992KB/s
  Write Speed #0:2.0x4495=8992KB/s
 GET [CURRENT] PERFORMANCE:
- Write Performance: 2.0x4495=8992KB/[EMAIL PROTECTED] - 12219391]
- Speed Descriptor#0:02/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
+ Write Performance: 2.0x4495=8992KB/[EMAIL PROTECTED] - 11826175]
+ Speed Descriptor#0:02/11826175 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
+BD SPARE AREA INFORMATION:
+ Spare Area:393216/393216=100.0% free
 READ DISC INFORMATION:
- Disc status:   blank
+ Disc status:   complete
  Number of Sessions:1
- State of Last Session: empty
- Next Track:  1
+ State of Last Session: complete
  Number of Tracks:  1
 READ FORMAT CAPACITIES:
- unformatted:  12219392*2048=25025314816
+ formatted:11826176*2048=24220008448
  00h(3000):11826176*2048=24220008448
  30h(3000):11826176*2048=24220008448
  30h(5000):11564032*2048=23683137536
  30h(1000):12088320*2048=24756879360
  31h(800): 12219392*2048=25025314816
 READ TRACK INFORMATION[#1]:
- Track State:   blank
+ Track State:   complete
  Track Start Address:   0*2KB
  Free Blocks:   0*2KB
- Track Size:0*2KB
+ Track Size:11826176*2KB
+FABRICATED TOC:
+ Track#1  : [EMAIL PROTECTED]
+ Track#AA : [EMAIL PROTECTED]
+ Multi-session Info:[EMAIL PROTECTED]
+READ CAPACITY:  11826176*2048=24220008448


--- cdrecord.minfo.blank2008-03-31 18:17:59.0 +0200
+++ cdrecord.minfo.formattato   2008-04-01 15:49:37.0 +0200
@@ -35,17 +35,36 @@
 Supported modes: PACKET SAO LAYER_JUMP
 Drive buf size : 2359296 = 2304 KB
 Drive pbuf size: 3932160 = 3840 KB
-Drive DMA Speed: 13496 kB/s 76x CD 9x DVD 3x BD
-Current Secsize: 0
+Drive DMA Speed: 13059 kB/s 74x CD 9x DVD 2x BD
+Current Secsize: 2048
 Disk type:  'BDW' (BD-RE)
 Disk class: 02
 Manufacturer:   'LGEBRE'
 Media type: 'S01'
 Disk:   is not in cartridge
 Media cartrige: write protect is off
+Free Spare Blocks:  393216
+Alloc Spare Blocks: 393216
+rzone size: 40
+rzone number:   1
+border number:  1
+ljrs:   0
+track mode: 4 copy: 0
+damage: 0
+reserved track: 0 blank: 0 incremental: 0 fp: 0
+data mode:  1
+lra valid:  0
+nwa valid:  0
+rzone start:0
+next wr addr:   0
+free blocks:0
+blocking factor:32
+rzone size: 11826176
+last recorded addr: 0
+read compat lba:0

 Capacity  Blklen/Sparesz.  Format-type  Type
-1221939220480 0x00  Unformated or Blank Media
+1182617612288 0x00  Formatted Media
 1182617612288 0x00  Reserved (0)
 1182617612288 0x30  Reserved (0)
 1156403220480 0x30  Reserved (0)
@@ -55,8 +74,8 @@
 Mounted media type:   BD-RE
 Disk Is erasable
 data type:standard
-disk status:  empty
-session status:   empty
+disk status:  complete
+session status:   complete
 BG format status: none
 first track:  1
 number of sessions:   1
@@ -67,5 +86,7 @@
  Track  Sess Type   Start Addr End Addr   Size
 ==
-1 1 Blank  0  -1 0 -1
+1 1 Data   0  11826175   11826176 -1

+Last session start address: 0
+Last session leadout start address: 11826176



-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Thomas Schmitt
Hi,

  READ FORMAT CAPACITIES:
 - unformatted:  12219392*2048=25025314816
 + formatted:11826176*2048=24220008448

Ahum. Looks really like initial formatting is needed.

I had a look into dvd+rw-format.cpp.

  fprintf (stderr,- you have the option to re-run %s with:\n
-format=full  to perform (lengthy) Full Certification;\n 
-ssa[=none|default|max|XXX[GM]]\n
  to eliminate or adjust Spare Area.\n,
  argv[0]);


It seems you could make an experiment with format 31h
(i.e. no spare area) by dvd+rw-format option
  -ssa=none

It might also be worth to check the impact of certification
on write error detection. I.e.:
  -format=full

I understand from MMC specs that certification is a read
process which evaluates the quality of data recording and
eventually records bad spots in a list. It is unclear to me
whether this list resides permanently on media.
But if we are lucky, the drive trusts the certified blocks
and refrains from reading them after write.
If we are a bit less lucky, then we need command WRITE12
rather than the usual WRITE10.

Hopefully the formatting will not damage the only media
you have. :)

I would propose to try both. It would be most economic to
do  -ssa=none  first, because i would expect it to be
the most likely to omit error detection on traditional
WRITE10 (SCSI command 2Ah).

With  -format=full  i would possibly expect that WRITE12
(command AAh) is needed.
There seems to be a WRITE12 experiment ready in
dvd+rw-tools-7.1/growisofs_mmc.cpp

Maybe Andy Polykov already knows more about that topic.
Andy ? Are you reading this ?


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Odd message from cdrecord

2008-04-11 Thread Bill Davidsen
cdrecord 2.01.01a35 (built from source), USB attached litescribe 
drive, TDK 16x DVD-R media. Recording is refused with a message

  DMA speed too slow (OK for 6x). Cannot write at speed 16x.
Since growisofs writes at 12x just fine (9.8x overall, 12x outer tracks) 
clearly there is an issue of some kind with deciding which speed to use, 
and speeds of 6x as working.


This is just FYI, I only use this setup to burn complete DVD images from 
precreated files (mkisofs+dvdisaster) and this isn't keeping me from 
backing up old data.


--
Bill Davidsen [EMAIL PROTECTED]
 Woe unto the statesman who makes war without a reason that will still
 be valid when the war is over... Otto von Bismark 




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Giulio Orsero
On Fri, Apr 11, 2008 at 3:28 PM, Thomas Schmitt [EMAIL PROTECTED] wrote:

 It seems you could make an experiment with format 31h
 (i.e. no spare area) by dvd+rw-format option
  -ssa=none

It took under a minute:
--- dvd+mediainfo.formattato2008-04-01 15:48:55.0 +0200
+++ dvd+mediainfo.ssa=none  2008-04-11 14:54:06.0 +0200
@@ -5,17 +5,15 @@
  Current Write Speed:   2.0x4495=8992KB/s
  Write Speed #0:2.0x4495=8992KB/s
 GET [CURRENT] PERFORMANCE:
- Write Performance: 2.0x4495=8992KB/[EMAIL PROTECTED] - 11826175]
- Speed Descriptor#0:02/11826175 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
-BD SPARE AREA INFORMATION:
- Spare Area:393216/393216=100.0% free
+ Write Performance: 2.0x4495=8992KB/[EMAIL PROTECTED] - 12219391]
+ Speed Descriptor#0:02/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
 READ DISC INFORMATION:
  Disc status:   complete
  Number of Sessions:1
  State of Last Session: complete
  Number of Tracks:  1
 READ FORMAT CAPACITIES:
- formatted:11826176*2048=24220008448
+ formatted:12219392*2048=25025314816
  00h(3000):11826176*2048=24220008448
  30h(3000):11826176*2048=24220008448
  30h(5000):11564032*2048=23683137536
@@ -25,9 +23,9 @@
  Track State:   complete
  Track Start Address:   0*2KB
  Free Blocks:   0*2KB
- Track Size:11826176*2KB
+ Track Size:12219392*2KB
 FABRICATED TOC:
  Track#1  : [EMAIL PROTECTED]
- Track#AA : [EMAIL PROTECTED]
+ Track#AA : [EMAIL PROTECTED]
  Multi-session Info:[EMAIL PROTECTED]
-READ CAPACITY:  11826176*2048=24220008448
+READ CAPACITY:  12219392*2048=25025314816

And now I can write at 2x!  Thanks, I didn't think about that (ssa=none)

cdrskin 0.4.5 : limited cdrecord compatibility wrapper for libburn
cdrskin: verbosity level : 1
cdrskin: NOTE : greying out all drives besides given dev='/dev/sg1'
cdrskin: scanning for devices ...
cdrskin: ... scanning for devices done
cdrskin: beginning to burn disc
cdrskin: status 1 burn_disc_blank The drive holds a blank disc
Current: BD-RE
Track 01: data  5259 MB padsize:  1024 KB
Total size: 5260 MB (598:33.37) = 2693353 sectors
Lout start: 5260 MB (598:35/37) = 2693353 sectors
Starting to write CD/DVD at speed MAX in real SAO mode for single session.
Last chance to quit, starting real write in   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
...
Track 01: 5260 of 5260 MB written (fifo 100%) [buf  98%]   2.3x.
^Mcdrskin: thank you for being patient since 548 seconds
Track 01: Total bytes read/written: 5514938368/5515986944 (2693353 sectors).
Writing  time:  548.333s
Cdrskin: fifo had 2692841 puts and 2692841 gets.
Cdrskin: fifo was 0 times empty and 270236 times full, min fill was 99%.
Min drive buffer fill was 43%
cdrskin: burning done

9.5 MB/sec !


 It might also be worth to check the impact of certification
 on write error detection. I.e.:
  -format=full

I think my kernel is too old, it exit after just 1 second:

$ dvd+rw-format -format=full  /dev/cdrom
* BD/DVD±RW/-RAM format utility by [EMAIL PROTECTED], version 7.1.
* 25.0GB BD media detected.
* formatting 0.0|:-[ FORMAT UNIT failed with SK=5h/INVALID FIELD IN PARAMETER LI
ST]: Input/output error
$

-- 
[EMAIL PROTECTED]


Re: Odd message from cdrecord

2008-04-11 Thread Joerg Schilling
Bill Davidsen [EMAIL PROTECTED] wrote:

 cdrecord 2.01.01a35 (built from source), USB attached litescribe 
 drive, TDK 16x DVD-R media. Recording is refused with a message
DMA speed too slow (OK for 6x). Cannot write at speed 16x.
 Since growisofs writes at 12x just fine (9.8x overall, 12x outer tracks) 
 clearly there is an issue of some kind with deciding which speed to use, 
 and speeds of 6x as working.

Just follow the instructions in the error message.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Odd message from cdrecord

2008-04-11 Thread Bill Davidsen

Joerg Schilling wrote:

Bill Davidsen [EMAIL PROTECTED] wrote:

  
cdrecord 2.01.01a35 (built from source), USB attached litescribe 
drive, TDK 16x DVD-R media. Recording is refused with a message

   DMA speed too slow (OK for 6x). Cannot write at speed 16x.
Since growisofs writes at 12x just fine (9.8x overall, 12x outer tracks) 
clearly there is an issue of some kind with deciding which speed to use, 
and speeds of 6x as working.



Just follow the instructions in the error message.
  


Since other software is able to write at higher speed than 6X I'll just 
use the fastest program available. I thought you might be interested in 
why it underestimates the DMA capabilities by at least 2x, I wasn't 
looking for hints on how to make burning take twice as long by running 
at a lower speed. With a disk plugged into that port I can get sustained 
write of 43MB/s, so it would appear that the hardware is capable of 16x 
operation and something is making cdrecord believe otherwise.


--
Bill Davidsen [EMAIL PROTECTED]
 Woe unto the statesman who makes war without a reason that will still
 be valid when the war is over... Otto von Bismark 




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Announcing cdrskin-0.4.4

2008-04-11 Thread Thomas Schmitt
Hi,

i wrote:
  (i.e. no spare area) by dvd+rw-format option
   -ssa=none
Giulio Orsero wrote:
 It took under a minute:
 And now I can write at 2x!  Thanks, I didn't think about that (ssa=none)

Thanks to dvd+rw-format and 04h FORMAT UNIT Format Type 31h.

This downgrades a BD-RE to kindof DVD+RW with 25 GB.
You lose defect management.
I understand that it is considered necessary because
25 GB media have a high risk to contain a bad spot
somewhere.

So it might be appealing to explore the ways with
certifying formatting. If we can talk that
into running at full speed by help of AAh WRITE12
then this would give us the opportunity to
repair bad spots by re-formatting.

I understand
  dvd+rw-format -format=full 
will apply 04h FORMAT UNIT Format Type 30h Sub Type 10b:
Full Certification: The entire data area shall be
 certified. The defect tables shall be initialized with
 defects discovered during the certification process.

I hope to have opportunity to check your BD-RE results
over the weekend with DVD-RAM.
Maybe i can make more proposals then.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Odd message from cdrecord

2008-04-11 Thread Joerg Schilling
Bill Davidsen [EMAIL PROTECTED] wrote:

 Joerg Schilling wrote:
  Bill Davidsen [EMAIL PROTECTED] wrote:
 

  cdrecord 2.01.01a35 (built from source), USB attached litescribe 
  drive, TDK 16x DVD-R media. Recording is refused with a message
 DMA speed too slow (OK for 6x). Cannot write at speed 16x.
  Since growisofs writes at 12x just fine (9.8x overall, 12x outer tracks) 
  clearly there is an issue of some kind with deciding which speed to use, 
  and speeds of 6x as working.
  
 
  Just follow the instructions in the error message.


 Since other software is able to write at higher speed than 6X I'll just 
 use the fastest program available. I thought you might be interested in 

star is the fastest program... you are missinterpreting messages

 why it underestimates the DMA capabilities by at least 2x, I wasn't 
 looking for hints on how to make burning take twice as long by running 
 at a lower speed. With a disk plugged into that port I can get sustained 
 write of 43MB/s, so it would appear that the hardware is capable of 16x 
 operation and something is making cdrecord believe otherwise.

I cannot help if your DVD drive is slow or has other deficits that make the
DMA speed test reporting too low numbers. This is not a cdrecord problem 
but a problem of your hardware or your OS.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Odd message from cdrecord

2008-04-11 Thread Bill Davidsen

Joerg Schilling wrote:

Bill Davidsen [EMAIL PROTECTED] wrote:

  

Joerg Schilling wrote:


Bill Davidsen [EMAIL PROTECTED] wrote:

  
  
cdrecord 2.01.01a35 (built from source), USB attached litescribe 
drive, TDK 16x DVD-R media. Recording is refused with a message

   DMA speed too slow (OK for 6x). Cannot write at speed 16x.
Since growisofs writes at 12x just fine (9.8x overall, 12x outer tracks) 
clearly there is an issue of some kind with deciding which speed to use, 
and speeds of 6x as working.



Just follow the instructions in the error message.
  
  
Since other software is able to write at higher speed than 6X I'll just 
use the fastest program available. I thought you might be interested in 



star is the fastest program... you are missinterpreting messages
  


I didn't know star could burn DVDs, it doesn't seem to be documented.
  
why it underestimates the DMA capabilities by at least 2x, I wasn't 
looking for hints on how to make burning take twice as long by running 
at a lower speed. With a disk plugged into that port I can get sustained 
write of 43MB/s, so it would appear that the hardware is capable of 16x 
operation and something is making cdrecord believe otherwise.



I cannot help if your DVD drive is slow or has other deficits that make the
DMA speed test reporting too low numbers. This is not a cdrecord problem 
but a problem of your hardware or your OS.
  


Since the hardware and the OS work at higher speeds with outer software, 
it's clear that cdrecord is making an incorrect estimate of the hardware 
capabilities. Since you seem uninterested in investigating why that 
happens I'll continue using software which can make better estimates of 
the hardware.


--
Bill Davidsen [EMAIL PROTECTED]
 Woe unto the statesman who makes war without a reason that will still
 be valid when the war is over... Otto von Bismark 




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]