https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #49 from Thomas Schmitt <scdbac...@gmx.net> --- Hi, > http://commits.kde.org/k3b/b189d1c39b52d5b646a089863eb8f44d3eeaa333 > libk3bdevice/k3bdevice.cpp: > emit infoMessage(i18n("Medium is not of multi-session type and does not > contain ISO 9660. Cannot emulate multi-session on it."), MessageError); To make this statement true, the list of overwritable media needs to be completed. K3B functions determineMultiSessionModeFromMedium() and setupMultiSessionParameters() have: if( info.mediaType() & (K3b::Device::MEDIA_DVD_PLUS_RW| K3b::Device::MEDIA_DVD_PLUS_RW_DL| K3b::Device::MEDIA_DVD_RW_OVWR| K3b::Device::MEDIA_BD_RE) ) { So setupMultiSessionParameters() will not look for ISO 9660 if the medium is MEDIA_DVD_RAM or MEDIA_BD_R_RRM. In this case the error message statement "does not contain ISO 9660" might be wrong. ------------------------------------------------------------------------ > libk3bdevice/k3bdevice.cpp Well, let's hope that we translated correctly from growisofs. (Everybody is invited to check.) What to do with growisofs_mmc.cpp : get_2k_capacity() which has special processing for BD-R POW ? It computes the remaining writable space on the medium. It seems that capacities computed in libk3bdevice/k3bdevice.cpp are about the overall capacity of the medium. Any idea where the writable space on medium is determined ? A tester could possibly tell, whether a BD-R with a first session written by growisofs shows any wrong numbers when inspected by K3B. ------------------------------------------------------------------------ Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
