azslow3

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.

Softube Console 1 is to control corresponding mixer strip. For "instruments", there are just 2 DAW independent solutions. For both you run the instrument in a wrapper. One is AKAI VIP and another is NI Kontrol. Both work with combined devices (keyboard + controller). AKAI VIP always was just "an attempt". NI Kontrol is well supported. Long time ago there was Novation Automap (with controllers without keyboard), but that line is not continued. All NI controllers use encoders, for me suboptimal for synthes (no "real" feel). But obvious advantage they are always "in sync" with parameters, so you can switch between banks/synthes without problem. If you don't really want the keyboard, there is M32. Even so it has 32 small keys, it has small size and can be used just as controller. They are almost optimal to control all NI plug-ins. Many third party plug-ins also have NKS support. But if you are serious about using Cakewalk and controller, I recommend as first to give your Launch Control a try with AZ Controller. After following "Quick start" (5-10 minutes), you will be able to use "a hint" from my previous post and have your device controlling one particular synth (may be 20-30 minutes for you). You can also try "Startup preset" (there is Youtube step-by-step video), to try "ACT Dynamic mapping" (another 15-20 minutes). After that, you will probably have the answers on following questions: are you really going to use controllers? do you think encoders will work better then finite knobs for you? do you want spend time making good for you layouts/presets or prefer "ready to go" solutions? And then you can start to think which other device to buy (or not...).

"MIDI learn" inside VST(i) is the thing of that VST(i). If you save the project, but the next time you load it the mapping is gone, that means the plug-in is not saving it. So you need to ask plug-in developers what is wrong, host (Cakewalk) has no influence on internal plug-in MIDI mappings. ACT in general is the only option if internal mapping is not saved by plug-in. ACT is using "Parameters" exposed by plug-in, not sending any MIDI to the plug-in. ACT "Dynamic mapping" can be tricky in terms of "remembering" the mapping (configuration XML files can be "corrupted") and focusing plug-in (you don't need it on monitor, but you need select it and "lock" it, then you can close it, focus other plug-in, etc.). An alternative approach is "Direct parameter control". But in your case it is available throw AZ Controller only (Cakewalk own ACT software use it exclusively for Mackie controllers). I must admit that peace of (my) software is not newcomers friendly (even so in practice, when you know what you should do, the mapping will take less then 10 seconds per control... The action list per control is "Rack <required synth> <parameter>" + Value (with default options for launch control), duplicate N times, MIDI learn and change the <parameter> in Rack action for each knob). The advantage over Dynamic Mapping (and MIDI learn inside plug-in) - you can control different parameters of different synthes/fxes at the same time.

Writing a VST3 from scratch is not an easy task... It is simpler to use frameworks, most common is JUCE: https://juce.com/ Also note that as long as you are (A)GPL compatible (your plug-in is open source or you don't distribute it to anyone), you don't have to pay and you don't need Steinberg registration. But in case you want make it close source, even if you don't ask money for it, you need Steinberg registration: https://steinbergmedia.github.io/vst3_dev_portal/pages/VST+3+Licensing/What+are+the+licensing+options.html and some license for the framework (JUCE is not cheap...). But may be you can do the trick with ReaJS (https://www.reaper.fm/reaplugs/ ). Then you can write processing (and GUI) using JSFX (https://www.reaper.fm/sdk/js/js.php, NOT JavaScript). Tons of scripts are already written. ----- But may be you are looking for Control Surface API, that is completely different from VST (and the only way really communicate with Cakewalk). Then you need https://github.com/Cakewalk ----- The only known Cakewalk API for VST3 is proprietary extension for ProChannel modules. It is not documented. There is no full scale DAW API which can be used from VST(3) plug-ins in Cakewalk (it is not REAPER...).

For this controller specialized solutions should work better then Mackie. Original or alternative.

On original Mackie MCU, there is "Control group" section (at least in Cakewalk layout), which switch between Tracks, Buses (AUX) and Mains. To switch from other devices, they have to send corresponding MIDI message (Note 76, 80 or 81). I don't know if Faderport send them (I don't have Faderport).

In year 2024... there is DAWProject ( documented XML format). Studio One is using XML (undocumented). REAPER - way simpler to read then XML own text format (semi-documented). That does not solved the problem with presets for plug-ins, they are in general blobs (even so many use XML, at least in part). So a DAW save FXP/vst(3)preset, but it is up to plug-in to interpret it. Relatively easy "hacking" original identity/version may "force" new plug-in version attempt to parse preset for old version, but the probability of success is strictly bound to plug-ins own presets backward compatibility. Saving project MIDI content as standard MIDI files will not work, the format does not define a possibility to add DAW specific info. It is possible to use "compatible" format, like in Yamaha Style Files, but simpler just use own format.

You first need to understand what NKS is... It is NI proprietary API extension for plug-ins. I have never seen any proposal from NI to integrate it into DAWs (does NI allows that?). It is not "hardware protocol", it is a protocol to communicate with NI software. What DAWs can support is KK (Komplete Kontrol) protocol, used by NI keyboard (throw software, "hardware protocol" is proprietary, not documented and not foreseen to be used by anyone outside NI). That is usually implemented by DAWs "control surface extensions". Possible features are DAW API dependent, but that is true for any controller. If you have M32 or Axx controllers, you can use https://www.azslow.com/index.php/topic,604.0.html. It provides more functionality then "standard" implementations then in other DAWs. I don't have Sxx, so related features are not supported and existing not tested. And I don't know if that will work with new Sonar/Next, currently I have no plans to use them.

DimPro from Sonar X3 times (or early) is plug-in which "will work forever". It requires no online activation (for serial activation in my experience it should be started once as Administrator, it reports "incorrect serial" otherwise). It works under Wine, so it is not even Windows dependent. Rapture Pro is from "online" era.

If "Quick start" is working (you can control track volume), your device is delivering what it should. For the Instrument. Start by looking if you can write an automation for the parameter in question (without controller, just try to add automation line for that parameter or write automation using GUI). If that is possible, you can assign it to hardware slider. If not, (2) and (3) will NOT work (VSTi normally support automations for parameters which make sense to automate, but there are cases when they "forget" to do that). I assume possible. For (2), replace "Strip" Action in the "Quick start" with "ACT" Action, select "Slider 1" in parameters. Try "ACT Learn"... if not working, follow "AZ ACT Fix" instructions I have linked.

The instrument has to support the feature explicitly. When supported, normally you can right click on the control and there is something like "MIDI learn" option. Then you send MIDI, like CC message, by moving/pushing/turning controller and plug-in remembers that. When there is no such option, instrument may response on some particular CCs. Normally mentioned in the documentation for the Instrument. In this case you externally configure the controller to send what is expected. Going with Surface Plug-ins (any of them) require first "MIDI learn" inside surface plug-in and then "ACT Learn" the parameter. As I have mentioned, the second part had quite some bugs in the history of Cakewalk. Check "AZ ACT Fix" utility: https://www.azslow.com/index.php/topic,297.0.html also read https://www.azslow.com/index.php/topic,13.0.html (some comments can be obsolete/fixed, but in general still valid). So using it allow editing mapping without "ACT Learn", but read the documentation, the utility is not intuitive. Note you can use it for control the mapping for any surface plug-in, you don't have to use AZ Controller. AZ Controller is most flexible but also most complicated surface plug-in. There are manual, tutorials and examples. If you master it (will take some time...), you will be able quickly assign your sliders to anything within seconds. To understand how "ACT MIDI" surface plug-in works (and optionally recreate its functionality in AZ Controller), read https://www.azslow.com/index.php/topic,107.0.html From that, even if you can not/will not follow, you will understand why the whole topic is not "simple". Note that ideas behind Control Surfaces in DAWs are almost the same for all controllers and all DAWs. Inside Cakewalk with AZ Controller you can learn these concepts without any background. In some other DAWs for the same you need programming skills (C++ in REAPER, Python in Ableton, etc.), and some DAWs don't have open API in public. So you have an opportunity to look "behind the scene" with relatively small effort.

May be REMOVING everything in "Control Surfaces" preferences is what you really want... Just make sure you set Omni MIDI as instrument input The explanations. Parameters of Instruments and FXes can be controlled 3+ different ways in Cakewalk: MIDI assign/learn inside the Instrument (many CCs are per-mapped). Some FXes may have MIDI input, in this case they can be controlled using the same approach. But FXes in general can be controlled used following methods only Using "ACT Dynamic Plug-in Mapping" feature, with "ACT MIDI", "Generic Surface", "AZController" plug-ins and corresponding configuration. The mapping work with plug-in in focus, the mapping is done with "ACT Learn" button. There was many bugs with the mapping, at least in the past. "AZ ACT Fix" utility can help keep persistence under control Using "ACT Direct Plug-in Control" feature, possible with "AZController" (also used by Mackie Cakewalk plug-in, but it works with Mackie compatible devices only). In this case you can control specific parameter of specific plug-in, so even several plug-ins in parallel. But for that you have to manually select what exactly you want control in the configuration. * Cakewalk has direct "Remote control" feature, so you can learn DAW parameters (and with some workaround Instrument parameters) directly. Unfortunately, 20+ years old design bug is still there (assigned MIDI still leaks to everything else) and I remember some other bug reports about persistence for assignments. So, till you do NOT use any MIDI instruments in the Project, I can't recommend using it (when unlucky, side effects can make you think you have serious problem with your minds...).

Good Sonar and Next overviews. Thanks! For stem separation, at least some time ago (when I was interested) my favorite was Ultimate Vocal Removal. Most (all?) separators differ just in trained model, and results depends from the music you separate (the quality of particular tracks is the source and model dependent, one model can deliver better drums while other better vocal, extracted from the same source...). UVR is a GUI with several parameters and models. It is offline and open source, as everything else it uses. Back-ends have good scientific explanations, comparisons and references.

For me https://www.bandlab.com/membership is just black... It contacts tons of trackers (google, tiktok, facebook, outbrain, etc.), my Firefox refuse to load it. From the beginning, "free" CbB was demanding re-activation every half an year. So it was clear it will not be really "free" forever. All these locking, started at Platinum time, especially after "new" version of Z3TA2 with online activation as the only visible change, and especially related bugs, was not convincing. Now the owner is different and management behavior is even less convincing: "our free product will be paid product... soon..." But I have thought may be there is re-start in the development. Unfortunately the video linked early in this thread has demonstrated the second change of GUI framework and several tiny features. No MIDI routing/VST and no offline pre-processing during playback and so I guess still the very same 20 years old engine. I am hobbyist, but last years I have payed quite some money for plug-ins and a bit for the DAW. And I have no regrets because each time it was absolutely clear for what I pay (and how much... for Bandlab membership I can't even find the price in euro and info about VAT). I want a DAW be able to run during lifetime (my! not DAWs!). And I know that is the case with Sonar X and my current DAW. Any version, at any time, offline. In other words, Sonar X (and CbB, till possible to run) projects will be supported by ReaCWP (I am still fixing bugs when spotted), but any changes in the format introduced by "new Sonar" will not be supported/fixed. I mean if you have project files from X/CbB, don't overwrite them when "testing" "new Sonar". Just in case you need ReaCWP in the future... who knows...

OSARA is a REAPER add-on, it has automatic installer but can be installed manually by copy one dll into expected directory (and loading shortcuts afterward). Works with any screen reader, under Windows and OSX. Sonar 8.5 was so popular because of CakeTalking (payed software) and JSonar (free). From what I know, developers was from the community, I mean not sighted developers with target users as testers, but other way around. Sonar X1 had completely new interface, Windows 8 also breaks several things. So, that direction is stalled long time ago. OSARA was born as a demand to move on somewhere. Since REAPER is the only other DAW with open API (in practice with way more possibilities then Cakewalk API), the choice of the DAW was simple. The idea was to make it free and open source, also the developer (AKA the owner) of REAPER is aware the community exists (clear from the REAPER's change-logs). All that is "alive", I mean there is active REAPER developer, active OSARA developer, active community "manager" and several sighted helpers. Most people have moved away from Sonar 8.5 (from what I know, including JSonar developer). I mean, I am not sending Annabelle down the rabbit hole, I just try to convince to take the route other have already taken (and not regret that). Cakewalk had intention to make CbB accessible. May be some day there will be yet another attempt. There are some people which in fact use Sonar X3/CbB, after creating the project in 8.5. With XTouch Compact and NI Keyboard that kind of works. But I can't recommend that, at least at the moment.

Unfortunately Speakerphone has no demo, so I can't check myself. May be worse to ask developers if the new version is JUCE based (most popular framework) and if so they should not forget to check accessibility. Recent JUCE version are accessible. As I have written before, for the host it is better leave Sonar 8.5. I know that is not easy, even for experienced people. But there is a big community which can help, most REAPER/OSARA users was working with Sonar 8.5 before. For plug-ins, fortunately there is movement toward native accessibility. JAWS / HSC / SIBIAC scripts for inaccessible plug-ins was fighting against the wall, and once something was developed there was a new version of plug-in and the work was voided.

You have even "liked" my post in the previous thread, about FluidSynth VST... I have checked and I am not delivering SysExes. I don't remember why, in the source I have a comment "todo" for it ? There was several technical problems with GM in VST3 format. And I have not invested time into GUI... But that does not prevent current version more or less working.

Some years ago I have tried to find multi-platform solution to use in place of TTS-1. And I have found nothing... Ended rolling my own based on SF2 synth, for sure far from perfect, not even with complete FluidSynth capabilities: https://github.com/AZSlow3/FluidSynthVST

That means my example with tempo change is not (or not only) the problem you observe... I don't have other ideas at the moment, but I will think more. So may be you can publish it (without audio, just .cwp file). Who knows, something there can give a hint (Cakewalk and I can see internal project structure), even when in its current state the bug is not reproducible. PS, OT Thank you for the clarification. I am long time present on this and previous Cakewalk forums, and there was several people which for one or another reason refused to communicate with me. Please don't get me wrong, I respect such decisions. But the silence sometimes irritates me, since in that case I don't know if my attempts to help make sense. Peace