[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Thomas Schmitt]

https://bugs.kde.org/show_bug.cgi?id=137436

--- Comment #67 from Thomas Schmitt <scdbackup at gmx.net> ---

Hi,

for shorter logs you could try to burn only 100 MB to reduce the number
of logged SCSI commands by about 1/7.

---------------------------------------------------------------------------

We may also for now leave the CDEmu problems undiagnosed and concentrate on
getting the K3B and cdrskin aspects fixed.

The need to add option -tao for "DVD+R" media is a CDEmu problem, too.
I will examine the opportunities to recognize a CDEmu drive with libburn's
automatic write type delection. But that will in any case only be a hack
that is not in effect with currently released cdrskin versions.

Unconditional "-tao" is clumsy and might cause other problems or unfulfilled
expectations of the user.

So you too should consider to detect CDEmu by the Vendor and/or Model
id string of the drive. From the "Devices" lines in
  https://bugsfiles.kde.org/attachment.cgi?id=102515
like


  DEmu Virt. CD/DVD-ROM 1.10 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
DVD+R) [DVD-ROM, DVD+R, CD-ROM, CD-R] [SAO, TAO, RAW, SAO/R96R, RAW/R16,
RAW/R96R] [%7]

i expect that the Vendor is "CDEmu" and the Model is "Virt. CD/DVD-ROM".
(You may ask by a run of: cdrskin --devices)

I believe that the Drives lines are composed in
  src/k3bdebuggingoutputfile.cpp
by

  Q_FOREACH( K3b::Device::Device* dev, k3bcore->deviceManager()->allDevices() )
{
     addOutput( "Devices",
                QString( "%1 (%2, %3) [%5] [%6] [%7]" )
                .arg( dev->vendor() + ' ' + dev->description() + ...

So this would be the device object properties to inquire for adding "-tao"
in the case of Device->MediaType values MEDIA_DVD_PLUS_R or
MEDIA_DVD_PLUS_R_DL. (In CdrskinWriter the field is burnedMediaType, i guess.)

Have a nice day :)

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.