azslow3

On 12/21/2022 at 5:37 PM, kzmaier said:

I was very happy to see this until I saw the date.  I tend to get lost in the details of Cakewalk/XTC configuration.  I rarely use the XTC for this reason.  I would love to get the device into my workflow.  Is there a Cakewalk/XTC for dummies reference out there??

Sorry to proliferate a old topic.

Thanks,

If you are blind, there is related solution: https://www.azslow.com/index.php/topic,346.0.html
But since LEDs make no sense in such case, the device stay dark all the time (and there is no on-screen display). So the solution is far from perfect for majority of users.
Well, you may find interesting to work just with audio feedback: you can stay away from the computer monitor nor look at XTC, and still have all important information...

I think that is a wish to use 8x oversampling, just for "safety" or really required by some crazy plug-in to work properly... In the second case it is better re-think and abandon the plug-in in question. It is definitively not written good when requiring such oversampling (and not providing it internally). In the first: that is "too much" in safety, do not forget that all less then a half of sampling frequencies are perfectly reproduced. Unlike 8x AA in graphics, extra high sampling rage does not "improve" anything. 96kHz by itself is already reproducing frequencies more that two times higher then any human (and audio equipment) can perceive. 

12 hours ago, John P said:

I'd consider trying to use AZ Controller to make a setup for Oxygen Pro Mini in Cakewalk, except I fear that it's complex enough that issues will arise, and when they do, my only option will be to try to work through them by talking with you on the Cakewalk forum.  You are a great guy, I just don't think such a talk is possible here.  

With me you can talk on this forum, my forum, WhatsUp/Skype/Phone.  On this forum you can "talk" to Mark (current supporter of Mackie Control in Cakewalk), Noel (long time Cakewalk developer) and other Cakewalk staff people. That is not the same as "support"  from Novation/Focusrite/M-Audio, where you normally can communicate just with (or throw) the "first level" support (people trained to answer common questions). People here not only know how all that works, but they are also able to modify related parts of the code in case that is required.

2 minutes ago, whoisp said:

Act midi only works on the 2) MIDIIN2 (LKMK3 MIDI) will not work on 1) LKMK3 MIDI to control a plugin like synthmaster so i am guessing the act control tech is more compatible with the whatever MIDIIN2 (LKMK3 MIDI)

Keyboard sends MIDI from each particular control to one port only. Which one depends from the keyboard settings, so currently loaded preset and activated mode. That is not something Cakewalk nor surface plug-in can influence (till plug-in knows how to switch mode/preset...).

The "bug" I have mentioned was rather confusing, in your example even so you could see let say "MIDIIN2" in the preferences, the DAW was actually using "LKMK3" instead. If that can happened in the current Cakewalk version I am not sure, I have not observed the effect for a while (but I try to be careful with connections...).

2 hours ago, whoisp said:

The one down side is from time to time when i reopen a project, i have to delete ACT MIDI Controllers and add them again for the 8 rotary knobs to work on synthmaster. For some reason they stop working and i am not sure where the bug is or if its me and why i was going to try "AZ Controller"

My first guess is a bug in Cakewalk, it likes messing with MIDI assignments of Control Surfaces (started in some version, then was changed/improved/modified, but I am not sure it is eliminated completely...). "AZ Controller" will not help if that is the issue, it also use Cakewalk MIDI (for that reason I was thinking several times to work with MIDI devices directly, but mentioned "one port for everything" case will be impossible then).

General rule with Cakewalk: always start it with the same MIDI devices connected into the same USB slots. Unfortunately that is not always practical or even not possible (I have several MIDI devices and I don't want switch all of them on every time I start a DAW, I also use different audio devices with different settings and that is real nightmare in all DAWs I use, why even "smartest" DAW developers can't at least remember one set of settings for each interface, better several presets, is a good question...).

4 hours ago, whoisp said:

 Like anything USB it acts as a storage device so to speak and with Novation, you need to update to the Novation USB drivers which gives you two midi inputs LKMK3 MIDI and MIDIIN2 (LKMK3 MIDI) and two midi outputs the same but different names. Do not ask me why not just one midi in and out i can not get anyone to tell me, i guess maybe a new protocol given its called MIII.

Here is the explanation: some DAWs are able to route one port (a MIDI device from software perspective) as "normal" MIDI (f.e. as input to VST Instruments) and to control the DAW. Obviously messages for controlling the DAW should be filtered out, f.e. Mackie sliders are sending "PitchBend" MIDI messages, you don't want change the pitch in your synth when you change the volume of your track.  DAWs in that category are Ableton and Cakewalk (while Cakewalk has no way to block the output to device in that mode, but that are details...).

But most DAWs need a separate  port (device) for DAW controlling. And if some device pretend it can emulate "standard" controllers, like Mackie, it can't send keys to the same port. That is not technically possible, even in Cakewalk (with Mackie surface plug-in).

Many controllers, including Lauchkey, are Ableton oriented. And so the have (or had) just one port. But if they want support "other DAWs", they have to implement at least 2 pairs of ports. And that has happened with MK3, they just want attract more users.

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

Which ports to use depends from what the device is sending, in most controllers (Launchkey including) that is freely configurable. In factory presets other then for Ableton, "DAW controlling" messages are send throw "DAW controlling port". And so this port has to be used to catch that messages.

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

"ACT MIDI" not only has strict limit on the number of controls, it also does not show the messages it receive. So you can't easily check which port you want.
Another limitation is just "banks" based switching what particular controls operate. That in practice is not flexible, especially with limited number of available controls.
How a control modify target parameter is also fixed, just "jump" and "catch" are possible. That is not always practical, at least not for all cases.

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

"AZ Controller" does not has these limitations. It supports unlimited number of possible controls, modifiers and combinations. It shows last receive MIDI message. I has several fancy modes for finite hardware controls.  It also support several instances, so several ports can be configured in one preset (for the "Master" instance) or separately. And when device has controllable LEDs, it can use them as well.

19 hours ago, John P said:

10. Click the yellow start button next to the red X button. In the popup window, click the Controller/Surface dropdown and select Mackie Control. Click the dropdown for Input Port and select MIDIIN3 (Oxygen Pro Mini). Click the dropdown for Output Port and select None.  Click OK to exit this popup window.

....

• Play some keys on the keyboard. If you don't hear sounds, check the In/Out section of the vertical track window on the left. It may work as Omni, but if not, trying changing it to MIDIIN3 (Oxygen Pro Mini) in the Input dropdown.  The Output dropdown should be set to Master. If still no sound, be aware that some VST instruments use only a subset of the piano keyboard. 

....

I can't promise that this will work for everyone, but it worked for me.  If there's a better way, let me know.

Bold parts can't work at the same time. Once MIDIIN3 is assigned to Mackie, all messages from it are blocked. And device is not sending keys there in any case (till in custom setup).

In general, you mention 3 different methods to use MIDI controller in Cakewalk:

1. throw Control Surface plug-in (AKA ACT, even so only one of such plug-in has "ACT MIDI" in the name). That you activate with Cubase mode on device and Mackie plug-in in Cubase mode in Cakewalk.  You doesn't mention/use that in "Testing" part.
2. "Remote Control" of particular Cakewalk elements. In "Testing" you recommend move controls "all the way" during learning. From my knowledge Cakewalk is not sufficiently "smart" to learn control type/range. It just take the first message and use corresponding default value range.
3. MIDI learn inside VSTi.

For 2 and 3 important is "simple" type of the message the control sends. In general on devices without touch function nor encoders that is default (till in Mackie/HUI imitating mode and the mode is activated), so I guess any "not DAW" preset for Mini can be used for both.

For 3 important is enabled echo on the track. So keys should work ("produce sound"). In Cakewalk that is default for focused track, but some users "manage" to switch that off.

Note that "ACT MIDI" supports an alternative way to control plug-ins, "Plug-in dynamic mapping" (also at many places/texts called just "ACT"...). Mackie does not support that way (it uses yet another way, "Plug-in direct control", which is not supported by "ACT MIDI"...). There are several differences between MIDI learn inside plug-in and plug-in controlling throw surface plug-ins:

• MIDI learn only works for plug-ins with MIDI input and only when that input is active ("echo on"). That means most FXes are not controllable that way (the have no MIDI input). Surface plug-ins can control any plug-in which expose automation parameters, independent from MIDI inputs.
• MIDI learned changes are recorded into MIDI clip, as "CCs" (assuming control sends CC). Surface plug-ins modify automations, so changes are recorded as automations.
• MIDI learned assignment are remembered by plug-in, this particular plug-in way. So can be preset dependent. Surface plug-ins mappings are saved separately by Cakewalk, they are activated any time corresponding plug-in is loaded, even with other preset or in other project.
• Note really a difference... But worse to mention: for Mackie, plug-ins mappings has to be manually written by user (also I doubt Mini in Cubase mode can select FX to control control). For "Plug-in dynamic mapping" all assignments are saved into 2 system-wide XML files, and sometimes Cakewalk can corrupt them, effectively loosing all created mappings (till good versions are backuped by user).

Finally, the only "perfect" way to integrate Mini into Cakewalk is AZ Controller. Mini has more controls then "ACT MIDI" support and its hardware controls don't match Mackie and so ineffective in that mode. But no-one has created corresponding preset so far. People normally just stop at "working acceptably", with any controller ?

For (1). MIDI can't get "out of tune", even on tempo changes. But most Synth react on "PitchWheel" events. Note that Cakewalk by default has "automatic echo" on MIDI tracks, so the track should not be armed to process external events, it just does not record them. Also note that some synth have "MIDI output" and Cakewalks "All MIDI Inputs" setting for MIDI track include also all software MIDI outputs. So, my guess you get some PitchWheel (or other events which produce pitch shift in particular synth), can be from (a) MPK (you touch the wheel or it is "self generating", not so unusual problem with MIDI controllers), (b) you cat if from MIDI output of some synth (c) in recording you somehow have "relative pitch shifting" CC and you don't reset it on looping, so it accumulates with time.

For (2). I guess almost no-one these days use synced arpeggiators in MIDI keyboard. They are good for hardware synth, but DAWs allow advanced arpeggiation in software. So it can happened related functionality is not well debugged in CbB. 

If there is ANY benefits in see/use/compare/correct multiple tracks, that is a good reason for Studio. Also some operations are simpler in Standalone, so not in a DAW.

But update price is in fact higher, independent which functionality was "updated". That is why I have not updated 4 to 5 till now (it is finally reasonable priced, for the first time since introduction...).  

On 12/4/2022 at 3:22 AM, Ernie Tamminga said:

A bit more info: I use Kontakt7 in Cakewalk, so any info pertinent to that, in this context, would also be appreciated.

If NI S61 is too expensive, NI A61 can be a good option for you. With NI keyboards you get pre-made auto-mapping for NI (and some other) synths, when used inside Komplete Kontrol. There is no official DAW integration into Cakewalk, but with my integration (A61 and M32 have the same DAW/synth controls) you will have good (I even claim better than in officially supported DAWs) functionality (targeting the time you play, so quickly want change the track/synth, jog, open synth interface, start recording, turn metronome, etc. especially since A61 is not "near notebook" device and so using mouse/computer keyboard in parallel is not convenient).

NI keyboards (all of them) have fine-grained encoders without raster. They are great for  continuous parameters (volume, frequency, etc.) and "effortless" switching pages/modes,  but far from the best option for live controlling a single synth, where finite knobs are more intuitive. Also note there are no faders and no pads.

Better visit a store where you can test several keyboard. All of them have completely different feel when you press keys, unlike "digital pianos" there is no "reference" they need to imitate. Even when disconnected, you can sort out variants you definitively don't like (too "soft", too "hard", too "clicky", etc.). Note that S61 has Fatar keys with after-touch,  A61 has "cheap" keys without after-touch. So the difference is way more then just build-in displays.

3 minutes ago, scook said:

While the track view only shows the audio FX rack, Instrument tracks have audio and MIDI plug-in racks. The FX rack displayed in the inspector depends on the ausio/MIDI tab selection at the bottom of the inspector.

That is one (from not so many) obvious possibilities which I periodically "discover" and then (completely...) forget ?

You can use MIDI FXes, f.e. "CC Map" from https://www.tencrazy.com/gadgets/mfx/

Note that Cakewalk has no "pre-FX", so recorded value will be original. You can Process/Apply Effect/MIDI effects to render the change permanently.

Also note you need MIDI track to insert these FXes, Instrument tracks show audio part FX bin, so you need to split it first.

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 ?

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 ?

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

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

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.

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... ?).
 

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.

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?
 

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.

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

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

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.

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