Hi, > I found a bug report for k3b (didn't turn up earlier, I guess I didn't search > well enough), which contains some patches to dvd+rw-tools 7.1: > > https://bugs.kde.org/show_bug.cgi?id=246170
Ahum ... the patches do not address this problem, i fear. Nevertheless, one of them addresses a known bug which Andy Polyakov declared harmless but which is suspect to correlate with BD-R burn problems: https://bugs.kde.org/attachment.cgi?id=49645 The auto-format size prediction problem is nasty. It does affect my own stuff with BD-RE. My test for image size and the auto-formatting happen in quite different modules. Probably i will have to perform auto-formatting several levels higher in the library stack. Nice behavior would be to first determine the image size and then to choose a formatting that allows to burn it - if possible at all. Less nice but still quite safe would be to apply default size auto-formatting to blank BD-RE before the size test is done. Well, at least i do not have such a problem with BD-R where a misburn or an inappropriate formatting spoils expensive media. > I wouldn't use more than 4x myself, but since the writing with defect > management was so slow, I figured 8x would at least speed it up. It didn't, > really. During writing with Defect Management it will frequently switch from writing to reading. This is what makes it so slow. Possibly the drive does not accelerate to full speed for the short writes. They can hardly be larger than the drive buffer. 2 MB or so. The drive has to checkread before it can discard the data from the buffer. To get smooth i/o, i'd rather write half buffer size and keep the other half ready for receiving data. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org Archive: http://lists.debian.org/94663414417...@192.168.2.69