Thanks, Ken.
kaspencer wrote: I would expect that the configuration of any organ sample set should not be affected by the configuration of any organ sample set which had been prevously loaded in the same session. Therefore I would expect that before loading the second organ, all consequences of the loading of the first organ would be obliterated - surely this is the case with all settings except the "Defaults to ON".
Just to be clear, nothing within Hauptwerk is directly setting the state of any given MIDI stop within any given organ unless you've mapped that MIDI stop to something within that particular organ (in which case Hauptwerk sets it to the default you specify). If a MIDI stop is mapped to a virtual stop in one organ, Hauptwerk simply leaves the MIDI stop in whatever state you specify for that organ when you unload it. If that particular MIDI stop isn't mapped to anything in a subsequent organ then it would still be in the state that Hauptwerk left it in from the previous organ (except that your MIDI hardware is turning it off and then on again later for some reason). It isn't the case that the 'configuration' of one sample set is affecting the configuration of another -- simply that one sample set is setting the state of the relevant MIDI stop (because you told it to), but another sample set isn't (because you didn't tell it to).
Strictly speaking, it wouldn't technically be possible in general that "
all consequences of the loading of the first organ would be obliterated", because for that to be true Hauptwerk would need to put all of the MIDI stops back into the states in which they were before MIDI was started (e.g. when Hauptwerk was launched). I.e. it would need to be able to query the initial states of all of your MIDI stops. In general there's no way within the MIDI standard that Hauptwerk could do that (digital organ bit-field MIDI implementations, such as Rodgers', conceivably excepted). For example, you might have had a registration drawn on a digital organ, or you might have certain couplers on a digital organ which you would almost always want to remain on (e.g. ventils, combination couplers, or a bass coupler).
Simply assuming that all of the console's MIDI stops were initially off, and thus explicitly setting them to off whenever stopping MIDI is something that one may not conceivably not want (e.g. for some digital organ couplers/stops as above, or for solenoid-actuated MIDI stops), but overall I think think it would be an acceptable compromise given that in Hauptwerk v6+ master combinations and functions can optionally be auto-detected 'for all organs'. Hence that's the change I made, which should give the behaviour that you'd personally prefer (assuming that your MIDI hardware abides by those 'off' messages as MIDI stops).
One last clarification:
mdyde wrote:As I understand, you would prefer that Hauptwerk always defaults all mapped MIDI stops to off when unloading an organ (instead of to their user-specified default states), especially so that those MIDI stops are off if they aren't mapped to anything in subsequently-loaded organs. I will change Hauptwerk to do that for the next major Hauptwerk version.
Since in v6+ master combinations can be auto-detected 'for all organs', currently you could probably simply auto-detect each relevant one of your MIDI stops to 'surplus'/unused master reversibles on a 'for all organs' basis. Then in theory (assuming your MIDI hardware doesn't do anything unintended with the MIDI messages) any MIDI stop that isn't mapped to any per-organ control in any organ you load would default (back) to the default 'for all organs' state of the reversible, which would be 'off' by default. That would potentially avoid the need to map that MIDI stop to anything for any given organ if you wanted it to default to off but didn't need it use it for any virtual stops for that particular organ.
Alternatively, you could just wait for the next major Hauptwerk version, for the change (always default to off) that I implemented for you. Either way, since I've already implemented the change to make Hauptwerk do what you'd prefer, let's move on from this topic for now, please.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.