Recent Posts

Pages: [1] 2 3 ... 10
Presets / Re: [azslow3, almeister_65] Behringer X-Touch Mini
« Last post by Rollings on Today at 12:22:39 AM »
Hello again,

I while ago I wrote about a suggestion of settings for the Xtouch Mini. If I had these settings on the controller it would be exactly what I need for my work combined with my touch screen etc. So now we are all happy that Gibson handed Cakewalk over to Bandlabs having this preset also would be fantastic.

I mentioned
1. a preset that would have mute solo on the two rows and volume for the rotaries eg. Layer A Light On
2  a separate one like Layer A Light Off  to be the same the rotaries would be Pan instead of Volume and keep mute solo in the two rows.

So I also thought we could put another two as below.

3. Then We could have a 3rd one for Channel Strip Like Layer B Light On with a few more options in the rotaries to control more sends.
4. and then if possible to have a 4th one like Layer B light off to be other commands like undo/redo, loop on/off, ripple edit toggle and things like that.

If this is possible or part of it is possible can the Xtouch Mini preset be changed to this?

I am attaching two images with more details on the commands. One image for Layer A Light On and Layer A light Off and a second image for Layer B Light on and Light Off

Open to chat! :)

News / AZ Controller 0.5r7
« Last post by azslow3 on April 20, 2018, 03:31:16 PM »
Please visit the documentation section in case you have never installed this plug-in before.

Download it now

There should be no Ads, spies or other nasty parts in this download. The installer does not try to connect to the Internet. If you see such a warning from your OS, stop the installation/use immediately. The DLL can theoretically write a log file into its own folder, but that should not happened with releases. If you turn on OSC in the AZ Controller preferences or load a preset with OSC turned on, AZ Controller is acting as a network server. You can get related warning from your firewall software. Even in this mode AZ Controller does not try to communicate with the Internet, while it will start respond to OSC Clients messages

This is the only place where you can get the original AZ Controller for sure. The license allows coping/distributing it unchanged, but I am not responsible for distributors misbehavior.

Changelog (since 0.5r6)
  • NEW: flag to avoid bundles when sending OSC
  • NEW: timed SysEx sending
  • NEW: echo from/to surface suppression
  • FIX: PC modules name in the Text action could be not correct
  • NEW: Set state by text
Discussions / MOVED: [AZ, dede] M Audio CODE 61 preset
« Last post by azslow3 on April 20, 2018, 08:15:57 AM »
Presets / Re: M Audio CODE 61 preset
« Last post by azslow3 on April 20, 2018, 08:14:36 AM »
I have re-attached preset to the first post and modified the text a bit (transport buttons must be in Mackie mode, Bank switching works when bank buttons are in Mackie mode as well, which tracks and bus are controlled is specified by WAI).
Presets / Re: [AZ] Mackie MCU (Pro) / LC protocol
« Last post by azslow3 on April 19, 2018, 05:43:50 PM »
Sorry, MCU preset is a mess  ;)
It was build as a prove AZ Controller can do everything MackieControl does, in addition attempting to mimic TouchDAW Phone compatibility (which has failed...).
The preset is almost untested and based on "outdated" AZ Technology. I do not want (and I do not recommend) to use it as a basis for anything.

In general AZ Controller 1 development is stopped. I plan to continue with AZ Controller 2, for Reaper or Reaper/CbB is not yet clear. In case BandLab will advance with CbB development, I can consider it as a target. But in its current state, CbB is technologically outdated (not only for Control Surfaces, but almost in all other parts). It becomes clear for me once I have tested Reaper.
Presets / Re: [AZ] Mackie MCU (Pro) / LC protocol
« Last post by Linzmeister on April 19, 2018, 03:28:35 PM »
Hi Alexy,

I now have my studio rack back at home and will pick up with the Yamaha 01V implementation again soon.  I recently bought an MCU. 

After playing with the default MCU template, I found that the VPots don't seem to control switch parameters well - the internal value didn't always get to 1.0 (or above half way in some cases) to turn a switch on, so I set about trying to modify the preset.

I have added VPot Switches "VS1-8" (MIDI Notes 32 - 39) but only added logic for Switches 3-5, for tr. Interleave, Phase and Input echo

I created Hardware controls called:
                 All above with Parameter Name and Value monitors

I also swapped the Interleave and Phase display and physical control order, as they were the reverse of Sonar screen.

I am sure that I have not been as tidy as you, but I was trying.. :D

My next goal would be to allow all the VSw to become ACT Buttons also...
In testing, I see that I have broken something in Sends SE. Mode.  Pushing any of VSw 3-5, sends the fader to -Inf or +6.0dB on consecutive presses - probably copied in some settings that I should have copied

In trying to read the preset, I struggle with some of your abbreviations
as in these examples:
Even understanding the Camel case and catching some of the words, I fail to understand their meaning in context.

I think I have to go and reconfigure my ACT learnings for the MCU.  I have downloaded the latest controller version and setup Multiple Instances (AZ 01V, and AX MCU) to try and avoid stuffing anything up.. the 01V still appears to be working as per our last efforts, but the MCU PC EQ seems to use the first 4 VPots and Faders and then duplicates them onto the last 4 VPots and faders even have read this thread about the multiple contexts.

Presets / [AZ, dede] M Audio CODE 61 preset
« Last post by dede on April 19, 2018, 10:10:07 AM »
Hi everybody, attached is the Code 61 preset Alexei generously developed for my new M AUDIO Code 61 controller, an awesome job making the best use of the AZ Controller plugin for Sonar. I'm impressed and full of gratitude.

it works like this:

Play = Play
Rec = Rec
Stop = Stop
FFW = Move to next measure
RWD = Move to previous measure

Transport mode, Button mode, Fader mode and Encoder mode must be set to Mackie mode.

F1= Master bus (a bus with name "Master") volume
F2= Track WAI 1 volume
F3= Track WAI 2 volume
F4= Track WAI 3 volume
F9= Track WAI 8 volume

Bank buttons move focus to next group of (eight) tracks (when in Mackie mode)

Shift+B1= changes buttons mode: Track-Rec-Solo-Mute
When set to "Track" button pressed brings focus to that track
when set to Rec button press arms/disarms that track for recording
When set to Solo or Mute, you guess...

B2= Track-Rec-Solo-Mute TRACK1
B3= Track-Rec-Solo-Mute TRACK2
B4= Track-Rec-Solo-Mute TRACK3


E1= Pan pot (current focused track)
E2= First Send Level (current focused track)
E3= Second Send Level (current focused track)
E4= Third Send Level (current focused track)
E5= Last tweaked parameter (current focused Plugin or PC module)
E6= Jog-Wheel (navigate time line)
E7= Navigate Tracks
E8= WAI Bus output volume

Please note that E5 works with last "tweaked" parameter/control on plugin UI, not last "touched" so you have to click on that button and actually move it in order to Code61 focus on that parameter.

Again, thanks Alexei for your generosity, incredible work on this AZ controller really.

Tutorials / Re: Cakewalk ACT MIDI Controller Explained. Only $40, for short time!
« Last post by azslow3 on April 19, 2018, 07:10:10 AM »
Hi Alexy,

in reply #4, there is a broken link

What plug-in can do
You can find my interpretation in the post or (in case you understand IDL) in the source code provided by Cakewalk (they have publish the latest version on github recently).


I think it should be:

In reply #5 there is another broken link at the end..

Feel free to delete my comment after it is fixed.
I have already explained... In short:
Sonar "Previous Marker" command is smart and does what people intuitively except from it.
AZ Controller Marker action is technical, it assumes you have 3(!) hardware buttons, "Previous", "Current" and "Next".
Pages: [1] 2 3 ... 10