Just found my old test notes, I had completely forgotten about them. Now I remember that I promised to report back some bugs I had found (+just found lots of new ones). Well, better late than never. Sorry about that.
Some of these points are already reported/requested by me (no answers), and there might be some things that others have reported/asked, sorry if there's duplicates.
Bugs/problems/usability/etc.: (hopefully this is readable, I split long lines)
1. Links in the about dialog doesn't work.
2. "Formats", "Decoders" and "Scripts" setting tabs doesn't have add/remove buttons like the "Encoders"
setting tab has.
3. Main window profiles dropdown menu: changing the profile doesn't change the "basket" icon to the
selected profile.. though the dropdown button shows the basket beside the selected profile name.
4. "Only if found" selected saving bug.
1) Clear CUETools appdata folder, i.e. start with "clean" settings before opening CUETools.
2) Start app and select e.g. "my music" folder so that you can access the "Action" settings in the main
window.
3) Select "Verify" and "only if found"
4) Open settings and click OK
= "only if found" reverted back to "default".
5. It's a bit confusing what is saved to a profile in the main window. The "Extra" settings "pregap" and
"data track" settings are global (gets changed to every profile) while "offset" is saved per profile. (Ok
ok, "pregap" and "data track" settings are in fact "session" only settings, no point of saving them, right?)
Same thing with the "audio output" settings; the 1st and 2nd dropdown selection boxes and "slider" settings
are global though the "lossless/lossy/hybrid/none" setting is per profile.
Also, "correct filenames" "mode" settings are global.
6. Why isn't the "format" (1st) dropdown selection box nor "compression slider" not disabled when "none" is
selected in the "audio output" section?
6.1. "Unhandled exception" bug when changing the "compression slider" setting while "none" selected in the
"audio output" section.
7. Is the small file browser "placeholder" seen in the far left designed to be that way? There's a very
small scroll button(s) seen in the bottom of it and one can select folder/files even though the browser is
"hidden".
8. "Data track" field disabled bug.
1) Clear CUETools appdata folder, i.e. start with "clean" settings before opening CUETools.
2) Start app and select e.g. "my music" folder so that you can access the "Action" settings in the main
window.
3) Change "audio output" to "none"
Side note: notice how "embedded" in the "mode" gets disabled. Still selected.. possible problem if
not noticed and changed before clicking "Go"?
4) Select "verify" in the "action" and back to "encode"
-> "Data track" gets disabled.
5) Select "lossless"
= "Data track" still disabled. Different types of main window "setting changes"/selections either does
or doesn't enable the "Data track" field, it seems that there's no logic to it at all.
9. "Empty" profile bug.
1) Clear CUETools appdata folder, i.e. start with "clean" settings before opening CUETools.
2) Delete one by one all profiles (except the default, impossible to do that).
-> profile dropdown lists only default profile.
3) Close app and start it again.
= Profile dropdown lists default profile AND an empty profile with no name. Happens because the empty "Profiles="
setting in the "settings.txt" is parsed incorrectly?
4) Select the "empty" profile and Close app.
-> A "profile-.txt" file is created in the appdata folder for the empty profile.
10. ReadMe.txt old/incorrect filename and path formatting variables.
1) Clear CUETools appdata folder, i.e. start with "clean" settings before opening CUETools.
2) Set the "logname format" to "%F.accurip" (without quotes).
-> that setting is changed in the settings.txt after OK clicked.
3) Do verify operation.
= The file created is "%F.accurip" (without quotes).
4) Close app and restart.
5) Open settings dialog.
-> Notice how the "logname format" is now "%filename%.accurip" (without quotes).
6) Click OK.
-> Only after this, that setting is changed in the settings.txt.
7) Open settings dialog.
8) Set the "logname format" to "%Y.accurip" (without quotes).
-> that setting is changed in the settings.txt after OK clicked.
9) Close app and restart.
10) Open settings dialog.
-> Notice how the "logname format" is still "%Y.accurip" (without quotes).
So, it seems that only the old "%F" is detected as a "failsafe" (updating from previous versions), AND
only when opening the settings dialog.
11. "Verify" profile used when running "CUETools.exe /verify *.cue" + other oddness.
Prerequisite: a rip of an album that is not present in the AR database.
1) Clear CUETools appdata folder, i.e. start with "clean" settings before opening CUETools.
2) Run CUETools.exe /verify "filename.cue"
= "Error: Object reference not set to an instance of an object." Error when no appdata folder
settings.txt file present?
3) Open and close app.
-> "settings.txt" created, no settings file for the "Verify" profile created.
4) Run CUETools.exe /verify "filename.cue"
= Again, "Error: Object reference not set to an instance of an object.".
5) Open app and settings, enable the "In source folder" under "Write AccurateRip log" setting, click OK
and close app.
6) Run CUETools.exe /verify "filename.cue"
= No errors, CUETools makes a "only if found" AR verification. Notice that there's no "Verify" profile
file at all!! And the "settings.txt" (=default profile + some general settings (which are not in other
profile files)) file has both "DefaultVerifyScript" and "Script" set to "default", which means that
CUETools has some "internal" default settings, at least, for the "Verify" profile.
7) Open app, change to "verify" profile and back to "default", close app.
= Now, for some reason, "settings.txt" has "DefaultVerifyScript=only if found" (no change to "Script"
setting). The created new "profile-verify.txt" file has "DefaultVerifyScript=default" and "Script=only
if found". So, suddenly default profile "inherited" the "DefaultVerifyScript" setting from the "verify"
profile "Script" setting!?
8) Open app, check "action->verify: used script" from both "default" & "verify" profiles.
= Both profiles have "only if found" scripts set with the "verify" action! Look at the point 7 result
text, the 2 settings are different, why is both profiles using "only if found" scripts?!
9) Close app.
= Oddness continues: now the "settings.txt" profile "Script" setting is changed to "only if found"!?
10) Open app, select "verify" profile, delete it and close app.
= "profile-verify.txt" is not deleted though "verify" is removed from the "Profiles" setting in the
"settings.txt".
11) Open app, change the "verify" action script to "default", close app.
12) Run CUETools.exe /verify "filename.cue"
= Still using the "only if found" script when checking!
13) Delete "profile-verify.txt" file from the appdata folder.
14) Run CUETools.exe /verify "filename.cue"
= Still using the "only if found" script when checking! Again, "internal" default settings?
15) Open app and settings, disable the "In source folder" under "Write AccurateRip log" setting, click
OK and close app.
16) Run CUETools.exe /verify "filename.cue"
= Again, "Error: Object reference not set to an instance of an object.". So, settings in fact read from
default profile file and from "internal" default settings?
Bug/problem summary from this point only:
1. "CUETools.exe /verify" doesn't work without settings.txt file and when "In source folder"
setting is set to off.
2. Using of "internal" profile default settings.. + using/mixing those settings with settings that
ARE saved to a file (e.g. "ArLogToSourceFolder" read from default profile, "only if found" script
setting read from "internal" default setting AND/OR from saved "verify" profile (ignoring the
"ArLogToSourceFolder" from that same profile)). Messy, eh?
3. "DefaultVerifyScript" and "Script" settings jumping across profiles & across those settings.
4. Profile files not deleted when deleting profiles from the GUI.
Maybe the profile/settings system needs a rethink/redesign? I'm really sorry to say this but, nicely put, currently it's a big mess (judging from black-box testing). There might be more bugs lurking because of the profile/settings design. Points 4, 5, 9, 10 & 11 attribute to this concern.
Feature reqs/misc.:
12. GUI beautification(?): CUETools started with /verify and filename -> window has no "proper" title bar (not really needed I guess) and shows "default" VS icon in the taskbar.
13. GUI beautification(?): "Tagging" settings tab: "Album art", "resize if resolution >" text field goes slightly over the above input field.
14. "Set read-only attribute to AR log file" feature in the options? Or how to amend the "only if found" script to do it?
14.1. Is there a manual of using the scripting feature? Kind of pointless to offer a script editing/adding feature if there's no language syntax nor method names to call for documented?
15. Include the version of CUETools in the log. IMO, it's always a good practice to log the app name+version.
Questions/notes:
16. Just noticed that there's an update to CUETools, the 2.0.4a version. I've been using 2.0.4 for some time.. with the annoying "logname setting not saved" bug (I wrote this part first.. all bugs/etc. listed in this post have been tested with the latest 2.0.4a version). Completely missed that ("silent") update. And "check for updates" in the app failed to notify me. Version value problems? (from the "2.0.4a" version package: CUETools.exe: 2.0.3.1, settings.txt: Version=203 and motd.txt: CUETools 2.0.4) Also there's no mention in the changelog that you made the "only if found" script to work with the "CUETools.exe /verify" (=changes to profiles system). Found it by accident just now when testing the new bugs I found. Maybe other people don't like to read changelogs but I do. I don't want to guess what's changed, or being surprised by them (especially if that happens later after they have already affected my "process").
17. What's the situation with CUETools? Are you still developing it? IIRC you wrote that you have moved on to other projects and you see CUETools ready? IMHO it's weird that the 1st post mentions that "Current stable version: 1.9.5a", and the last version changelog says "Experimental profiles system". Is the 2.0.4a still an unstable/experimental version? Also, maybe an installer to finish off the app? Manual (online)? E.g. the "%filename%['('%unique%')'].accurip" should be documented (picked that out from this topic). IMHO, lots of polish needed to call this app ready.
18. Does CUETools use the local AR "cache" (it's sometimes a stale cache) in "*\Application Data\AccurateRip\AccurateRipCache"?
19. It seems that "ArCueDotNet.exe" does not/can't use any profiles, is this true?
P.S. Congrats on the very high number of downloads, CUETools is a success.
P.P.S. Sorry about this "bomb".. I wouldn't have done this much free work for a program I don't like. (Here's hoping that it doesn't go to waste.)