There may be times when you are working with another DAW, or perhaps controlling a rack full of external devices, that you will find it advantageous to remain on the Fader menu page. It allows you to switch from one MIDI channel to the next and set the relative levels, pan positions and effect send levels very easily.

To enter the Fader menu, press the Fader button (next to the Auto-fader). Doing so will bring up the following display: (Image 1).

In Internal mode this menu behaves like a General MIDI channel strip. Here’s what’s possible using the default settings for the Auto-fader group:

• The fader will control the volume of the target device using MIDI CC# 7
• The Mute button will transmit values of MIDI CC# 12 
• The Solo button will transmit values of MIDI CC# 13
• The Data encoder will control parameters such as Pan (CC# 10), Send 1 (CC# 91) and Send 2 (CC#93). Sends 1 and 2 correspond to the Reverb and Chorus send levels, respectively.

Note: ‘Mute’ and ‘Solo’ are not part of the GM2 specifications, so you may need to reassign them according to the requirements of the software you use.

Each of the arrows on the display menu buttons has a particular function:

• M1/M2 (down/up arrows): Determine whether Pan, Send 1 or Send 2 will be controlled by the Data encoder
• M3/M4 (down/up arrows): Select the MIDI channel number on which the Auto-fader, the Mute/Solo buttons and the Data encoder transmit (Global or 1-16)
• M5: Returns to the Internal mode home page

To change the MIDI CC# assignments for these controls, as with any other, access the Control Edit page from the Internal mode Setup menu. Then move the fader or press one of the buttons to call up the page you want.

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.

1. Once you’ve downloaded the template, unzip the file and locate the ‘live_template.syx’ file for your Panorama model. This file needs to be transmitted to the Panorama and to do that you’ll need to download a sysex tool. We recommend Send SX:

• Send SX

1. Open Send SK and set the MIDI Output to ‘Panorama P*’ as shown in the ‘Send SX’ image on the right.
2. Load the.syx file associated with you Nektar controller into Send SX.
3. Click the ‘Send’ button.
4. The P-series controller’s page will now say ‘Loading Memory Bank Via Sys ex’

2. With the transfer complete it’s now time to copy the ‘Panorama’ folder you unzipped to the following location:

C:\\Users\\\\AppData\\Roaming\\Ableton\\Live \\Preferences\\User Remote Scripts

(See the ‘File Path’ Image on the right).

Note:This is a hidden directory. To access this directory you will need to configure Windows to ‘Show Hidden Files and Folders’ and deactivate ‘Hide Protected Operating System files’. Please follow the instructions on this page: Show hidden files.

3. Launch Ableton Live and open the mapping template file you unzipped ‘mapping_template_1.2.als’. In order for this mapping to be recalled each time you restart Live, you must save the Live set as your default. To do this, go to the ‘File’ menu and select ‘Save Live Set as default set…’. See the ‘Default Set’ image on the right.

4. With the preferences window still open select the MIDI Tab. Select ‘Panorama’ from the list of Control Surfaces and set the Input port to Panorama. See the ‘Link/Tempo/MIDI’ image on the right.

1. Once you’ve downloaded the template, unzip the file and locate the ‘live_template.syx’ file for your Panorama model. This file needs to be transmitted to the Panorama and to do that you’ll need to download a sysex tool. We recommend Sysex Librarian:

• Sysex Librarian

Next, open your Sysex tool of choice and transmit the data to the Panorama. Below is how its done using Sysex Librarian.

• Drag the file ‘live_template.syx’ into the window as shown in the ‘Sysex Librarian’ image on the right.
• Choose ‘Internal’ as the destination (in older versions of OSX, you may see a port called ‘Panorama’, instead)
• Click play

2. With the transfer complete it’s now time to copy the ‘Panorama’ folder you unzipped to the following location:

 ~/Library/Preferences/Ableton/Live**/User Remote Scripts

(See the ‘File Path’ image on the right.

Note:This is a hidden directory, to access this directory do the following:

• Open a Finder window
• Open the ‘Go’ menu at the top of the screen
• With the Go menu open, hold the Alt/Option key on your keyboard
• Select ‘Library’ from the Go menu
• In the Finder window, open the ‘Preferences’ folder
• Open the ‘Ableton’ folder
• Open the folder for the most recent version of Live

Open the ‘User Remote Scripts’ folder and copy the ‘Panorama’ folder into this directory.

3. Launch Ableton Live and open the mapping template file you unzipped ‘mapping_template_1.2.als’. In order for this mapping to be recalled each time you restart Live, you must save the Live set as your default. To do this, go to the ‘File’ menu and select ‘Save Live Set as default set…’. See the ‘Default Set’ image on the right.

4. With the preferences window still open select the MIDI Tab. Select ‘Panorama’ from the list of Control Surfaces and set the Input port to Panorama. See the ‘Link/Tempo/MIDI’ image on the right.

If you are encountering problems with your Panorama setup after completing the installation process, the next step depend on whether you:

– are installing Panorama in OS X 10.11 (El Capitan) or higher for the first time.

– have updated your OS X from OS X 10.10.5 (Yosemite) or below to OS X 10.11 or higher.

– are installing Panorama in OS X 10.10.5 (Yosemite) or below for the first time.

If your Panorama is not being recognized by Reason or other DAW applications, Audio MIDI Setup (AMS) can help you identify the problem.

To access Audio MIDI Setup follow these steps:

1. Open a Finder window. (Image 1)
2. Click on the ‘Go’ menu at the top of the screen and select ‘Utilities’. (Image 2)
3. Double-click on the Audio MIDI Setup icon. (Image 3)
4. Go to the ‘Window’ menu at the top of your screen and select ‘Show MIDI window’. If it says ‘Hide MIDI window’ then you should already see the ‘MIDI Studio’ window. (Image 4)

Image 5 shows how Panorama should appear in Audio MIDI Setup (AMS).

If your Panorama has never been detected by AMS, it will look like Image 6.

You may need to click the ‘Rescan MIDI’ button or restart your computer so that AMS can detect your Panorama.

If you see Panorama in AMS as in Image 7, it means that it’s detected without the Nektar driver.

Have you installed the latest driver? If so, try restarting your computer.

If Panorama appears greyed out like in Image 8 , it means that the driver is installed but AMS does not detect Panorama.

Try clicking the ‘Rescan MIDI’ button or power-cycling your Panorama. Are you sure the USB cable is connected to your computer?

Finally, if you see Panorama in AMS with a question mark (Image 9), you may have a driver installation issue.

First try restarting your computer. If Panorama still doesn’t get detected correctly, run the Uninstaller that was included in the .dmg file you downloaded, restart your computer, then Installer the drivers again. Make sure your Panorama is not connected when running the Installer.

If you continue to have trouble setting up your Panorama in Reason or any other applications, please contact tech support.

In some cases Windows may not associate Panorama with its driver correctly. Panorama may be recognized by your computer as a Class Compliant USB MIDI device but your DAW won’t be able to Auto-Detect it.

1. Open the search bar and type ‘Device Manager’ (Image 1).
2. Select device manager from the top of the search results.
3. With Device manager open click on the ‘>’ icon next to Sound, video and game controllers.
4. Now right click on Nektar Panorama P1/P4/P6 and select ‘Update Driver Software…’ (Image 2).
5. Choose ‘Browse my computer for driver software’ (Image 3).
6. Click ‘Let me pick from a list of device drivers on my computer’ (Image 4).
7. Select ‘Nektar Technology USB MIDI’, ‘Nektar Panorama P1’ or ‘Nektar Panorama P6’ then click ‘Next’ (image 5) .
   Note: If you see more than version listed on this page, choose the most recent one.

Thats it. Panorama should now be detected by your DAW. If you’re still having trouble please check the links below or contact one of our support staff.

Windows 10 MIDI port issue

We have seen an issue with some Windows 10 20H2 installations, especially on computers with Intel Tiger Lake processors. The problem seems to affect a lot of class compliant USB MIDI and Audio devices.

We have had some reports that simply running the automatic update utility in Windows will fix the problem but that doesn’t seem to work for everyone.

You can check the Device Manager for a device called ‘Intel Smart Sound For USB Audio’ and disable it:

1. Right-click on the Windows button in the lower-left corner of your screen.
2. Select ‘Device Manager’.
3. Expand the ‘Sound, Video and Game controllers’ category.
4. If you see a device called ‘Intel Smart Sound For USB Audio’, right click on it and select ‘Disable’.

Once you have done that, restart your computer with the controller connected. Applications should be able to see the controller’s ports at that point.

1. Open the Start Menu and right-click on ‘Computer’.
2. Click ‘Properties’.
3. Click ‘Device Manager’.
4. Click on the ‘+’ next to Sound, Video and Game Controllers.
5. Right-Click on ‘Panorama P*’ and select ‘Update Driver Software’ (where * represents the Panorama model you are using).
6. Click ‘Browse my computer for driver software’.
7. Click ‘Let me pick from a list of device drivers on my computer’.
8. Select ‘Nektar Technology USB MIDI’. 
9. Click ‘OK’.
   Note: If you see more than version listed on this page, choose the most recent one.
10. Now open Reason and use the Auto-Detect button in the Control Surface preferences.

After a few seconds, both of Panorama’s control surfaces should be detected by Reason.

There may be times when you are working with another DAW, or perhaps controlling a rack full of external devices, that you will find it advantageous to remain on the Fader menu page. It allows you to switch from one MIDI channel to the next and set the relative levels, pan positions and effect send levels very easily.

To enter the Fader menu, press the Fader button (next to the Auto-fader). Doing so will bring up the following display: (Image 1).

In Internal mode this menu behaves like a General MIDI channel strip. Here’s what’s possible using the default settings for the Auto-fader group:

• The fader will control the volume of the target device using MIDI CC# 7
• The Mute button will transmit values of MIDI CC# 12 
• The Solo button will transmit values of MIDI CC# 13
• The Data encoder will control parameters such as Pan (CC# 10), Send 1 (CC# 91) and Send 2 (CC#93). Sends 1 and 2 correspond to the Reverb and Chorus send levels, respectively.

Note: ‘Mute’ and ‘Solo’ are not part of the GM2 specifications, so you may need to reassign them according to the requirements of the software you use.

Each of the arrows on the display menu buttons has a particular function:

• M1/M2 (down/up arrows): Determine whether Pan, Send 1 or Send 2 will be controlled by the Data encoder
• M3/M4 (down/up arrows): Select the MIDI channel number on which the Auto-fader, the Mute/Solo buttons and the Data encoder transmit (Global or 1-16)
• M5: Returns to the Internal mode home page

To change the MIDI CC# assignments for these controls, as with any other, access the Control Edit page from the Internal mode Setup menu. Then move the fader or press one of the buttons to call up the page you want.

First, to access the PB Assign page, press PB1 and PB2 at the same time. This will bring up a page that looks like Image 1.

Control Functions
The two large dots on the left side of the display show you what the current assignments are for PB1 and PB2. The one that is lit red is the one that is currently selected for editing, and the red text on the right side of the display shows you the current function for the selected button. In the picture above we can see that PB1 is selected, and its current assignment is Transpose -.

PB2 is not selected, so it is in white. But the text underneath the icon for PB2 tells you that it is currently assigned to Transpose +.

If you want to change the assigned function of one of the Performance buttons (PB), simply press it  to select it. Then choose the desired function using Menu buttons 1 or 2 (the Down/Up arrows).

Here’s a description of each of the control functions in the left column. Either button can be assigned to any of the following:

• Transpose –  Transpose the keyboard downward by one semitone
• Transpose +  Transpose the keyboard upward by one semitone
• Program –  Decrease the program number by one value
• Program +  Increase the program number by one value
• Global Ch –  Decrease the Global MIDI channel number by one value
• Global Ch +  Increase the Global MIDI channel number by one value

MIDI FX
The main thing to know about the MIDI FX is that using them involves two controls at the same time: you press and hold the selected Performance button (PB) and move another control such as the Mod wheel, a fader or an encoder. Then what the MIDI FX do is alter the order in which the MIDI data is transmitted by the control being moved.

Without the PB held down, controls transmit data in a linear fashion: from 0-127 and back down again. But with the PB held down while the control is moved, the full range of data is still available, but it will be sent in broken groups: for example, 0-12, then backward from 24-13, then forward from 25 to 37, etc., or some other arrangement of the data.

As you can see, this introduces an element of unpredictability, and it can be a lot fun when applied to filter frequency, say, or an LFO rate, or any parameter that can be controlled. So when you’re ready for something completely different, try them out! Because of their non-linear approach they may well be just the missing element that was needed to spice up a performance.

Here’s the list of MIDI FX. Some of these would be too complex to describe, so the best thing to do is give them a try! We think you’ll find them useful:

• Vortex 7
• Pyramid
• 4 Step
• Back Step 4
• Invert
• RipSaw 7
• Auto Pan
• Invert-Pan