I decided to map airwave and jup 8000 v to my panorama p1. I discoved a some things.
Loading another “song” or starting a new project in cubase, does not mean i need to start all over. Cubase remembers whatever CC was used for the respective knob on each cc induvidually . this is great . saves alot of time not needing to map out knobs whatever decive you use again.
However , its be better if these setting where also changed per song . lets say you keep you physical knob cc mathcing you vst for 14 songs. then for some reason map them differently . unless you could save the midi mapping as a preset for the vst its gonna mean u just broken midi mapping how it was in the previous projects .
cubase is able to store knob positions , for all vst that dont have a native patch system. I think i should also have store midi mapping for each vst as “cubase patches” .
No, I think , I just pulled up the vsts editor and used RMB on each knob to get “midi learn” and moved my knobs or sliders for the assign. worked on the airwave . could not RMB and use cubase midi assign on jup 8000 v so i use the learn on its midi page when you open the advanced page.
2 : Panorama p1 got 2 modes . 1 is updating itself to the DAW , but i think its too clunky (slow) i cant comment too much about it. I use the “internal mode” that is it does not update itseöf if u change tracks in cubase , all knobs are sending whatever CCs you told them to send . And that mode comes with 20 presets ,some preconfigured for stuff, like m minimonsta , prophet 8 etc. These can be edited load/saved renamed .
Then it sounds like you are assigning MIDI CCs to parameters using features created by the plugin manufacturers. Cubase would not be involved in that process at all.
Cubase saves the MIDI configuration (which you have assigned) of Arturia VSTi (Jup-8000 V) within the project. When a saved project is opened, the last settings are restored per instance of the instrument. The MIDI configuration is also saved in Cubase’s VST3 presets.