• Make sure you have at least Studio One 6-7 or Fender Studio Pro installed. The integration does not work with Studio One versions below 6.
• Make sure you completed both the installation of ControlCore as well as the Fender Studio Pro.install file. Both need to be installed and updated to the same version for the system to work. Drop the .install file directly on an open Fender Studio Pro window and the process  will start.
• Try different USB cables. You may have been using your USB cable for a long time and it works with everything else, however try different cables anyway. It’s rare but not uncommon that the most stubbon situations are finally resolved by changing a cable.
• Try different USB ports. If you have a USB hub, try both connecting to it and connecting directly to ports on your computer.

Map files created in Nektarine can generally be read by ControlCore and will therefore work in Fender Studio Pro. However there are situations where it doesn’t work as intended so here are some of the key issues to be aware of.

• Make sure the plugin format you map in Nektarine is the same as your DAW. Some plugins are named the same regardless of format however many are not so AU plugins will be named differently from VST3 plugins etc. It’s a good idea to stick to one format where possible and disable VST and AU plugins formats in Nektarine’s Settings menu so only the prefered format plugins can be selected.
• Start by saving a map file from Fender Studio Pro first, then open the plug-in in Nektarine. Nektarine is capable of mapping plugins with thousands of parameters and Fender Studio Pro is currently limited to about 1000. By saving the map file first in Fender Studio Pro, Nektarine is aware of the diffrence and ensures the final map file can be read by both. You can find more information about creating and saving map files in the Nektarine manual. https://support.nektartech.com/nektarine/control/
• If the mapping you created in Nektarine is not loaded when you load the plug-in in Fender Studio Pro, first check there is a map file for the plug-in in …/Documents/Nektar/Nektarine/Mapping Files/Inserts. If you don’t see the .npm map file there, try saving the map from Nektarine again. If the map file still doesn’t appear, there may be a folder permissions issue preventing Nektarine from writing files to that directory. In that case, move the ‘Nektar’ folder out of …/Documents (to your desktop or somewhere you can find it later). When you restart Nektarine, the folder is created again with factory default settings which may resolve the issue.

The symptoms can also be described as “CS12 does not work with Reaper”. It looks pretty bad but it’s usually because the “ControlCore would like to receive keystrokes from any application” message did not appear in step 6. of the setup instructions, or another application is blocking key strokes to ControlCore.

To fix this,  go to //Applications/Nektar/ControlCore. You should see an app called ‘ControlCore Panel’. If you see that double-click on it (if not, run the latest ControlCore installer again). If the ControlCore panel says ‘Start ControlCore’, click the button. If it says ‘Stop ControlCore’, then close that app. You will need to activate the Input Monitoring options for ControlCore and Cubase. Please follow these steps:

1. Click on the Apple logo in the upper-left corner of your screen.
2. Select ‘System Settings’
3. In the window that appears, go to ‘Privacy and Security’
4. Find the ‘Input Monitoring’ category and click on it.
5. Activate the options for ‘ControlCore’, ‘Nektarine’ and ‘Cubase’.
6. It will ask for your password and recommend restarting those applications, if they are running.

If you do not see those applications listed, you can click the ‘+’ button at the bottom of the window to add them. When you click the ‘+’ button it will bring up a finder window. You will find ‘ControlCore’ in the following location:

//Library/Application Support/Nektar/ControlCore

You will find Nektarine in the following location:

//Applications/Nektar/Nektarine

You will find Reaper in //Applications

If you needed to add these, then we recommend restarting your computer after doing so. When the computer has finished starting up, you should see the ControlCore link symbol on the CS12’s display is green. If you see that, the Reaper welcome screen should appear on the CS12’s display when you open a Reaper project.

INPUT MONITORING IS ENABLED BUT CS12 IS STIL NOT RESPONDING

Applications that intercept key stroke messages, such as Karabiner Elements, by default will intercept any messages intended for Panorama CS12.

1. In Karabinger Elements go to the ‘Devices’ page and locate Panorama CS12 in the list. 
2. Turn off the ‘Modify Events’ option for CS12.
3. Launch Reaper following to verify it’s now working. If not, restart your system and check again. 

If you are using a different application designed to intercept key stroke events look for  similar options to enable or disable interception to specific devices. 

• Make sure you have Reaper 7 installed. The integration does not work with lower versions.
• If you installed ControlCore before Reaper, contact us at support@nektartech.com. Reaper will not be able to find the ControlCore files needed and reinstalling does not solve the problem.
• Try different USB cables. You may have been using your USB cable for a long time and it works with everything else, however try different cables anyway. It’s rare but not uncommon that the most stubbon situations are finally resolved by changing a cable.
• Try different USB ports. If you have a USB hub, try both connecting to it and connecting directly to ports on your computer. 
• If ControlCore was installed before you installed Reaper, it can cause Reaper to operate as a portable installation. In that case you will need to remove Reaper’s folder structure and install it again. Please follow these steps: 

MacOS: 

1. Close any applications you have open
2. Open the Applications folder in a finder window
3. Open the ‘View’ menu at the top of your screen.
4. Select ‘Sort by’, then select ‘Date Added’
5. Now, delete the files and folders which were created in Applications after you ran Reaper for the first time.
6. Open the ‘Go’ menu at the top of the screen
7. With the Go menu open, hold the Alt/Option key on your keyboard
8. Select ‘Library’ from the Go menu
9. In the finder window, open the ‘Application Support’ folder
10. Find the ‘REAPER’ folder and delete it.
11. Empty the trash.
12. Start Reaper
13. Quit Reaper
14. Run ControlCore installer
15. Start Reaper again.

Windows: 

1. Open a File Explorer window.
2. Navigate to C:\Program Files
3. Find the ‘REAPER (x64)’ folder in that directory and delete it. 
4. Navigate to ‘C:\Users\<your user name>\AppData\Roaming‘ (note this is normally a hidden directory, follow the instructions on this page to unhide: Show hidden files).
5. Find the ‘REAPER’ folder in that directory and delete it.
6. Install Reaper again
7. Start Reaper
8. Quit Reaper
9. Run the ControlCore installer
10. Start Reaper again

Map files created in Nektarine can generally be read by ControlCore and will therefore work in Reaper. However there are situations where it doesn’t work as intended so here are some of the key issues to be aware of.

• Make sure the plugin format you map in Nektarine is the same as your DAW. Some plugins are named the same regardless of format however many are not so AU plugins will be named differently from VST3 plugins etc. It’s a good idea to stick to one format where possible and disable VST and AU plugins formats in Nektarine’s Settings menu so only the prefered format plugins can be selected. 
• Start by saving a map file from Reaper first, then open the plug-in in Nektarine. Nektarine is capable of mapping plugins with thousands of parameters and Reaper is currently limited to about 1000. By saving the map file first in Reaper, Nektarine is aware of the diffrence and ensures the final map file can be read by both. You can find more information about creating and saving map files in the Nektarine manual. https://support.nektartech.com/nektarine/control/
• If the mapping you created in Nektarine is not loaded when you load the plug-in in Reaper, first check there is a map file for the plug-in in …/Documents/Nektar/Nektarine/Mapping Files/Inserts. If you don’t see the .npm map file there, try saving the map from Nektarine again. If the map file still doesn’t appear, there may be a folder permissions issue preventing Nektarine from writing files to that directory. In that case, move the ‘Nektar’ folder out of …/Documents (to your desktop or somewhere you can find it later). When you restart Nektarine, the folder is created again with factory default settings which may resolve the issue.

1. Locate “Panorama_Mainstage_Support” installer in the zip file you downloaded from your Nektar account page, then run it.
2. If the installer displays a “can’t be opened because it’s from an unidentified developer” dialog, right-click on the Installer and select ‘Open’. You will see the same warning but you will be given the option to continue anyway.
3. With installation complete, make sure your Panorama controller is connected to your computer and switched on.
4. Launch MainStage.
5. When you open a concert, Instrument Mode will be activated automatically and the name of the first patch in the concert will appear on Panorama’s display.

For an example of how Panorama should be configured in Mainstage try creating a concert based on the Keyboard Quickstart template. Panorama’s encoders will automatically map to Smart Controls in that concert and you can look at the settings for those controls to get a better idea of how things should be mapped in your custom concert.

When using Panorama in Mixer, Instrument modes, with Mainstage, you will need to send and receive data via the ‘Instrument PANORAMA‘ ports. In these modes control data is transmitted on MIDI Channel 1. If you hover your mouse over an assignment, you will see a downward facing arrow. Click on that arrow to see the ‘Hardware Input’ settings as shown on the right.

Here is a list of CCs for Panorama’s controls in Mixer/Instrument Modes:

2×4 group of encoders:

• 1 – CC64 (make sure that when you use this control, it’s not part of the ‘All Devices’ group or the group which sends note data to your instruments)
• 2 – CC65
• 3 – CC66
• 4 – CC67
• 5 – CC68
• 6 – CC69
• 7 – CC70
• 8 – CC71

Encoders above faders

• 1 – CC48
• 2 – CC49
• 3 – CC50
• 4 – CC51
• 5 – CC52
• 6 – CC53
• 7 – CC54
• 8 – CC55

Black faders

• 1 – CC8
• 2 – CC1
• 3 – CC2
• 4 – CC3
• 5 – CC4
• 6 – CC5
• 7 – CC6
• 8 – CC7

Buttons below faders (only use these in Mixer Mode, in instrument mode they are used for patch/set navigation, by default)

• 1 – CC16
• 2 – CC17
• 3 – CC18
• 4 – CC19
• 5 – CC20
• 6 – CC21
• 7 – CC22
• 8 – CC23

Motorized fader

• MSB – CC15 (use this for full range control)
• LSB – CC47
• Touch – CC13

Buttons next to motorized fader

• Mute – CC30
• Solo – CC31
• Fader – CC105

Transport buttons

• Loop – CC80
• Rewind – CC81
• Forward – CC82
• Stop – CC83
• Play – CC84
• Record – CC85
• |<< – CC86
• >>| – CC87
• Undo – CC88
• Click – CC89
• Mode – CC90

Display buttons

• 1 – CC106
• 2 – CC107
• 3 – CC108
• 4 – CC109
• 5 – Do not use

Nav Buttons

• Shift – CC96
• Track- – CC91
• Track+ – CC92
• Patch- – CC93
• Patch+ – CC94
• View – CC95

When making control assignments for the encoders make sure that the ‘Type’ is set to ‘Relative (2’s complement)’.

When setting up feedback for a control, make sure the MIDI Thru is set to ‘Do not pass through’ and ‘Send Value to’ is set to ‘Instrument PANORAMA’.

See the ‘Encoder Configuration’ image for an example of a encoder assignment with feedback and the ‘Fader Configuration’ image for a fader assignment with feedback.

If you find that fader 2 acts as a Modulation Wheel or the first encoder in the 2×4 encoder group acts as a Sustain Pedal, it’s because those controls are set to receive data from all ports, rather than from a specific port. The images on the right show how to setup Modulation and Sustain functions.

If Panorama does not switch to Instrument Mode when you open a concert, first check that Panorama’s MIDI ports appear correctly in Audio MIDI Setup, as described here: Troubleshooting Panorama in OSX in MacOS 10.11 and later

If you recently updated to macOS 10.13 (High Sierra), you may have encountered the problem described on this page: Small warning when updating to macOS 10.13 High Sierra

Take a look in this directory: ~/Music

1. Open a Finder window
2. Open the ‘Go’ menu from the top of your screen
3. Select ‘Home’
4. Open the ‘Music’ folder

If the ‘Audio Music Apps’ folder appears as an alias (with a small curved arrow at the bottom-left of the folder icon), as shown in the image below, delete the alias and then run the Mainstage support installer again.

Panorama products are set up the same way in FL Studio. In our example here, we use a P6 but just substitute the model number with the Panorama model number of the unit you own and you’ll be fine.

You’ll need to have completed the driver installation and firmware update for you unit as described in the Panorama installation instructions.

• In FL Studio go to Options/MIDI Settings. See MIDI Settings images on the right.
  
• In the output section set the ‘MIDIOUT2 (Panorama P*)’ to port 160, in MacOS the port is called ‘PANORAMA P* Instrument’.
  
• In the input section, enable the ‘Panorama P*’ Input port and set it to Generic Controller, with no port number. In MacOS this port is called ‘PANORAMA P* Internal’
  
• Enable the ‘MIDIIN2 (Panorama P*)’ Input port and select “Nektar Panorama P4” from the Controller Type drop down list. Set this input to Port 160. In MacOS this port is called ‘PANORAMA P* Instrument’.
  

Panorama should now be connected to FL Studio and the controllers display will appear as shown in the ‘Mixer’ image on the right.

With Panorama and FL Studio now up and running, let’s take a look at the functionality. It works quite different from our integration for other DAWs but it’s pretty powerful. The ‘Control Surface Functions’ image on the right provides a brief overview of what each control does. You will notice that all 16 encoders and 9 faders are freely assignable to your liking but the main navigational buttons are configured so you don’t have to worry about it. Let’s take a look at what each button does:

First press the [Track -] and [Track +] buttons. This will bring up the mixer in FL Studio and for each press, either move forward or backwards one mixer insert/send depending on which button you press. 

The info-bar updates showing Mixer insert name/Song Position Meter/Blank (see the ‘Mixer Control’ image).

Next press the [Patch-] and [Patch+] buttons. This time you are navigating the FL Studio channels with associated instruments and you will notice that the mixer follows the selection also. 

You can also press [Shift]+[Track+] (Bank>) to jump 8 mixer insert/send forward from your current position or [Shift]+[Track-] (<Bank) to go 8 channels backwards. Note: This does not change the assignments of the 8 faders. 

If your Panorama has a motorized fader, now try moving it. This will change the mixer volume for the current mixer insert/send. When you select a new mixer insert/send (using either the mouse or the navigation buttons on Panorama) the motorized fader will move the fader volume position to correspond with that insert/send. The solo and mute buttons associated with the motorized fader will similarly update with mixer insert/send selection. The Fader button allows you to record arm the selected track.

The 5 buttons below the display are currently labeled Pan/Stereo/EQ1/EQ2/EQ3 (again, see the ‘Mixer Control’ image).

By default, Pan is selected so you can now control pan for the selected Mixer insert/send using Panorama’s Data Control. Parameter feedback is displayed in the top info-line. 

Pressing any of the other display buttons will change the assignment of the Data Control encoder to control Stereo (separation), EQ1 Gain, EQ2 Gain, EQ3 Gain.