What are User Funstions anyway?

[pough]

Sorry, a little confusing there.

I appreciate it! Please forgive me, I'm having to both interpret your understanding and also my own fumbling around in Waveform testing things undocumented. I think I have it mostly worked out.

User functions are not what you think. They are neither user nor function*. They are buttons on the quick actions panel.

See attached image:

User Functions.png

I used the stupidest font I own.

If you associate a controller button with "User function 1" then it will activate whichever button is first on the active quick actions panel. If you change which quick actions panel is active, it will change to be the first button on that panel. If you have more than one panel visible, User function 1 will be the first button of the top panel.

At least, that's how it seems to work for me.

* Technically, you can make a macro named User function 1 and then create a new quick actions panel and have the first button trigger your macro and then things will seem to make sense, but really it's best not to think of User functions as working that way.

[Watchful]

Is that a Harry Potter font?

[Peter Widdicombe]

Sorry, a little confusing there.

I appreciate it! Please forgive me, I'm having to both interpret your understanding and also my own fumbling around in Waveform testing things undocumented. I think I have it mostly worked out.

User functions are not what you think. They are neither user nor function*. They are buttons on the quick actions panel.

Ah, thanks for that explanation. It makes sense now. If it had been UserButton x or other, it might have made sense. Sort of like the "Useful Context Menu" that all newbies need, but is by default secreted away to frustrate or turn away new users.

In my excitement for actually having user functions available (but totally undocumented), I had taken the programmers view that a UserFunction could indeed be comprised of a a list of other "system functions" to perform a hybrid/usable task; and had assumed we could actually create user functions; and the only place that seemed possible/logical was under the Shortcuts/macros section.

... so I had created a User Function 20 as a macro. Thinking it was a viable method of doing so.

So, I suppose the way of accomplishing that is to create a macro, create another "bar" with the list of the (now macros) I want, in sequence, and PROVIDING that bar happened to be in focus then that functionality works when the stars all align (that bar is the current active one). Or, it might randomly change my user interface or split clips if the wrong bar is selected.

[dysjoint]

Interesting reading, and without testing I think Peter has the right idea for creating a quick actions row with custom macros to make it work.
All I want now is an updated API (I'm no script writer whatsoever) and this is actually an incredibly useful, if somewhat hidden, feature.

[pough]

Is that a Harry Potter font?

Even more magical than Harry Potter, it's a Chank font!

[pough]

In my excitement for actually having user functions available (but totally undocumented), I had taken the programmers view that a UserFunction could indeed be comprised of a a list of other "system functions" to perform a hybrid/usable task; and had assumed we could actually create user functions; and the only place that seemed possible/logical was under the Shortcuts/macros section.

Yes, I had gotten the strong sense that you had wandered down the dark path of expecting things to make sense.

[dysjoint]

Anyways, I managed to get something to work. it looks like the user functions refer to the buttons on the quick actions panel. If you show the quick actions panel, User Function 1 will be the first button in the panel shown, User Function 2 the second button, etc.

This seems to be the correct answer. User Function 1 will select the first Quick Action (in the top layer of actions if multiple layers are active) This works whether the Quick Actions bar is visible or not. So User Functions act as a link to custom macros in a round about way.