Updating the Guides: What Needs Work?

Cantabile
21

It is, but I need to manually run a script on the server to generate it - which I only do from time to time. I’ll try to figure out how to run it automatically so that it’s always up to date.

22

Thanks for that detail.

1 Like
23

There are certain things in bindings that are mysterious to new users (even some of us older ones… :slight_smile: )

For example:
Load state by Index vs Program
ReInvoke Load Bindings
Engine:User Trigger

Those are some that come to mind. Not sure if there are any others that are not necessarily self-evident.

24

Thanks @mavriq,

I’ll look to adding these to the guides, but I’m reluctant to get into documenting every single binding point.

In the meantime:

Load By Index vs Program

Index means load the song/state at position X
Program means load the song/state with assigned program number X

Reinvke Load Bindings

Cause all the OnLoad bindings to re-trigger. eg: if your rack does things on load state and you want to do them again for some reason you can use the Reinvoke Load Bindings binding point to retrigger all those bindings.

User Triggers

This is a carry over from Cantabile 2 where you could invoke a “user trigger” with a specific number. They’re still present and work in Cantabile 4. If you look in the source and target sides of the Engine bindable object, you’ll see ability to fire a user trigger (on the target side) and ability to respond to a user trigger (on the source side).

These days, not sure how useful or required this is, but lets you have one binding fire a user trigger and then a whole bunch of triggers in all your song and rack all respond to that trigger.

1 Like
25

Thanks that is useful. However, would it be better to just change the name from “Reinvoke Load Bindings” to “ReTrigger OnLoad Bindings”? Pretty clear what the second one does. Don’t know if you need to even say “ReTrigger”. Perhaps just “Trigger” is fine.