Thanks, Dom.
Theorbe wrote:Hi Martin / other users
Would it be worth my while adding a feature to my random detuning utility to automate the cache rebuild? The same automation and list extraction / processing techniques I'm already using for the detuning would seem to apply in this case.
Thanks very much, Andy. If you have the time an inclination, I expect some people would appreciate that.
Note that the Organ Configuration Wizard will pop up the first time that any given organ is loaded in v6. If the organ was last used in v5+ it will just prompt to confirm the audio quality settings, whereas if last loaded in v4 it would also show the wizard pane giving the option to reset or migrate audio routing, etc. Hence if sending keystrokes to automate it you'd potentially need to handle those cases, so as to send the appropriate number of 'next' wizard button keypresses (Return/Enter on Windows, although that keyboard shortcut doesn't seem to work in Qt wizards on macOS). You could perhaps read the OrganID [assuming the organ definition isn't encrypted], then read the version it was last loaded in via its organ-configuration XML file, then send the appropriate number of key-strokes to tab through the wizard screens when the wizard finally appears after loading an organ. However, that might not help much, since it wouldn't work for encrypted organs. Perhaps it would be possible and better to get the utility simply to monitor the windows that appear and then send the appropriate number of 'next' screen presses accordingly. It would be rather fiddly. Still, I suppose you would need to make the mechanism have some means of detecting when an organ has finished loading anyway, in order to know when it would be appropriate to initiate loading the next one.
Edit: P.S. You could conceivably try to find the OrganIDs for encrypted organs by searching Hauptwerk's logs for the INF:2157 messages with the appropriate organ definition filenames (assuming that the user had loaded the relevant organ in the not-too-distant past, since the logs get rotated and old events will eventually be purged from them, so that they don't grow indefinitely).
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.