You’ll be fine, there’s a few of us here that will help you out.
In Cubase 12 there’s a new MIDI Remote function, it’s possible you may wish to go that route instead of the Nektar ‘deep’ integration. Depends on your needs, of course.
Just remember that the ‘P’ series will be 10 years old this year, so may need a little bit of attention to get things running how you want.
Yes, Cubase Remote is much better… and a good thing to learn now as I suspect it’s going to evolve with a lot more advanced features
Would there be other better choices of 49key controllers with the best expression methods and newest easy to use features with at least key velocity & aftertouch hopefully not large or heavy. I was wanting to stay under $240. So I first chose an $180 used PANORAMA NEKTAR T4 MIDI Controller and then jump over my intended $240 limit T4 and ordered a $250 used Nektar Panorama P4 MIDI Controller splurging up to a new total of $430 – can’t help but thinking about other possibilities in that $430 range if there are any? That is really more than I should spend, maybe should send one of these back, or resell one. I read the details about the strengths of each the T4 vs P4 they are each better in different ways and I couldn’t decide which I wanted and thought that really crazy thought best way to know is to test each. Maybe use each for their given strength doing different tasks. The P4 sounds pretty easy to map and the T4 has chord mode and note repeating, but I will have to try each out and see.
Do you use the new Cubase 12 MIDI Remote function with your Panoramas – Do you know of other as good or better choices for 14 key MIDI Controllers with some sliders and knobs, would a little joystick help much? I don’t think I will get into using the Pads all that much. I don’t know how long or when the P4 & T4 got release – I do think they both are still in the current Nektar linup still both on the current market.
Anyway… If you might comment on new or easier units might help.
P.S. - These are the Other MIDI Controllers I have reviewed and think that I would prefer Nektar P/T over: { Arturia KeyLab MkI, Arturia Keystep 37, Native Instruments Komplete Kontrol, M-Audios, AKAIs }
I have Korg’s MicoKeys 37 & 61-air and have been getting into several Soft Synths - I don’t use Native Instruments very much – just prefer different Soft Synths, like {Sylenth, Spire, Ava, Phase Plant, Korg Classics, SynthMasters, DS Thorn, Halion }.
So I think I have maybe done my research to arrive at the NECTAR’S in proper analysis.
“Do you use the new Cubase 12 MIDI Remote function with your Panoramas”
Above the screen the Panorama has 4 modes. the 4th button puts it in to a generic midi controller mode. This is the mode I’d used for Cubase new Remote Editor. Using the other mode for the downloaded integration. Using the 4th mode you can create pages in the Remote Editor with in Cubase and scroll through those, depending on what you want to control.
I can’t really recommend any keyboard controller as I’m selling my P6. I’ve bought a Mobi One Q3 instead https://www.qubeaudio.co.uk/ for my controller and reverted back to my old Virus TI synth as a Master keyboard, which has an amazing keybed. I’m not really a fan of faders, an endless rotary encoder works better. The rotary doesn’t need a pick up or a motor to be where it’s at in reality vs virtual.
And, the Mobi knob layout suits the EQ section in Cubase much better than any of the 8 knobs layouts we get on a keyboard controller, you have to use the shift functions etc when jumping dials for Q etc, which ends up not being an improvement than just using the mouse. The Mobi has everything you need at your finger tips.
Novation Impulse was nice but the screen viewing angle was more for if you were stood the wrong side of it, it’s a decent size screen but the pixels are way too big, otherwise a beautiful keyboard. I did love the Nektar but the 8 knob and shift function isn’t for me (ruling out all of them). Perhaps each knob having a press function to switch them would help here (which yes, the Mobi has that too).
Hey Thanks for that input, that is interesting
Maybe someone could help me with a “used” Nektar Panorama P4 - flashed it with the cubase firmware, reset to factory defaults. The very first example in the user guide is to simply use the track +/- key to move to different tracks in cubase 11 and when I press one of those keys the P4s screen display begins flashing very rapidly as if there is some kind of midi feedback and I have to restart everything to get it to stop - any one know or have ideas why this is happening? Is this used P4 broken or is there a bad config somewhere - I am completely new with midi-controller use.
When I press the “Instrument” button it says “NO INSTRUMENT” , but the instrument IS displayed when pressing “Veiw”. Probably means I need to get into the MAP for the instrument, I am guessing…
More testing does show that other functions ARE working - transport control, solo, mute, faders.
I will say that I can’t get midi-ox to monitor the P4 - It gives the out of memory error which indicates the P4 driver is in use which of course, it is.
The other thing is - there is a discrepancy in the P4 “Cubase Setup & User Guide for Panorama P-series_Windows.pdf” MIDI Port Setup it shows conflicting settings in the “visible” i/o port settings.
Do you have tracks in the project with the same name? The Panorama does not like this. Each track name needs to be unique, otherwise it gets stuck in an endless scrolling loop.
Hey - Thanx for the input. Some of my trk name were same in the first 10 chars so I made all of them different in the first characters - didn’t help 
I think maybe my Cubase Studio Midi Setup is not correct for the P4 - Nektar web pgs are contradicting them selves, even in the same document. They really don’t have it together with their docs. There is so much that they have taken on to configure all these software objects, I am not surprised after all these years it is a mess. Broken links, conflicting configs - Oh my…
If you have a P4/6 in Cubase 11 - could you post the config in ‘Studio/Studio Setup/MIDI Port Setup’ AND ‘Studio/Studio Setup/Nektar Panorama P4/6’ - I could really use and actual working configuration example.
Thanks So Much!
I am gonna post what my P4 is in/out’ing in windows - I see an input when I hit a control to send output - not sure it should do that.
So you helped me with this problem. I started with an empy project and just add 3 synths that the T4 knows and now it is working. And I did switch from the P4 to the T4. I will try connecting them both.
But any way - Thanks for the HELP!! Doubt I would have figured out this limitation of the Panorama’s with Cubase.
Hi Skijumptoes, thanks for your replies.
Are you using a Nektar Panorama with Cubase 12s Midi Remote function? Can the Panoramas get their displays updated by Cubase 12 Midi Remote Controllers? Or any other controller while using the Cubase 12s Midi Remote “User Custom Profiles” that has text displays and leds on its hardware?
I have gotten the P4 & T4s working and it is nice to see Cubase text and data displaying on the Panoramas leds and data screen. I started with a clean and simple project, it was apparently issue where the track names weren’t parsing correct.
Can the user expect these bidirectional communication to function with Cubase 12 Midi Remote “User Custom Profiles” Functions? Should I ask this in a NEW thread and maybe not just specific to the Nektars?
OR - Maybe with the way Cubase 12 Midi Remote works - this issue maybe just a moot point and not really needed to get a good workflow - what do you think?
thanks
I use a Komplete Kontrol mostly, my Panorama is in a box and i’m not sure what to do with it. I’ve been thinking about creating a MIDI Remote script that has all the screen feedback and such like though - It can’t be that hard to reverse engineer it as i’m super familiar with them with other work I’ve done.
…it sounds like you’ve done that already perhaps? Or is that via the Cubase integration that they developed a while back?
I don’t know if Nektar would be interested in creating an ‘official’ MIDI Remote for that line though, seems to me that they’re moving away from their transparent mappings and wanting plugins to sit within their Nektarine wrapper.
It may be worth asking the question, perhaps? 
I’m in the middle of moving everything around which is a pain or I’d get the P6 out. Trouble with the MIDI Remote functions is the stupid 8 “Focus” quick control limit, with no paging options.
If you want to map a synth (i.e. put filter controls on the rotaries, and envelopes on the fader) you’re really out of luck with the MIDI Remote, unless you create a specific page for each instrument you need to map. Comeon Steinberg! Puurrllleeaasse! lol
Yes, I myself am very eager for what improvements we’ll see to Remote Manager next update.
I don’t have Cubase 12 yet, so what I have done is via P4/P2 Cubase integration from Nektar.
Yeah - not so sure Steinberg or Nektar are going to do an OEM midi integration script for a 10 year old product - but they ARE still selling them
Hmm…
IF I was to get Cubase 12, I could do that - but I can not be sure it would be better than the Nektar Integration - ALL THESE reviewers / tutor videos by the guys that are closely tied to Steinberg are NOT using controllers that require a user defined script with ANY feedback to the hardware. And, when they do a user defined script the controller they use has NO feedback displays at all. 
This guy is a more independent reviewer - says “feedback” to the hardware DOESN’T happen! So, yeah, don’t think that will work with user defined script. this review is pretty clear on that. https://www.youtube.com/watch?v=0SLObxUJnP4&t=1612s (please let me know if it is not ok to post a link here, please)
So what is advertised as this wonderful new function looks like it has the potential to be a $99 dollar, not so great disappointment. At least I have been at this long enough to not just dive in without understanding, that it is really just not going to work for me. One thing I am not sure about is what is would be like to use the Nektar’s as with working all it’s controllers and seeing the updates all happen in the Cubase display - and not on the hardware controller. That “MIGHT” be just fine. I just don’t have any experience using midi controllers so I just don’t know if that would be better than Nektar’s integration with Cubase 11.
Insights would be helpful, if you have opinion on using a controller without hardware feedback.
CHEERS!
I’ve got it talking to the Komplete Kontrol and sending parameter names and data, plus VU meters via the JS/API side of things:
Trouble is, with the Komplete Kontrol it’s very much a hack as you have to work within the refines of their mixer view, and the standard controls are horribly setup so you have to filter out and translate to get some kind of normal feel to the rotaries.
I’ll have a play with the Panorama next week and if I get anything done i’ll send you some screenshots of what I manage. It’d certainly future proof them, as you’d get a decent integration without needing Nektar to maintain updates. If it works, C12 goes on sale - then bingo! haha.
Mine’s gone a bit yellow with age, the drum pads are pretty unusable, and keys not as good as the KK - which breaks my heart as I love everything else about them… But since moving things around, I just don’t have room for it full-time right now.
Sale is the way I HAVE TO LIVE NOW, so yeah, for sure. As you know I bought used controllers, get used plugins, or deep discounts, etc - knobcloud is kinda cool in that respect.
My P4’s a bit yellowed, not so bad, all the controllers work great tho, the pads are super responsive - I had to soak all the knobs in alcohol to get the gum off em, geez, what a mess.
Ok your post answered some of my questions - still all seems to indicate there is no output of data changes going out of Cubase back to the controller without a Manufacturers Plugin running to facilitate outputs like that.
This post seems similar to me, How do I make 'Quick Control' value/name info appear on my Midi Controller display (Komplete Kontrol s25)? but I don’t yet understand if it is not applicable since it is QuickControls
EndOyear is coming.
Reminding me of SONAR PRO Panels so long ago.
So far I have spent time in the P4 - after initially just getting the T4 to interface and check out the controllers - come to think of it I better make sure I did all that before I can’t send it back - buyers get 14 days for used’s from GC.
I figured after I get into the learning curve on these I’ll go back and re-read the stuff you guys traded about the map files and all that stuff about nektarine and the formats, mubo jumblo blah vlah da…sh.i.stuff.
Like I said b4 , pretty much just want to use these for Synth performance, like you said - filters & envelops. just figure need to kinda understand what they are doing if I press buttons, cause they can seem a bit mysterious
Ok - this post MIDI Remote API Controller issue - DisplayValue doesn't follow automation DOES indicate that my concerns of not getting the controller displays to follow the DAW host changes - seems to be a non issue if I can get my hands on this scripting API spec - no more posts till I do more research.
Nektar will send you new knobs and fader caps if you contact them, its a known issue with the original ones that came with the P series.
Oh Cool Thanks
Great tip - Nektar are sending me new knobs right now.
In fact, I’ve found their customer service to be excellent thus far.
BAZINGA!
Was in the same boat - nothing worked until I deleted all the Nektarine maps and edited my own, then copied it across to \Common\
Sorry for the Nek-ro post, but I had to say thanks to you all, so - Thanks!!!
Also, the new knobs arrived in less than 10 days so my P1 looks all spiffy now.
