Zebra 2 template for NI KORE

[aMUSEd]

I've added Zebra 2 to my pack of templates for NI KORE - can be downloaded here:

http://www.fingermarks.co.uk/music/KORE_Synth_Pack.zip

(also includes templates for a dozen or so other synths - for full details see here:

http://www.kvraudio.com/forum/viewtopic.php?p=2815714)

So far I've only done setups for the Oscs (not FM) and Filters (including XMF) but I need to make a decision about the rest. Since it's a modular I've adopted a one page per module approach but since it has 4 oscs and tons of filters it has taken 10 pages just to model those and since the automatable limit for KORE is 8 pages I'm wondering whether it's worth it to continue and do the other modules or just stop here (most patches won't have all 4 oscs and more than a couple of filters at once though so it's not going to be a problem most of the time) I should do the comb filters at least I think.

However re the Comb filters -each of those would take 2 pages if I mapped every control and personally I feel that would be a pain ergonomically - I could do it but on the other hand I'd prefer (pragmatically) to maybe prioritise the 8 most used controls (in relation to having significant impact on the sound in a live playing context) so I can get them onto one page each but having to think about which ones to use - any suggestions?

I've mapped all params that can be mapped but there's a few like the "Overload" knob in the XMF filter and some of the osc controls that don't seem to expose themselves to VST automation in KORE (and presumably elsewhere?) so I couldn't map those to a hardware knob (they do respond to standard midi learn but KORE doesn't use that).

----

946 parasites

[raikard233]

Thank you! I'll try immediately, i was thinking about doing that thing, but the modularity of Zebra has ever gave me doubt cause the lots of parameters to assign.

[aMUSEd]

Yes I found that daunting but then I realised one page per module might be the best approach when I noticed once assigned to a module KORE is good at remembering that module's assignments even when it's used in different positions in different patches.

How do you think I should tackle the Comb filters - 2 pages each or prioritise the 8 most used params?

Surge is a bit problematic too.

[Howard]

How do you think I should tackle the Comb filters - 2 pages each or prioritise the 8 most used params?

Two pages each.

[aMUSEd]

OK I bit the bullet and did 2 pages for each, and then I also added the shapers and noise oscs too for good measure. It's now up to 18 pages! Not sure how usable that really will be in practice. I've uploaded the single file so people don't have the dl the whole bank again:

http://www.fingermarks.co.uk/music/Zebra2.ksd

I've also found out if I add a mapping for a modulation target KORE can remember it even if I change target - I made an assumption it wouldn't be able to do that. Damn - I might have to add those next (which will add a few more pages and might get complicated).

[aMUSEd]

I've finished with this for now at 27 pages !!

All the oscs and filters are now mapped to KORE controls inc the FM oscs, COMB and XMF filters - most on 1 or 2 pages apiece. Where possible I've also added in modulation assignments as well. I left out very little but some just don't seem to be assignable such as "Keyscale" and a few other osc functions as well as most buttons.

Download from here:

http://www.fingermarks.co.uk/music/Zebra2.ksd

and I've also added the updated file to the Synthpack now it's finished.

I could go on and do all the other modules but there's a limit to how practicable this would be with dozens of pages and in hosts only the 8 first pages are automatable anyway so bear this in mind - you may need to rearrange the page order for some patches to be fully automatable. I've laid out the page order the way it appears in the matrix but the order can be changed on the fly easily enough and even saved as a new patch so it can be called up again for a particular project.

[Urs]

Woah... I don't have Kore, but that sounds like a cool thing!

Thanks,

Urs

[aMUSEd]

You're welcome - makes it more handson playable for some people.

Any reason why there are a few knobs I can't assign (they seem midi learnable well enough)? Would be nice if I could assign buttons too (KORE has 8 assignable buttons per page)

[Urs]

You're welcome - makes it more handson playable for some people.

Any reason why there are a few knobs I can't assign (they seem midi learnable well enough)? Would be nice if I could assign buttons too (KORE has 8 assignable buttons per page)

The reason some parameters are not visible to the host is... some hosts see up to 128 parameters, others see up to 1024... and only some can see them all. Thus I'm always into keeping the number of public parameters small. Hence most menu-parameters and many knobs of lesser importance are kept internal...

oh... and there was a bug on MacOS X that would have weird side effects for AUs with more than 500 or so public parameters... that seems fixed with Tiger though...

Cheers,

Urs

[bluedad]

whoa! thank you for this, my friend! I know that was a lot of work.

[ew]

whoa! thank you for this, my friend! I know that was a lot of work.

Indeed it was. A round of applause from me as well...


ew

[aMUSEd]

Thanks - just a pity KORE (or any other host) can't "see" Zebra's presets list - if it could I could run it mouse free most of the time using KORE.

[raikard233]

I'm trying your koresound with kore2 and i noticed a problem with the morph feature, is impossible to morph with zebra through the A-B-C-D-E-F-G-H snapshot that you can store.
When you morph from a snap to another the sound stops.
After i leave the knob the sound "reappear".
Start form A with sound--->move to B and you haven't any sound"--->leave to B and you hear the B-snap sound.

Other plugins seems to be not affected by this problem.

[Urs]

the morph feature

Hmmm... I can't imagine how that would work... Zebra uses a pretty nifty preset format which doesn't plainly save the parameter values...

Or... is morphing supposed to happen only to the published VST parameters?

hmmm...

Urs

[darem]

the morph feature

Hmmm... I can't imagine how that would work... Zebra uses a pretty nifty preset format which doesn't plainly save the parameter values...

Or... is morphing supposed to happen only to the published VST parameters?

hmmm...

Urs

Kore morphing isn't between two presets, but between different settings of the same preset, for example different filter settings. You don't have to save those in Zebra for the morphing to work, it is saved within the Kore .ksd file that stores all presets.