New Maps for +100 VST instruments from Arturia, Rob Papen, Korg, Kontakt, U-He and many more.
More info here: http://www.nektartech.com/tablet/reason ... pdate.html
Don't forget the mappings we have done. viewtopic.php?t=7491466JacobiusWrex wrote: ↑25 Oct 2017Just bought a p1, I was wondering when these features would be added, now I'm a very happy customer[emoji2][emoji106][emoji106]
Sent from my iPhone using Tapatalk
That's a pity, grab would be very useful for devices with no mapping.TChandler wrote: ↑25 Oct 2017Hi all, thanks for continuing to support Nektar!
To answer the question regarding GRAB, it's not possible to use GRAB with unmapped VSTs. Unfortunately a VST must appear in the scopes to get any form of control from Panorama/Impact at all. This is something I hope will change in the remote technology one day.
I hope that Propellerhead adds some wysiwyg editor to edit and create remote maps without having to fiddle with text files.TChandler wrote: ↑25 Oct 2017We can not realistically cover every VST so we focused on INSTRUMENTS, first and prioritized.
It would be really helpful if there are VSTs you would like to see supported that are not, and ofcourse any that are listed as supported and may not be working for some reason please contact support.
If a user such as myself created the scope in the map file. Would saving and writing to the map file be something that could be done via Grab. Having to redo grabs when the project is closed would get old quick... Would be great for custom maps. Something like this is what I hope for if Reasons remote override was updated...TChandler wrote: ↑25 Oct 2017Hi all, thanks for continuing to support Nektar!
To answer the question regarding GRAB, it's not possible to use GRAB with unmapped VSTs. Unfortunately a VST must appear in the scopes to get any form of control from Panorama/Impact at all. This is something I hope will change in the remote technology one day.
To control unmapped VSTs, use reason's remote override - the fader section in Transport mode is reserved for remote override (Panorama only).
We can not realistically cover every VST so we focused on INSTRUMENTS, first and prioritized.
It would be really helpful if there are VSTs you would like to see supported that are not, and ofcourse any that are listed as supported and may not be working for some reason please contact support.
Best Regards,
Tim
Just pressing shift causes the grab. Europa's Envelope position moves on an Init patch once you press shift it grabs the envelope position. It is a control it should not grab because there is no way to control that. There is no remote info for it. Sorry just checked the export there is Remote info for it It can't be controlled though. What's displayed on the P1 screen is EnvPo. If the Loop is disabled it stops modulating the fader on the P1 screen.
Tim,TChandler wrote: ↑25 Oct 2017Hi all, thanks for continuing to support Nektar!
To answer the question regarding GRAB, it's not possible to use GRAB with unmapped VSTs. Unfortunately a VST must appear in the scopes to get any form of control from Panorama/Impact at all. This is something I hope will change in the remote technology one day.
To control unmapped VSTs, use reason's remote override - the fader section in Transport mode is reserved for remote override (Panorama only).
We can not realistically cover every VST so we focused on INSTRUMENTS, first and prioritized.
It would be really helpful if there are VSTs you would like to see supported that are not, and ofcourse any that are listed as supported and may not be working for some reason please contact support.
Best Regards,
Tim
Double pressing shift was not working for me for the parameters grabbed while the steps/the sequencer on Step was playing on Step or on Europa's EnvPo a complete restart of reason was required.TChandler wrote: ↑30 Oct 2017Please send exported device remote infos for any VSTs that are not working (particularly if they are meant to work!) to support.
It's not possible for the codecs to determine if an incoming parameter value caused by mouse movement, or automation, so yes it makes sense to grab parameters without the sequencer running.
Double pressing SHIFT will remove any parameter mappings grabbed in error.
If you map a VST in the legacy mapping format, you won't be able to use Grab. The new mapping format is not documented, but take a look at Europa and the Reason 9 players for reference. The main differences are:
1. The underscore at the start of the device name signifies a mapping in the new format.
2. Controls are mapped by number in the Ctrl ID list rather than by name string.
You can use the usual navigation and ctrl labelling methods, although there is a CTRL_MAP and CTRL_MAP_TRIG label required when you want an display button to be a toggle/trigger control in the new format.
As you can probably tell, it's far easier to translate exported device remote infos into a basic map in the new format. Plus, you don't need to map every parameter since Grab will allow access to those required less frequently.
But, the legacy mapping method is maintained for full customization of a device across Panorama's controls.
Regards,
Tim
This is because it relies on the new grab feature.
What? The previous mappings got broken because of a new feature?Carly(Poohbear) wrote: ↑07 Nov 2017This is because it relies on the new grab feature.
We do have the full mapping for all of the new devices plus many more on this thread viewtopic.php?t=7491466
I have just looked at the code and it should be there but for some reason the buttons are not being displayed.
Thanks!Carly(Poohbear) wrote: ↑08 Nov 2017I have just looked at the code and it should be there but for some reason the buttons are not being displayed.
Looking into this.
Users browsing this forum: No registered users and 9 guests