azslow3

Press the button it to top right corner, so right from "X" button. Horizontal at the level of "Import ACT Data...". That is "+" button, drawn a bit unfortunate for noobs (I remember I also was confused... looong time ago ?)

I am almost completely agree with all that. Just with 2 notes: ACT as a whole API is usable (not *almost*), it just has several long existing bugs. Unfortunately, Plug-in Dynamic Mapping learning is a part of ACT with bugs. At the moment VST3 "On/Off" was introduced as the first "parameter", which in turn broke Dynamic Mapping for VST3 completely, Cakewalk has definitively noticed there are problems. But they have preferred just "hot fix" it, instead of looking deeper to understand from where all these bugs come. Plug-in Dynamic Mapping is also usable. It is just of Sonar X2 quality, so "usable if you avoid some particular operations" Plug-in dynamic mappings was indented to be easily definable in GUI. In practice, it is simpler to edit XML then get it work reliably. It was not much fun to edit XML for me, so I have written ACT Fix (there was also "Map editor" for BCR2000 from one of the users, for the same purpose). Note that for Mackie, editing INI file is the only option to define plug-in mappings. Interesting there are no complains about that, even so majority of surface "pro" users are using Mackie. Once the mapping for particular plug-in is created (with some luck using ACT Learn), from my experience it works fine.

For X-Mini, it is simpler to start with https://www.azslow.com/index.php/topic,377.0.html But for learning plug-ins, you should also follow the last link in the post, AZ ACT Fix. Cakewalk still has bugs in the association (ACT Learn), some plug-ins can't be learned, some parameters prevent learning, etc. Forgetting mappings (a part of AZ ACT Fix functionality), getting "default one" (by starting Cakewalk again and bringing plug-in into focus) and then re-assigning in AZ ACT Fix allows control plug-ins with problems. Making backups allows keeping working configuration. "Eventual assignment" in fact needs luck to work.

You are in a music shop... If you are here to buy particular piano, that is simple. But if you want "a guitar"... man, there are 100s of them... What the hell??? Why there is no big shield telling me which one should I buy? OMG, most of them have 6 strings. So, why so many options? Are they different? Tell me why! Seriously... There are 2 different programs (Generic Surface and ACT MIDI). Yes, they both work with controllers. And they both can work with ANY MIDI controller. How you want Cakewalk "tell you" the difference, other then explaining the functionality of each in a separate manual section? CONTROL SURFACES ARE COMPLICATED DEVICES, RELATED SOFTWARE IS ALSO COMPLICATED. Most musicians know that playing snare can be as easy as just hit it by something... but that is not really musical... and playing it good takes time and patience. Yet they see something with 20 buttons, 8 faders and 8 knobs and immediately think "ha! that I can use strait away to control what I want, since it LOOKS LIKE AN ANALOG MIXER". The complexity starts with terms... "ACT" is used for several different things. "ACT API" is programming interface used by all Cakewalk surface plug-ins (a kind of VST for surfaces). "ACT MIDI" is one particular program. "ACT Learn" is Plug-in Dynamic Mapping part of "ACT API" and so related functionality of some (not all!) surface plug-ins. Unfortunately, Cakewalk omit the second word at many places. Lets take screenshots from your post: "ACT" button - "Plug-in Dynamic Mapping" related, really "Plug-in Dynamic Mapping Learn" button, at other places called "ACT Learn" or "AL". "Exclude this bank from ACT" - also about "Plug-in Dynamic Mapping"! That is the place to enable/disabled particular bank of faders/knobs or individual buttons for plug-in control! "ACT follow context" - "ACT MIDI" (surface plug-in) follow Cakewalk context. If you click on console, tracks or VST(i) GUI - that change the context. And "ACT MIDI" change (or not change) what your device control. "Active Controller Technology" - again "Plug-in Dynamic Mapping"! Should be enabled to control plug-ins. When enabled and "ACT follow context" is disabled, "ACT MIDI" will always control plug-in (by controls not marked by "Exclude this... from ACT", and if some plug-in ever was in focus). To learn more, read https://www.azslow.com/index.php/topic,107.0.html I explain how "ACT MIDI" works (using "ACT API") in all details there. Read one (two, three...) more time. "You can edit the cell label...". That is the text which is "R1", "S1", "B1", etc. Than you want something AZ Controller or at least AZ ACT Fix: https://www.azslow.com/index.php/topic,297.0.html But exact procedure you describe does not work great in practice... Remember how long it sometimes takes to find required parameter to automate in drop-down menu, there can be 1000s of them. And in many cases they don't have meaningful names at all (or just "Macro 5", to whatever it is assigned to current preset). So modifying in the GUI is normally way simpler then selecting from menu. AZ Controller is using that approach, but allows "click on cell" to associate with particular "Plug-in Dynamic Mapping Virtual Control". In my previous post I have mentioned: "MIDI learn" associate device control with "virtual" control, "ACT Learn" associate VST(i) plug-in control with "virtual" control. F.e. "Slider bank 2, slider 3" in "ACT MIDI" is "virtual" slider (2-1)*8+3 = 11. "Slider 3" in any bank is physical slider 3 on your device (once you have MIDI learned it). Generic Surface has a bit different approach and configuration. It supports unlimited number of controls, but at most 16 virtual controls for "Plug-in Dynamic Mapping". PS. "Mackie Control" surface plug-in is also "ACT API" based plug-in. But it does NOT support "Plug-in Dynamic Mapping" (so no "ACT Learn" possible). It is using "Direct Plug-in Control" part of "ACT API" for plug-ins, the mapping is (manually) defined in a text file... There are times that has advantages. "ACT MIDI" and "Generic surface" do not support "Direct Plug-in Control" method. PSPS. AZ Controller supports both "Plug-in Dynamic Mapping" and "Direct Plug-in Control".

May be I better repeat in other words... Cakewalk has Control Surface API for that purpose. Since there can be any logical "wishes", just adding more options for "MIDI assign" can't cover them.

For many people that means "my DAW support it" . Once JUCE can officially produce CLAP plug-ins, that will be sufficient to start "global change". AAX is supported just in one DAW... Audio Unit just on one platform. Yet that was never a reason to say "these are not interesting plug-in formats".

If you read (and understand... probably requires read several times) user manual for "Cakewalk ACT MIDI" (and "Cakewalk Generic surface") plug-ins, you can get relatively far away in controlling plug-ins (except problem with persistence, I mean if after restarting Cakewalk your mappings are messed... then you need AZ ACT Fix and related explanation from my site). In short: don't mix "MIDI learn" and "ACT learn". You do "MIDI learn" by clicking in the lower part of cell and using hardware control. You do this once and forever. Then (and only then) you do "ACT learn". By pressing "ACT" button in particular (VST(i)) plug-in top-bar (or in surface module or in surface plug-in GUI). You learn by touching parameters in sequence (with mouse) and using related hardware controls (previously learned with "MIDI learn"). If you use banks, make sure required bank is selected. You do this for each VST(i) separately, hopefully once. banks are software feature. "ACT MIDI" supports 8+8+(8+1) physical controls, and no more. There are 8 buttons + shift button, so you can use up to 16 button commands in parallel. For faders and knobs there is just one current bank (for each type) with 8 controls. Bank has to be somehow selected to be active. selected banks, activating ACT, etc. can be assigned to buttons. Unlike "ACT learn", that has to be done in surface GUI, on the second tab.

Your "scenario" sounds extremely (over)complicated for me... And you start with "MIDI assignment", which means limited to the project and particular track assignment, in addition without LED feedback. All together that means the result is almost useless is practice. Your controller is designed for Ableton and SoftSynthes steering. In Cakewalk I propose you use Control Surfaces approach with it. For anything fancy you will need AZ Controller (or write your own plug-in in C++). Then it is possible to do tricky assignments (if you really going to use them...). F.e. knob 1 select band in ProChannel EQ on the current track and knob 2 controls its gain in endless imitation mode. But better keep things simple and just create music with this keyboard, using it's transport (also throw Control Surface, but that is easy with Generic Surface or ACT MIDI) and the rest to control SoftSynthes (MIDI learn inside VSTi way). ?

If some control(s) send value on there own, f.e. when you operate other controls (and that seems like the case), it is better think these controls are broken and don't use them at all. What re-enabling the device as a whole will bring you? You just know "it can randomly modify my mix now...". I don't think its worse to use such controls. So, knobs are useless. You have a set of transport buttons, tiny faders and strip buttons. Assuming you for some reason don't want change the controller and still want to use what you have, I think the only reasonable approach is DIY preset. Use the controller in "native" move with AZ Controller plug-in. You can instantiate "Startup" preset https://www.azslow.com/index.php/topic,154.0.html with 3 buttons per strip and assign controls which are still working. There is video how to do this, I think you can manage all that in a half an hour. Initially you will loose LEDs feedback, but that can be added (once you have working preset you can upload it to my forum and ask to add feedback, till you want read and understand https://www.azslow.com/index.php/topic,336.0.html...). Also AZ Controller has several modes for finite controls like your faders: jump (what you have now), catch, instant (with curves) and endless imitation. It can happened you like some of them.

MIDI Learn inside VSTi: needs implemented in hardware "pages" to control more parameters then physical controls require MIDI input with controls routed to the track and echo enables VST(i) should support MIDI control rarely support encoders, almost no changes for feedback (plug-ins don't send current MIDI values back to device) can be recorded as MIDI ACT approach (not only "ACT MIDI" Cakewalk surface plug-in, but all surface plug-ins in general): switching which parameter hardware control at given time is configured in software works independent from MIDI routing inside the project works on Automation level, also fro VST without MIDI input works with encoders, can provide feedback since current parameter value is known can be recorded and automation So, if the goal is record performance, including changes in VSTi parameters together with notes, MIDI learn in plug-in the way to go as really "direct approach".

Long time ago I have tried to workaround self-moving faders of my StudioMix. My conclusion: the only good solution is replacing the hardware.

Just in case you have not realized... "Mackie Control" plug-in block the whole device, so everything it sends, and use all messages for itself. But other Surface Plug-ins (f.e. "ACT MIDI", "Generic Surface") block only assigned messages. So you can "MIDI Learn" transport buttons there, all not learned controls (faders, other buttons, etc.) still will work "to send CC for other purpose". I mean you don't need shift+key binding "trick" just if you want transport keys to work as such. Sure, if you really want transport buttons by default also not work as transport buttons (till cycle is pressed), what you have done is the simplest approach (since to do this with Surface Plug-in you need AZ Controller with non trivial configuration, even so it opens even more possibilities...).

It will be nice in case you keep updating github... Every time, after reading some fancy Mackie request, I think "well.. may be I should produce MR...", I remember you have not updated repo with current version, so that make no sense

As I wrote, keys are subjective. I like MPK Mini's keys and they technically have reasonably controllable velocity curve. An opposite example, getting predictable velocity from NI M32 seems like technically impossible. But mentioning Akai I was writing about bigger controllers with full size (in width, they are shorter then usual... grr. that is for Roland keys, which I also like) keys. For the topic, Novation and Arturia will do what you want. If something you consider will have trouble with DAW controlling, we can solve that online in an hour (20-30 min mapping controls, 10-15 min copy/pasting buttons LED feedback, the rest for "hello" and "goodby" ?).

In such devices most important are keys, followed by purpose and corresponding usability of controlling part. Keys are up to you (you should like them, so better try before buy, I personally prefer Akai but they are special, so can be "no go" for other). For controlling part: if the purpose is controlling plug-ins throw MIDI, all will do the trick and it just depends which controls you need (pads, sliders, etc.). For controlling Cakewalk: Panorama has no reasonable integration, so probably most frustrating choice for Cakewalk. Other also have no native integration, but as other write Arturia function more or less as Mackie (note these posts are about relatively expensive MK2, not Essential). Impulse kind of support HUI, which it turn kind of supported by Mackie plug-in. But don't expect more then transport and basic strip control. Also since faders are not motorized, steering projects with more then 8 tracks can be annoying. If direct controlling MIDI synths, Arturia software, faders and pads do not have priority for you, especially if you plan to use NI (or other NKS compatible) synths, have a look at NI keyboards. There are semi-weighted S, which are really expensive, and "budget" A. Later can be used with my own deep integration, S is probably better to use in Mackie mode.

Currently there is no such feature, but it is relatively easy to implement. Keep pinging (may be in Feedback loop, since that is a future request) till Mark react ? Note that will sacrifice some button on device, Control Surfaces don't have direct access to computer keyboard input.

Late buffers means some processing does not manage to finish in time. Try to increase the buffer size (and so the time available to process it) till the problem disappear. While that also increase the amount of data to process in one buffer, some plug-ins do quite some "extra" work per buffer. Also longer available time helps with the system latency (f.e if your system is blocked for 5ms, nothing can be processed during that time, even so required processing may be takes just 1ms). High specification of computer system by itself just means theoretical possibility to run more plug-ins when optimized for audio. "Out of the box" any processor under Windows can't run at low latency at all, defaults settings are for power saving since that is what most consumers want. I mean "rule out" a problem with computer is only possible in case the computer is from Studiocat (or comparable manufacturer), after letting support check everything is fine. Otherwise even 100 top gaming PCs which can't run with 1ms latency is not an indication the problem is not computer related ? Multi-threaded processing/load balancing/oversampling/etc. Cakewalk settings obviously influence what can run smoothly. As well as the rest of the system and drivers with all there settings and other currently running programs as well.

That is definitively not currently foreseen way to get current Mackie plug-in. There was significant updates recently. Note that in current Cakewalk by Bandlab version you should see "Copyright 2022..." in the lower right corner of the plug-in interface.

I recommend to start with Mackie Control. From what I know it should be installed with CbB. There is no ready to use AZ Controller preset for that device. Making such preset requires quite some knowledge and time (even so the result may be more usable then Mackie mode with standard CbB plug-in, when done properly).

See But note that Cakewalk has not even published ProChannel API.There was time of Constrol Surface API and CAL, at that time Cakewalk has tried to be relatively open. But that was decades ago..

Also after ReaCWP (free) you can use AATransplator (payed). Sure, clear understanding what can be transferred and what is not is still required.

I don't think any controller give you the same level of features as you have with P4+REAPER. Partially because there is no comparable hardware (keboard + motor fader + display + many controls), partially because control surfaces are more limited in Cakewalk. May be it is worse to setup TouchDAW, this several $ app on a tablet emulate complete Mackie device and so you can test what and how is controllable in Cakewalk, before making decision what to buy. Another "test" can be yet another several $ app with https://www.azslow.com/index.php/topic,295.0.html

Finally someone is seriously working to stop VST... I hope that happens soon. There is no reason to allow one company have power to enforce own rules on "standard interface" between hosts and plug-ins which have nothing to do with the company.

For the list of alternative solutions, check https://www.azslow.com/index.php/board,10.0.html F.e. if you had plans to use NI(NKS) keyboard, M32/A25-61 can be integrated into Cakewalk using this way. And as key-less solutions, there are Behringer Mini / Presonus Faderport (one strip version)/ BCR2000 /Web browser based transport/Android app/etc. But note that way is using unofficial proprietary (my...) software. For pure mixing with small fixed set of FXes, better go Mackie way as proposed (by developer...) before. Since that is official and open source, you will be on safe side.

It depends what you expect from the DAW. Each has some benefits and consequences. Cakewalk has almost everything a DAW can provide. So I will just mention "weak" sides of it. I mean if nothing from the following is in your "must have"/"must be simple" list, Cakewalk will serve you well: MIDI FX in Cakewalk is DX only. While all other support VST. That means pure MIDI processors (chord generators, arpeggiators, etc.) can't be MIDI track FX. Corresponding VST plug-in will be "an instrument" in Cakewalk and that requires additional routing and has some other difficulties. control surfaces do not support Cakewalk explicitly. Some can be used with Mackie emulation, other with DIY solutions. Cakewalk has real-time engine only (some other DAWs can "cheat" with playback tracks). So computer should be audio optimized to allow recording with in DAW monitoring (f.e. with amp sim) and the set of plug-ins used on other tracks can influence effective latency. CbB is Windows only. unlike X2, CbB has no license key based authorization nor can it run under Wine. Unlike Platinum it requires periodic re-authorization. So theoretically in case of EOL there can be problems using it. But such problem exists with all DAWs (except REAPER).