peterlemer
Logician
NI and I have discovered the following:
With the default keyset, I can enter text freely in the Database search field of Kontakt3.
take the character 'a' which in L8 gets 'Track Automation':
in K3 it gets the letter 'a' in the search field.
IOW, L8 ( or Apple) allows the text entry for K3 to take priority over L8.
but...
If I re-assign 'a' to be 'Arrange' ( to open the Arrange window - something I've been doing for many years), then I cannot type 'a' into K3!
If I try, I open the Arrange window!
So in this case, where I've reassigned a Keystroke, L8 ( or Apple) have /not/ allowed K3 to take priority over L8.
Repeat this problem for all the other keystrokes I have re-assigned!
Solution:
1. Revert to the default keyset or
2. put up with manual searching for sample and instruments in K3
has anyone come across this before?
has anyone found that, despite reassigning their key commands, K3 works well?
what is the best way to report this?
how can I improve the language of the report?
cheers
peter
With the default keyset, I can enter text freely in the Database search field of Kontakt3.
take the character 'a' which in L8 gets 'Track Automation':
in K3 it gets the letter 'a' in the search field.
IOW, L8 ( or Apple) allows the text entry for K3 to take priority over L8.
but...
If I re-assign 'a' to be 'Arrange' ( to open the Arrange window - something I've been doing for many years), then I cannot type 'a' into K3!
If I try, I open the Arrange window!
So in this case, where I've reassigned a Keystroke, L8 ( or Apple) have /not/ allowed K3 to take priority over L8.
Repeat this problem for all the other keystrokes I have re-assigned!
Solution:
1. Revert to the default keyset or
2. put up with manual searching for sample and instruments in K3
has anyone come across this before?
has anyone found that, despite reassigning their key commands, K3 works well?
what is the best way to report this?
how can I improve the language of the report?
cheers
peter