Comment 14 for bug 1458230

My work on verifying that this is genuinely a problem in libburn has stalled. I apologise for this, but more so for having neglected to provide a potentially critical interim update (which now follows upon the prompting of someone having clicked a “me too” button).

Whilst I was in the process of preparing back-ups, for eventual storage on BD-R (hence, in effect, gathering the materials for further testing of the behaviour I'd reported), I became aware that all USB ports on the “test” computer were version 1.1. (I have no explanation of how this had eluded me for so very long.)

The laws of physics seem to establish that, for my initial burn, using the k3b GUI, I must have got the ISO image onto an internal HD. My memory is does not assist me with that point, though.

Certainly, all the libburn Blu-ray burns (but not the libburn DVD-RW test burn) were of ISOs held on an external HD, connected via a USB port (now recognised as USB 1.1). (I suspect I'd fooled myself by creating the ISOs using a laptop, rather than the desktop in which the burner is mounted!)

Pulling out some xoriso stats, from my earlier post:
   xorriso : UPDATE : 10189 of 10189 MB written (fifo 0%) [buf 60%] 0.2x.
   xorriso : UPDATE : Closing track/session. Working since 10285 seconds

My burn speed was 0.99 MB/s or 7.9 Mbit/s. USB 1.1 is rated at a maximum of 12 Mbit/s. I could not find a definite answer as to whether that is for the payload or for payload + error correction + control, but it does not seem unreasonable to think the 7.9 Mbit/s was the limit of my USB connection.

I subsequently put a USB 2.0 card into the PC, but it will be a few weeks before I can pick up the testing again. For the moment, I think the most likely conclusion for this bug report is closure on grounds of raiser's idiocy. However, I suggest that anyone, who feels he may be experiencing this “bug”, posts his detailed observations (ideally without missing the obvious).