Re: Announcing cdrskin-0.4.4
> 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 :)