Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

135 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. There is no more problem with AZ Controller. Was my fault 🙄
  3. 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...
  4. 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.
  5. 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.
  6. 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).
  7. 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 🙄
  8. 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).
  9. 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.
  10. 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?
  11. 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...).
  12. And I have uploaded moded version there 😉
  13. 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 ? 😉
  14. 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.
  15. 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.
  • Create New...