search

GrandOrgue / grandorgue

GrandOrgue software
Other
179 stars 43 forks source link

Merging a new ODF with existing .cmb #1671

Closed Bumblebee001 closed 1 year ago

Bumblebee001 commented 1 year ago

I am working on a new sample-set and having an issue with the cmb file. The organ was voiced and the cmb file transfered to another computer having the same set and an error comes up that the "file does not exactly match the current odf...."

If I try to import the file a window comes up that asks for either a yaml or cmb file.

What exactly should I be doing? I cannot publish this set because of this. Besides, I need to add the crescendo pedal to the voicing data and use the same for different versions of the same instrument....... same instrument, same switches (ranks), same crescendo pedal but different features especially with regards to pistons.

How do I best get about all this?

Mark

Bumblebee001 commented 1 year ago

Ideally, the relevant data is made part of the odf somehow and editing possible to adapt / correct accordingly.

larspalo commented 1 year ago

To get the .cmb file "universally" usable for other people on other computers you may not do any kind of personal customizations for the organ on the computer you generate the .cmb file from that doesn't exist for any other user. To achieve this you need to open the sample set completely clean on your .cmb generating computer (without any previously saved settings at all). Nor can you do any adjustments to the odf afterwards (without triggering the warning message) when the .cmb is generated.

For your use case you should, from a completely clean opening of the sample set, only program the crescendo without anything else done to it until you've packaged the organ for distribution - only then will it work without warnings.