Summary: | different speed setting behaviour for k3b? | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Joerg de la Haye <haye> |
Component: | general | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Joerg de la Haye
2006-01-21 12:56:49 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 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). 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.
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. Auto in K3b means that K3b decides. And that will not change. |