https://bugs.kde.org/show_bug.cgi?id=398190
--- Comment #2 from Thomas Schmitt <scdbac...@gmx.net> ---
Hi,
the wodim option -raw96r is unusual and (years ago) was a source of trouble
for me. Any idea how K3B came to think that it is good to use it ?
It is chosen in libk3b/projects/k3bcdrecordwriter.cpp if
d->writingMode == K3b::WritingModeRaw
This seems to be configurable. Try to choose "TAO" or "SAO" instead.
(I see code which sets WritingModeRaw in src/k3bwritingmodewidget.cpp)
---------------------------------------------------------------------
I further wonder about the strange file addresses, like
/tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/Track02.wav
I assume that this is one path, not five. But why the blanks and why
four directories "SO U" ?
Can this be due to a misconfiguration of K3B ?
Does a directory "/tmp/SO U/SO U/SO U/SO U" exist while K3B is
attempting to do its job ?
---------------------------------------------------------------------
A cdrskin run from command line (without CD-TEXT for now) would look
like (while being in the directory with the Trackxx.wav files):
cdrskin -v dev=/dev/sr0 speed=48 -audio Track01.wav Track02.wav \
Track03.wav Track04.wav Track05.wav Track06.wav Track07.wav \
Track08.wav Track09.wav
Production of CD-TEXT would need a file for option "textfile=" which
K3B prepared and which you would need to prepare, too.
CD-TEXT has few influence of the burn success.
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
