Automation problem using the morphing buttons

Hope I can explain this okay, but I'm having problems getting the Koresound variation buttons to automate correctly within Cubase SX 3. I have found the only way that I can get the sound variations to automate is by assigning one of the morphing buttons A-H to a knob on a blank User Page (at the performance level). This knob then correctly jumps in increments corresponding to the 8 sound variations when the 8 buttons are pressed (provided the Kore controller is displaying the morphing page).

This would be fine if only Cubase would then record these button presses when the track is armed to write automation. Although the knob with the assignment moves when the buttons are pressed to the correct letter (as well as moving on the morphing page), Cubase will not pick this movement up as an automation. Bizarrely, it will only detect automation of the knob when moving it in the software with the mouse, showing that Cubase detects the automation ID for that particular controller within Kore.

I have tried unsuccessfully to change settings in the automation list (I know that the X and Y morphing settings are auto assigned to the first 32 automation slots for the host), I've tried deleting them here but to no avail. Other button assignments automate absolutely fine in Cubase, but there seems to be no 'level' you can go into that shows the sound variation page on Kore, so I'm stuck as to what I am doing wrong.

Hope someone can help, as I feel this would be a really powerful feature if only I could get it to work properly!

 

Has nobody else found this problem when automating within a host, help would be very much appreciated!

 

i'm interested too...I didnt get the automation working either...That sucks...

 

Working fine in Podium, Sonar and Tracktion.

 

I'm away from my music machine at the moment (like, MILES away) but I've recorded morph knobs with no problem. In fact, the piece of music I'm working on at the moment owes its existence to recorded morphs. If you want details of my setup (and working practise) let me know and I'll get back to you when I get to the studio (which the wife longingly refers to as 'the dining room').

 

Thanks for the responses, it is not that I cannot get the automation working with two of the controller knobs automating the x and y of the sound variations, this is fine in Cubase, but I want to take that a step further and automate the eight buttons to cycle through the eight sound variations (for controlling things like drum patterns live). So far I can use the buttons to do this, but cannot get Cubase to record any automation that recalls when the buttons have been pressed. Not sure if it is just me or if anyone else has had any success doing this.

 

i have had a similar problem. i can only record automation for morphing when i slide between the A-H buttons. I can NOT record when i press the buttons for 'step' transitions.

i posted this problem months ago, and no one responded.

 

I too have been unable to record button presses. I bypassed the problem by using the knobs and editting the result OR by simply drawing in the required change. Possibly not as elegant as simply pressing a button and recording but, for me, the end is all.

 

Thanks for the responses, I raised a ticket with NI when I first posted this thread and I have finally received a response about this problem.

"This is a known bug of Kore 2 and will be hopefully fixed with a future update. Unfortunately I can't provide you with a more detailed information.

Your NATIVE INSTRUMENTS Support Team"

 

Hi Kenny, I have a similar problem in Logic 8. Sometimes the automation works, sometimes it doesn't. I do find that if I just use a komplete 5 instrument, it works. Shame the I can't automate sounds exclusive to Kore 2.

 

Any comments from the NI team if the bug will be fixed soon? It would be very nice if one could record the sound variations button presses. fast rhythmic preset switching can produce very cool sounds!

 

If I had any news, I'd tell you.

ew

 

the button presses don't work for me either, in live 7. after a few hours of wondering "why doesn't this sound cool, like when i recorded it!"
it's because the button presses won't automate.
if i wanted to draw animation, i would take an art class.
i want to record a performance with kore, too bad the software is incapable of capturing a performance.
kore claims to be an instrument due to the expressiveness of these knobs, and the software developer's failure of exposing it's automation capabilities prevent it from being used in a (professional) production environment.

perhaps the morph button press state can be emulated by switching presets (defining which grid square is activated per preset selection).

but then again, that defeats the purpose of having buttons on the hardware, doesn't it!

everytime i try to use kore it just prevents me from doing what i am supposed to be doing.

edit: i just checked and the preset feature doesn't remember morph button state! fail!

 

i'd like to bump this thread.

this still has not been fixed in 2.1.

 

From what I've heard, Matt, it may not be. Why? It's due to how AU hosts treat x/y values generated from a button.

ew

 

bummer, ahh well :-(

 

Doesn't Alchemy exist as a AU though? It seems to manage fine with an almost identical system. Even if it is an AU problem why should the majority of users miss out because of a failing of one format?

 

Yeah, it does- and yes, it makes me wonder what's going on. I should ask Cornelius to contact Ben; I know they've talked on numerous occasions.

ew

 

Just to add - and this is another reason I think it's strange not to support this - not all KORE Sounds using the morph pad do smooth transitions - there are quite a few in the KORE library itself that rely on button presses or clicks on the square to switch pad - in fact morphing is an option in the pad (on right click). How then is one to automate those switches? It seems a bit of a waste of time having them (at least the best one can do - as I do at the moment - is to record straight to audio but that rather gets away from the whole point of having them a midi based solution)

 

Well this is very strange - it turns out that there is one app that DOES support automation of the buttons in Kore 2 - Acid 7. God knows why when nothing else does (and I have tried everything I can lay my hands on legitimately) but it records the button presses perfectly (even though it's not the easiest app to setup to work with softsynths) - just a pity it has such a horrible interface and is so buggy

The big question is what is Acid doing that other apps are not? (especially since NI deny that it is even possible) - if that could be replicated in other hosts this might be very useful.