Mute and solos would be tied to the mixer. Sounds unfortunate, but you may not miss it. As a Panorama user I still tend to use the mouse most of the time. Yes I know that statement. So no change since then. And is it true that mute/solo/volume can not be set on the active track? Anyway I'm also a P...

@selig I don't want to be off-topic here so I've just posted a question to the SL MKIII topic continuing this discussion. Thanks for your help.

So as far as I see this controller has no mapping for the Mixer view. Is it right?
If so does it mean that it's not possible to mute/solo and change volume even of the selected track from the controller?

After much research on the Keylabs, I ended up going the Novation SL mkIII route instead. It gave me decent Reason integration, a killer sequencer, two voices of CV/Gate for Eurorack, a useful arp and scales function, lots of nice lights including across the keyboard (handy for the sequencer), and ...

I'm also interested in it. Is there any progress with Reason integration of KeyLab MKII controllers?

iramrezso wrote: ↑

04 Oct 2018

I can't setup Panorama even if I uncheck its MIDI4 and MIDI2 ports in Easy MIDI list. Setting up Panorama manually and selecting MIDI port 4 the OK button is disabled.

Ignore it. I must set keyboard input to not selected. However I still get Unkown Error when opening Preferences tab.

I can't setup Panorama even if I uncheck its MIDI4 and MIDI2 ports in Easy MIDI list. Setting up Panorama manually and selecting MIDI port 4 the OK button is disabled.

After starting Reason 10.2, it says that Panorama midi port number has been changed. I deleted and added it back by selecting midi port 4 (instead of 2 that was used before). From that point the Preferences window in Reason crashes with unknown error and cannot be opened again. Is there a solution f...

Ignore it. I've re-installed the driver, and now it works. I can't understand the difference between the Panorama.remote and PanoramaP1.remote files on Dropbox. As far as I see he P1 file is for the P1 controller. But does it contain more mapping than the standard one? Depends what you are calling ...

Ignore it. I've re-installed the driver, and now it works.

I can't understand the difference between the Panorama.remote and PanoramaP1.remote files on Dropbox. As far as I see he P1 file is for the P1 controller. But does it contain more mapping than the standard one?

I downloaded that remote map file and copied it to the proper place. I have a P4. However Reason can't load the mapping as it breaks because of tons of unsopported mapping items. I've installed lates drivers from Nektar tech site (2017). Could somebody help me? What is one of the errors? check one ...

Dropbox updated.. https://www.dropbox.com/sh/sberq7vvyfitnzh/AACE-2ovSLhN2_5Cw0lhT4sra?dl=0 [...] I downloaded that remote map file and copied it to the proper place. I have a P4. However Reason can't load the mapping as it breaks because of tons of unsopported mapping items. I've installed lates d...

Thanks for the 1.7.0 update!

TChandler wrote: ↑

08 Nov 2017

There's an update in the next few days that will fix the problem with older device mapping. Sorry for braking that it's due to a typo in the Lua code.

When do we get that update?

As Carly states Europa and Grain mapping is slimmed out 'by design'. We cover the most important params in the maps avoiding the need for menu diving. The GRAB feature allows access to any parameter on Europa or Grain, with the additional advantage that you can 'mix up' parameters on the same page....

TChandler wrote: ↑

08 Nov 2017

There's an update in the next few days that will fix the problem with older device mapping. Sorry for braking that it's due to a typo in the Lua code.

Sounds great! Looking forward to get it. Thanks.
(The Europa and Grain don't have menu for sub-pages in the factory mapping, is it by design?)

The current documentation still mentions the [Osc2>] button to switch to second oscillator. However no such button present even when the Oscillaltors menu is selected. I have just looked at the code and it should be there but for some reason the buttons are not being displayed. Looking into this. T...

The current documentation still mentions the [Osc2>] button to switch to second oscillator. However no such button present even when the Oscillaltors menu is selected.

Regarding the new devices (Europa and Grain) the mapping seem to be very basic and incomplete. There's no menu for different control pages and thus most of the controls are not available on the controller. Does anybody experience the same? This is because it relies on the new grab feature. We do ha...

I've updated the Nektar driver and I'm using Reason 10. The old reason instrument mappings seem to be broken. Changing to Oscillators I can't switch between ocsillators (only the 1st can be edited) the buttons remain the same as by the Main page (e.g. Btn 1, Btn 2 etc. by Thor). Same with LFOs, and ...

dagwood wrote: Can't I just add the Players text from your post and add it to my old Remote file?

You should.

They're crazy

Yeah, but i see this as a workflow barrier and am going to suggest a change in remote. Just wanted to make sure i got it right before laying it out. I think Reason would profit from being able to play instruments while controlling a Player or connected FX in a quick one button action. I've recently...

Scales&Chords doesn't seem to support sus4 and sus2 chords.

Carly(Poohbear) wrote:

iramrezso wrote:

Replace the players with our mappings.. If you need instructions just shout out..

Thanks, I may give it a try.