azslow3

There is a DAW with flexible MIDI routing. In that DAW all strips are tracks, but they can act as an audio track/MIDI track /bus (audio and/or MIDI)/folder, even at the same time (all that are separate strips in Cakewalk, which can be used for one purpose only). Any Track can have up to 128 audio channels and up to 128 MIDI buses (mono/stereo/surround audio or one MIDI bus for MIDI track in Cakewalk). Any track can send/output to any other track (audio and MIDI) (audio can be sent to buses or patch points in Cakewalk, MIDI can't be sent directly). You can explicitly specify which audio channels and MIDI bus are used for every FX/Instrument on the track, separately for each (always complete set for the strip in Cakewalk). You can easily use VST MIDI processors (in Cakewalk you need DX formatted processor or declare VST MIDI processor as a synth, routing its MIDI outputs to a separate MIDI track, which introduce extra MIDI latency and makes explicit MIDI input specification mandatory for all MIDI tracks). You have "Input FXes", so you can process audio/MIDI before it is recorded (can't be done with MIDI in Cakewalk, for audio only possible throw patch-points/aux tracks). MIDI and audio can modulate parameters (f.e. you can control value of a synth/fx parameters by current level from your mic), parameters can modulate other parameters (both not possible in Cakewalk). SysEx and (N)RPNs (the later are in fact a series of specific CCs) and sent to VST(i). Event List view exists. MIDI event handling is directly as VSTi get it (in Cakewalk it is DX oriented). As already mentioned, you can run both DAWs in parallel, with ReWire and/or Audio Link. Or just open Cakewalk project (not everything will work one-to-one, some adjustments may be required). --- Please note I don't say that other DAW is "better in everything and for everyone". Cakewalk is toward "created by musicians for musicians". The other DAW is more "created by programmers for programmers"... 😏 But if your work with GUI-less VSTi(s), need Ctrlr or similar mappings/control, want use in-DAW modulations/parameter linking or scripted MIDI/audio processing, you need something designed with all that features.

In that part of preferences, you don't choose which interface you want to use now. You just set the latency for each interface separately. It is ok that after "Apply" you see the first (for whatever reason) interface Cakewalk see in the system. If after setting correct value for Steinberg and pressing "Apply" (so you again see Tascam) you still have wrong value for Steinberg (check with loop-back), then it is time to wipe audio settings / look for different solution. But in supposed to work (just with weird behavior of configuration dialog).

Writing from memory... "Record Latency Adjustment" is per interface, so can be set for Realtek AND for other. The setting for currently used driver will be used, but configuration dialog list all (starting from the first, not selecting currently used). There was a thread about that in this forum, but I can't find it fast. Do NOT install ASIO4All if you ever use other ASIO drivers. Under some (unknown) conditions, it can do "something" (still not understood what ) and disturb other ASIO drivers. Uninstalling ASIO4ALL will not help, you will have to reinstall Windows or wait till major Windows update to fix that. If correct latency adjustment is applied can be easily checked with loop-back recording (2 inputs with the same signal, one directly and one throw the DAW and loop-back cable, exact required "shift" in samples will be visible then).

Ableton Live has specific workflow and related surfaces like SmartPad are that workflow oriented. You can control Cakewalk/Sonar with any controller, but it has different workflow and so "controllable" functions are also different. There are many "not Ableton Live" oriented controllers. And they are still more or less "Mackie like". Like mixers and consoles. Some people still record what they play on normal music instruments, without wish for "if I jump twisting my hands over head, my controller produce super-expressive music...". Drumming with drums, play guitar, etc. Sure at some point you want "record in a loop" (and that is supported by Cakewalk/Sonar and can be triggered from controllers), but that is not the same as recording "loops". And many (most) DAWs are still related workflow oriented. ACT is a C++ API. It is bi-directional. If you don't want program in C++, you can use AZ Controller. "ACT MIDI" and "General Surface" are simpler (bi-directional response in general requires controller specific logic, it can't be generic). If you don't want AZ Controller and your controller doesn't provide Cakewalk support - that was your choice to buy such device. It is controller producers who are responding for supporting or not supporting particular DAW, ask them.

I don't think OP is a human which want use some control surfaces with Sonar... For me it looks like AI generated text for subject "Cakewalk can't work with Ableton controllers, Sonar is not Live" 😏 I mean apart from mentioned "subject", almost all statements are wrong or have questionable meaning. Well, sometimes people also write something like that...

Don't hunt "excellently priced" old low-middle interfaces, till you need something special (like having 6+ analog inputs crazy cheap). That will not increase stability nor decrease latency... I am writing from experience (I have several still laying around, 2 in use... but I also have one "real" audio interface 😏).

Written million times, but in short: you may have 2 DIFFERENT general problems (one, another or both...): audio interface need "the next buffer" at the time it starts convert its samples into analog signal. The time is fixed. Absolute "deadline". No matter what is in the buffer, it should be there. Failing so produce cracks/pops and (bad) driver crash, up to interface (hardware) stuck. Any 10MHz DSP beats most "speedy" and powerful PC in that respect. The "power" does not really matter (except my 2x faster driving example... so can have "improving" effect). Reasons of failure there: system (hardware and related software) own "latency", they can simply "lock" the resources and so not allow delivering "in time"; badly written drivers, which fail to deliver even when the system allows. the buffer doesn't get the information you want. I mean it can't be filled with results from all your synths and effects when it has to be sent to the interface. Here the DAW, plug-ins, RAM, disk, so general "power" is required. Since "too long" processing in any plug-in will reduce the "speed". The reasons from (1) also influence (2), the processing can be "too long" just because CPU/memory/disk required for it was just locked by something else. But everything else is also relevant. Note that "CPU load" is not an indication you have/don't have these problems. Except when everything is at 100%, you know your system is definitively "underpowered". With good optimized system (and well written plug-ins... rarely the case...) you may have no problems at 90% or more, but on bad system you may experience problems with 10% (or even less). Cakewalk and all mentioned utilities don't really show you what the problem is. Latency Monitors are great to understand from where SOME problems MAY come, only sometimes they demonstrate from where the problem definitively come. So the only way to be sure is with your concrete project observe what is going on with real-time buffers (1) and what is going on with processing (2). And there is a way to see that, as I have pointed in my first post...

Xeons are server processors, they are designed to work at 100% continuously (assuming cooling system match it, and in ready-to-use towers it usually is). But if Throttlestop significantly improve something, check your Powerplan is correct (also listed). I personally prefer avoid Throttlestop and other "hardcore" tweaks, but it is one of good tools to see what is going on (even so it is not easy to interpret). Till you target latency toward 1-2 ms... not possible with your interface in any case... standard bios settings and Ultimate Powerplan should allow use your system reasonably. So, I repeat, check which bottleneck you hit and them target the reason. You know, an attempt to drive 2x faster can bring you to the destination 2x faster. But that is not the first thing to consider in case you have chosen 10x longer road 😏

If you really want optimize audio performance, and not "I will click here-and-there may be it helps...", you need to understand what is the bottleneck (for concrete system, with concrete project). For "clicking everywhere" approach, I have old but for most staff still valid "checklist": https://www.azslow.com/index.php/topic,395.0.html To understand what is the problem, search "Performance monitor" in my checklist. Once you know what you want/need improve/fix, you significantly increase your chances be successful.

I don't think you need video console... The only connectors are for Fairlight Audio Interface and 1x in each direction MADI (4x in each direction with extender). But I guess no PC will help you to get a single from 2000 Core Audio Tracks, you need a Mac... 😉

They always was. They exist like 20+ years, almost unchanged. But as you can guess, I had to have a good reason to write AZ Controller (MPK Mini was my first surface) instead of using or extending "standard" solutions 😉

There are also "standard" solutions, with "Cakewalk ACT MIDI" and "Generic surface"

I don't have TD-50, but even my simpler module works well over USB. Don't forget to use Roland drivers (even so it may work without). The latency of Roland Audio Interfaces is not the best in the world, but ok to play throw Drum VSTs in the DAW (even so you probably will notice the response is slower). MIDI also works fine in terms of latency, when connected throw quality MIDI input (I mean connecting throw "MIDI to USB cable" for $1 make no sense).

Search for GeneralMidiSMFs in: https://legacy.cakewalk.com/Documentation?product=SONAR&language=3&help=INI_Files.5.html

The proposal was to loop MIDI externally and hope SysEx will be delivered (Aux track recording was just to record audio, inside Cakewalk). I have quickly checked, but it seems like that does not work... Several applications can use ASIO, but only some drivers allow that (f.e. RME). Single application can't use multiple ASIO, that is an ASIO creator (and owner) decision. You can wait for Cakewalk implementation, try to use ReWire or other multi-app tricks... or just switch to another DAW with reasonable MIDI routing, find (or create) Ctrlr (or similar) panels for controlling and proceed with music creation. Cakewalk MIDI editing is nice, but (may be apart from Step Sequencer...) I don't think there is something significantly harder to achieve in other DAWs. MIDI routing and processing are definitively not in the list of Cakewalk advantages (only "workaround" style VST MIDI processing and simply no MIDI routing at all). With the DAW I propose you can: open your Cakewalk project and continue or ReWire / ASIO link Cakewalk to use both in parallel. Sorry, I don't have other proposals...

AZ Controller is not communicating with Mackie. You have asked it to control the same parameter and Cakewalk sent feedback to Mackie/iCon. That is not happening directly. So, Arturia -> MIDI -> AZ Controller -> API -> Cakewalk -> API -> Mackie -> MIDI -> iCon. You have controlled fader by controlling the volume (to control the volume of the second track, you need to select the second track in the Strip action for the second encoder).

I just can confirm when msmcleod has already written. Communication between different surfaces is not foreseen by Cakewalk, nor support for multiple MIDI inputs to the same surface. Mackie Control and AZController can do the internally, by only for other instances of themselves. But you can use AZController independently with the second surface, with Action list like "Strip <current>"+"FX (by position or name) (parameter by position)"+"Value (encoder)" for each encoder. In AZ Controller there is no separate INI for mapping (so no separate "C4 mapper" like utility), you assign parameters explicitly within preset (but with this approach AZController technically does the same as Mackie Control with INI). If you want follow track/bus focusing, display currently controlled parameter and value somewhere, implement several "banks" of parameters etc., the preset for AZController will be a bit more complicated (but possible to make).

I was doing exactly that in my test, but for some reason MSSupertLooper was not getting sound. Well, as I wrote, probably I was doing something wrong (or just hit some bug after changing settings without stopping transport... I remember that was "no go" for CW all the time I was using it... ? )

I have tried that, these are inputs. And Cakewalk with some plug-ins support sidechain inputs, so they are shown. I have not managed to get the signal there, but may be I was doing something wrong...

(N)RPNs are implemented using CC numbers you have trouble with. You drive MIDI "throw" plug-ins, when plug-in is capable to use (N)RPN, it will most probably block CCs you mention. But that can be plug-in setting.

6,38,98,99,100,102 (also 96, 97) are used for (N)RPN messaged (https://en.wikipedia.org/wiki/NRPN) If something (plug-in) works with (N)RPN, it will not work with individual CCs which are used to implement them. Cakewalk always was not flexible with MIDI routing. But let be realistic, how are you going to use 3 banks of the same finite controls directly to MIDI, so without catch, even if you remember what all these controls are? ? Well, you can assign CCs from different channels. As long as target interpret them channel dependent way, with that you can avoid assigning "reserved" CCs.

All depends what you want to do, preferences, and the type of the track. In general, you can turn off echo for current track with: Strip <Track> <Current> <Inp. Echo> Value <0> (or <toggle>) For MIDI tracks you normally use "automatic echo" on strip selection ("A" on echo button). With Preferences option MIDI/Playback and Recording/Always echo current MIDI track you just need to select the track to echo it, deselected track echo will be auto-disabled. So you don't need to manipulate Echo/Mute for previously selected track (and really you can't when the option is set). For recording, just check you have "Allow MIDI Recording without an Armed Track" enabled (in the same preferences section). So mentioned Actions make sense for audio tracks (f.e. a button to toggle echo for mic or guitar) and in exotic situation for MIDI tracks, when auto-echo can't be used. PS. unlike ACT MIDI and keyboard assignments with CAL scripts, AZ Controller support feedback (f.e. turning LEDs on controller). So if you plan to use AZ Controller, MIDI controllers with LEDs have advantages. Also note if you don't want/need MIDI controller, AZ Controller also support gamepads and phones/tablets (with OSC apps). The last option can be used for feedback only, f.e. to show the name of current track on the phone (useful if you play away from monitor). It can even speak the track name when you change the selection, useful when you are away from monitor and don't want other display ? PS.PS. "MIDI-Shift" with MIDI assignments is used to inform Cakewalk you use a key for control, f.e. with left pedal as shift you can send 88 commands from 88 keys keyboard. But there was more then one reason for me to write AZ Controller instead of using existing possibilities. BTW you can mimic the behavior in AZ Controller (with unlimited number of Shift/Ctrl/etc. modifiers).

Or with AZ Controller (www.azslow.com). After installation (there are videos) and following "Quick start" (https://www.azslow.com/index.php/topic,9.0.html), you will know how to map a button and what is the Action list for control. The action list for your purpose can be: Strip (Track, <First>, +0 or +<other track, counted from zero>) Function "Select strip" For more buttons, practical is "Dup" button on the Options tab. So you just need to re-learn MIDI and adjust "+X" to define more buttons. You can also do track name based selection. For that you will need to define "Software States Set" in the Options tab, like "Tracks" with States "Drum", "GTX", etc. And then adjust "Strip" Action for the button, changing "<First>" to "Tracks" and then selecting f.e. "GTX". That way your button will select "GTX" independent from the position it has.

It assumes synth MIDI learning is working, and in OP the problem it does NOT work. In addition it introduce yet another mapping (note "I don't use ACT control because it is a bit complicated" in the OP) and it assumes the DAW has good and stable working MIDI routing (Cakewalk tend to mess it). BC Remote Control has mentioned by you disadvantage... Finally, this plug-in cost almost the same as a DAW which can do way more tricks with controlling on its own and in more easy to follow way (since it can use MIDI and directly parameters, including modulating (also by audio)). With third party extensions or scripts it is possible to do even more crazy things there. ? Sorry, I don't say BC plugin is bad or will not work with Cakewalk, I just claim it is not going to help with discussed topic.

https://www.azslow.com/index.php/topic,206.0.html Some controllers show assigned parameters. NI Sxx controllers have displays for that (M32 has tiny display... it also shows current parameter and value, but it is hard to see). Mackie (and compatible) devices have per control displays. And for all controllers you may have a separate window which shows the layout (at least with "Cakewalk ACT" and AZ Controller). So if you have space on monitor (or a dedicated monitor.... or in case of AZ Controller a phone/tablet with TouchOSC or other OSC client installed...), you can have current "labels" for hardware controls.