A little disappointed: Nektar P Series

[Chritet]

I'll buy a panorama for sur if Nektar made an editor for Rack extension ... Please do it !!!!


Envoyé de mon iPad en utilisant Tapatalk

[DinoJ]

@Lizard

Thanks for posting this info on the remote maps, it got me started on having a mess around today trying to see if it was something we could do ourselves.

It got me thinking is there anything similar that already has a map that I can experiment with, had a look through and thought logically it might be an idea to have a go at creating an ABL3 map based on the ABL2 remote map included in the filem especially as it is a relatively simple device to get started with.

Unfortunately it did not work, without guidance from Nektar, I am not really sure why. I basically copied the ABL2 map and changed it to ABL3 zeroing the references to features ABL3 does not support such as Drive, Distort etc. I am fairly confident I got all the encoder elements right as they would just be the same as the ABL2 ones (minus the non existent features in ABL3). Will keep trying though.

[auricle]

It's gone very quiet in this thread. I wonder when/if someone from Nektar will respond here.

[DinoJ]

It's gone very quiet in this thread. I wonder when/if someone from Nektar will respond here.

I am still fairly confident that we will hear something, they did say in that last response I posted that they were going to discuss this, it may just take them a little time to get together and have that discussion and decide on a response or course of action, we shall see I suppose

[Lizard]

Well… to keep it a little alive… Details on writing remote maps is available to anyone if they want to apply as a developer. There are documents that describe things on both sides of remote technology which is the LUA Codec and then the remote maps. The Codec should not have to be messed with (I would think) and certainly hope not. You can pull it up in any editor and you’ll see what I mean. But the remote map looks to be very straight forward. As I’ve mentioned previously, these maps are still more complex than most remote maps. They just need some explanation. However Nektar may not be able to discuss that information here if it is under Propellerhead NDA. I am not sure how that works.

@DinoJ

I will point out this one thing about the remote maps if you tried. Entries made in map are delimited by tabs so if you do not have the proper tabs between the fields it will not work. Pay attention to how examples in the existing file are spaced. This may make all the difference for you.

[tiker01]

Someone created a utility to edit the Panorama Logic templates which Nektar even distributes so I think either they or us should make one for Reason/Rack extensions.

Video https://youtu.be/Y3DR86aFZgU?t=43s

[justin3am]

Hello fellow Reason users,

First off, I'd like to thank you all for your patience and thank you for your kind feedback. We really do appreciate it.

I acknowledge that we haven't been keeping up with new REs mapping in a timely manner but rather than go into details, I'd like to offer something of substance...

Mapping Rack Extensions for Panorama
On this page you will find a link to updated remote maps for Panorama P4/P6 (which use the same file) and Panorama P1.

I have added mapping for some new REs but you will notice that these new maps only have an Instrument Home page (no page navigation) and patch navigation. This is only temporary. We will have complete maps for new REs in a future update, but as usual, I can't discuss time-frames or release dates. Here is a list of the new maps which are included in this update:

AudioRealism - ABL3
Blamsoft - Zero
Jiggery Pokery - Combo310
Jiggery Pokery - Combo x705
Jiggery Pokery - Combo B3T
Jiggery Pokery - Republik
Lectric Panda - Korde
Lectric Panda - Propulsion
OchenK - Driver
Pitchblende - Auto Theory
Primal Audio - FM4
Project SAM - Orchestral Sampler
Rob Papen - Quad
Rob Papen - Vectro
zvork - Oberon


On the page linked above, you will also find instructions for creating your own, simple maps for Rack Extensions. We plan to add these instructions to the user guide for our Reason integration, so I want to make sure that the instructions are easy to understand. I’d really appreciate any comments or criticisms.

All the best,
Justin Sullivan
Nektar Technology

[justin3am]

I'd like some feedback as you guys are checking this out, if you don't mind...

Are the instructions easy to follow?
Are you able to change the mapping for the REs listed above without encountering errors?
Are you able to create a new map without encountering errors?

All of the maps listed above were created with the template provided in the link, to make sure that it would all work as described. Still, I want to see if you guys encounter any issues which I hadn't thought of.

Thanks in advance for your help and comments.

- Justin

[EnochLight]

Hello fellow Reason users,

First off, I'd like to thank you all for your patience and thank you for your kind feedback. We really do appreciate it.

I acknowledge that we haven't been keeping up with new REs mapping in a timely manner but rather than go into details, I'd like to offer something of substance...

Mapping Rack Extensions for Panorama
On this page you will find a link to updated remote maps for Panorama P4/P6 (which use the same file) and Panorama P1.

I have added mapping for some new REs but you will notice that these new maps only have an Instrument Home page (no page navigation) and patch navigation. This is only temporary. We will have complete maps for new REs in a future update, but as usual, I can't discuss time-frames or release dates. Here is a list of the new maps which are included in this update:

AudioRealism - ABL3
Blamsoft - Zero
Jiggery Pokery - Combo310
Jiggery Pokery - Combo x705
Jiggery Pokery - Combo B3T
Jiggery Pokery - Republik
Lectric Panda - Korde
Lectric Panda - Propulsion
OchenK - Driver
Pitchblende - Auto Theory
Primal Audio - FM4
Project SAM - Orchestral Sampler
Rob Papen - Quad
Rob Papen - Vectro
zvork - Oberon


On the page linked above, you will also find instructions for creating your own, simple maps for Rack Extensions. We plan to add these instructions to the user guide for our Reason integration, so I want to make sure that the instructions are easy to understand. I’d really appreciate any comments or criticisms.

All the best,
Justin Sullivan
Nektar Technology

Wow - thanks for this Justin! And thanks for the update; will definitely give this a try. As for the instructions in general, they're relatively clear and easy to follow. It's just a lot more complicated than some may be able to traverse. I'll let you know how I personally get on when I get some free time - my weekend is already booked though.

[Lizard]

Well I tried to make a simple one work. I Tried to do Blamsoft's DC-1 to no avail. I used another effect from the map already and used the guide as close as I could. Of course the guide uses a synth like Quad. I thought I go simple. Here is the code I entered but it will not work. What's wrong?

Code: Select all

Scope	Blamsoft, Inc.	com.blamsoft.DC1
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"DC-1 Distortion"		HOME
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		""			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		0					Instrument
Map	X3		0					Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument

Map	Ch Knob 1		Tone		Name	Instrument
Map	Ch Knob 2		Distortion		Name	Instrument
Map	Ch Knob 3		Mix		Name	Instrument
Map	Ch Knob 4		Level		Name	Instrument
Map	Ch Knob 5		0		Name	Instrument
Map	Ch Knob 6		0		Name	Instrument
Map	Ch Knob 7		0		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

[justin3am]

What exactly are you having trouble with? When I use your map*, I don't encounter any errors and when I create a track for the DC1 effect, I can see the mapping is working (but you removed the encoder name elements, so no parameter names appear).

I'm glad you figured out how to use the Bypass function. Perhaps I should create two templates, one for instruments and one for effects.


*I noticed that the forum turns tabs into three spaces when you post something as code. If I quote a post I can see the code with the tabs preserved.

[Lizard]

Ok.... Think I got it! As least these work for me. I mapped the Blamsoft Shredder Series. If you copy the following code to the bottom of your remote map and save these should work if you have these devices.

DC-1 Distortion

Code: Select all

Scope	Blamsoft, Inc.	com.blamsoft.DC1
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"DC-1 Distortion"		INST
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		""			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		0					Instrument
Map	X3		0					Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument


Map	Name Element 1		"Tone"			Instrument
Map	Name Element 2		"Distortion"			Instrument
Map	Name Element 3		"Mix"			Instrument
Map	Name Element 4		"Level"			Instrument
Map	Name Element 5		""			Instrument
Map	Name Element 6		""			Instrument
Map	Name Element 7		""			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Tone		Name	Instrument
Map	Ch Knob 2		Distortion		Name	Instrument
Map	Ch Knob 3		Mix		Name	Instrument
Map	Ch Knob 4		Level		Name	Instrument
Map	Ch Knob 5		0		Name	Instrument
Map	Ch Knob 6		0		Name	Instrument
Map	Ch Knob 7		0		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

DC-9 Overdrive

Code: Select all

Scope	Blamsoft, Inc.	com.blamsoft.DC9
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"DC-9 Overdrive"		INST
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		""			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		0					Instrument
Map	X3		0					Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument


Map	Name Element 1		"Tone"			Instrument
Map	Name Element 2		"Drive"			Instrument
Map	Name Element 3		"Mix"			Instrument
Map	Name Element 4		"Level"			Instrument
Map	Name Element 5		""			Instrument
Map	Name Element 6		""			Instrument
Map	Name Element 7		""			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Tone		Name	Instrument
Map	Ch Knob 2		Drive		Name	Instrument
Map	Ch Knob 3		Mix		Name	Instrument
Map	Ch Knob 4		Level		Name	Instrument
Map	Ch Knob 5		0		Name	Instrument
Map	Ch Knob 6		0		Name	Instrument
Map	Ch Knob 7		0		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

t00b

Code: Select all

Scope	Blamsoft, Inc.	com.blamsoft.t00b
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"t00b"		INST
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		"Bass Boost"			Instrument
Map	X3_Labeli		"Tone"			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		Bass Boost		CTRL			Instrument
Map	X3		Tone		CTRL			Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument


Map	Name Element 1		"Tube Model"			Instrument
Map	Name Element 2		"Distortion"			Instrument
Map	Name Element 3		"Mix"			Instrument
Map	Name Element 4		"Level"			Instrument
Map	Name Element 5		"Bass"			Instrument
Map	Name Element 6		"Mid"			Instrument
Map	Name Element 7		"Treble"			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Tube Model		Name	Instrument
Map	Ch Knob 2		Distortion		Name	Instrument
Map	Ch Knob 3		Mix		Name	Instrument
Map	Ch Knob 4		Level		Name	Instrument
Map	Ch Knob 5		Bass		Name	Instrument
Map	Ch Knob 6		Mid		Name	Instrument
Map	Ch Knob 7		Treble		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

[Lizard]

Here is another. Paste to bottom of remotemap...

Codediggers - DQ Band Dynamics Processor

Code: Select all

Scope	CodeDiggers	ru.laboratoriait.DQ
Define Group	Mode	Instrument	Mixer	Transport	Channel
Define Group	force_patch_Feedback	Patch 1	Patch 2

Map	Mixer Mode		Mode=Mixer
Map	Instrument Mode		Mode=Instrument
Map	Transport Mode		Mode=Transport
Map	Channel Mode		Mode=Channel

//Device name that appears on Panorama's dispaly
Map	Device Name		"DQ Band Dynamics Processor"		HOME
Map	Patch Name		Patch Name			Instrument	Patch 1
Map	Patch Name		Patch Name			Instrument	Patch 2

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		"Filt P"			Instrument
Map	X3_Labeli		"Thresh P"			Instrument
Map	X4_Labeli		"DR Link"			Instrument
Map	X5_Labeli		"Lkahead"			Instrument
Map	X1		0		BYPASS	Instrument
Map	X2		Detection Filter Preview		CTRL	Instrument
Map	X3		Threshold Preview		CTRL	Instrument
Map	X4		Link to Detection Range		CTRL	Instrument
Map	X5		Lookahead Enabled		CTRL	Instrument

//Display Encoders
Map	Name Element 1		"HP Freq"			Instrument
Map	Name Element 2		"LP Freq"			Instrument
Map	Name Element 3		"Thresh"			Instrument
Map	Name Element 4		"Makeup"			Instrument
Map	Name Element 5		"PR LF"			Instrument
Map	Name Element 6		"PR HF"			Instrument
Map	Name Element 7		"Attack"			Instrument
Map	Name Element 8		"Release"			Instrument
Map	Ch Knob 1		Detection Highpass Freq		Name	Instrument
Map	Ch Knob 2		Detection Lowpass Freq		Name	Instrument
Map	Ch Knob 3		Threshold		Name	Instrument
Map	Ch Knob 4		Makeup		Name	Instrument
Map	Ch Knob 5		Processing Low Freq		Name	Instrument
Map	Ch Knob 6		Processing High Freq		Name	Instrument
Map	Ch Knob 7		Attack Time		Name	Instrument
Map	Ch Knob 8		Release Time		Name	Instrument

//Faders

Map	Fader Name Element 9		"Comp/Expand"			Instrument
Map	Fader 9		Comp/Expand Intensity		NAME	Instrument

[Lizard]

DLD Technology - HM-1 Headphone Monitor

Code: Select all

Scope	DLD Technology	com.dldtechnology.headphonemonitor
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"HM-1"		INST
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		""			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		0					Instrument
Map	X3		0					Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument


Map	Name Element 1		"Angle"			Instrument
Map	Name Element 2		"Model"			Instrument
Map	Name Element 3		"Head"			Instrument
Map	Name Element 4		""			Instrument
Map	Name Element 5		""			Instrument
Map	Name Element 6		""			Instrument
Map	Name Element 7		""			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Speaker Angle		Name	Instrument
Map	Ch Knob 2		Speaker Model		Name	Instrument
Map	Ch Knob 3		Head Model		Name	Instrument
Map	Ch Knob 4		0		Name	Instrument
Map	Ch Knob 5		0		Name	Instrument
Map	Ch Knob 6		0		Name	Instrument
Map	Ch Knob 7		0		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

[Lizard]

Ochen K. - Carve

Code: Select all

Scope	Ochen K.	com.ochenk.CarveEQ
Define Group	Mode	Instrument	Mixer	Transport	Channel
//	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

//Device name that appears on Panorama's dispaly
Map	Device Name		"Carve"		INST
Map	Patch Name		Device Name			Instrument

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		""			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS			Instrument
Map	X2		0					Instrument
Map	X3		0					Instrument
Map	X4		0					Instrument
Map	X5		0					Instrument


Map	Name Element 1		"Ref In"			Instrument
Map	Name Element 2		"HP"			Instrument
Map	Name Element 3		"LP"			Instrument
Map	Name Element 4		""			Instrument
Map	Name Element 5		"Amount"			Instrument
Map	Name Element 6		"Attack"			Instrument
Map	Name Element 7		"Release"			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Ref In Sensitivity		Name	Instrument
Map	Ch Knob 2		High Pass		Name	Instrument
Map	Ch Knob 3		Low Pass		Name	Instrument
Map	Ch Knob 4		0		Name	Instrument
Map	Ch Knob 5		Amount		Name	Instrument
Map	Ch Knob 6		Attack		Name	Instrument
Map	Ch Knob 7		Release		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

[EnochLight]

@Lizard - thanks for posting these!

[Lizard]

Everyone's favorite....

CRAPRE

Code: Select all

Scope	Peff	com.peff.crapre
Define Group	Mode	Instrument	Mixer	Transport	Channel
Define Group	force_patch_Feedback	Patch 1	Patch 2

Map	Mixer Mode		Mode=Mixer
Map	Instrument Mode		Mode=Instrument
Map	Transport Mode		Mode=Transport
Map	Channel Mode		Mode=Channel

//Device name that appears on Panorama's dispaly
Map	Device Name		"CRAPRE"		HOME
Map	Patch Name		Patch Name			Instrument	Patch 1
Map	Patch Name		Patch Name			Instrument	Patch 2

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		"SPRinG"			Instrument
Map	X3_Labeli		""			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS	Instrument
Map	X2		Reverb		CTRL	Instrument
Map	X3		0		CTRL	Instrument
Map	X4		0		CTRL	Instrument
Map	X5		0		CTRL	Instrument

//Display Encoders
Map	Name Element 1		"Input Gain"			Instrument
Map	Name Element 2		"Tape"			Instrument
Map	Name Element 3		"Volume"			Instrument
Map	Name Element 4		""			Instrument
Map	Name Element 5		""			Instrument
Map	Name Element 6		""			Instrument
Map	Name Element 7		""			Instrument
Map	Name Element 8		""			Instrument
Map	Ch Knob 1		Input Gain		Name	Instrument
Map	Ch Knob 2		Tape		Name	Instrument
Map	Ch Knob 3		Volume		Name	Instrument
Map	Ch Knob 4		0		Name	Instrument
Map	Ch Knob 5		0		Name	Instrument
Map	Ch Knob 6		0		Name	Instrument
Map	Ch Knob 7		0		Name	Instrument
Map	Ch Knob 8		0		Name	Instrument

[Lizard]

@Lizard - thanks for posting these!

np bud! Let me know if they don't work for you. I think they should. I can only work on the ones I have though. Hopefully others will map some too. These are easier. I'll see if I can understand pages and menus if I can. That's big time right there.

[Lizard]

Before my trial runs out...

Primal Audio - PMS-20

Code: Select all

Scope	Primal Audio	com.primalaudio.PMS20
Define Group	Mode	Instrument	Mixer	Transport	Channel

Map	Mixer Mode		Mode=Mixer
Map	Instrument Mode		Mode=Instrument
Map	Transport Mode		Mode=Transport
Map	Channel Mode		Mode=Channel

//Device name that appears on Panorama's dispaly
Map	Device Name		"PMS-20"		HOME

Map	Bypass		Enabled					Instrument	

//Display buttons
Map	X1_Labeli		"Bypass"			Instrument
Map	X2_Labeli		"Rage"			Instrument
Map	X3_Labeli		"Auto"			Instrument
Map	X4_Labeli		""			Instrument
Map	X5_Labeli		""			Instrument
Map	X1		0		BYPASS	Instrument
Map	X2		Rage		CTRL	Instrument
Map	X3		Auto		CTRL	Instrument
Map	X4		0		CTRL	Instrument
Map	X5		0		CTRL	Instrument

//Display Encoders
Map	Name Element 1		"HP Cutoff"			Instrument
Map	Name Element 2		"HP Mod"			Instrument
Map	Name Element 3		"HP Peak"			Instrument
Map	Name Element 4		"Input"			Instrument
Map	Name Element 5		"LP Cutoff"			Instrument
Map	Name Element 6		"LP Mod"			Instrument
Map	Name Element 7		"LP Peak"			Instrument
Map	Name Element 8		"Output"			Instrument
Map	Ch Knob 1		Highpass Cutoff		Name	Instrument
Map	Ch Knob 2		Highpass Modulation		Name	Instrument
Map	Ch Knob 3		Highpass Peak		Name	Instrument
Map	Ch Knob 4		Input Level		Name	Instrument
Map	Ch Knob 5		Lowpass Cutoff		Name	Instrument
Map	Ch Knob 6		Lowpass Modulation		Name	Instrument
Map	Ch Knob 7		Lowpass Peak		Name	Instrument
Map	Ch Knob 8		Output Level		Name	Instrument

//Faders

Map	Fader Name Element 9		"Mix"			Instrument
Map	Fader 9		Mix		NAME	Instrument

[decibel]

my nektar p6 is gathering dust at the moment (have been using novation midi keyboard instead) maybe i need to have another shot at it ? if only i had the spare time lol

[Goan]

I think it's time for a sticky thread with a more positive title

[justin3am]

Hi Lizard,

Fantastic work. I'm glad that you've had success mapping those REs.

- Justin

[tiker01]

Hi Justin,

By any chance are you going to map the Revert function of the Reason browser?

[justin3am]

Revert function? Browser functions are difficult, as they cannot be accessed via the Remote system. We handle Browser functions by sending QWERTY key commands to Reason. Is there a specific key command for the revert function? Can't you revert using the 'Undo' button on Panorama?

[Lizard]

I think it's time for a sticky thread with a more positive title

I couldn't agree more! I will try to get together a thread that will try to wrestle all this information together for people on how to make templates and for others to be able to copy and paste maps as they are created so they can stay up to date as quickly as possible. If it gets a sticky... that will be up to the moderators. Let's hope.

EDIT : I have now created a thread title with a more positive aspect. I have copied some fo the relevant info from this to that so that a healthy discussion on Nektar Remote Mapping can occur there. Thanks for all the feedback everyone.