problems with Pipe999LoadRelease

[davidgritter]

I recently had an instance where I would occasionally get a very long release from several notes of a pedal rank. I was able to trace this to the fact that this, and several other ranks did not have the necessary entry "Pipe999LoadRelease=N" entry for pipes within the ranks in question. I was able to fix this problem in GoOdf by doing a RESET/CLEAR all pipes, then reload the pipes for the rank. However, I found no way by inspecting the settings within GoOdf to determine if this line was indeed in the ODF for the individual pipe nor for the rank. There appears to be no way to change the presence of this line for a Pipe within a rank, either individually or for the whole rank, and if I do the RESET/CLEAR, I loose all the pitch tuning and Gain data for the individual pipes. I would have expected if this Line was not present for a pipe that the "Load release in attack" check box would be set for the relevant pipes (or possibly for the whole rank.) Am I missing a feature somewhere that would let me deal properly with this issue?

[larspalo]

You can find/inspect/set the LoadRelease property for each individual attack in the dialog that's shown when you select an attack and then press Ctrl+E (or right click the attack and select the "Edit attack properties" in the pop-up menu).

There's no inheritance of LoadRelease so this property must be specified on a per attack basis (the default is the inversion of the Percussive setting - which on the other hand is inherited and by default is false at [Organ] level so the LoadRelease would normally be true). The Pipe999LoadRelease applies only to the "first" or "default" attack for a pipe Pipe999, all the other Pipe999Attack999 also need Pipe999Attack999LoadRelease if a false value is desired for them.

It's possible to copy the properties from one existing attack to all other attacks in the same directory (within same stop/rank) but make sure that all properties for that attack applies to all other attacks as it's an all or nothing affair with that copying.

I'm planning for a more flexible way of setting properties for multiple stops/ranks/pipes/attacks/releases at will with complete control what exact property/properties will be set/applied to the selected target(s), but for now it's unfortunately not possible to do in a really easy way if properties in individual pipes, attacks or releases would differ.

[davidgritter]

Thank you, I had missed this item in the attack properties, since I was looking for it in the pipe properties. This works very well for me, since the gain and pitch are in the pipe properties, and I can propagate the change in LoadRelease from the attack properties without changing gains/pitch.