Log the details of every found multi-sample during Analyse (the run log proposed in #336)

documentation/CHANGELOG.md

@@ -4,6 +4,7 @@
 
 * New: Added support for the E-mu Emulator II (IMG, EMUIIFD, HFE). One disk becomes one multi-sample: the key map of the bank gives the zones with their key ranges and root keys and each voice its name, its loop and its audio, which is expanded from the companded bytes the sampler feeds to its AM6072 DAC. A bank which is larger than one floppy is reported as continuing on another disk. Read only.
 * New: A note is logged when a loop of a converted preset audibly clicks at its wrap-around point (the step back to the loop start is many times the normal movement of the waveform and a substantial part of the level). Sample libraries ship such loops surprisingly often - 17 of 152 presets across three commercial Ensoniq libraries - and without the note the first hint is the converted preset ticking on the destination device. Nothing is changed: the loop is written as the source authored it, and the note points to the snap-to-zero-crossing and loop cross-fade processing options which remove such clicks. A loop which already has a cross-fade is not reported.
+* New: The Analyse run can log for every found multi-sample what it contains (option "Log analysis details", on the command line `-ad`): the mapping of its zones with their sample format, loops with their cross-fades, envelopes, LFOs and the filter with its modulators. Only attributes which a source actually uses are logged, so searching the log finds the sources which use a specific feature - e.g. all presets of a library with a filter envelope, a loop cross-fade or a release trigger. The details describe the source as it was read, before any processing is applied.
 * Fixed: The sample and program files which a preset references are now looked up ignoring the upper/lower case of their name. Sampler file systems are case-insensitive and their CD-ROMs store all names in upper case, but a preset might well reference them in lower case. On a case-sensitive file system, which is the normal case on Linux, none of those samples could be found (e.g. 'STR SEC.6 -L.WAV' referenced as 'STR SEC.6 -L.wav'). This affects the Akai S5000/S6000 (AKP/AKM), Akai MESA, Akai MPC and MPC1000, FL Studio DirectWave, Teenage Engineering OP-XY and Synclavier Regen formats as well as all formats which use the common sample search (Ableton, Deluge, EXS24, NI Kontakt, NI Maschine, 1010music, SXT and TX16Wx) - the latter did only try the file ending in all upper and all lower case, so a name which differs in its case anywhere else was still not found.
 * Fixed: When a sample was not found next to its preset, the search jumped the configured number of folder levels up in one go and took whatever the recursive search found first. Two libraries below the same folder which name their samples alike - the normal case for the variants of a library - then fed a preset the sample of the other library, which sounds wrong and, since the preset keeps its own loop points, clicks at the loop. The search now goes up one level at a time and stops at the first level which contains the file, so a sample close to the preset always wins over one of the same name further away.
 * Fixed: The category names 'Winds' and 'World' were not detected when they were read back from a preset which stores the category as text: 'Winds' was detected as FX - from the 'Wind' sound effect - and 'World' was not detected at all. The name of a category is now a keyword of its own, which is checked for all of them.

documentation/README.md

@@ -102,7 +102,7 @@ For Linux (BSD not tested) there is also a `Makefile` for build and install with
 6. Choose the type of the created output format: either single presets, a preset library which contains all found source files, a performance which contains several presets with settings or finally a library of performances. Only some destination formats support libraries and performances, all others are greyed out.
 7. Press the *Convert* button to start the conversion. The progress is shown with notification messages in the log area, which you should check for potential errors like defect source files, skipped folder, etc. This log is also written to a file in the output folder.
 
-Alternatively, press *Analyse* to analyse all potential source files but do not to write any file(s). Use this to quickly check for errors before finally running the slower conversion process.
+Alternatively, press *Analyse* to analyse all potential source files but do not to write any file(s). Use this to quickly check for errors before finally running the slower conversion process. If the option *Log analysis details* is enabled, the run additionally logs for every found multi-sample what it contains (see the Options section below).
 
 ## Picking specific source presets (Contents...)
 
@@ -132,6 +132,7 @@ Clicking the *Process* button open a dialog to configure processing options whic
 
 * **Create folder structure**: If enabled, sub-folders from the source folder are created as well in the output folder. For example, if I select my whole "Sounds" folder, there are sub-folders like `Sounds/07 Synth/Lead/01W Emerson'70 Samples`. In that case the output folder would contain e.g. `07 Synth/Lead/01W Emerson'70.multisample` if Bitwig multisample is selected as the destination format.
 * **Add new files**: Starts the conversion even if the output folder is not empty. Duplicates will get unique names by adding numbers.
+* **Log analysis details**: If enabled, the *Analyse* run logs for every found multi-sample what it contains: the mapping of its zones (key/velocity ranges, root note, sample rate, bit resolution, channels, length), loops with their cross-fades, envelopes, LFOs and the filter with its modulators. Only attributes which a source actually uses are logged, so searching the log finds the sources which use a specific feature - e.g. all presets of a library with a filter envelope or a loop cross-fade. The details describe the source as it was read, before any processing is applied. On the command line use `-ad` instead of `-a`. The attribute names are deliberately not translated, so search patterns do not depend on the language of the user interface.
 * **Dark Mode**: Toggles the user interface between a light and dark layout.
 
 [1]: https://github.com/git-moss/ConvertWithMoss/blob/main/documentation/SupportedFeaturesSampleFormats.ods
@@ -149,7 +150,7 @@ First display all of the available attributes by typing:
 The following output is displayed (the processing parameters are omitted):
 
 ```
-Usage: ConvertWithMoss [-afhPV] -d=DESTINATION [-l=LIBRARY]
+Usage: ConvertWithMoss [-afhPV] [-ad] -d=DESTINATION [-l=LIBRARY]
                        -s=SOURCE [-t=TYPE] [-p[=KEY=VALUE...]]...
                        SOURCE... DESTINATION_FOLDER
       SOURCE... DESTINATION_FOLDER
@@ -158,6 +159,14 @@ Usage: ConvertWithMoss [-afhPV] -d=DESTINATION [-l=LIBRARY]
                              using a wildcard), followed by the destination
                              folder to write to.
   -a, --analyze            If present, only analyzes the potential source files.
+      -ad, --analyze-details
+                           Like --analyze, but additionally logs for every found
+                             multi-sample what it contains: the mapping of its
+                             zones, the sample format, loops, envelopes, LFOs
+                             and the filter. Only attributes which a source
+                             actually uses are logged, so searching the output
+                             finds the source files which use a specific
+                             feature.
   -d, --destination=DESTINATION
                            The destination format.
   -f, --flat               If present, the folder structure is not recreated in