KORE 2 Bug

Hello all,

I ve got a big probleme using Kore 2 (live or studio...)
(Mac Book pro Intel OS 10.4.11 / Komplete 5)
When i move from a preset to another , 1O% of the time, the sounds who should play are "muted" like. I made million of test... The simplest: 2 Koresound "Sound 1 and Sound 2" cointaining each two channels. Each channel contain 1 Sound A and B.So I got sound 1A and 1B in the first Koresound and sound 2A and 2B in the 2e Kore sound. OK ?
Then I make 54 preset:
preset 1: Sound 1A playing Sound 1B disabled (X on the channel) Sound 2 disabled
preset 2: Sound 1B playing (Sound 1A disabled and Sound 2 disabled)
preset 3: Sound 1 disabled , Sound 2A playing
etc...

Then when I jump from any preset to another, I have this "mute" problem very often

Did somebody has got the same problem ?

Thanks
Xavier

 

Nested Koresounds?

Hi Xavier, I think I have had this issue you are talking about. Are you using a nested Koresound? In other words, do you have a koresound within a koresound? I have attached a picture of what I believe you have described. 2 Sound Channels that each contain additional koresounds and the goal is to effectively switch between them all without mysterious 'no sound' issues?

If so, I had this issue when designing the performance file for INTERPOL. This is also described in the CDM article here. Search that page by 'nested' and you will find the relevant section.

As you have found, using source channel bypasses is not consistent on recall and causes 'no sound' issues for 'daughter' sounds within nested channels. The solution or workaround is to avoid using source channel bypasses and instead use the sound bypasses themselves. In other words bypass/disable each individual sound instead of the whole channel. However, Kore by default does not include the sound bypasses in its channel pages. This means that performance presets will not by default recall these settings. Therefore, you must select the top level 'mother' koresound and create a new USER control page. Don't select the channel at the top with the header, but select the top level sound of interest. There is a hierarchy of pages you can review in the sound manager editor so try to make the user page in the right place by selecting the top sound.

Once you have a user page created, assign the buttons of that page to the sound bypasses down below(not the channel bypasses). The article shows this as well as the attached image. Next, move up top to the next 'mother' channel and select the next 'mother' koresound and do the same for its 'daughter' sounds by creating a new user page with bypasses. You might label channels, sounds and bypasses properly for organization as shown in both article and image.

Now that you have user pages setup for the nested koresound bypasses, I would recommend this next trick. Begin by creating an ALL OFF performance preset in position 1. Then, every time you need to create a new performance preset, you start with this one knowing there are no dingleberry sounds left enabled. You will find overall that this method of switching your nested sounds is entirely reliable and avoids 'no sound' issues.

Lastly, my next important tip is very important and has to do with 'new' content or plugins you may add to your kore matrix. It is imperative that you begin this whole process of designing your setlist or performance presets with everything loaded and instanced that you will use. Try and predict what plugins will be required and load them upfront. If you make performance presets, and then add a new plugin, the existing presets are completely ignorant of this new resource. In your switching scheme, you must explicitly and manually disable the new resource in all the 'older' presets to stamp them with the new information. Typically, the new resource should be disabled in all the older presets so as not to corrupt or alter their sound. Kore is not intelligent enough, yet, to handle this conflict. For every older preset, you must toggle the bypass of the new resource saying hey kore, you better F&^%$ make sure this is F(*&% turned off when I want to play this preset. Do you understand? Go to the older presets and click the new resource ON, and then OFF again to 'stamp' that state to the older preset, then STORE that older preset updating it to know about the new resource.

The consequence of this means that building your setlist or performance preset list progressively is dangerous and it might make you lose your mind if you don't understand what is happening. For every new resource you add, you may be faced with increasingly more manual disable 'stamps' to make on older 'ignorant' presets. Therefore, try as best you can to plan your sounds and requirements upfront, load them, and make your performance presets based on this.

Hope this helps and happy holidays!

jonathan adams leonard
Keyboard and Midi Tech INTERPOL
Lead Specialist Synthax Inc.
RME | AXON | ALVA

 

Thanks, Jonathan =)

By the way, give me a call one of these days...

ew