How to read and interpret clipboard current registration data

[aah]

The menu item "Copy registration to clipboard" appears to be placing RAW data on the clipboard (the clipboard probe shows the string "The app cannot read the current registrations from Hauptwerk"). I'm working on an app which needs to read this data. Can you please tell me what the RAW Identifier string is and how to interpret the corresponding data?

Thanks!
AAH

[mdyde]

Hello Aah,

Hauptwertk's 'Copy reg' function copies the data to an internal combination within Hauptwerk (from which you can use Hauptwerk's 'Paste reg' function); it doesn't copy any data at all to the OS clipboard, and there's no way that you could extract the data from there, I'm afraid. (You can, however, use the 'List current ...' function to view all other combinations.)

[aah]

Thanks for the quick answer, Martin.

Too bad, I was hoping this idea could work.

I did see the "List/View combinations..." option and already tried a few things with it. The problem there is that the user has to uncheck lots of options in a dialog, and even then the output is too much information, and not quite the information I want.

What I'm looking for is a way to get the current state of all the stops, regardless of whether the registration has been saved in some way. Is there no way to do that? No MIDI message? No menu option?

Thanks!
AAH

[mdyde]

Thanks, Aah.

What I'm looking for is a way to get the current state of all the stops, regardless of whether the registration has been saved in some way. Is there no way to do that? No MIDI message? No menu option?

There's no native way to export the current states of all stops/switches to a text file, I'm afraid. You could conceivably configure all of the virtual switches individually to output MIDI on/off messages (e.g. NRPNs) and write an external application to receive them all and keep track of the states of the stops.

[aah]

There's no native way to export the current states of all stops/switches to a text file, I'm afraid. You could conceivably configure all of the virtual switches individually to output MIDI on/off messages (e.g. NRPNs) and write an external application to receive them all and keep track of the states of the stops.

Thanks for the answer. If I understand correctly, I could take the time to set up every stop to send out MIDI messages when turned on and off, and this would have to be done for every stop on every organ, which might work but obvisouly isn't practical, especially if my app is intended to be used by anyone other than myself.

For an app as expensive as Hauptwerk, options should be there for third party developers to read the current registration. To my mind, the easiest option would be to simply put the data on the actual clipboard when that menu option is used, since that's what it says it's doing (but it isn't) - and that's not hard to do. You just give the data a RAW identifier string and add it to the clipboard object. An app which knows the identifier and how to read the corresponding data can the do something with it. All you have to do for developers is document the format of the data on the clipboard so we can parse it. Otherwise you could add an option to send out a MIDI dump per sysex command (a lot more work on both sides). Ultimately it doesn't matter what form the data takes. It could be text, MIDI bytes, bytes in a binary file, it doesn't matter as long as it's readable. The easier the better, and whatever it is, it should have a keyboard shortcut.

Thanks!
AAH

[mdyde]

Hello AAH,

Thanks for the suggestion. I've logged as an enhancement request that you would like some means for external software to query the current states of all stops/switches, and added your notes to to that enhancement request.

[aah]

Thanks very much Martin. All the best in 2025.

[mdyde]

Thanks, AAH. You too.