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?

Anyone using M-Audio Oxygen Pro Mini 32? ive read only works with Pro Tools and Studio > Honestly its given me head ache. Not to fused about the keys, more so needed for work flow for pitch/Mod Wheel then to fine tune after with automation, simple pads and buttons. Something maybe with presets and doesn't break easy, Nektar Impact do list cakewalk Also looking at The Novation Mini MK III Akai Mini MK3 Nektar Impact LX MINI Native In KK A25 MiniLab 3

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

Stephen, for what it is worth, the Nektar P4 is not designed to fully integrate with Cakewalk, but the Nektar LX+ series is. I have the Nektar LX49+, it works completely as advertised and I am happy with it. The trade-off is that the LX+ series is not as technically advanced in some ways as the P series, which is more focused on plugin and instrument control. So neither is perfect and each person has to decide what is more important to them.

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.

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.

- I don't currently have an Audio Interface (I don't own any real instruments or xlr microphones yet, will do soon tho) - I'm on Windows 10 (build 1709) - Midi controller is connect to my PC with an USB-B to USB-A cable (for power and use) - Keyboard is Nektar Imapct GXP49 - Using latest Nektar drivers (I just bought the keyboard, I used it maybe less than 5 hours) - Using Cakewalk version 2021.12 (Build 102, 64 bit) - Issue appeared using Xfer Serum I thought it was something simple to fix just by changing some parameters.

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/

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

I’ve also got a Nektar Impact LX88+ and it works pretty well with Cakewalk. However, the SE series you are mentioning is Nektar’s entry level keyboard and doesn‘t have as many DAW controls as the LX series, so if I were you I’d consider going for the slightly more expensive LX49+.

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?

If you have a controller/synth with Expression input port then I can recommend this NX-P pedal from Nektar: https://nektartech.com/np-1_np-2_nx-p/ I just got one, its throw length is on a short side a bit but the MIDI response is very smooth. And it's priced brilliantly cheap. I bought Nektar Impakt GXP series MIDI keyboard, was aiming at a cheaper Nektar keyboard but got this instead for the extra Expression jack and MIDI DIN ports.

I don't have that unit, but there is some possible good news in the upcoming release of Cakewalk 2022.06, currently available as an Early Access download. This new feature worked very well for me with a different brand of controller that is Cubase compatible, but never worked very well with Cakewalk before. With the controller set to Cubase DAW Mode, and with Cubase Mode selected in the revised Cakewalk Control Surface definition it's 99% compatible for me now. Mackie control surface improvements The Mackie Control surface includes several new enhancements. New compatibility modes In addition to the recommended Cakewalk/SONAR mode, the Mackie Control surface now supports two extra emulation modes that can be used if your control surface does not provide a dedicated Cakewalk/SONAR mode: Mackie Control Universal (Universal Mode). Emulates Mackie’s default button layout. Mackie Control Universal (Cubase Mode). Emulates Mackie’s Cubase/Nuendo button layout. The NEKTAR is Mackie Control Universal (MCU) compatible, and NEKTAR DAW integration supports Cubase. So this might work! Give it a try! There are a few bugs in the Early Access that have already been reported, and fixes are being pushed into the final release, so you may want to wait until then.

Hey folks, I searched the forum but didn't find anything on this, so hope it's not a repeat thread. Anyone have experience using a Nektar Pacer floorboard to control CakeWalk, DAW and/or instruments? Looks like it could be pretty darn helpful. Later,

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

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

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

Thanks for your answer! It didn't really solve my problem, but I still appreciate the attempt to help. I have done a little more testing, and have narrowed it down quite a bit. I checked the sample rate as suggested. The setting in CbB and ASIO panel were both 24bit/48kHz while the setting in Windows was 16/48. I wasn't even aware that there was such a setting in Windows - I have never adjusted it before. Now it's 24/48 everywhere. As for the Nektar software, I haven't uninstalled it (yet). However I did delete the control surface that was set up for using the DAW controls of the LX88+. Now I can load projects and everything works like a charm. Well, everything except the DAW controls, that is. Whenever I try to enable DAW integration by inserting a new control surface entry, we're back to the same problem again - everything looks fine and dandy until a project is opened, and then the application dies. I did mention the audio interface disappearing from the list of available devices, and I now know why that happens. The application isn't really terminating - it's still alive in the background, but draws nothing to the screen. The interesting thing is that it can't be killed from Task Manager. It only says "you need admin privileges to do this". But if I try again with admin privs, it says "access denied" and still refuses to die. Anyway, this "ghost process" is obviously still holding on to the audio interface, which explains why it is unavailable when I start a new CbB process. It dies after a few minutes, but it looks like the audio interface is somehow never released, because it stays unavailable even after the old process is gone. So the problem definitely has something to do with the Nektar software, but that doesn't make it OK for the CbB process to just stop responding and slowly die in a corner. I will try to contact customer support at Nektar to see if they have any tricks up their sleeve. In the mean time, any other suggestions would be appreciated!

At this point I would un install all the software that came with the Nektar and see if the problem goes away. Also make sure the sample rate is set correctly in all locations. Windows, Cakewalk and the ASIO panel for the interface.

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?