I'm considering purchasing a NI Kontrol Keyboard. Does anything related to Pianoteq show up on the screen on the keyboard or is everything through the interface on the computer? I'm looking to select presets and maybe change some eq settings from the keyboard.
Thanks.
Hopefully someone can answer your question directly, but I believe there is some level of integration based on this discussion (including a complete list of supported NKS parameters as of 2018):
Yes. I have a Komplete Kontrol 88 and it has a great interface for Pianoteq. However, I posted this a long time ago with no answers. There is one problem. The menu interface for Pianoteq on the Kontrol is all in JAPANESE. Can't switch it to English for some reason.
Yes. I have a Komplete Kontrol 88 and it has a great interface for Pianoteq. However, I posted this a long time ago with no answers. There is one problem. The menu interface for Pianoteq on the Kontrol is all in JAPANESE. Can't switch it to English for some reason.
I wonder if that is something to do with the NKS version?
If you update Komplete Kontrol and the Pianoteq software maybe that could make a difference?
I imagine you tried those things a few times over though?
Perhaps reinstall Pianoteq to a different location on the drive?
Hi :-)
NI Kontrol-Keyboards are out now (received mine yesterday) - and i would like to talk about the NKS2-Standard and how modartt takes use of the possibilites.
Actually the Komplete-Browser (within the Keyboard) recognizes Pianoteq 6,7 and 8 (and it is possible to navigate within the 8 Sites of parameters.
It would be great, if Modartt would go further with the NKS2-Standard and use the groups-functionality of the NKS2-Standard
By the way: Organteq (1+2) are missing in the Browser (filtered by Brand Modartt). There is the workaround to load it within Komplete Kontrol as a VST or VST3, but It would be great to see Organteq within the Browser of the keyboard - again using NKS2-Groups for parameters :-)
If it is possible (with NKS2) to use the Keyboard-Display with both of the standalone-Apps that would be great too!
Is ist possible to tell us, on which topic you (moddart) are already working at ;-) ?
I've recently tried to use Pianoteq 8 with my Komplete Kontrol keyboard after a period of time where I had hoped that issues would be resolved. Running the plugin works fine but you cannot use the Komplete Kontrol plugin and use any of the Perform knobs. If you switch over to Perform in Komplete Kontrol (either the latest 3.0 version or the older 2.x version) it will cause both the plugin and your DAW to crash. load it up, play all you want but do not touch the knobs. I have seen the issue with the Japanese language before as well but for some reason I don't see that anymore. Currently all of the preloaded CC banks are completely blank except for the name and turning the knob will show it change in Komplete Kontrol but won't reflect in the Pianoteq app. Usually a crash will happen within 30 seconds after that point.
I love playing pianoteq on my S88 Mk2, I would very much like to be able to control it using the KK software and the KK knobs. It's been not working like this for a couple of years now. I am not sure if the problem applies to all versions of KK or only Apple Silicon (which I am using)
I love playing pianoteq on my S88 Mk2, I would very much like to be able to control it using the KK software and the KK knobs. It's been not working like this for a couple of years now. I am not sure if the problem applies to all versions of KK or only Apple Silicon (which I am using)
I think I came across the same issue with Pianoteq8, S88 MK2 with Win11.
I reported this to NI, see https://community.native-instruments.co...ent/121626
I also observe crashes, see my screenshot in that posting.
The support there was fantastic, see the post itself and download the fixed nksf library.
@Modartt support: Please check this above posting and include the fixed library in your next release!
Hi I reported this as a bug - it appears to be a migration problem, while NKS created with the VST2 do open in the VST3 it appears the automation IDs do not translate properly so nothing was working (which was also making it unstable). I had to recreate the template for Pianoteq from scratch with the VST3 then apply it to the factory NKS - the fixed NKS library is available here:
https://www.dropbox.com/scl/fo/p7shlavo...z&dl=0
I can also create a more comprehensive mapping actually, I can see a number of areas where this could be improved
EG https://www.dropbox.com/scl/fi/a4syblxt...j&dl=0
Hi I reported this as a bug - it appears to be a migration problem, while NKS created with the VST2 do open in the VST3 it appears the automation IDs do not translate properly so nothing was working (which was also making it unstable). I had to recreate the template for Pianoteq from scratch with the VST3 then apply it to the factory NKS - the fixed NKS library is available here:
Hi Muze
thanks a lot for creating these. question: where do i need to put these files (on a mac)? thanks and cheers, blomquist
MUZE wrote:Hi I reported this as a bug - it appears to be a migration problem, while NKS created with the VST2 do open in the VST3 it appears the automation IDs do not translate properly so nothing was working (which was also making it unstable). I had to recreate the template for Pianoteq from scratch with the VST3 then apply it to the factory NKS - the fixed NKS library is available here:
Hi Muze
thanks a lot for creating these. question: where do i need to put these files (on a mac)? thanks and cheers, blomquist
For anyone who is also looking for these files, I finally found them here:
/Library/Application Support/Modartt/Pianoteq 8/nks
Cheers, blomquist
Pianoteq 8.2.0 just released. The nks files are still not functional so have to be replaced by the files created by Muze.
Do we have a statement from Modartt about nks integration? possibly nks 2 integration even? is this coming?
cheers, blomquist
8.3 just released and NKS still doesn't work for me - or am i missing something?
i still need to use the upper workaround.
PLEASE modartt-team: work on this, that's honestly annoying to fix this for us for every update you do manually!
I'm using pianoteq 8.2 and now 8.3 in NKS mode on two Komplete Kontrol keyboards, I have a Kontrol keyboard S61 MK2 and a 88MK3 control keyboard.
On both keyboards pianoteq works flawlessly in my studio setup (ableton based). I can select the presets, my own user presets, change almost any parameter (including EQ and hamer hardness, etc.) and can easily switch between the effects in the chain (like for instance when I add an external reverb). Everything can be done on the keyboards itself, you don't need to go to the computer and use the mouse, it's all integrated in the keyboard. I prefer the new MK3 keyboard, it has one large screen and it's so easy to operate. The MK2 works also, but there you have two screens on the keyboard.
Here it never crashes, I can control ableton and pianoteq and for instance record stuff all directly from the keyboard itself. It's then recorded in your daw on your computer.
Great midi controller!
Hi Robinez,
glad to hear, that this works for you - and maybe many others.
On my System (MacOS M1Max) it doesn't work - even after a complete uninstall of Pianoteq 6,7,and 8 and reinstalling 8.3 again
Neither with the Komplete Kontrol Standalone App, nor with StudioOne 6.5 as a vst.
As described above, i also see Chinese Characters when turning knobs and turning knobs does nothing.
You're right: Komplete Kontroll S61 mk3 i a great midi controller - only Pianoteq 8 doesn't work here.
I sent a message to the support in parallel to this message - hope they can help me and others to fix this (and that we don't have to use MUZE's Workaround described above any more - also because actually with the release of the Boesenforfer it is not up to date any more)
Thomas
I'm using pianoteq 8.2 and now 8.3 in NKS mode on two Komplete Kontrol keyboards, I have a Kontrol keyboard S61 MK2 and a 88MK3 control keyboard.
On both keyboards pianoteq works flawlessly in my studio setup (ableton based). I can select the presets, my own user presets, change almost any parameter (including EQ and hamer hardness, etc.) and can easily switch between the effects in the chain (like for instance when I add an external reverb). Everything can be done on the keyboards itself, you don't need to go to the computer and use the mouse, it's all integrated in the keyboard. I prefer the new MK3 keyboard, it has one large screen and it's so easy to operate. The MK2 works also, but there you have two screens on the keyboard.
Here it never crashes, I can control ableton and pianoteq and for instance record stuff all directly from the keyboard itself. It's then recorded in your daw on your computer.
Great midi controller!
Hi Robinez,
glad to hear, that this works for you - and maybe many others.
On my System (MacOS M1Max) it doesn't work - even after a complete uninstall of Pianoteq 6,7,and 8 and reinstalling 8.3 again
Neither with the Komplete Kontrol Standalone App, nor with StudioOne 6.5 as a vst.As described above, i also see Chinese Characters when turning knobs and turning knobs does nothing.
You're right: Komplete Kontroll S61 mk3 i a great midi controller - only Pianoteq 8 doesn't work here.
I sent a message to the support in parallel to this message - hope they can help me and others to fix this (and that we don't have to use MUZE's Workaround described above any more - also because actually with the release of the Boesenforfer it is not up to date any more)
Thomas
Hi Thomas,
I'm using komplete kontrol on windows, so maybe that is something that is different to your situation. There are also some mappings issues with the latest 8.3 nks implementation (8.2 was working fine), but I've reported it and they will fix that in the next update.
regarding your language, the text used in the native suite applications are by default based on your preferred language setting in your native instruments account, did you by any change set that one to Japanese?
you can check it by logging in to your account on the native site and then check the preferred language in your account details:
https://www.native-instruments.com/en/account/
that should be set to English over there as far as I know, you could try that.
Hi Robinez,
ok, checked that - the language is aready set to english and location is set to Germany (correct). So this doesn't seem to be the solution. - But thanks, could have been a simple workaround ;-)
Thomas
TWhunter74 wrote:Hi Robinez,
glad to hear, that this works for you - and maybe many others.
On my System (MacOS M1Max) it doesn't work - even after a complete uninstall of Pianoteq 6,7,and 8 and reinstalling 8.3 again
Neither with the Komplete Kontrol Standalone App, nor with StudioOne 6.5 as a vst.As described above, i also see Chinese Characters when turning knobs and turning knobs does nothing.
You're right: Komplete Kontroll S61 mk3 i a great midi controller - only Pianoteq 8 doesn't work here.
I sent a message to the support in parallel to this message - hope they can help me and others to fix this (and that we don't have to use MUZE's Workaround described above any more - also because actually with the release of the Boesenforfer it is not up to date any more)
Thomas
Hi Thomas,
I'm using komplete kontrol on windows, so maybe that is something that is different to your situation. There are also some mappings issues with the latest 8.3 nks implementation (8.2 was working fine), but I've reported it and they will fix that in the next update.
regarding your language, the text used in the native suite applications are by default based on your preferred language setting in your native instruments account, did you by any change set that one to Japanese?
you can check it by logging in to your account on the native site and then check the preferred language in your account details:
https://www.native-instruments.com/en/account/that should be set to English over there as far as I know, you could try that.
just installed the new 8.3.1 version, and all the knob mapping errors I reported are already fixed in that NKS control implementation, Great job development team!
so now the NKS control plugin works flawlessly again on my system.
Great to hear, that it works on Windows now.
And i have an Update too for the MacOS-Users on Apple Silicon: Here's the answer from Pianoteq Support:
----------
Unfortunately the situation with NKS on the M1 macs is very complicated and a bit hopeless for Pianoteq 8. This is due to the fact that we made a mistake regarding the compatibility of the VST2 and VST3 versions of Pianoteq 8 (NKS is based on VST), and that Komplete Kontrol only supports VST3 when running natively on M1/M2/etc macs, while it still supports VST2 on other platforms. This is why you have issues with the knobs mappings. I’m afraid we will not be able to have a decent solution until Pianoteq 9.
-----------
My Answer back:
-----------
thanks for this kind and honest answer!
Well, as a huge fan of Pianoteq (just upgraded to the Studio-Version to have all Pianos) i’m patient to wait for Version 9.
This shouldn’t be far away… if not around the corner ;-) (next 6-12 months i hope)
So: I really hope that your team works on it and then this bug/issue is definitely „history“ ;-)
------------
--> It seems, we Mac-Users will have wait - and that's OK for me, as long as V9 will solve the issue.
Great to hear, that it works on Windows now.
And i have an Update too for the MacOS-Users on Apple Silicon: Here's the answer from Pianoteq Support:
----------
Unfortunately the situation with NKS on the M1 macs is very complicated and a bit hopeless for Pianoteq 8. This is due to the fact that we made a mistake regarding the compatibility of the VST2 and VST3 versions of Pianoteq 8 (NKS is based on VST), and that Komplete Kontrol only supports VST3 when running natively on M1/M2/etc macs, while it still supports VST2 on other platforms. This is why you have issues with the knobs mappings. I’m afraid we will not be able to have a decent solution until Pianoteq 9.
-----------My Answer back:
-----------
thanks for this kind and honest answer!
Well, as a huge fan of Pianoteq (just upgraded to the Studio-Version to have all Pianos) i’m patient to wait for Version 9.
This shouldn’t be far away… if not around the corner ;-) (next 6-12 months i hope)So: I really hope that your team works on it and then this bug/issue is definitely „history“ ;-)
--------------> It seems, we Mac-Users will have wait - and that's OK for me, as long as V9 will solve the issue.
I'm not on Mac but I applaud this kind of honesty.
Rest assured, I have every confidence that they will fix that for version 9.
I'm guessing they put significant resources into developing the iOS version last time.
Hoping 9 will bring the biggest upgrade in the engine itself since it's original release.
No need for more bells and whistles, or cosmetic makeovers if they could pull that off.
Regardless I really appreciate their way of doing business.