Jump to content

azslow3

Members
  • Posts

    668
  • Joined

  • Last visited

Posts posted by azslow3

  1. 1 hour ago, murat k. said:

    FL Studio ASIO is a WASAPI drive actually.

    This is why the file's name is ILWASAPI2ASIO. Means Image Line (company name) WASAPI (The actual driver) To ASIO (Acts like an ASIO driver)

    Thanks for the suggestion. I was thinking to buy a simple mixer to route audios which is cheaper than you suggest then I gave up because I have no trouble with latency anymore with this solution. Also these are extra profits which comes besides working with multiple interfaces:

    And the new prefence "Enable MMCSS for ASIO Driver" made it better. In the past sometimes I was getting audio crackling on the playback, nowadays I don't get any issues.

    Well... a mixer was my second "audio interface", the third was VoiceLive Play (really that time I couldn't put all music equipment together into one place, so I had to use 3 computers as well, lol). Sure, I was also experimenting with ASIO4ALL at that time, more as an attempt to put VoiceLive Play and build-in Realtek together. Later was more interfaces and more software.

    What I mean, I took rather long way to RME. With many "aha!" and "omg..." moments. And I can't say it was not interesting.  My current desktop setup is still a "workaround". I wish at least 8 inputs interface with low latency, which can work standalone. Some day I probably get UFX (or switch to Motu...). But the primary reason I don't have it already, is an attempt to come to the goal "cheap". I mean I have 8x8 + 2x4 interfaces permanently connected which do almost everything I need (8x8 can mix standalone). Just not perfect (latency and quality are not top).

    So I just try to recommend everyone to find something which perfectly serve wishes from the beginning. I mean I recommend the short way instead of workarounds 😉

  2. 8 hours ago, murat k. said:

    I have had no issue with ASIO4All since I found a way to use it. In the beginning, people get some issues and leaves it, but after getting its working principle, you can handle it without a problem.
    But the problem with ASIO4All and some other drivers, you can't get sound outside of the DAW. There is a solution with WASAPI Shared but it has too much latency. With the MME(32bit) you get sound crackling eventually. Suspending the Audio engine is not working all the time depending on the task you want. 
    With FL Studio ASIO you don't get any issues with the sound or latency. I mean it also focuses on your DAW, but still allows you to hear/send other audio on your PC and still get low latency.
    Yes, there is a way to get low latency with no audio issues. Having multi-input/output soundcard with the internal one and connecting one to another. But you don't need this since you have a working solution called FL Studio ASIO.
    Also, it reduces the CPU load on the DAW, you can see the difference when you switch between WASAPI and FL Studio ASIO.
    And also you can switch the active playback/recording sound device easily without having to open the Preferences menu.
    This is why I recommend FL Studio ASIO to people when the topic comes to sound drivers. I tried all others and came back to it all the time. 

    "FL Studio/ASIO4ALL/other generic" ASIO is visible from applications as ASIO. But they have to access hardware driver, which is not ASIO. Back in time, proxies sitting in the "kernel" could reduce latency a bit. MS has done relatively good job with WASAPI, on some hardware it even beats dedicated ASIO driver in latency. So for normal use, extra proxies are pointless.

    I agree that for using multiple interfaces in parallel (tricky in any case since that needs hardware sync between them) or using several applications in parallel they still can be used. But if that is "usual" activity, getting an interface which natively allow that is the best way to solve the problem. In my experience,  "tricking" with fancy external software till some degree works, but can't be perfect (such software still has to deal with "laggy" hardware and Windows design). Note that is not automatically expensive. Like 8 years ago I have payed around 20€ for M-Audio Audiophile FireWire, it has own ASIO and allows other apps in parallel. And it is still my "default" interface for desktop 😏

  3. 2 hours ago, Byron Dickens said:

    Talk about understatement. The Realtek ASIO driver is even worse than ASIO4ALL.

    Well, unlike ASIO4ALL it has never corrupted all ASIO drivers on computer for me. And I was using Realtek ASIO not at "prehistoric" times (ASIO4ALL almost make no sense since introduction of WASAPI).

  4. 6 hours ago, Krishna Ramsundar said:

    Thanks for your reply. WASAPI Shared is the only one that give me no trouble. It slightly improved but its still there.  The delay is constant however. So if I can tell exactly how much it's off by, I can use that number to precisely trim each track

    I didn't know about nudge until now. That's neat! Now I gotta set it up.

    I think you question is not about latency by itself, but about recorded material shift between tracks coursed by that latency and the fact Cakewalk has not way to calculate it correctly. There is "Record latency adjustment" setting which you can try to set. For that you need to loop-record or just use your "constant delay", if precision is not important. You can really see it in "samples" (as required by the setting) in timeline.

    I recommend make WASAPI Exclusive to work (if WASAPI Shared works, that should be an option as well). Shared mix other audio from computer (youtube, etc.), so that is "convenient". But it has higher and more unpredictable latency.

    Dedicated audio interfaces with ASIO driver are nice and allow auto-calculation working (or almost working), but if you don't record mics nor guitar and you don't have studio monitors nor studio headphones, almost all there features and advantages are void for you. Note that modern Realtek (build-in chip in most if not all PCs) has ASIO drivers. Not the best, but it's latency is comparable with what you can get from $100 interface (you will need to invest more and optimize the computer for audio to really go lower). So dedicated interface will be more stable,  has better sound quality and  pre-amp(s). But you need some way to use these features, and that is not possible in under $100 price range (you will need to spend more that $50 just for headphones).

    Getting Realtek ASIO working can be tricky, especially on notebooks. They sometimes have "own" drivers which don't include it (or not include its controlling panel). But normally you can Google for solution (like downloading original Realtek drivers, sometimes just copy something from it, sometimes install it and then specialized drivers...). WASAPI Exclusive normally has almost the same performance, so start with that.

    Most important is matching sample rate in Windows settings and sample rate in Cakewalk. Just use 44.1 or 48 for everything, whatever you prefer.

    PS. when/if you look for an interface, plan in advance. Manny non-professionals (me inclusive) too the "long road" and have collected several interfaces before getting something they like, just wasting the time and money. I understand that $500+ price tag sounds like "OMG, that I don't need for sure..." at first. But it all depends what you do and will do. Also in some situations second hand middle-high range interfaces can be not so bad choice. In other, Yamaha AG can be the thing (unlike "normal" interfaces in that price range, it can work stand-alone). I repeat, better plan then just follow the idea "something under $50", I have 2 of such (second hand, originally in over $200 price range) laying around and collecting dust... :)

     

  5. When preset is generated with "ACT" selected for plug-in mode, knobs can be learned to control parameters of plug-in in focus. The procedure is "Plug-in Dynamic Mapping", unfortunately also known as "ACT" (which means several different things).

    Alphatrack has display, so you can see what is controlled by encoders. That is not the case for buttons (and device does not have many of them). So only encoders can be assigned. But they can be assigned to "buttons/switches" in plug-ins as well. The same is used f.e. in Komplete Kontrol by NI. They use encoders only for all plug-in parameters.

    Alphatrack encoders are assigned to the first  5 "Rotaries" for the mapping purpose, 3+2 parameters in 2 pages. Well, not many... but that is what this device has. The 3d encoder is the second page is "Quick dial". It can control whatever parameter is last modified. F.e. you start control some parameter with mouse, and the continue tweaking with this encoder. No "ACT Learn" is required for that. But that does not work if you have automated some parameter(s).
    Also note that the slider can be "flipped" with any of encoders.

    PS. To be sure everything you have learned is persistent, you need to use "AZ ACT Fix" from my site. At some moment you can find that all your mappings are gone or what you learn is no longer mapped after Cakewalk restart. That utility check that mapping files are not corrupted, allow quick backup/restore of mappings and can help with mapping for plug-ins which do not react on "ACT Learn" correctly. 

    PSPS. Plug-ins normally have many parameters. And Alphatrack has just 3 encoders. For convenience it is better to have at least 8 physical encoders, f.e. "Behringer X-Touch Mini". For Soft Synths it is way more convenient when everything is pre-mapped. F.e. NI NKS.

  6. I am a programmer  and I am not working for BandLab. They have skilled people which understand what CLAP is and how much work is required to support it (as you could see in the answer from Noel, that is unfortunately not easy).

    I just thought leaving this thread in the state "users don't see a point" was not good. I prefer to support progressive ideas. And when something "is not there" and I can make it on my own, I try to do this (f.e. you can find my post early today what was not possible yesterday, but possible now, even so the number of "users" of the feature is probably close to... 😏).
     

  7. I have seen a question about editing Drum Maps as text (for convenience). And I have realized I have almost everything to create corresponding utility:
    https://www.azslow.com/index.php?action=downloads;sa=view;down=92

    How to use:

    1. Create Drum Map in Cakewalk, with desired Instruments/Ports/Channels/patches defined. So, create at least one key mapping for each distinct Port/Channel pair. Name mappings the way you can recognize in text form (which mapping is for which port/channel). Save this drum map as preset (to create .map file)
    2. Run the utility with map file as the only parameters, f.e. cakedm MyMap.map. That should create MyMap.txt file.
    3. Copy text file, so you know it is edited version (the file name will be new map name).
    4. Edit text file. From previously defined key mappings you will notice the format, "Name",InNote,OutNote,Channel(zero based),Port[,Shift,Scale]. Do not insert extra spaces in mapping lines (all lines not started with " are comments). So copy/paste existing line and change name, in and out notes.
    5. Run the utility to produce new map: cakedm MyMap.map MyNewMap.txt. Note you need to specify original map and edited text file.
    6. Restart Cakewalk so its see new map.

     

    • Like 2
    • Thanks 1
  8. 14 hours ago, Asato Maa said:

    The development of a new feature should solve some problem for a large number of users, or bring new value to them.
    Given that:
    1. There are practically no applications on the market
    2. They are co-developed with Bitwig
    3. 99% of any applications can be found in VST 2 and VST3 - there is no special need for it
    At least for myself, I don’t see the point in CLAP.

    1. Yup. But that means Cakewalk can be in the short list of pioneers. It was with ARA, even so there was practically one plug-in for it.

    2. So what? Is Bitwig evil? The standard is open and not owned by any company (unlike all currently "common" formats).

    3. you know that new developers are not allowed to write VST2. And VST3 has many problems (along with the fact the owner can declare it "obsolete" any time, and unlike with VST2 even currently developers will have to abandon it in flavor of whatever creature Steinberg declare as "the new one"). Right?

    For long time no-one could see "the point" in e-cars. And then.... ups...

    Also Cakewalk's DX driven MIDI engine has to be replaces. VST2 is obsolete. VST3 doesn't really support MIDI. So, why not target CLAP there?
     

    • Like 2
    • Great Idea 1
  9. If you still have Novation, try to find the way to control plug-ins.  With Automap software (assuming it is still working, I have not checked for a long time) you will need to use the wrapper plug-in, but the keyboard should work as desired. Alternatively try to get some MIDI from controls (probably hard without Automap server) and use them with "Cakewalk ACT MIDI". For Cakewalk there is nothing new in that area, there are still "dynamic mapping" (which is still buggy, but usable) and "direct mapping" (you will need to write all parameters for each plug-in into text file and your device should be Mackie MCU or one of its full clones).
    Getting parameter on the display and encoder rings on Novation is rather hard with ACT.

    From what I know, there is no controllers with display and ring feedback which will work with ACT out of the box. Theoretically NI S keyboard can do the trick using my solution, but practically that was never tested (I have only M, its tiny single display is able to show only single parameter/value). Note that NI keyboard have great own mapping for plug-ins wrapped into Komplete Kontrol , so great for VSTi but tricky for FXes.
    If you want "play" with ACT  using on-screen display, you can try Behringer X-Touch Mini with my solution for it.

  10. 57 minutes ago, Starship Krupa said:

    Hmm. I guess I need to investigate this further. The Saffire Pro 40 has a loopback feature, but I've ignored it. If it makes it easier to capture audio from Windows, I'm in. I do this all the time to capture dialog samples.

    Once in a while (decade or so) people "discover" new features of the (same) interfaces 😉

    http://forum.cakewalk.com/Track-Loopback-Focusrite-Saffire-MixControl-m3122377.aspx

    But under Windows, RME "loopback" is by far more flexible then other solutions I have observed. Any mix (including for digital outputs) can be declared "loopback", after that corresponding "input" get loopback signal . So several separate mixes can be "looped back" even with Babyface.
    F.e. communication (f.e. ZOOM) + screen recording (f.e. OBS) can get desired separate mixes (from DAW(s) and other programs outputs , hardware inputs), apart from mixes for headphones and monitors. In that example, you probably want record everything, send some mix including your mic to the peer while having some different mix (at least without full own mic) in headphones/monitors. "Simple" looback hit its limit in such cases...

     

    • Thanks 1
  11. On 11/1/2022 at 7:15 PM, Oscar Myer said:

    I know what you mean about all the "K" stuff.  Keep in mind that I didn't have a clue and put all my faith in my sales rep.

    I found 3 libraries by Indiginus that I just HAD to have.  Their site said that I would need a paid version of Kontakt in order to use them.  So I went shopping for Kontakt.  Sales guy pointed out an open box version of Kontakt Komplete 13 Select package for $179 US dollars.  I live in Canada and have to pay the exchange rate, tax and $48 duty.  Total cost was north of $250  I installed it only to find out that it was Kontakt 6 PLAYER.  I needed the full version of Kontakt in order to use the plugins I wanted.  Long story short;  Another $400 plus and I now have the full version Kontakt 7 (included into Komplete 14 Standard).  Of course I didn't buy it from the same store.  I got it directly from NI and was even able to pay for it in Canadian money.  It came bundled with a few libraries that I'll never use... oh well... at least I have it now.

    This expensive experience can be chalked up to being my own fault because I didn't do enough research.  But I can say that I know what all those "k"s mean now.

    I also noticed that Indiginus have now made it very clear what is needed to use their libraries on their site... in big bold font.

    In your post "K"s have a bit misleading meaning. There is no "Kontakt 13" nor "Kontakt Select". There are just "Kontakt Player" (free) and "Kontakt" (payed), current version 7. There was "Komplete 13 Select", which  (as free "Komplete Start") 'includes'  "Kontakt 6 Player" only.

    "Komplete Select" full price is around 200 $/€. It's upgrade to "Komplete Standard" full price is around 400 $/€. So my corrections match these numbers.

    For "Kontakt 7" alone full price (without upgrade/cross-grade) is 300 $/€. But cross-grade is 200 $/€, and I think there are still free libraries for cross-grade. I mean over $400 just for Kontakt is way too much.

    ---

    The cheapest routes for Komplete which was possible 2022 - NI M32 during "special sale" with "Komplete Select" included (normally includes "Komplete Collection"), update to "Komplete Standard" during "upgrade sale". Total price ~300. Or just NI M32 -> "Komplete Select" (offer after registration) -> "Komplete Standard" during "upgrade sale". Total price ~350. Sure, that was for Kontakt 6. But includes Komplete Kontrol hardware, well usable for NI products (not so usable as keys, but for some synth sounds can be sufficient...).

  12. 11 hours ago, whoisp said:

    I have a strange issue with my Novation Launch Key 25 the new MKIII version and Novation could not help but i have it working if anyone interested. 

    For a start the MKIII brings in 2 midi inputs Device names with how Windows handles USB devices; LKMK3 MIDI & MIDIIN2 (LKMK3 MIDI)   so you need to add 2 act midi controllers for the one device.

    (ACT MIDI controller 1 )  = LKMK3 MIDI 

    (ACT MIDI controller 2)   = MIDIIN2 (LKMK3 MIDI)    

    Now this creates a problem with having 2 controllers with "1 hardware device" The  Novation Launch Key 25 "New MKIII version" and i am not sure if other hardware have this same bug or programming issue, i would suspect yes when it comes to USB. You also have to install the Novation USB driver, most keyboard controllers act as mass storage device, they will run some start up software for mapping or presets or registration etc

    Keyboards with Mackie emulation (according to the documentation, Launch Key 25 MKIII has it) always have to exposed themselves as 2 MIDI devices, one for "normal" MIDI (at least keys), other for DAW control.

    "Standard" setup for this case is what abacab has described, try to follow "Cubase" section in Novation documentation and "Mackie Control" in Cakewalk. In Cakewalk Mackie settings you set "Cubase"  and "Disable handshake".

    Other port can be used for "ACT MIDI" or for direct MIDI learning in VSTi (some FXes also support MIDI input).

    You switch "modes" on device, using Novation provided method.

    --------------------------------------------------------------------

    Note. This thread is about nanoKontrol 2. It has no second pair of ports no live mapping switch. Arturia / Novation MK3 methods are NOT usable with this Korg.
    With AZ Controller it is possible switching modes in software, one device with fixed MIDI mapping can be used for ACT (DAW or plug-in control) and for MIDI learn in VSTi. But that is the only ACT Control Surface plug-in which supports that.

  13. 1 hour ago, Terry Andrews said:

    On James Argo post, I can't seem to find 'Controller/Surface Settings' box with the drop down settings. Obviously, I'm doing something wrong....

    Suggestions?

    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 😏)

    • Great Idea 1
  14. 2 hours ago, Simon Wilkinson said:

    Sometimes ACT Learn picks up what I'm teaching it but after a while it just randomly stops recognising my movements (even if it's a parameter that it recognised previously). A restart of Cakewalk usually gets it working again (or as you say, by using your ACT Fix app). But then it happens again at some random point. The fact that after a restart it will then recognise exactly the same thing that it didn't recognise before the restart makes it look like some kind of bug in the way ACT works.

    ACT is *almost* usable but it's just a bit too buggy and fiddly in its current state. Hopefully at some point the use of control surfaces in Cakewalk will get an overhaul :)

    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.

  15. 10 hours ago, Simon Wilkinson said:

    I'm in the same situation as @Starship Krupa in that once or twice a year I dig out my MIDI controller (either a Behringer X-Mini ...

    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.

    • Like 1
  16. 8 hours ago, Starship Krupa said:

    At the start, when giving step by step instructions, it says "if you want to use Active Controller Technology, or if your controller/surface is not listed, select either the Cakewalk Generic Surface or the ACT MIDI Controller."

    I should flip a coin here? When I'm reading instructions and the instructions give me a choice that I am not informed about in any way, my train of learning gets derailed. Which is it? If it makes no difference, why have two options? If it DOES make a difference, tell me why before I make the decision. 🤦‍♂️

    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:

    8 hours ago, Starship Krupa said:

    image.png.d6fc345da05541ff56cb2311ad268e94.png

     

    image.png.897b055cca2c3676af311a890db8110f.png

     

    "image.png.d47417797fa552d12f965111a3d0717a.png The garbled characters indicating what the control surface is controlling are an interesting touch. Accurate, in a certain sense.

    "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.

    8 hours ago, Starship Krupa said:

    The documentation has it completely wrong here: "You can edit the cell label by clicking the label and entering a new name in the Edit Label dialog box."

    Um, no I can't, when I click anywhere in the cell it puts the entire dialog into "MIDI Learn" where it stays until I move a knob or click back in the cell.

    Read one (two, three...) more time. "You can edit the cell label...". That is the text which is "R1", "S1", "B1", etc.

    8 hours ago, Starship Krupa said:

    The way I would like it to work is that there would be a dialog where you would click to add as many cells as you wish to assign. Then you would click in that cell and have a way to choose the parameter you want from a list populated with the same information that the plug-in exposes to Cakewalk's automation. Then you would choose which knob you want to control that parameter, either by using MIDI learn or by typing in the MIDI CC number.

    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".

  17. 1 hour ago, Bruno de Souza Lino said:

    So far only BitWig and REAPER support CLAP plugins.

    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".

    • Like 4
  18. 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.

     

    • Like 1
  19. 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). 🤒

  20. 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. 

  21. 1 hour ago, User 905133 said:

    Hope I am not derailing the discussion, but I am wondering what the advantages are of using either a Control Surface style setup or an ACT style setup over a more direct approach.  For software synths, I usually just right click on a parameter control in a VST (unless the VST requires an additional parameter mapping step), select MIDI Learn in the VST's UI (assuming the manufacturer implemented it), and move the desired hardware controller on my keyboard.

    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".

     

    • Thanks 1
  22. 17 hours ago, Milton Sica said:

    Hello, some time ago I opened a topic of my own and made comments reporting that my PAN controls are sometimes changed.
    I use a Nano KOntrol 2 and found that the changes, even without any movement on my part, only happen when the surface is active.

    So for me it would be important if there was some way to turn NanoKontrol ON/OFF without having to go to preferences and disconnect.

    Do you have any suggestions or tips for this operation to be better performed? Maybe some BUTTON SENSITIVITY command?

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

    • Thanks 1
×
×
  • Create New...