https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #45 from Thomas Schmitt <scdbac...@gmx.net> --- Hi. a summary of the winded road which brought me to the current diagnosis. After my theory of lack of multi-session support on overwritable media brought us to the code where this support is already implemented, i first thought it was only about a missing media type in the list of overwritables. But the code for detection of BD-R in POW state made it clear that i misinterpreted the list of overwritables in growisofs. The growisofs list does not contain BD-R POW (profile 0x41 + feature 0x38) but rather BD-R RRM (profile 0x42), which is still missing in K3B's list. Since growisofs does not format BD-R to RRM by default, there had to be a different deviation of K3B's determination of Next Writable Address from growisofs method of determination. I found this deviation when comparing K3b::...::getNextWritableAdress() with plusminus_r_C_parm() in growisofs_mmc.cpp. Discovered problems along that road: Obviously the K3B code to predict growisofs decisions was not completely updated after growisofs introduced support for BD media. One would possibly have to compare all media related gestures with those of growisofs. (I compared the computation of lastSessionStart for BD-R POW and found it correct. But other aspects may still offer pitfalls.) One known deviation is the difference between the list of overwritables in growisofs (DVD+RW, DVD+RW DL, formatted DVD-RW, DVD-RAM, BD-R RRM, and BD-RE) to the ones in K3B (MEDIA_DVD_PLUS_RW, MEDIA_DVD_PLUS_RW_DL, MEDIA_DVD_RW_OVWR, MEDIA_BD_RE). I.e. DVD-RAM and BD-R RRM are missing in the K3B list of overwritables. It seems essential that both programs use the same list. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
