Think of the synergy and possibilities of Native Instruments combining its technology and 3rd party sound library ecosystem with Cubase and the Yamaha synth and keyboard ecosystem:
- Halion and KONTAKT could use the same underlying sample engine - combining the best features forom both. For a time Halion would appear identical to how it does now - only with added support for NI libraries behind the scenes and merging of how automation and control is handled.
2 ) Having KONTAKT in the Steinberg ecosystem would allow better integration into VST 3 and thus Cubase itself.
3 ) Better support throughout for Kontakt string libraries in Cubase
4 ) A big one - Yamaha, NI or Steinberg ( via use of Yamaha’s best manufacturing resources ) could launch a new line of stage keyboards which use KONTAKT libraries - in RAM optimised form. There cold even be rack mounted type plugin servers for supporting the VST libraries more substantially -aimed specifically at the new stage keyboards - as an alternative to MainStage type rigs - where robustness of operation coupled with huge RAM into track devices were combined optimally. For example redundancy could be built into the rack units so a keyboardist would have a Kontakt supporting stage keyboard connected via ethernet (DANTE) to two KONTAKT server rack units working in failover redundancy mode.
5 ) Steinberg could optimise NI’s. KOMPLETE KONTROL. software and infrastructure (NKS ) for Cubase. AND a future version of VST3 - allowing a much more sophisticated amount of hardware integration and tie-ins between VST hosts etc - with Cubase leading the way.
Imagine if Cubase on the iPad could run RAM-optimised. Kontakt and REAKTOR libraries!
Imagine if a stage keyboard made by Yamaa could run both of these two - merging existing tech in Yamaha synths such as AWM too…
Imagine an ultimate composer-studio based keyboard controller range which focused on Cubase control and NI libraries to the max.