Native Access and Kontakt 8 Improvement requests
This discussion was created from comments split from:
Session Percussionist – Update Available!
Comments
-
Native Access improvements
Rather not have a new release every other year on Kontakt - the migration UX is still not great - focus first on fixing Native Access:
- Native Access uninstall support on all products important (uninstall instruction text for manual uninstall in Native Access does not count on MacOS). Uninstall button expected on all products and expansions.
- Smooth improved UX in Native Access when migrating Kontakt and Komplete Kontrol to another big release with supported DAWs (for instance migration button in Native Access would be nice). Fix this!
- Moving libraries UX with new GUI in Native Access should be a priority if you want to sell more sample libraries. Look at Steam.On Kontakt 8 the MIDI CC Editor page needs to be improved:
- Continue support class drag and drop assign - new instruments require you to use Learn button instead which is not smooth.
- Would also like to see copy and paste setting which would be smart when you build an orchestral template. This entire are needs some proper love and care. Assigning MIDI CC on Kontakt instruments are still needed for custom hardware setups and should be supported with better tools!
- Make sure new Kontakt instrument still have been bult with components which can assign MIDI CC - for instance Claire has a mic menu which cannot assign MIDI CC - that's bad design.
- Make the GUI more expandable so I dont have to scroll too much when assigning MIDI CC.
Kontakt 8 Classic Pages
- Many of the Classic pages have still not been converted to modern Kontakt 8 versions what is that status on this? I get we need legacy UX for backwards comp but where are the improvements to modernise the GUIs? It does not feel ok to see improvements firs t in Kontakt 9 for an obvious tech debt.
On Kontakt 8 frontend in general
- We still dont have a purge button at the top on Kontakt 8 with MIDI CC support and preferably a button on Komplete Kontrol Hardware.
- Priority of a Shop button over other buttons shows som desperation - I never click this button but rather see other button take up this space. Keep the shop button one on the browser page. I paid for this software so ads etc should be kept to a minimum and non intrusive or not at all.
- There are lot of Classic Mode buttons still hidden forcing many users to open the classic mode for status info and additonal buttons. Any other frontend improvements planned to fix this dissonance between new and old? IMO keep classic mode for legacy but transfer most of these components in a modern version and call it advance mode. Again seeing the old GUI Classic components just makes the experience feel old and not modern.0 -
Please send the improvement requests to the Native Access team and the Kontakt team.
0 -
@Jeremy_NI
Would also see a response on how Kontakt 8 will improve and update the MIDI CC Editor page and possible other general GUI fixes. The priority of pushing a Shop link front and center on a pay to use sample player over other buttons is not a great look.0 -
My biggest request would be to try to ensure that new software was actually compatible with older models of your hardware. It's not cheap to buy even the least expensive NI hardware and it feels quite irritating to see NI cease support for even relatively new musical hardware.
It shows a total ignorance of the way that the music industry has evolved, where there are studios still using equipment that was made in the latter half of last century, while NI makes 'hardware' that barely lives out a decade. It makes upgrading to new versions of your software doubly or trebly expensive. And it's super unhelpful when NI develops systems that make it impossible to even access software that its customers have paid for.
If NI doesn't want to respect its existing customers and only wants to sell to new people and go for the whole marketing churn mentality, that's NI's choice, but I'd say making your new software accessible to people who've previously purchased NI products seems like an easier route to market. Because after a while there just won't be enough churn to keep you happy.1 -
@Lionzinio I am not sure what this has to do with Kontakt feature requests, which is the point of this thread.
@MLARS I'll follow up shortly.
0 -
On Kontakt 8 the MIDI CC Editor page needs to be improved:Would also like to see copy and paste setting which would be smart when you build an orchestral template. This entire are needs some proper love and care. Assigning MIDI CC on Kontakt instruments are still needed for custom hardware setups and should be supported with better tools!
I'd love to hear a bit more about this. Which instruments are you referring to? Not every instrument has the same MIDI CC capabilities per se.
Continue support class drag and drop assign - new instruments require you to use Learn button instead which is not smooth.
Make sure new Kontakt instrument still have been bult with components which can assign MIDI CC - for instance Claire has a mic menu which cannot assign MIDI CC - that's bad design.
Such decisions are really up to the instrument builder/designer. I can certainly advise, but in my capacity, I work with the Kontakt team, and can only serve up the capabilities that instrument builders use. For Claire, that's Galaxy Instruments. I think they are already aware of this feedback.
Make the GUI more expandable so I dont have to scroll too much when assigning MIDI CC.
Could you talk more about what you mean exactly here? Kontakt is resizeable, generally speaking. Are you referring to a specific instrument, or perhaps a piece of Edit View?
Kontakt 8 Classic PagesMany of the Classic pages have still not been converted to modern Kontakt 8 versions what is that status on this? I get we need legacy UX for backwards comp but where are the improvements to modernise the GUIs? It does not feel ok to see improvements firs t in Kontakt 9 for an obvious tech debt.
See my answer further down: they won't be modernised per se, but eventually retired once Default View has evolved to a point where the functionality can be used there instead. I hope you've noticed a recent behaviour change on our side too.
As of 2025, we've been committed to a frequent release cadence, with at least one update every 6 weeks. Each update brings a mix of new features, improvements, and fixes, and we plan to continue to update Kontakt 8 every month, but more importantly, predictability and reliability, as the feedback loop is tighter now. Suggestions and issues emerge, lingering unaddressed feedback makes it up the backlog, and in all cases are never more than a few weeks away from release, priority pending.
We have no plans for a Kontakt 9 in 2025, or even 2026. Version updates are non trivial. They have to have a reason to exist, as even with a ton of exciting new features, they can inflict pain on users and builders, who have to adopt, transition, replace, update, etc. Kontakt 8 adoption is going really well. In a short space of time, we're close to eclipsing both Kontakt 6 and 7, and we have to stay committed to regularly improving Kontakt 8. Small GUI upgrades do not make a major version worth paying for. They do however provide enormous value for the users of that current version.
On Kontakt 8 frontend in generalWe still don't have a purge button at the top on Kontakt 8 with MIDI CC support
Whilst true, we do of course have a variety of purge functionality available globally or per instance. Can you talk me through the use case for it being MIDI mappable?
Priority of a Shop button over other buttons shows som desperation - I never click this button but rather see other button take up this space. Keep the shop button one on the browser page. I paid for this software so ads etc should be kept to a minimum and non intrusive or not at all.
It's perhaps a philosophical disagreement here, but I don't view that as desperation nor is it really advertising anything. It's an unobtrusive button that loads a URL in your browser of choice. And whilst you may not click it, a considerable enough number of people do use it to hop into the store quickly and browse or grab a sound they may be looking for. It doesn't take up much space - indeed there is plenty of space to the side of this button for any other functions we may want to add. But to be very clear, I do agree that ads should be kept to a minimum, and be non-intrusive.
There are lot of Classic Mode buttons still hidden forcing many users to open the classic mode for status info and additonal buttons. Any other frontend improvements planned to fix this dissonance between new and old? IMO keep classic mode for legacy but transfer most of these components in a modern version and call it advance mode. Again seeing the old GUI Classic components just makes the experience feel old and not modern.
Yeah I agree with this, and feel it deeply. The GUI is still in a state of transition. The Default View is built on a new graphical framework, and is intended to be the home for future developments moving forward. It will eventually be a unified, and the only, experience you see. However, we could not and would not deprecate Classic View until all of the important functions have been fully transitioned over. The more functionality that transitions, the more users will themselves transition. Right now, it's about 50/50 usage split between the two views, which also reflects a bit who uses what. We evolve this a little bit every month. Sometimes in ways you'll notice, sometimes in ways you won't. What would really help is to hear from you what the main capabilities or functions exclusive to Classic View are, that prevent you from using Default View.
0 -
On Kontakt 8 the MIDI CC Editor page needs to be improved:Would also like to see copy and paste setting which would be smart when you build an orchestral template. This entire are needs some proper love and care. Assigning MIDI CC on Kontakt instruments are still needed for custom hardware setups and should be supported with better tools!I'd love to hear a bit more about this. Which instruments are you referring to? Not every instrument has the same MIDI CC capabilities per se.
Response: For instance when you build an orchestral template today you create a single instance per track like the NI Symphony Series Ensemble Strings you need to add extra MIDI CC settings for tonal parameters, mic on/off and mic volume etc. You go to Classic View - Side Panel (MIDI Automation) - > Which is the MIDI CC Editor in Kontakt and then from sidepanel drag and drop MIDI CC assign for controls which do not have them (or a default one you want to adjust to a new MIDI CC assign)
Usually you create a track Strings Violins 1 Long (track) with a selection of long articulations routed to a specific reverb. Then you create a track for Strings Violins 1 Short (another track) with short articulation. Those two are on the same loading and can dublicated where the MIDI CC settings carries over. But then you load Violas Long in another instance on another track for long and another track for Violas short. Each time you have to load in Kontakt a new instance the MIDI CC assigned settings resets and you have to repeat the process of assigning similar MIDI CC again.To simplify the process of building templates with Kontakt, for instance when I setup my custom MIDI CC Assign on the first track Violins 1 Long, I would like to have a feature (like a copy and a paste MIDI CC settings button beside the Learn button) to copy MIDI CC settings and paste them in the next track Violins 1 Short and so on.
At the moment I have to do this manually drag and drop assign on most tracks (when duplicate track is not feasable) which is not a great experience for templates with hundreds of tracks.
Continue support class drag and drop assign - new instruments require you to use Learn button instead which is not smooth.Make sure new Kontakt instrument still have been bult with components which can assign MIDI CC - for instance Claire has a mic menu which cannot assign MIDI CC - that's bad design.Such decisions are really up to the instrument builder/designer. I can certainly advise, but in my capacity, I work with the Kontakt team, and can only serve up the capabilities that instrument builders use. For Claire, that's Galaxy Instruments. I think they are already aware of this feedback.
Response: From Galaxy Instruments response it sounded like there are limitations in the MIDI CC Assign editor (MIDI Automation) on new Kontakt 8 instruments. According to them NI need to update Kontakt 8 to support drag and drop MIDI CC assign for them to support it (you have to use the Learn button instead to make it work which is not as practical or that useful in many situations), hence me asking for you to look into improvements MIDI CC Assign editor (MIDI Automation) UX.Make the GUI more expandable so I dont have to scroll too much when assigning MIDI CC.Could you talk more about what you mean exactly here? Kontakt is resizeable, generally speaking. Are you referring to a specific instrument, or perhaps a piece of Edit View?
Response: Classic View - Side Panel (Mini Automation) - > Which is the MIDI CC Editor in Kontakt. There are over 100s MIDI CC assign a Column view might help for Ultrawide displays. Helps with the overview to see what MIDI CC has been assigned too.
Kontakt 8 Classic PagesMany of the Classic pages have still not been converted to modern Kontakt 8 versions what is that status on this? I get we need legacy UX for backwards comp but where are the improvements to modernise the GUIs? It does not feel ok to see improvements firs t in Kontakt 9 for an obvious tech debt.See my answer further down: they won't be modernised per se, but eventually retired once Default View has evolved to a point where the functionality can be used there instead. I hope you've noticed a recent behaviour change on our side too.
Response: I just saw the new Kontakt 8 update where you are measuring people using Classic view to gauge the current situtation. It is very important to UX test with composers and advance users (and not the casual audience in mind) and not check how many are advance users to assess how big priority this is, remember the tech debt on the GUI with possible underlying improvements is pretty big.
Talkt to composer and advance users, try to understand the needs to make it work with their current setups and templates when migrating and turning off older GUI. The MIDI CC Editor is a great example for this, we are seeing SSL and others starting to offer tailored fader control experience with Spitfire libraries but the underlying MIDI CC settings still needs to be there.
As of 2025, we've been committed to a frequent release cadence, with at least one update every 6 weeks. Each update brings a mix of new features, improvements, and fixes, and we plan to continue to update Kontakt 8 every month, but more importantly, predictability and reliability, as the feedback loop is tighter now. Suggestions and issues emerge, lingering unaddressed feedback makes it up the backlog, and in all cases are never more than a few weeks away from release, priority pending.
Response: I would interview composers ahead of this and test GUI changes with their templates if they have a test machine ready. If they are happy you are very likely covering the need of more casual users on the basic features.We have no plans for a Kontakt 9 in 2025, or even 2026. Version updates are non trivial. They have to have a reason to exist, as even with a ton of exciting new features, they can inflict pain on users and builders, who have to adopt, transition, replace, update, etc. Kontakt 8 adoption is going really well. In a short space of time, we're close to eclipsing both Kontakt 6 and 7, and we have to stay committed to regularly improving Kontakt 8. Small GUI upgrades do not make a major version worth paying for. They do however provide enormous value for the users of that current version.
Response: Very happy to hear this. Four year life cycle minimum is reasonable in my opinion - but with constant update on the current version. Yes, would hope we see many of the older GUIs in Kontakt 8 improved to lower that tech debt. We still need that migration button (for supported DAWs) in Native Access for Kontakt 9 when the time comes.
On Kontakt 8 frontend in generalWe still don't have a purge button at the top on Kontakt 8 with MIDI CC supportWhilst true, we do of course have a variety of purge functionality available globally or per instance. Can you talk me through the use case for it being MIDI mappable?
Response: Advance users ask for this to quickly globally purge the memory instead of using a mouse to open up Kontakt go to a menu and do it. It is a quality of life thing. It should also be in the GUI (maybe beside the panic button.Priority of a Shop button over other buttons shows som desperation - I never click this button but rather see other button take up this space. Keep the shop button one on the browser page. I paid for this software so ads etc should be kept to a minimum and non intrusive or not at all.It's perhaps a philosophical disagreement here, but I don't view that as desperation nor is it really advertising anything. It's an unobtrusive button that loads a URL in your browser of choice. And whilst you may not click it, a considerable enough number of people do use it to hop into the store quickly and browse or grab a sound they may be looking for. It doesn't take up much space - indeed there is plenty of space to the side of this button for any other functions we may want to add. But to be very clear, I do agree that ads should be kept to a minimum, and be non-intrusive.
Response: If the Shop button gets in the way move it to the Browser page. Personally I never use it.
There are lot of Classic Mode buttons still hidden forcing many users to open the classic mode for status info and additonal buttons. Any other frontend improvements planned to fix this dissonance between new and old? IMO keep classic mode for legacy but transfer most of these components in a modern version and call it advance mode. Again seeing the old GUI Classic components just makes the experience feel old and not modern.Yeah I agree with this, and feel it deeply. The GUI is still in a state of transition. The Default View is built on a new graphical framework, and is intended to be the home for future developments moving forward. It will eventually be a unified, and the only, experience you see. However, we could not and would not deprecate Classic View until all of the important functions have been fully transitioned over. The more functionality that transitions, the more users will themselves transition. Right now, it's about 50/50 usage split between the two views, which also reflects a bit who uses what. We evolve this a little bit every month. Sometimes in ways you'll notice, sometimes in ways you won't. What would really help is to hear from you what the main capabilities or functions exclusive to Classic View are, that prevent you from using Default View.
Response: For me in the Classic view header I like the status info, MIDI Channels, snapshots and instrument preset submenus (less interested in balance, pan and volume within Kontakt, but for legacy reasons needs to be placed somewhere - maybe move this to an expandable mix header).Consider how saving and managing saved instances can be improved with a better library UX. Currently it differs between products like Guitar Rig, Komplete Kontrol and Kontakt.
The sidepanel it is MIDI CC editor (MIDI Automation) which needs a better overview and more tools and better support for partners to fully support MIDI CC assign UX properly, perhaps a column view to see all MIDI CC (not having to scroll) for a better overview when you assign MIDI CC.
For drums/perc I may need to access the mixer (which hasnt aged well) for DAW routing. Master panel not so much (maybe combine volume, pan, balance with the current master panel)Overall would like to see more posts on the progress on improving GUI and overall UX in Kontakt 8.
Dont forget to forward the specific feedback about Native Access to the Native Access team too.
1 -
@Matthew_NI see my responses above
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 66 NI News
- 879 Tech Talks
- 4.5K Native Access
- 17.3K Komplete
- 2.2K Komplete General
- 4.7K Komplete Kontrol
- 6.2K Kontakt
- 1.1K Reaktor
- 404 Battery 4
- 900 Guitar Rig & FX
- 458 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 8K Traktor
- 8K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators