• SONAR
  • Kontakt 5 full version problems in Sonar.
2018/06/09 02:23:10
z1812
Hi All,
 
Early this week I bought Komplete 11 during the 50% off sale. I upgraded from Komplete 6. Kontakt 4 came with Komplete 6 and it was working well in Sonar Platinum.
 
I have both Sonar Platinum and Presonus Studio One 3 professional. Kontakt 5 was installed from Native Access. It works perfectly in Studio One without any problems at all. However in Sonar there are some problems.
 
From Komplete 11 I have only installed Kontakt 5 so far. Here are the problems I would appreciate help with. 
 
The most important first. I prefer to use Sonar so having things work properly in it is important for me.
 
1. In Sonar, when I open up Kontakt, I can only produce sound using my keyboard controller if I use the midi omni setting on my sonar track and also on the Kontakt instrument. I hear sound and see the track level indicator moving.
 
Individual midi channels do not work with my keyboard controller.  The signal is not getting to the track, as I see the level indicators are not working and no sound to the speakers. Naturally I want to use different channels for each instrument. I can always get sound from the Kontakt software keyboard that displays under the instrument. But not from my keyboard controller.
 
I think the problem is in Sonar as there are no problems in Studio 1. I have no idea why this is happening. All worked well until I installed Kontakt 5 ( full version ).
 
This problem is only apparent when using Kontakt. All other instruments are working well in Sonar.
 
Any help would be much appreciated. I have been trying different approaches for days and now and I have not had any luck.
2018/06/09 04:06:21
vladasyn
Your MIDI controller should send MIDI data on certain MIDI tracks. Your Sonar Track needs to be set to let's say MIDI Track 5, your Kontakt instrument should receive on Ch 5. The fact that you get signal on Omni tells that it receives on "all" channels, but not on individual because you have mismatch. 
2018/06/09 05:19:46
Daibhidh
Have you tried installing the latest version of Cakewalk to see if that solves your problem?
2018/06/09 15:04:52
z1812
vladasyn
Your MIDI controller should send MIDI data on certain MIDI tracks. Your Sonar Track needs to be set to let's say MIDI Track 5, your Kontakt instrument should receive on Ch 5. The fact that you get signal on Omni tells that it receives on "all" channels, but not on individual because you have mismatch. 

 
 
Thanks for your reply but I do have the channels matched and it does not work.



2018/06/09 15:07:47
z1812
Daibhidh
Have you tried installing the latest version of Cakewalk to see if that solves your problem?



No I have not tried that but I may have too. I am still a little reluctant to install bandlab.
2018/06/09 20:05:52
abacab
1. In Sonar, when I open up Kontakt, I can only produce sound using my keyboard controller if I use the midi omni setting on my sonar track and also on the Kontakt instrument. I hear sound and see the track level indicator moving.
 
Individual midi channels do not work with my keyboard controller.  The signal is not getting to the track, as I see the level indicators are not working and no sound to the speakers. Naturally I want to use different channels for each instrument. I can always get sound from the Kontakt software keyboard that displays under the instrument. But not from my keyboard controller.

 
You will need to set the controller to transmit on the desired MIDI channel.
 
For example, if the instrument you want to play in Kontakt is set to channel 2, then set your controller to transmit on channel 2, and either leave the Cakewalk MIDI track input set to Omni, or set it to 2.
 
If you leave the Cakewalk track input set to Omni, it will pass data on whatever channel your controller sends on to the instrument.  However, if your controller is sending on 1, changing Cakewalk's input to channel 2 will not alter the MIDI data coming from your controller.  It will remain as sent from your controller, resulting in silence from your Kontakt instrument listening on channel 2. The track level is only showing that data is present, not which channel it is on.
 
By changing the Cakewalk track input to anything but Omni, it will only allow the selected channel to pass, filtering out the others.  But it will not re-map the channel coming from your controller.
2018/06/09 20:35:14
abacab
And I checked in Studio One.  Changing the MIDI channel in the S1 track appears to re-map the MIDI input sent from the controller.
 
I tried it in Reaper, and it works just like Cakewalk.
 
So the bottom line is that you cannot expect all DAWs to work exactly the same.  You will need to be aware of the differences and take them into account.
2018/06/09 21:04:12
z1812
abacab
And I checked in Studio One.  Changing the MIDI channel in the S1 track appears to re-map the MIDI input sent from the controller.
 
I tried it in Reaper, and it works just like Cakewalk.
 
So the bottom line is that you cannot expect all DAWs to work exactly the same.  You will need to be aware of the differences and take them into account.



Thanks for your response. Are you saying that it works that way only for Kontakt 5 because all my other VST's work normally without considering the controller channel. It is automatic just like Studio1. 
In fact Kontakt 4 worked seamlessly in Sonar as well.
 
 
2018/06/09 23:02:27
abacab
I really couldn't see how DAW MIDI input handling on the front end could be VST dependent on the back end, so I tested this with Cakewalk and a few other plugins that I have that are multitimbral and multi-channel MIDI.
 
SampleTank 3 = same as Kontakt 5
AIR Xpand!2 (uses channels 1-4) = same as Kontakt 5
Dimension Pro (in multitimbral mode using channels 1-4) =  same as Kontakt 5
AIR Structure 2 = same as Kontakt 5
 
Only VSTs with multitimbral mode need to see a specific MIDI channel in order to route the MIDI to the proper instrument slot.  I suppose most other VST instruments are actually Omni by default.
 
I don't have Kontakt 4, so cannot comment on that one.  But it seems that the MIDI channel selection in Cakewalk is consistent with any multitimbral VSTi that I tested.
 
I grabbed a few other plugins that are not multitimbral, and they could care less what channel I am sending MIDI on, as long as the Cakewalk track was set to either Omni, or the actual channel that my controller was set to transmit on.
2018/06/09 23:14:55
z1812
abacab
I really couldn't see how DAW MIDI input handling on the front end could be VST dependent on the back end, so I tested this with Cakewalk and a few other plugins that I have that are multitimbral and multi-channel MIDI.
 
SampleTank 3 = same as Kontakt 5
AIR Xpand!2 (uses channels 1-4) = same as Kontakt 5
Dimension Pro (in multitimbral mode using channels 1-4) =  same as Kontakt 5
AIR Structure 2 = same as Kontakt 5
 
Only VSTs with multitimbral mode need to see a specific MIDI channel in order to route the MIDI to the proper instrument slot.  I suppose most other VST instruments are actually Omni by default.
 
I don't have Kontakt 4, so cannot comment on that one.  But it seems that the MIDI channel selection in Cakewalk is consistent with any multitimbral VSTi that I tested.
 
I grabbed a few other plugins that are not multitimbral, and they could care less what channel I am sending MIDI on, as long as the Cakewalk track was set to either Omni, or the actual channel that my controller was set to transmit on.


Thanks for your response. It seems that a few people are having problems with Cakewalk, controllers, and Native instruments products.
http://forum.cakewalk.com...walk-CxB-m3759903.aspx
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account