SOLVED! Exported Settings-Error

Tags: #<Tag:0x00007f977b89a9f8> #<Tag:0x00007f977b89a908>

Hello Brad & all,

there is still a bug inside of Cantabile as far as I can judge it.
Here comes a 11 steps navigating to uncover this:

  1. Open Cantabile with a new song (without saving).

  2. Create a new linked Rack by choosing “Add Object” in the Routing-Panel.

  3. With activated rack uncheck all active state behaviors but not “Exported State”.

  4. Go into the rack by double clicking on it.

  5. Add any plugin by clicking on “Add Object” inside the rack.

  6. Uncheck all State Behaviors of these plugin.

  7. Create two rack states inside the rack.

  8. Enable the Exported State Behavior “Run and Bypass Mode” of the Plugin.

  9. So far, check the behavior by bypassing the plugin and switching between the rack states. The plugin bypass should not be affected by the rack states.

  10. Now save the rack with Strg+S, save the song with Strg+Shift+S (“save all”) by giving him a name of your choice. (This should be the first time saving song in this example!) Close the song by clicking Strg+N (“new song”) and reopen it by clicking Strg+O. Open again the rack inside and unbypass the plugin for one of the two rack states.

  11. Now switch to the other rack state and you should see that the plugin is again bypassed.

I’ve been struggling with this now for more than 4 weeks, so that I still couldn’t use Cantabile for my last gigs. I tested it with two machines (WIN 10 64Bit and WIN 7 64Bit) and many other plugins, but in all cases it behaves like this.
This is a fundamental function inside of Cantabile affecting his main concept, also described here under “Exported States”:


I’ll wonder if this error wont regard other Cantabile-users, albeit nobody has been responding to my last posts belonging to this til now.

So the time has come for the one and only,
the founder of the best VST-Host over the world,
the wonderful

Mr. Brad Robinson himself.

:sparkler: :confetti_ball: :boom: :sunglasses: YEAH

Kind regards,
Peter

1 Like

Very well explained Peter, I sure it will get addressed by @brad ! :grinning:

Dave

1 Like

Hi @Borg,

OK I think I’ve fixed this for the next build.

The problem was that when switching states on the rack, the outer captured state of the song wasn’t getting captured so when the next state was loaded and merged with the song state it reverted the setting back to how it was before.

The fix I’ve made is to change the way states are loaded. Since this might affect other users I’ve written up a separate post for comment before releasing this.

Brad

2 Likes

Hi Brad,

thank you so much! :heart::heart::heart:

Peter