azslow3

I was looking for some GM synth which works under Linux (in fact I was looking for something working under Linux and Windows under REAPER). And since I have found nothing, I have rolled my own from FluidSynth. There is no legal way to write VST2 (there is only "gray" way), but there is GPL3 license for VST3. So, I have tried to use it. GM synth without program changes is obviously "no go", so I have searched really hard in all forums. As usual, I was also reading VST3 SDK source code and related documentation (and least for the topic in question). My conclusion I have already mentioned, the source code does not match the documentation... In all cases, unlike with VST2 it is not possible to deliver arbitrary MIDI messages to VST3 plug-in. They have decided MIDI messages are obsolete. Well, it is still possible to SEND MIDI messages from VST3 plug-in, related functions have "legacy" prefix. That was introduced years after VST3 was published, under heavy pressure from users. For receiving something, plug-in should organize separate infrastructure for each message type. For PC, plug-in should expose a list of presets. And then Host can (yes, just can, not must...) automatically convert PC messages into preset changes. For 128 possible values on 16 different channels.... yup... 1024 presets should be exposed to the host. BTW for CC, plug-in should create separated parameter for each CC on each channel. At least they do not ask to created something for each value of each CC parameter, for PC they effectively do. I (and some other) use my FluidSynth VST3 https://github.com/AZSlow3/FluidSynthVST It does not work in Cakewalk (I have not looked why), but it does work in REAPER. It seems like I have understood the concept right (I doubt it could work otherwise).

OP and some other worries mentioned in this thread have made my choice of the DAW to use. One DAW with true offline (no Internet required on any device) activation still exists. I don't trust dongles... Special dongles are not cheap (for home users) and license recovery in case of lost/broken is nightmare. To be on safe side, I have also written project converter. It is not perfect, but served the purpose reasonably well for many users. ------------- At the same time, it is really great Cakewalk has implemented activation inside the DAW. I am starting CbB periodically to support my surface plug-in (and sometimes for other reasons ), and dealing with Assistant (which could never update itself and so I had to reinstall it) was annoying. And so I think related changes are ?

You can write thanks to Stainberg for killing MIDI in VST3 and making VST2 obsolete... Not a joke. You can also ask Overloud to change Program Changes to Control Changes (which are still allowed in VST3) or implement horrible workaround to support PC and check it really works in Cakewalk (Steinberg SDK does not really follow Steinberg documentation for that SDK in that part, so no one really knows how to make it work universal way... again, that is not a joke).

BTW original discussion and working workaround (for single tracks): I think better solution is to have 3 (!) modes: arm is switched independently (as it is now) arm is project exclusive (at most one track/group can be armed) arm is input exclusive (at most one track/group per particular input(s set) can be armed, down to LEFT on one track + RIGHT on another is allowed, but STEREO track disarm both)

There is no "standard" way. But there are several. I think the simplest to try (and completely free) is WebTransport: https://www.azslow.com/index.php/topic,288.0.html If you ask Cakewalk to rewind on stop, that can be sufficient (in case you have other controllers / happy with mouse and keyboard). The next level is mentioned TouchDAW or TouchOSC: https://www.azslow.com/index.php/topic,295.0.html TouchOSC has some advantages and disadvantages. It works "directly" throw OSC, so without extra loopback daemons, it shows complete track/parameter names (TouchDAW emulate MCU, which has tiny displays) and you can adjust what it does/how it looks yourself (not so easy, but possible). But TouchOSC is a bit less stable and linked preset covers less then MCU (well, as you can notice at the end of the video, Dr. Mike rarely use anything except transport ? ). WiFi requires proper configuration and can influence performance (many WiFi/BT adapters in notebooks trigger huge system latency, you get clicks/pops under low buffer settings then). If you can use wires, use ANY wired MIDI controller. You can configure it to do anything you need and that is not hard (in case wishes are not extraordinary). The cheapest I know is Behringer X-Touch Mini. Some people prefer tiny "full scale DAW controllers" like Korg nonKONTROL Studio, other "one strip" controllers from Behringer or PreSonus, with idea "one good fader is better then 8 toys". But all that is relatively expensive.

We better discuss on my forum, since it is off-topic here... Try to run actfix.exe in the installation folder. If it does not work as well, there is some problem with MS runtime (I don't remember which is used, I always had it on all computers). Once you see it in Utilities menu, it is loaded fine. On multi-monitor system, check all monitors (the GUI is displayed by Cakewalk, may be it remember "off screen" positions...). Otherwise it appears in brackets in the Control Surface settings, in recent CbB versions check assigned MIDI IN/OUT are currently connected.

It can be you also have a workaround, unfortunately the link to Github does not exist and another link is to some "subscription"... ?

I guess (semi)pro users accept current behavior as it is. In fact there are many situations when several tracks should be armed in parallel even for 2x2 interfaces (f.e. Guitar + VOX) and MIDI input (multi-zone keyboard). There are scenarios when that is inconvenient. F.e. a "noob" (like me) record several tracks using one single instrument (guitar or mic). There are already several points to "remember" during that process (press "Rec" instead of "Play", arm something, echo, etc.) and remembering one more thing, to disarm previously recorded tracks, is annoying. There are also clear scenarios when that make no sense at all: if several audio tracks have the same input, it is hard to imagine when someone wants more then one of them armed. ----------------- Cakewalk is long time aware about "auto exclusivity", there is "Auto echo" (effectively implicit switching MIDI keyboard between tracks). And there is mentioned "exclusive arm" for takes. Many "concurrents" have addressed the problem (f.e. "auto arm" in REAPER, mentioned "exclusive arm" in Ableton). So, clearly the idea is not a joke. ----------------- When too annoyed, I used "macro" inside AZ Controller, to disarm all tracks + arm required. But that was working from surface(s) only. In case someone wants try the behavior, I have updated AZ Controller and have made a tiny preset: https://www.azslow.com/index.php?topic=298.msg1453#msg1453 It works without any surface:

"Cakewalk ACT" / "Generic surface" / (AZ Controller...) can do that. But in any case you need to "prepare" your Akai using its configuration utility. I recommend "CC" mode of pads instead of notes. If you use, make sure pads generate "unused" CC number which don't clash with knobs. F.e. assign "undefined" from the table https://www.midi.org/specifications-old/item/table-3-control-change-messages-data-bytes-2 Fo the plug-in to use. If all actions you want are in "Generic surface", it is the simplest to understand and use. Otherwise use "Cakewalk ACT". Both are well described in Cakewalk documentation (any many videos). If you want something unusual (f.e. LEDs under pads show current transport status, tricky sequences of operations not available as a single "command", etc.), you will need AZ Controller (and long time to configure it...).

The same with DAWs checking current time... The intention is also questionable and the implementation sometimes also produce unexpected issues ?

Cakewalk exists for too long, v27 ? Roland has not foreseen that Windows 8 drivers can work in Windows 10, so many devices was instantly "obsolete". AZ Controller also checks host version... fortunately it is still "supported" and so the bug could be fixed.

There is no more problem with AZ Controller. Was my fault ?

I have an idea concerning AZController misbehavior with 2021.1... Can it be that surface loop/midi can be called multi-threaded now? I mean f.e. calling MIDIIn while in idle loop? Not that is not allowed, but I have never observed that in any previous versions. There are some reasons AZController is not re-entrant. But the "protection" code can be buggy, since it was never tested...

Unlike other plug-ins, AZ Controller allows fancy things... And Heinz has decided to do jogging a bit unusual way, as you can see in his videos, he is jogging by fader. In addition he is calling "Go to prev/next measure" for that. I also support "normal" jogging, including by fader/knob. But somehow he had better results with commands before. Why he could get 127 changes from controller even on fast movement and why that "works" only 2 times in 2021.1 and can be "reset" by preset reloading stump me as well ? I have no ideas so far.

We will try to find out the reason for observation with AZ Controller "offline", but it will be helpful to know if something was changed in: input MIDI and the way it is delivered to Control surfaces, so something which can affect the number of received messages (when there are many of them, f.e. a knob is turned fast). commands processing, so processing of many commands (like go to the next measure) coming fast.

That is like looking for low cost auto with all possible feature, which work flawlessly on each road type at any speed ? Transport and fixed set of parameters will work using any keyboard (as long as it has corresponding hardware controls). "Fixed set" means you need "setup time" to bring each fader/knob in sync with Cakewalk, so once you change what you control (f.e. switch the sync or preset in the synth, move to the next block of tracks, etc) you need "setup time" again. Note that Synth control is normally work the same way as keys, so the DAW is not involved in that process (it just pass MIDI to plug-in). For anything else (Mix, FXes, complicated synths control) low cost keyboards are not a good. Which more expensive keyboards to choose depends from required operations. F.e. for synth parameters adjusting while switching synths, NI is probably the best option. While for 8 channel mixer combined with keyboard, Motör can be better. My usual quick and dirty advise: with TouchDAW you can get an idea what (expensive) DAW controller can do in Cakewalk, for $5. As low cost hardware try X-Touch Mini for $50. Put on your PX201, it can somehow imitate (expensive) NI keyboard experience with synths while providing reasonable DAW controlling functionality (NI can't do that currently in Cakewalk).

You already hit the first reason Control Surfaces are difficult... Names!? ---- ProTools support HUI (protocol) only. So, if you select "ProTools" target, DM will speak HUI. HUI (device) was produced by Mackie (company) with special HUI protocol, later they have produced Logic and then MCU (Pro) devices, commonly known as "Mackie" (device). And MCU can be switched to "ProTools" mode (HUI protocol). So, switch DM to "ProTools" mode and use MIDI devices to configure "Mackie Control" surface plug-in in Cakewalk. In that plug-in select "HUI (Beta)" protocol. Start with MIDI In/Out which you think control channels 1-8 and should also send transport and other buttons(*). When that work, add "Mackie Control XT" with In/Out for the next group of 8 channels. And so on. * that is why you see some "CC" from transport on USB-1. Note they are a bit more complicated that just "CC"... mcmcleod is the author of "HUI (Beta)", so you will be supported in case something goes wrong on the software side (BTW "Mackie Control" is Open Source, in case you have some experience with C++ and want to have a look how all that works...) ---- If you want to observe which messages are sent and how they are interpreted, you can initially use AZ Controller with mentioned by be "HUIv2" preset loaded on USB-1 (Instead of "Mackie Control", do not try to use in parallel). Unlike other plug-ins, it display what it receives and how it interpret (for not yet assigned complex messages you will need to play with interpretation "Options", see my previous post for explanation). But there is no "XT", so you will be limited to 8 channels + transport, till you extend the preset (far from easy without experience) or switch back to "Mackie Control" + XT(s). ---- MMC is a (fixed) set of SysEx messaged, originally indented to sync hardware MIDI devices. Cakewalk CAN send them for that purpose, but you do NOT want to use MMC as "MMC" in any case, just as SysEx messages assignable to some actions in Generic Surface (if you are not in ProTools mode...). For Generic Surface read (3-5 times, not a joke...) the documentation of Cakewalk. I repeat, at least 3 times. I have stopped after reading it 2 times, could not understand it, and started to write AZ Controller ?

AZ Controller support all MIDI messages Not a joke, in fact that is more difficult than someone can guess... HUI has "triggered" support different CC modes in one preset 14bit CC sequences (including (N)RPNs) are supported with standard as well as arbitrary order, including mapping a part of the value to separated controls (A&H style) complex SysEx mappings (Roland and Yamaha digital mixers in "native" mode) Mackie handshake and Roland checksum, Mackie style ring feedback (other feedback I have seen so far could be organized in presets without special code in plug-in). But I can't claim the same for OSC, f.e. Behringer DMs OSC is not supported, I guess NI MK2 OSC also needs some addition in the code. Well, NI MK2 MIDI (native mode) will be hard to support too, but not in the MIDI parsing part... My HUI example was tested with Nocturn only, one user has tested with d8b http://www.azslow.com/index.php/topic,223.msg1386.html#msg1386 BTW I have complex preset for Yamaha 01V in MIDI mode, can happened something in it can work for other Yamaha mixers (if MIDI implementations overlap). But that is not recommended since controlling DAW using DM native MIDI means DM can no longer be used as a mixer (Cakewalk project will influence sound processing in the mixer).

It depends... Configure DM's DAW control mode (preferably "Mackie", in case it has it, but HUI should also work somehow). And then use Mackie surface module in Cakewalk. For anything else (in case you are not happy with simple approach), you will need deep understanding how all that staff works. F.e. you probably don't want MMC function as originally intended (to control hardware devices) even in case you have corresponding hardware, but you can use MMC sending buttons as generic Control Surface buttons, to control Cakewalk transport (or something else in Cakewalk...). You can even use MIDI DM signals, originally independent to sync DMs and/or save parameters, to control something in the DAW. But that is relatively difficult.

I also can't remember faders ever followed CC7 events. Logically CC7 envelopes was always separate from CC7 events in the clip, the fader is working with envelopes (and there is no mode switch for it), so how could it follow two different values at the same time?

I guess in case that is true, my old 8x8 USB2 interface couldn't work on it's lowest settings when connected to 10m USB hub in parallel with several USB1 devices. But it works. USB specification deals with different standard/speed devices much better then making everything slow. ? Also under 1ms RTL is never "comfortable". Computer should be top optimized and plug-ins carefully selected. Yes, there are no USB interfaces with such feature. But 3.3ms is really usable, with USB2 and moderate buffer size. In practice, the difference can be rarely perceived (taking into account that moving your head 30cm in any direction change latency by 1ms...).

And I have uploaded moded version there ?

Also note in case you use the same plug-in for several devices (f.e. "ACT MIDI" for both), Preset names will be bugged (both will show the same preset name, while in fact they will load correct preset for each instance). BTW @msmcleod are there any plans to fix that ? ?

We better discuss that on my forum... Upload your current preset there (v6 preset in the link doesn't produce WAI picture shown) and I will try to adopt it.

Unfortunately Digitech documentation say nothing about MIDI these devices send (they just describe how they work with in-house software). Please check the following: remove ACT MIDI and start recording "RPx400 MIDI" device into MIDI track. Press each button for 2-3 seconds. Then stop recording. Open "Views/Event List" in Cakewalk. It should list what buttons send to Cakewalk. Write us what you see in the "Kind" and "Data" column, Alternatively you can use any MIDI monitoring tools you now.