azslow3
That will not work with 90% of controllers. It will work with some buttons and even less encoders, that is not worse the effort.
As feedback, devices in general expect NOT the same values as they send (f.e. MCU and compatible encoders, all colored pads), sometimes not even the same messages (f.e. Faderport), require special timing (Alphatrack, Akai pads) or special care in which situation the feedback is sent (most motorized faders). And that is not even counting "not controllers"  such as Digital Mixers, which need special interpretation/timing in both directions.

Sure, Even in the same controller (i.e. Nektar Impact LX+) there are 3 kinds of back-lit buttons.
the colored pads who's  lights are only internally driven, 1 button that expects a different parameter than 7f or 0 to light a led next to it and 2 buttons who do turn on/off when receiving a 7f/0 to the same CC.
 
One of the features I like the most in Samplitude, is its hardware controller management.
It is excellent, despite the fact that it doesn't have the automatic vst parameter mapping like ACT does.
It has 4 modifiers, Shift and Shift lock and 2 others that I have no idea how to use yet.
And it has a global "Echo on" with the possibility to disable feedback for individual controls.
In my humble opinion it would have been smarter to have it reversed:
Global Echo off with the possibility to enable feedback for individual controls.
But... that's just me.
 

As you can guess from my signature, AZ Controller is going to be ported to Reaper
Not in next months, it will take quite some time (a year or so).

That's great news!!!
 
I have no doubt that you're going to do a great job and that it will be, for me, another enticement to adopt Reaper.
 
Best Regards.

TheMaartian
I was never able to get usable results with the control surface on my P6. The Reaper integration from Nektar is buggy and hasn't been touched in years

 
I'm a bit surprised.
See? I've been a little in touch with Nektar's support and they were extremely friendly and helpful.
And I only have the little, modest but smart LX25+.
 
The Panorama being their flagship product, I have a hard time believing that they would ignore or dismiss any existing bugs.
 
The only reason why I'm not using the Nektar DAW integration is that In the DAW integration, there is a whole section dedicated to VSTis but I have the Komplete Kontrol s25 taking good care of the VSTis.
I bought the LX25+ to Komplete the Kontrol: to control the VSTs.
 
I hope that you will enjoy more using the P6.
Sometimes problems can be solved with a bit of communication.

Jazzy2040

TheMaartian
I was never able to get usable results with the control surface on my P6. The Reaper integration from Nektar is buggy and hasn't been touched in years

 
I'm a bit surprised.
See? I've been a little in touch with Nektar's support and they were extremely friendly and helpful.
And I only have the little, modest but smart LX25+.
 
The Panorama being their flagship product, I have a hard time believing that they would ignore or dismiss any existing bugs.
 
The only reason why I'm not using the Nektar DAW integration is that In the DAW integration, there is a whole section dedicated to VSTis but I have the Komplete Kontrol s25 taking good care of the VSTis.
I bought the LX25+ to Komplete the Kontrol: to control the VSTs.
 
I hope that you will enjoy more using the P6.
Sometimes problems can be solved with a bit of communication.

I worked with Nektar support, and yes, they were friendly and trying to be helpful. There's a bug in the .sysex file (one specific command fails every time it's called). I sent them the log file. And that was that. None of the shift functions worked (like bank shifting; who needs that anyway, right?). The transport was screwed up. And more.
 
The Panorama line may be their flagship, but it's years old. None of the native support drivers (Studio One, Reaper, Bitwig, etc) have been updated in years.
 
The Reaper support worked better, but could not coexist with the Studio One support. I dealt with their tech support back then. They said it worked for them and they could have all the different native supports installed with no problem. Must be nice.
 
Like you said, nice peeps. Doesn't make them a great company. I'm currently 0 for 2 with them, for tech support not fixing my problem. I'll not be buying any more of their products.
 
Too bad. Good keybeds and ergonomics. I like the P6 as a keyboard. Use it daily. I bought a FaderPort, which is working great for me. Once I get an FP8, the P6 control surface will become meaningless anyway.
 
Waiting on NI to release the second generation of the S88 keyboard. I've played piano since the late 50s and I really miss having 88 keys!

TheMarrtian
I worked with Nektar support, and yes, they were friendly and trying to be helpful. There's a bug in the .sysex file (one specific command fails every time it's called). I sent them the log file. And that was that. None of the shift functions worked (like bank shifting; who needs that anyway, right?). The transport was screwed up. And more.
 
The Panorama line may be their flagship, but it's years old. None of the native support drivers (Studio One, Reaper, Bitwig, etc) have been updated in years.

Not looking good indeed!!
 
 

In all fairness, I should add that I did find a good use for the 9 manual faders on my P6. I was able to map them, transposed, on to the 9 drawbars on my B3 VSTi. 
 
The 100mm ALPS fader goes up and down when I power the P6 on...and them becomes a 10th manual fader. 

Nice,
When you're creative you always find a good use for things.