Topic: A challenge – Kore automation

Yes I am. I really meant it just ignores them. So do most hosts but as you can see Acid manages it somehow and just using normal automation (in touch or latch modes).

Just to help explain the problem here is an image of Kore 2:

http://www.spincity.nl/images/Kore2_Composite_white.jpg

The Morph pad is the 4×2 rectangle that records 8 states (patch variations) and enables one to morph smoothly between them using either the mouse of the hardware controller. You can also snap instantly to a square using mouse clicks or button presses (you see the buttons on the Kore hardware – each corresponds to a square).

Most hosts including Podium can record the smooth changes between params in the Morph Pad (whether done with the mouse or hardware) but apart from Acid all the rest cannot seem to record the fast snaps using the buttons or mouseclicks approach. Fast snaps are useful in performance though as you can use them as fast patch changes or for more dramatic effect than the smoother changes.

Kore uses standard VST (host) automation to send information to the host – not midi cc (although it can do that too) if that’s any help.

@Zynewave wrote:

Is it the same VST parameter number(s) that gets recorded both when using the morph pad and the quick buttons?

If so, then I’m guessing the problem lies with the way that Kore uses the VST BeginEdit/EndEdit commands to notify about parameter changes. These commands are used to allow the host to ignore automation playback as long as the user has grabbed a control in the plugin. That it works in Acid could be because Acid ignores the BeginEdit/EndEdit system. Just guessing. I also read in your linked topic that NI responded with “This is a known bug of Kore 2 and will be hopefully fixed with a future update”.

Yeah but later on someone else from NI states that a fix is hard without breaking AU compatibility (for some reason) so it might be a long time coming. Clearly though Acid is recording something (even if it’s due to Acid not sticking to specs – that would be ironic)

Yes it does use the same param ID (you can see in the picture for comparison I recorded some button presses then a stretch of smooth morphs to check this and it uses the same envelope for both – e.g. one is designated param 21) – there is a demo version if you want to investigate (you won’t need the hardware – you can replicate the button presses by clicking on the square as opposed to dragging between them)

thanks