Search the Community

Hello, I just got my first MIDI keyboard, and I wanted to connect it to Cakewalk. I'm using the base version, no paid upgrades. My keyboard is a Nektar Impact LX88+ I have followed all the instructions that came with the board for setup, but it won't show up in the MIDI devices panel. What am I doing wrong, and/or missing?

Just in case you missed this, the LX series have custom software that enables quite good integration with Cakewalk. It has to be downloaded separately from Nektar after registering your keyboard with them. Looking at your screen shots where the keyboard was identified just as MIDI1 and MIDI2 leads me to believe you have not downloaded and installed this software. Cakewalk should see two inputs [Impact LX88+ and MIDIN2 (Impact LX88+)] and one output [Impact LX88+] for your LX keyboard. If you use other DAWs as well, they have separate software for each DAW, you can download and install as many as you want.

Just a quick question to what people use as i am thinking of a new keyboard controller 49-61 keys. This is my list what iv'e narrow it down too but i could have missed one out. . Here's my first place which i believe i prefer. Anyone use these with cakewalk? 1: Novation Impulse 61-49 key version sounds the best all rounder. 2: Nektar Panorama P6 (seems expensive) 3: Arturia KEYLAB 61 Iv'e also looking at M_Audio and Akai but few people say they break easy but not sure Any experiences and opinions welcome for easier work flow and obviously we are the main instrument so maybe something that gets our juices going.....

I'm currently experiencing a strange problem with my CbB installation. Yesterday I got rid of my old MIDI keyboard, and replaced it with a Nektar Impact LX88+. To use all the fancy bells and whistles of the new keyboard, I installed the Cakewalk integration package from Nektar. That's when all hell broke loose. Immediately after adding the control surface, I got a message box saying that no audio device was available. In the preferences dialog, I could see that my audio interface (Roland Quad-Capture) had mysteriously disappeared from the list of available devices. First I tried to simply restart CbB, but that did not fix anything. Then I uninstalled and reinstalled the Quad-Capture device driver, and also upgraded CbB to the newest version. The list of available devices would now be filled up with cryptic entries that made no sense to me. However, the Quad-Capture was also listed, but every time I tried to select it and click Apply, I would get an error message about the current audio format not being supported on any device. However, after a couple of reboots and a bit of experimenting with the settings, things suddenly seemed to be back to normal again. But much to my disappointment, as soon as I tried to open a project, CbB would terminate. This happens consistently whenever I try to open an existing project or create a new one - even if it's empty. CbB will perform the usual actions as indicated by the popups in the lower right corner, but just when it's ready to update the GUI, the application dies. No error message or anything - it just disappears. This is obviously a bit of a showstopper, so I really need to find out what's going on. I also observe that the Quad-Capture will repeatedly disappear from the list of available devices. Rebooting the computer fixes this, but it's still annoying. Any suggestions on where to begin the troubleshooting?

If the Nektar LX+ controllers otherwise meet your requirements, you should not be put off by the threads where some people could not get them to work as they had hoped. I don't know what they did wrong, but I just got an LX49+, and had no trouble quickly connecting it with CbB. Their website clearly documents what it will do with each of the DAWs it supports, and it does everything they say it will with no user mapping/programming required. It has separate dedicated plug-ins for each DAW, including Sonar/CbB. You have to register with Nektar to download the plug-ins and installation instructions. I just followed those instructions and it works flawlessly. I also set it up with the free version of Studio One 5, and it works as advertised there too. The Nektar LX+ keyboards also allow for quite a bit of additional user programming for more specific control of VST instruments for example, if you are so inclined. I haven't gone down that path yet, and may not need to. Everyone's needs are different, but yours may be similar to mine. I did a lot of research to find the best controller for me, especially considering that CbB is my DAW of choice, and have not been disappointed in any way. I think these are the only controllers anywhere near the price that do have a dedicated plug-in for Sonar/CbB. If you use one of the "major" DAWs, there are more choices. If you want the nine faders, you'll have to go for 49 keys. The 25 key version only has room for one fader.

Thank you for the responses. I currently have a Nektar Panorama P4 that works GREAT in both Reason and Reaper -- just not Cakewalk. I'd make a switch of I can find a comparable piece that does the same things and recognizes Cakewalk as well. It's not terrible though since I also use a Yamaha MO8 that has a DAW Control function that DOES work with Cakewalk in a limited way - but is to my right, not front and center as the P4 is.

Just wondering if anyone else ran into this....I was trying out Spitfire Labs with Cakewalk and everything would crash and close. Sometimes it'd happen right away, other times it'd be after I switched instruments. Funny thing is, it was happening when I had a Nektar keyboard hooked up. I was just playing around now using the virtual keyboard, and no issues. BTW, I am totally new to Cakewalk and DAWs in general, so am pretty clueless when it comes this stuff. I didn't like the keys on the Nektar board, so I'm getting a little 32-key Arturia instead. We'll see how that goes 😀

The Nektar, being a controller, makes no sound of its own, so the signal must go through some other synthesizer, such as the Microsoft GS Wavetable synth in many computer sound cards, or a software synth. The soft synth's output will be audio and go through the interface.

Does anyone knows how to connect Nektar GX 49 to Cakewalk?

Install the driver if necessary Connect the Nektar GX 49 to your USB port Open Cakewalk - head to Preferences - MIDI - Devices - enable input Too easy!

Have you tried looking at the documentation? https://nektartech.com/getting-started-nektar/

I have the Nektar LX88+ and it works fine with cakewalk. They have a special driver that you install. The only thing I could't get it to do was switch the sliders from controlling the tracks to control busses.

Hello, can someone confirm me that the Nektar SE49 will work fine with Cakewalk compatibility-wise?

I have a Nektar Panorama P6 which has a control surface that supports cubase. will this work with the mackie emulation in the new cakewalk version?

Ah that's a pity The two top runners for me at the moment are the Nektar Impact LX 49+ or M-Audio Oxygen 49 Mk IV. I can get the latter slightly cheaper (£104 inc VAT vs 115). I'm reading through a lot of Cakewalk forum threads about both and trying to decide. I already have all of the software that comes with the Oxygen but not Bitwig that comes with the Nektar (but do I need yet another DAW?!). From reading through various forums I'm unsure whether the built-in preset configurations of the Nektar are really worth having as ACT config in CbB doesn't seem too hard (I also use Cubase, Reaper and Studio One but much less than CbB). Would be interested in any opinions of anyone who owns either. I should probably start a new thread with an appropriate heading.

That is frustrating. Over the long haul Nektar does an excellent job of integration with Daws but issues crop up. One thing to keep in mind is Lx61 uses 2 midi streams to talk with Cakewalk. One is the usual music stuff and the other is transport and mixing control. Worst case, reset Lx61 to factory preset and reinstall the Nektar Cakewalk package. Good luck.

Yes, some of them can be terrible with velocity, the worst one I ever played was an Alesis V61. It was unplayable with random velocities all over the place. If your starting out though, I would recommend the Nektar LX 49/61 (if you want the pots/faders etc) or the Nektar GX49/61 (straight keyboard). They are well priced, you don't get aftertouch, but the keys are reliable and you have 4 different velocity settings. They also integrate completely with Cakewalk, you just download the Sonar drivers for them from the Nektar website, nothing to do, everything works EXACTLY as it should. I've got both at the moment, I liked the LX61 but too big for my setup so I got the GX61 but was surprised that the keybed was completely different to my original LX model, more piano like than synth like. Still ok, just a difference I wasn't expecting. If I were upgrading, I would probably get a slightly more synth like action (semi weighted?) with aftertouch, but still simple keyboard only, not sure, the GX is growing on me. I don't think there are many to choose from, maybe the Studio Logic 61? Unless your planning to both learn and play piano style with heavier keys then I would avoid 88 keys. I tried the Behringers (springy, tiring keys), the Korg microkeys (tiny, spongy keys) The Alesis V series (the worst keyboard I have ever played, unplayable random velocities). Also the M-audio Axiom (horrid sticky keys) and Oxygen and Novation impulse. These last 3 were difficult to set up, lots of stuffing about and depending on which DAW you are using as to how well they perform. I don't think aftertouch is essential, especially if you are starting out however, the keybeds of keyboards that have aftertouch are generally better feeling than those without. My experience has taught me that the Nektar Impact GX/LX series rules when it comes to budget midi controllers. The M-audio keystations are good as well though. An M-Audio Keystation 49 is a fantastic start out keyboard, plug it in use it, unplug it and put it away.

Hi, I'm searching for a low cost midi keyboard with controls like faders, knobs, pads and transport controls which will work flawlessly with CbB. I have been trying to find something on the used marked, but the ones I have found until know doesn't seem to work very well with CbB. For example I found the Nektar Impact LX25+ which has all I need, but then I find a forum thread which makes me think that this is not the one: Problem integrating Nektar Lx25+ with cakewalk - Cakewalk by BandLab - Cakewalk Discuss | The Official Cakewalk by BandLab Forum I have an old Technics px201 digital piano, that I want to use in the setup, so I don't need a full size midi keyboard. Which midi keyboard with all the controls can I expect to work without too much of a hassle? Thanks in advance. /Stig

I saw on another thread that you are also considering a Roland RD-88 and other higher end keyboards for your midi controller. The Nektar LX+ series is definitely not in the same league as something like that as far as the keyboard is concerned. Even though Nektar say that the 88 key version is semi-weighted, the whole thing weighs only 18#, compared to the RD-88's 30#. There's just no way to get even a half-decent piano action in something that weighs much under 30#, so if that is a priority, the LX+ is probably not what you're looking for. Also, the layer/split capability of the LX+88 is simpler than the RD-88. They are different in so many ways, they can't really be compared. The DAW integration of the LX+, on the other hand, is good, while the RD-88 has none that I can see. 😏

It doesn't surprise me that you're surprised. FL Studio hasn't been a toy since over a decade ago. It's development speed is somewhat of a marvel, too. It grew up VERY fast. It's also, practically, industry standard in the Trap and Hip Hop production markets. Not supporting FL Studio pretty much shuts you out of those markets, for the most part... It is a very large market that you are de facto ceding to Nektar, Akai, Arturia, and other competitors. Not supporting Cakewalk is ignorable because the markets where it was strongest have been completely run over by Studio One and REAPER, among others. The market share isn't there to justify investing in and maintaining support. Cakewalk can force itself back into that conversation by increasing its market share. Perpetuating divisive stances on DAW choice doesn't help, as it forwards this culture of "Must Choose One." That will not work in Cakewalk's favor, at this particular juncture. I notice Nektar doesn't cite SONAR/Cakewalk support with the latter product lines, either. That's a shame. In any case, most controllers do have HUI support (that likely doesn't apply to Native Instruments, though I may be wrong). I do, however, find it surprising that you call FL Studio a "Toy Sequencer" and refer to Cakewalk as an "Increrdible One." The fact that FL Studio is such an amazing Pattern-Based Sequencer and Beat Making Solution - with an incredible Piano Roll - while Cakewalk's Sequencers, etc. feel half-developed is probably why it has been able to be so successful and take over those markets. FL Studio is used for everything from Trap and Hip Hop to Orchestral and Film Scoring. The only DAWs even approaching FL Studio in its "concentration" (primary market) areas are Beat Making DAWs like Native Instruments Machine and AKAI MPC 2, and FL Studio usually wins out over them because of Lifetime Free Updates and better plugins/instruments. Cakewalk doesn't even Register in that conversation. It's great at mixing, and that's why it's worth having both it and FL Studio if you don't mind learning how to use two DAWs. Produce or Sequence in FL, Arrange and/or Mix in Cakewalk. FL can be hosted in other DAWs, so instead of poo pooing them, advocate their use so people don't drop Cakewalk wholesale when they realize the deficiencies in its tooling vs. those other DAWs (which, in some cases, specialize in those areas). This is why VST, ReWire, etc. exists. So we don't have to fight petty DAW wars. We can create allies, instead. Lastly, most people only care about what a DAW can do for them today, not what it couldn't do for them 15 years ago.

Hi All, I'm using Auto Track Zoom in a project that has multiple tracks in multiple folders. When I use my MIDI Controller's Next Track or Previous Track function, Cakewalk won't Auto Zoom to the track if it's in a Closed Folder. I would like it to Open a Closed Folder and Auto Zoom the nested track. And if could Close the Folder when I move from the last nested track to the first nested track of the next Closed Folder and Open that one3, that'd be perfect for my workflow. Mind you, Cakewalk does indeed move to the appropriate track using the Next and Previous Track functions on my Controller. But it doesn't Auto Zoom the track. The Folder holding the track remains Closed. Does Auto Zoom work with your controller? Is it possible it's only a problem with my Controller? Nektar Impact LX88+. Thanks for any insight! Tom

I have a 2021 Macbook Pro and use a OWC Thunderbolt Hub. Have a couple USB 2.0 devices plugged, Samsung Memory Stick/Waves License, iLok, Nektar 88+ Keyboard Controller, and in the Thunderbolt ports have 2, 2TB SSD External Storage devices for all my orchestral samples and Time Machine Backups. The hub charges the laptop and provides all connectivity except Video, but my Macbook has an HDMI port so it doesn't matter. I use this one from OWC, they aren’t cheap but add much convenience and zero issues. https://eshop.macsales.com/item/OWC/TB4DOCK/?gclid=EAIaIQobChMIuZ-Qwqmo9gIVBylMCh2wwwF_EAAYASAAEgIbXfD_BwE

There are a lot of variables in "best". My first MIDI keyboard/controller was a Nektar Panorama P6 (61 keys). I was very happy with the feel of the keys, but never got their proprietary interface software to work properly (there were demonstrable bugs in the sysex file they provided (I provided steps to reproduce and even the line numbers of the faulty section of code in the sysex file). They refused to even recognize that there were errors ("works fine in our testing"). Then the color display started failing, so I sent the P6 to the local landfill and bought an NI S61 Mk2, which I am very happy with. Love the feel of the semi-weighted keys. I use it with Kontakt, UVI Workstation (the excellent VI Labs pianos), Spitfire LABS and many other VIs with no problems. I would like to eventually add an NI S88 to my home studio (no 92 key controllers to support the full keybed of the 92 key Börsendorfer), but would like to have a fully weighted hammer action controller for piano playing. NI's S88 is as good or better than anything else in its price range, but the question comes down the what you want for a control surface. The S series controllers have NO faders, but do have a fairly complete set of DAW control buttons and some control knobs. If I ever need a control surface, I'll buy a PreSonus FaderPort; I don't need or want that on my MIDI keyboard. But that's just me. My $0.02.

David, Thanks for the listen. The high strings are a patch called 18V Sus LITE in Hollywood Strings Opus Edition, the default setting is a Legato but there are numerous articulations available in the patch. Also using a Bass and Bass Pizz patch, Harp and Alto Flute from East West. Some patches from Project Sam Symphobia, Strings with Low Brass and Horns with Trombone. Organ is just the stock NI Kontakt patch. All going through various EW Spaces Verbs. That's it, nothing too elaborate. All parts were playing live using a Nektar 88 Keyboard MIDI Controller. In the past I have either played in parts or entered them in the piano roll by mouse and later added in the Expression, Modulation, etc.. That doesn't really work for me as I need to hear what the Expression and Mod are doing in real-time as the parts are going in. This is the part I was missing in the past. In this project the notes and Expression/Modulation were recorded together in realtime. I later went back and tweaked some of the automation but it was pretty close the first time through. Have been watching some Ryan Thomas Tutorials on the East West YouTube channel that are very informative. Regards

Hi all - I'm using EastWest Hollywood Orchestra Opus edition in CbB to write some pieces. I've set up articulation maps as follows: Each instrument has its own Opus instance. Within each instance are several articulations, each assigned to a separate MIDI channel. As an example, 1st Violin has a legato patch on channel 1, a staccato patch on channel 2, and a pizzicato patch on channel 3. The articulation maps have a group with 3 entries (legato, staccato and pizzicato). Each entry has 2 MIDI transform definitions, one for notes and one for CC data. So when a note is assigned to a legato articulation, regardless of the note's channel (usually ch 1), it is sent to the Opus patch for legato via channel 1; the same thing happens for the other 2 articulations - the notes are sent to the appropriate patch. However, the CC data appears to be unaffected, in that I can control CC1 and CC11 for the first articulation/patch, but not for the other 2. I'm using a Nektar LX88+ as my MIDI controller, with the mod wheel controlling CC1 and the master fader controlling CC11. Any thoughts? TIA...