Nektar Panorama Remote Maps Thread

[EnochLight]

Carly - is there a place where we can get the Remote files that have already been done for said VST, or are they spread out over the 18 pages of this thread?

Yes, try this location there is a sub folder called VST
https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

Cool; thanks!

@Lizard: perhaps consider updating the OP with sticky links?

[Carly(Poohbear)]

Dropbox updated.. https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

New Mapping
VST Xpand2



New Files Added
remoteVST xpand2.txt (Individual mapping)


https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

NOTE: The file Panorama.remotemap contains all the Rack Extension mappings talked about on this thread.
VST will have to be download individually.

This file has to be replace\merged and can be found at:-

Windows: C:\ProgramData\Propellerhead Software\Remote\Maps\Nektar
OSX: //Library/Application Support/Propellerhead Software/Remote/Maps/Nektar


When backing up the existing file, back it up to a totally new directory (there have been issues reported if backing up in place).

[EnochLight]

Dropbox updated.. https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

New Mapping
VST Xpand2



New Files Added
remoteVST xpand2.txt (Individual mapping)

The "patch -" and "patch +" buttons don't do anything on the Panorama. Even if I have Xpand2's browser open... they don't work.

[Carly(Poohbear)]

Dropbox updated.. https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

New Mapping
VST Xpand2



New Files Added
remoteVST xpand2.txt (Individual mapping)

The "patch -" and "patch +" buttons don't do anything on the Panorama. Even if I have Xpand2's browser open... they don't work.

It does work but not the way you want it to, the patch - and patch + change the patch on the VST interface not VST it self, this is the same for all VST's which is a real shame as it's one thing I do want to control...

[Pinkbox]

Is the ABL3 map working for you?
It doesn't work on my P1 and I don't understand where the problem is coming from.
I don't have any error, but the P1 just says "NO MAPPING".

Here is the mapping I took from the dropbox file :

Code: Select all

Scope	AudioRealism	se.audiorealism.abl3
Define Group	Mode	Instrument	Mixer	Transport	Channel	
Define Group	force_patch_Feedback	Patch 1	Patch 2
//	Control Surface Item	Key	Remotable Item	Scale	Mode

Map	Mixer Mode		Mode=Mixer
Map	Instrument Mode		Mode=Instrument
Map	Transport Mode		Mode=Transport
Map	Channel Mode		Mode=Channel
		
Map	Device Name		"ABL3"		HOME
Map	Patch Name		Patch Name			Instrument	Patch 1
Map	Patch Name		Patch Name			Instrument	Patch 2

Map	Force_patch_change		force_patch_Feedback=Patch 1			Instrument	Patch 2
Map	Force_patch_change		force_patch_Feedback=Patch 2			Instrument	Patch 1

Map	Bypass		Enabled			Instrument

Map	X1_Labeli		"Wave"			Instrument
Map	X2_Labeli		"Dist"			Instrument
Map	X3_Labeli		"HiPass"			Instrument
Map	X4_Labeli		" "			Instrument
Map	X5_Labeli		"Random"			Instrument
Map	X1		Waveform		CTRL_VALUE	Instrument
Map	X2		Distortion Type		CTRL_VALUE	Instrument
Map	X3		Hipass		CTRL_VALUE	Instrument
Map	X4		0				Instrument
Map	X5		0		RANDOMIZE	Instrument

Map	Ch Knob 1		Cutoff				Instrument		
Map	Ch Knob 2		Resonance			Instrument		
Map	Ch Knob 3		Envmod				Instrument		
Map	Ch Knob 4		Decay				Instrument		
Map	Ch Knob 5		Tuning				Instrument		
Map	Ch Knob 6		Accent				Instrument		
Map	Ch Knob 7		Pattern				Instrument		
Map	Ch Knob 8		Distorted			Instrument

Map	Fader 9		Volume			Instrument

[Carly(Poohbear)]

Is the ABL3 map working for you?
It doesn't work on my P1 and I don't understand where the problem is coming from.
I don't have any error, but the P1 just says "NO MAPPING".

Here is the mapping I took from the dropbox file :

Code: Select all

Scope	AudioRealism	se.audiorealism.abl3
Define Group	Mode	Instrument	Mixer	Transport	Channel	
Define Group	force_patch_Feedback	Patch 1	Patch 2
//	Control Surface Item	Key	Remotable Item	Scale	Mode

Map	Mixer Mode		Mode=Mixer
Map	Instrument Mode		Mode=Instrument
Map	Transport Mode		Mode=Transport
Map	Channel Mode		Mode=Channel
		
Map	Device Name		"ABL3"		HOME
Map	Patch Name		Patch Name			Instrument	Patch 1
Map	Patch Name		Patch Name			Instrument	Patch 2

Map	Force_patch_change		force_patch_Feedback=Patch 1			Instrument	Patch 2
Map	Force_patch_change		force_patch_Feedback=Patch 2			Instrument	Patch 1

Map	Bypass		Enabled			Instrument

Map	X1_Labeli		"Wave"			Instrument
Map	X2_Labeli		"Dist"			Instrument
Map	X3_Labeli		"HiPass"			Instrument
Map	X4_Labeli		" "			Instrument
Map	X5_Labeli		"Random"			Instrument
Map	X1		Waveform		CTRL_VALUE	Instrument
Map	X2		Distortion Type		CTRL_VALUE	Instrument
Map	X3		Hipass		CTRL_VALUE	Instrument
Map	X4		0				Instrument
Map	X5		0		RANDOMIZE	Instrument

Map	Ch Knob 1		Cutoff				Instrument		
Map	Ch Knob 2		Resonance			Instrument		
Map	Ch Knob 3		Envmod				Instrument		
Map	Ch Knob 4		Decay				Instrument		
Map	Ch Knob 5		Tuning				Instrument		
Map	Ch Knob 6		Accent				Instrument		
Map	Ch Knob 7		Pattern				Instrument		
Map	Ch Knob 8		Distorted			Instrument

Map	Fader 9		Volume			Instrument

What happens if you use our P1 file from the dropbox?

[Pinkbox]

"No mapping"..!

[Carly(Poohbear)]

"No mapping"..!

Sorry but I have to ask that you are using the ABL3 and not the ABL2?

(working at this end on my P4)

[Pinkbox]

"No mapping"..!

Sorry but I have to ask that you are using the ABL3 and not the ABL2?

(working at this end on my P4)

I am.

[Carly(Poohbear)]

Sorry but I have to ask that you are using the ABL3 and not the ABL2?

(working at this end on my P4)

I am.

I'm not sure what is going on there, it's not one of my mappings however it's so basic there is nothing I can see what would cause an issue.

I take it other mappings from your P1 file are OK after the point the ABL3 appears?

[Tobi Rice]

Does anyone know about the progress of the work of nektartechs Reason 9.5 compatibility ? On the website they write "We are working on an update which will add mapping for VST plugins. Work on this update is underway and it will be available soon." But this anouncement is there for a long time without update. would be great to have it.

[Carly(Poohbear)]

Does anyone know about the progress of the work of nektartechs Reason 9.5 compatibility ? On the website they write "We are working on an update which will add mapping for VST plugins. Work on this update is underway and it will be available soon." But this anouncement is there for a long time without update. would be great to have it.

unfortunately I think the company as a whole has their eye on the bigger markets and there is really only one guy at Netkar working on this and from what I've gleamed from the past it's not his\companies priority to sort things out with the Reason side of things.

I did poo poo their last offering but to be fair it was not that good, maybe I should go and build some bridges..

I do think we offer better mappings here but when I look back at my first mappings there were basic however the latest ones work very well (for me they do, talking about navigation of the mappings more than anything).

I could quite quickly write an automatic mappings of VST\RE however the order of the controls will be all over the place as it comes down to how the original mapping file looks (see exporting of the remote files from Reason).

If you would like to help with the mappings even if it's only your favourite VST\RE then we would be grateful.

PoohBear

-------------------------------------------------------------------------------------------------------
Recent Music made with Reason
(Electronic) Poly Madness
(Electronic) Solar Dance
(Electronic) Into The Night
(Upbeat) The Players Took Me There Made in Reason 9 with heavy use of the players
(Electronic) 5 Steps (Video added) Updated
------------------------------------------------------------------------------------------
My Soundcloud Page ....... Nektar Mappings
------------------------------------------------------------------------------------------

[Carly(Poohbear)]

Dropbox updated.. https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

New Mapping

Europa
Grain
Humana
Klang
Pangea





New Files Added
Individual mapping plus comment plates for the above.


https://www.dropbox.com/sh/sberq7vvyfit ... T4sra?dl=0

NOTE: The file Panorama.remotemap contains all the Rack Extension mappings talked about on this thread.
VST will have to be download individually.

This file has to be replace\merged and can be found at:-

Windows: C:\ProgramData\Propellerhead Software\Remote\Maps\Nektar
OSX: //Library/Application Support/Propellerhead Software/Remote/Maps/Nektar


When backing up the existing file, back it up to a totally new directory (there have been issues reported if backing up in place).

[geronimo]

NEKTAR reacted with version 10 of REASON .

http://www.nektartech.com/panorama-vst- ... pport.html

[EnochLight]

NEKTAR reacted with version 10 of REASON .

http://www.nektartech.com/panorama-vst- ... pport.html

It's cool that they were cooking up a Remote map update for version 10, but it blows me away that they are still missing VST maps for some industry greats:

• No Reveal Sound Spire map (yet they have the RE)!
• No Vengeance Avenger
• No Synapse Audio Dune 2
• No Sonic Charge Permut8 (although they have Microtonic and Synplant)!
• None of the Roland cloud stuff (no Juno 106, no Jupiter 8, etc)

Oh well - at least it's a start. Maybe we'll see Nektar Tech add those in a year or 3. Seriously, if it weren't for the work that Carly, Lizard, and others have done, I would have gotten rid of my P4 a long time ago (so thanks, guys)!

[AttenuationHz]

Just realised FX plug-ins too. No FabFilter Q2 or C2! Hope they are compatible with the Q1 Q2 maps.


http://www.nektartech.com/panorama-plug ... pport.html

[Carly(Poohbear)]

NEKTAR reacted with version 10 of REASON .

http://www.nektartech.com/panorama-vst- ... pport.html

It's cool that they were cooking up a Remote map update for version 10, but it blows me away that they are still missing VST maps for some industry greats:

• No Reveal Sound Spire map (yet they have the RE)!
• No Vengeance Avenger
• No Synapse Audio Dune 2
• No Sonic Charge Permut8 (although they have Microtonic and Synplant)!
• None of the Roland cloud stuff (no Juno 106, no Jupiter 8, etc)

Oh well - at least it's a start. Maybe we'll see Nektar Tech add those in a year or 3. Seriously, if it weren't for the work that Carly, Lizard, and others have done, I would have gotten rid of my P4 a long time ago (so thanks, guys)!

Don't mean to knock them but their maps are so basic. Better than nothing, well the ones that we have not mapped are better than nothing.

With Europa (one of the ones that have done more mapping on as most of the mappings are only 2 pages) they have mapped ~60 controls, with our mapping we mapped over 250 controls (and you can times that by 3 as with our mapping you choose what is mapped where with regards to encoders, faders and upper encoders) or about 37 pages.

I like that "Grab" feature and for a second I thought the settings you grabbed were going to saved with the patch, now that would have been cool..

Now I could probably write something that would just take the export file (export device remote info) and slap it in a mapping, it would be in order of the export file, would that be better than nothing?

[EnochLight]

Now I could probably write something that would just take the export file (export device remote info) and slap it in a mapping, it would be in order of the export file, would that be better than nothing?

Christ yes - anything is better than nothing!

[Carly(Poohbear)]

Currently looking into how to change the patch of the VST it self.

I have noticed if there is no mapping you can changes the patch using Patch- & patch+, with the new VST mappings you can change it however I have not been able to get it to work yet.

In this pic,
Blue2 new mapping
Xpand2 my mapping (Map Patch Up Select Next Program)
Blade no mapping

Capture.JPG (83.04 KiB) Viewed 5120 times

[EnochLight]

Currently looking into how to change the patch of the VST it self.

I have noticed if there is no mapping you can changes the patch using Patch- & patch+, with the new VST mappings you can change it however I have not been able to get it to work yet.

In this pic,
Blue2 new mapping
Xpand2 my mapping (Map Patch Up Select Next Program)
Blade no mapping

Capture.JPG

According to Nektar Tech's release, the only way the Panorama series can change patches on VST is if the actual VST adheres to the VST standard for patch change info, which very few plugins do these days. I don't know how you got your Panorama to change patches for those at all, because it doesn't work on mine (I have all 3).

[Carly(Poohbear)]

Currently looking into how to change the patch of the VST it self.

I have noticed if there is no mapping you can changes the patch using Patch- & patch+, with the new VST mappings you can change it however I have not been able to get it to work yet.

In this pic,
Blue2 new mapping
Xpand2 my mapping (Map Patch Up Select Next Program)
Blade no mapping

Capture.JPG

According to Nektar Tech's release, the only way the Panorama series can change patches on VST is if the actual VST adheres to the VST standard for patch change info, which very few plugins do these days. I don't know how you got your Panorama to change patches for those at all, because it doesn't work on mine (I have all 3).

Out of the 3, which ones do you have mapped?

[Carly(Poohbear)]

According to Nektar Tech's release, the only way the Panorama series can change patches on VST is if the actual VST adheres to the VST standard for patch change info, which very few plugins do these days. I don't know how you got your Panorama to change patches for those at all, because it doesn't work on mine (I have all 3).

[/quote]

Actually that was a very useful peace of information.

Sure enough Xpand2 does not work even when there is not a mapping (the other 2 do change patches) and my mapping for Blue2 is OK. Well that will stop me from banging my head against the wall (for the time being)... LOL

[AttenuationHz]

hmmm. If the patches were saved in Reason it might work. You would have to go through every default patch for the VST device and SaveAs the reason patch for the VST.



Also weird glitch/bug in that....

[EnochLight]

hmmm. If the patches were saved in Reason it might work. You would have to go through every default patch for the VST device and SaveAs the reason patch for the VST.



Also weird glitch/bug in that....

Wow - that could be incredibly labor intensive, but I might have a go some day.

[Carly(Poohbear)]

hmmm. If the patches were saved in Reason it might work. You would have to go through every default patch for the VST device and SaveAs the reason patch for the VST.



Also weird glitch/bug in that....

As EnochLight pointed out from the notes, if the plugin does not support it then it won't work, that VST PROG thing is a Reason thing not a Nektar thing.