Bug: "Use different rack" doesn't re-wire all bindings

I’ve been busy replacing organ racks in my songs to feature the new IK Hammond B3X. After doing this with “use different racks”, some bindings still point at the previous rack (and throw an error in verify “Unknown binding target …” with the target still being the previous organ rack.

It looks like i’ve identified part of the reason behind it: the bindings affected appear to have StateBehavior->Target enabled. Could it be that Cantabile doesn’t go through the states list to replace targets across all states when replacing a rack?

@brad: maybe you can have a look at this?



1 Like

Hi @Torsten

Thanks for reporting. Your theory seems sound. I’ll check it out.


@brad: while you‘re checking - guess it would be useful to check state-controlled route targets as well.

Also, state-dependent rack states usually create issues when replacing a rack, but I don‘t know if simply overwriting them with an initial state would be a good idea. Maybe leave the „old“ state name in place, but have it greyed out, so the user know that action is necessary for a specific ?



1 Like

This issue will be fixed in the next build. FYI: it’s not specific to “Use Different Rack” but affects any rename of an object that’s that target of a binding with Target state behaviour.

This is already working.

I’ve made a few changes here:

  • Previously replacing a rack with another rack cleared the selected rack state on in the parent song. Now it leaves it as it was.
  • If a song has a state selected for a rack, but the rack doesn’t have that state it’ll now display “(Missing: rackstatename)”.

Next build should be later this week/early next week.



Build 3630 (available now) has these fixes.

1 Like