Hello Neil,
Briefly (since we no longer officially support Hauptwerk v4, although the same would apply in v6):
When deciding which pipe sample note number to reference for each given virtual pipe note number, the CODM compiler bases its decision upon the presence or absence of the primary attack/sustain sample. If the attack/sustain sample is present then it assumes any additional specified short-release samples will be too.
I've had a look at the Salisbury rank that you mentioned, and I can confirm that that particular note has its '03 release' sample missing. (I don't know off-hand why that was, but I imagine that perhaps Brett discarded that particular sample because it had some noise in it.) I wasn't aware that there were any sample sets that had short-release samples missing just for certain notes. I'll log as an enhancement request that it would be useful if the CODM compiler also specifically checked for any such cases and remapped those missing short-releases to the next-shortest release sample available (and/or maybe even skipped the samples for that note number entirely).
Currently you could either:
- Avoid specifying the '03' release samples for that rank as a whole, i.e. just reference the primary attack/sustain samples and the '02' release samples for the rank (assuming that the same situation doesn't arise with any of the 02 samples), or:
- You could probably make a copy of either the next-highest '03' release sample file, or the next-lowest (i.e. 073-C#.hbw or 075-D#.hbw) and rename it to 0754D.hbw. Assuming the sample has the pitch stored within the file, I think it should then get re-pitched appropriately when Hauptwerk plays it (but do check for good measure).