Bug 120548 - different speed setting behaviour for k3b?
Summary: different speed setting behaviour for k3b?
Status: RESOLVED INTENTIONAL
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-21 12:56 UTC by Joerg de la Haye
Modified: 2006-11-13 15:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg de la Haye 2006-01-21 12:56:49 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I discovered a bug in growisofs 6.0 which lead me to a follow up in k3b. This is the mail I wrote to the author of growisofs yesterday, see below that for my thoughts concerning k3b:



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

Hi Andy,

I found a bug in growisofs 6.0 that hasn't been there in earlier versions.
If I start a burn without setting the speed manually via "-speed" it burns 
like it should at the maximum speed the drive and the media is capable of 
(thanks for that fix, it didn't work with the version before).
If I set the speed manually growisofs starts to burn at 4x speed, no matter 
whether I set the speed to 1x, 2x, 8x or 16x (my drive has a maximum speed of 
16x).

I came along that one as I burned one DVD on the command line and the next one 
via k3b, which passes the speed-option for every burn.

Any idea for a quick fix? I've had a quick look at the code, growisofs.c seems 
to be alright, speed_factor is set correctly so the problem must be somewhere 
in growisofs_mmc.cpp, but I haven't recognised it.

Regards,
Jörg

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



It is definitely a bug of growisofs 6.0, it did work the version before, but as a follow up in k3b I can't burn faster than 4x. k3b seems to set the speed-Option of growisofs every time, even if I choose "Auto" in the GUI. And if you don't refresh the speed options it may choose a suboptimal one. Wouldn't it be easier if k3b only sets "-speed" for growisofs if I choose a certain speed in the menu? With this behaviour you won't need to do a refresh of the speed options in k3b's burning dialogue if you choose "Auto" (and let growisofs do the job of choosing the maximum value). Apart from that an important bug is fixed in growisofs version 6.0, it can burn at full speed now.
Comment 1 Joerg de la Haye 2006-01-21 13:27:58 UTC
As a workaround in k3b you have to choose "Ignore" for speed at the burning menu. Now k3b burns flawlessly at maximum speed of the media/burner combination, thanks to growisofs 6.0 :-). But I still think "Auto" should have the same effect.

I discovered additional information about that bug in growisofs 6.0 and sent them to the author, maybe they are interesting for other users also:



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

Hi Andy,

concerning my bug report from yesterday:

My burner is a LG GSA-4167B, its minimal burning speed for DVD-/+R is 2x, so 
it seems to have something todo with your changes you mentioned in your 
changelog ("allow for more intuitive interpretation of -speed factor with 
units returning minimal velocity other than 1x").

Regards,
Jörg
Comment 2 Joerg de la Haye 2006-01-30 11:21:17 UTC
The speed bug in growisofs has been fixed in version 6.1, so my problem has gone away.

But I think it would be nice to let growisofs handle the burning speed if you choose "Auto" in k3b (see above).
Comment 3 Sebastian Trueg 2006-01-31 09:37:55 UTC
On Monday 30 January 2006 11:21, Joerg de la Haye wrote:
> But I think it would be nice to let growisofs handle the burning speed if
> you choose "Auto" in k3b (see above).


why? k3b does the exact same thing as growisofs does. choosing the max. But 
Auto is intended to also choose a lower sped for on-the-fly copy in the 
future as is done for audio projects.
Comment 4 Christoph Burger-Scheidlin 2006-11-11 22:29:07 UTC
If I understand the bug report correctly, k3b should only set the speed option explicitly, if it was set to something other than max. If it is set to max, then leave it up to growisofs. The problem I see with that is that the max option is then semantically dependent on growisofs' behavior and the interface has to be updated everytime growisofs changes.

So can this be closed as WONTFIX, since k3b determines the best possible speed just like growisofs does?

I wonder if it is worth to convince the growisofs folks to have an option -speed=max so that this setting can be passed to growisofs. On the other hand, k3b needs to determine speeds anyways, since it needs some way of selecting the speeds to present to the user, so this is only an issue for growisofs 6.0.
Comment 5 Sebastian Trueg 2006-11-13 15:36:29 UTC
Auto in K3b means that K3b decides. And that will not change.