Hello VulcanStarlight,
VulcanStarlight wrote:ey everyone, thanks for the help!! I just tried that method and it works wonderfully. The bells engage and start ringing.
Thanks. Excellent.
VulcanStarlight wrote:Now, how would I do this for a publishable custom organ definition? To include no samples from Jiri Zurek would be most ideal and of best legality. I’d love to be able to share my set and not be stepping on toes. Is there a way to do this without including the wav files? :wink: The Zimbelstern completes the set I think, it would be amiss not to include it.
That's a bit tricky, given that Jiri's naming for those files wasn't compatible with the CODM. There would essentially be two options:
a) Change your CODM ODF back to refer to Jiri's original installation package and folder structure. Just for development/testing purposes (so that you can get the CODM ODF to compile during development), temporarily copy your renamed files back into the same folder that has Jiri's original Zimbelstern files. Once the CODM ODF has compiled, edit the resulting 'full-format' ODF in a text editor to change those particular sample filenames back to Jiri's original names. Then check that the 'full-format' ODF still loads properly, and distribute that (instead of the CODM ODF directly). (Editing 'full-format' ODFs isn't officially supported, but it would be a simple edit in this case, e.g. by searching the text for the relevant folder name.) You might find it easier if you turn off ODF XML auto-compacting on the General Preferences screen.
b) The other option would be to contact Jiri to ask whether you could have his permission to distribute your installation package including the renamed copies of his Zimbelstern samples. There would then be no need to distribute a full-format ODF, and you could distribute your CODM ODF directly.
In either case, see the '
Section 3: Installation package definition file tables' within '
Design tools | Custom Organ Design Module, installation package, ... format documentation' for the format required for component installer package files (in order to package full-format ODFs and/or installation packages). If distributing publicly, you would also need to use an OrganID and/or InstallationPackageID that are globally unique. Contact Francois at
support [at] hauptwerk.com to be allocated some IDs if you haven't already done so.