Recent Posts

Pages: [1] 2 3 ... 10
Discussions / Delay jumping of motorized faders
« Last post by cupax on Today at 10:16:55 AM »

I mapped the jog wheel to quickly switch up-down between tracks. Each track I select the motorized fader quickly jums to it's volume value.
Now, switching between track 10 and 1, the fader will jump 9 times which is annoying.

How would I insert a short delay before the fader catches up vith the volume value? Let's say half a second, before it jumps to the volume of the selected track.
Discussions / Re: How to activate (focus) the Next/Previous Track
« Last post by azslow3 on Yesterday at 11:53:04 PM »
Switching between bus and tracks works without bug only in case you "switch" to current strip type first. So, if focus is in tracks, "Switch to tracks" + "Switch to buses" does the trick (and reversed).
For that you need to know currently focused strip type, proper way is monitor "Recall"ed focused strip, remembering changes in Parameter Name monitor.

All that is a bit tricky to explain "step by step". In "X-Touch Mini" preset that is done in "_Strip" control (and corresponding monitor). The button operations are in "_fEBStripSet(_Ch)", the control serve  8 different buttons, relevant part is with  Ch:7 condition.

Note the "Strip" is not System set, you need to define it yourself in the Options tab (as in mentioned preset, the first state is "Track" the second is "Bus").
Discussions / Re: How to activate (focus) the Next/Previous Track
« Last post by cupax on Yesterday at 09:35:41 PM »
'Move Input Focus...' is to change between buses and tracks (buggy on Cakewalk side, let me know if you need that so I can describe workaround).

Yes please, I need this workaround. Thanks!
Discussions / Re: Startup Actions
« Last post by azslow3 on November 23, 2020, 07:36:33 PM »
In AZ Controller nothing is "simple" :)

There is no dedicated "on startup" controls (apart from WAI Action can be asked to apply on startup). But that can be organized:
1) add some Software State Set in the Options Tab. Let say "Init". By default it will have one state, "Default", and that is fine for the perpose.
2) somewhere add "Init" Monitor (the same way you did for Loop). That monitor will be triggered on startup (precisely on preset load, which happens on Cakewalk startup).

* parameter and state monitors are triggered at startup (triggered by "unknown" -> "something" change), so extra Initial feedback is only required in case you want put your controller into some mode, send Hello, send "reset everything". I mean there is no need to duplicate in Initial messages you send from individual controls
* there is "Monitor reset" <All> action, which can be used to (a kind of) imitate startup. Sometimes useful when controller was switched to some other mode, to "resync".
Discussions / Re: Step By Step Tutorial for LED button
« Last post by azslow3 on November 23, 2020, 07:22:27 PM »
And that is correct for "Loop". Loop is so called "system state set", AZ Controller change it in sync with Cakewalk "loop". So this monitor can be anywhere in the Logic tab and the result will be the same.

"Mute" is different, there is no general Mute. Every strip has Mute button (and there are "Automatable mute" for strips and "Rude mute"...). So, there must be some way to tell which mute you want to control. In AZ Controller "Mute" is parameter you can make "current", using Strip Action. There you select the strip and the type of mute. Once "current", parameter can be used by Value and Monitor <parameter value> Actions. So in such case Monitor should be in the same Logic list, after Mute is selected.

For MIDI actions your solution is good general solution. It explicitly mention which MIDI message to send in which case. What I have mentioned is solution for Mute and Mackie: LED use the same MIDI message as the button send (some not Mackie controllers use different messages for buttons and corresponding LEDs), for such case there is <Use Ctrl MIDI> parameter for MIDI Action, instead of specifying it explicitly. And in Parameter Monitor (so, works for Mute but not for Loop) there is "value", so setting Value parameter of MIDI Action to "value" applies it.
Discussions / Startup Actions
« Last post by cupax on November 22, 2020, 11:19:07 PM »
Maybe a simple question, I just can't find the answer:
How do you set the actions on Cakewalk startup without touching anything on the controller?

I would like to reset my controller to the default state when I run Cakewalk or load new song.
Discussions / Re: Step By Step Tutorial for LED button
« Last post by Trebot on November 22, 2020, 09:23:01 PM »
I'm new to this but here's how I did it for my controller's loop button. I went to the logic tab and edited "loop on/off". I changed no existing actions. I added a new action "monitor". I set that to "monitor state" and set the state to "loop". Then under the feedback tab I found "loop on/off: state monitor". I added a new action. In the first drop down box I set 'loop(on)". In the second drop down box I chose "MIDI". In the third I chose "Note" then set my midi channel, the note number my button sends, a value of 127, and "0 sends on". I copied and pasted that action and changed 2 settings on this copied action: "loop(off)" and set value to 0. This may not be the best or easiest way but it worked.
Discussions / Re: Step By Step Tutorial for LED button
« Last post by azslow3 on November 21, 2020, 09:01:55 PM »
If you have implemented Mute control following "Quick start" tutorial, I think it should be clear how to add 2 mentioned Actions (one in Logic following by one in Feedback). I have mentioned options for these actions you need to change (leaving other options as defaults). I don't think I can be more detailed...

How monitoring is working in AZ Controller is explained in all details in already mentioned tutorial. Yes, that is lengthy thread with relatively complicated technic. But DAWs + controllers can't be explained in several words, especially feedback from the DAW. Usually that is programmed in C++ (python, JS, DAW dependent...) by (semi)professional programmers. AZ Controller can be used without such skills, but understanding what is going on is still required.
Hello Alexey

Thank you for adding the "FX Bin Enabled" functionality.  I checked it out on the latest version of Cakewalk and it works perfectly.

Right now I am assembling the prototypes of my digitally controlled analogue mixer which I will use with Cakewalk and AZ Controller.  I'll send you a couple of photos once the boards are tested.

Again thank you for your continued support!



b406 should be able to bypass FX Bin (strip parameter "FX Bin enabled", since API define logically revered to "bypass" value, so "1" means enabled and "0" disabled").
Discussions / Re: Step By Step Tutorial for LED button
« Last post by cupax on November 20, 2020, 08:34:10 PM »

Thank you for your reply, but it didn't help me, it wasn't clear enough.
I believe the logic should be:
- monitor the value of mute (engaged or disengaged)
- if mute = engaged, then LED=on
- if mute = disengaged, then LED=off

How do you define the status for LED ON and LED OFF based on monitor reading of mute status?
Pages: [1] 2 3 ... 10