Bug 82666

Summary: File example should use current disk
Product: [Unmaintained] kaudiocreator Reporter: Eric Seynaeve <eric>
Component: generalAssignee: Gerd Fleischer <gerdfleischer>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Eric Seynaeve 2004-06-01 22:39:54 UTC
Version:           1.0 (using KDE 3.2.2, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.4-54.5-default

The example in the file location wizard(s) should use the current inserted disk. If there is no disk, or the disk is not known in the database, the example should revert back to the default settings.

At the same time, also add the example, in smaller font, under the location text fields in the Encoder Configuration. This immediatly shows the user whether the current settings are any good.

Otherwise, great application. With the new multitrack disk support, it's getting even better :-) Kudo's
Comment 1 icefox 2004-06-08 14:50:16 UTC
One of the reasons the example string is used is that each part is different.

For example something silly like:

Album: Destiny's Child
Group: Destiny's Child
Track 6: Destiny's Child
Comment 2 Eric Seynaeve 2004-06-11 21:08:19 UTC
But how many times does that occur? Most of the albums I have, have clearly seperate names. The ripper I used under Windows (can't remember the name) did this. Even more, it showed a list or dropdown or could cycle (don't remember exactly) with the name of all the tracks according to the current schema. This provided a very easy way to check the effect of the schema.

And even in the rare cases where there are silly things like you suggest, combining this with the (very clear - congratulations) wildcards, it would become clear what would happen. At least it would tell me more than the settings from an album I'm not familiar with.
Comment 3 Justin Zobel 2021-03-09 03:51:50 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Christoph Cullmann 2025-06-10 16:05:24 UTC
This project is unfortunately no longer maintained.

If a new maintainer wants to step up and take care, the project is archived here:

https://invent.kde.org/unmaintained/kaudiocreator

You can just clone it in your private namespace on invent.kde.org and if you have started to work on it and fixed/implemented something get it reviewed and the project unarchived.

Sorry for the inconveniences.