Flexibilty with controller numbers?
I haven't yet found a way to change the default Controller numbers, if there is any. I have a keyboard with 8 sliders all set up to work with my 17GB template, and I don't want to change the assignations for just one new instrument. Is it possible to change the defaults, like with The Trumpet?
D
D
Comments
We can further discuss this topic if you wish.
Giorgio
D
I understand you wanting to protect your technology, but isn't that possible without totally disabling the ability to edit instruments? Surely only the macros you use and the samples themselves need to be protected. Not everything.
D
Daryl wrote: I understand you wanting to protect your technology, but isn't that possible without totally disabling the ability to edit instruments? Surely only the macros you use and the samples themselves need to be protected. Not everything.
echoecho wrote: I too would like the flexibility to change CC's. I prefer to have vibrato on aftertouch for example.
This has unfortunately nothing to do with protection of our technology. Plainly stated, Kontakt scripts do not recognise aftertouch as incoming midi data. This is a well known issue, never addressed by NI.
As a consequence, since our instruments are script-based, we can't use aftertouch as a Midi CC. This is the sad truth.
As to remapping, please note, that, differently from traditional sample-based libraries, our virtual instruments use several CCs. Providing remapping facilities for each CC would be most inconvenient.
We therefore need to ask our customers to identify the most essential CCs, for which remapping is deemed essential.
If this turns out to be feasible, we will be happy to satisfy your requests.
Best,
Giorgio
Daryl wrote: I understand you wanting to protect your technology, but isn't that possible without totally disabling the ability to edit instruments? Surely only the macros you use and the samples themselves need to be protected. Not everything.
echoecho wrote: I too would like the flexibility to change CC's. I prefer to have vibrato on aftertouch for example.
This has unfortunately nothing to do with protection of our technology. Plainly stated, Kontakt scripts do not recognise aftertouch as incoming midi data. This is a well known issue, never addressed by NI.
As a consequence, since our instruments are script-based, we can't use aftertouch as a Midi CC. This is the sad truth.
As to remapping, please note, that, differently from traditional sample-based libraries, our virtual instruments use several CCs. Providing remapping facilities for each CC would be most inconvenient.
We therefore need to ask our customers to identify the most essential CCs, for which remapping is deemed essential.
If this turns out to be feasible, we will be happy to satisfy your requests.
Best,
Giorgio
Thanks for the explanation. That seems fair enough, although it would seem that if the instrument weren't protected to the extent it is, a regular LFO could be set up by the user with whatever controller we wanted. There doesn't seem to be any compelling reason to use a macro for the vibrato other than for the controller info to appear on the display.
Daryl wrote: I understand you wanting to protect your technology, but isn't that possible without totally disabling the ability to edit instruments? Surely only the macros you use and the samples themselves need to be protected. Not everything.
This has unfortunately nothing to do with protection of our technology. Plainly stated, Kontakt scripts do not recognise aftertouch as incoming midi data. This is a well known issue, never addressed by NI.
As a consequence, since our instruments are script-based, we can't use aftertouch as a Midi CC. This is the sad truth.
As to remapping, please note, that, differently from traditional sample-based libraries, our virtual instruments use several CCs. Providing remapping facilities for each CC would be most inconvenient.
We therefore need to ask our customers to identify the most essential CCs, for which remapping is deemed essential.
If this turns out to be feasible, we will be happy to satisfy your requests.
Best,
Giorgio
Hey, don't put words in my mouth. I never said that.
Regarding the CCs, I'll have a think over the next few days and see which ones cause the most workslow.
D
Giorgio
I wanted to make a suggestion in the same direction but it has to do with wind controllers and The Trumpet.
I just got my Akai EWI USB wind controller 2 days ago and I´m quite happy how The Trumpet behaves with this controller. I fact I believe a wind instrument should always be played with a wind controller
I mentioned it in another thread. It would be nice, if you could route controller numbers to the articulations triggered by the keyswitches (the Chris Hein Horns do provide this). The wind controllers do send out assignable #cc numbers and it would be nice if these could trigger effects like falls, doits or shakes. The Akai (for example) has 2 pitch bend plates which are assignable to any #cc number. This would be ideal to trigger those effects. What do you think?
The only disadvantage of using the Akai with the trumpet is that you loose this wonderful semi-valve portamento which is controlled by key velocity. Is there any idea how to preserve this? I´m not sure how The Trumpet interpretes the Akai controllers anyway. The Akai sends out #cc2 which is used for velocity (that´s what I presume) and channel aftertouch (which normaly modulates volume. From what you said above, Kontakt scripts don´t understand aftertouch?? So how is the volume after the initial velocity information modulated?
If the Aftertouch information isn´t used, I could change it to #cc5 to control portamento. It just came into my mind, maybe this might work.
Best regards
Raindog
The Trumpet, in Windcontroller mode, is supposed to work with portamento time controlled by CC5. Thus, it makes perfect sense changing the Akai setting to send CC5 instead of aftertouch.
As to your other question, I'm a bit unsure. Do you mean controller-to-note mapping to activate the KS?
Plase let me know how my suggestion works. Our beta testers using this setting reported satisfactory results.
Best,
Giorgio
The Trumpet, in Windcontroller mode, is supposed to work with portamento time controlled by CC5. Thus, it makes perfect sense changing the Akai setting to send CC5 instead of aftertouch.
As to your other question, I'm a bit unsure. Do you mean controller-to-note mapping to activate the KS?
Plase let me know how my suggestion works. Our beta testers using this setting reported satisfactory results.
Best,
Giorgio
Hi Giorgio,
I´ll try that out tonight (aftertouch -> #cc5). Sounds very promising.
Yes, I meant controller-to-note mapping. Chris Hein has this implemented into his horns. Various controllers can (regardless of the controller value) trigger sound effects just like keyswitches. This means, if you activate #cc 3 (just an example) it triggers falls or doits or growl in an all or nothing manner.
best regards
Raindog