[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
Thomas Schmitt
bugzilla_noreply at kde.org
Thu Dec 1 11:57:53 UTC 2016
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #57 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,
> Or the code should in that case select a burning tool that can do that.
> (cdrecord? wodim? cdrdao?
That's well an option with cdrecord or wodim.
cdrdao is not as good a candidate because it does not understand the same
options as the others. I assume it gets its sector formats by the TOC or CUE
file which controls its actions, not by a global K3B write mode.
cdrskin has an option
fallback_program=...path...
which delegates the burn job to the given program path (e.g. /usr/bin/wodim)
if it detects options which it does not support, and if there are no
options which only cdrskin supports (e.g. drive_scsi_dev_family=).
I have to admit that i did not test this since years.
Are there K3B use cases known which would need -raw* writing ?
Have a nice day :)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the k3b
mailing list