Kore early

[riley4reason]

Just pretend likes it's May 8th and tell me everything!
Riley

[aMUSEd]

How much was it?

[seamoss]

I'd be tempted to leave the folders themselves there in case a future installer looks for them being there).

What I did was just leave the factory stuff there and create/assign a second folder.

oops..

I meant to say, what I would have done is...

sickle, are you able to create scenes and not have samplers (kontakt!) reload samples? this is how forte does this and this is a must for fast scene changes.

forte lets you select all your samplers and sample based vstis in preferences, so that those particular vsti's are not slowing down the scene changing process. this is a must for live use. the trick is that you load your sampler with everything that you need for a set and have the host (kore?) reroute midi channels/ ports etc.


can you comment on this?

[flametop]

Ok, finally installed. Yay!!

Next is the VST scan. That took (as usual) an age, but eventually the Kore control lit and away I go

I'll give a full writeup when I've had a chance to digest just what this thing does. But alrady I can comment..

1) Kore interface. So far, very nice. Even without reading the manual (like I would with all those lights ) i'm zooming around the control.

2) Browser. Wonderful!!! A real database thats very easy to use.

3) Patches. So far very interesting. Some very complex layers.

More tomorrow

[Sickle]

can you comment on this?

Sir, I am unaware of any such activity or operation - nor would
I be disposed to discuss such an operation if it did in
fact exist, sir.

[ugo]

oops..

I meant to say, what I would have done is...

fiend
and here i thought you only had inside info.


-ugo

[Sascha Franck]

Two things:
- The audio interface part of the controller isn't all that bad, really. The drivers allow for low latencies (2ms = 4ms in total on my system), which is nice for USB. And they don't seem to tax the system too much. So it's at least a great solution for mobile stuff.
- While I really, really don't like things to be installed to C: without any option to change that during installation (so NI should change that on future installers), it's a good idea to place the "My Documents" folder somewhere else anyways. Windows allows for this without any extra tools (properties, look for the target location, change it).

[ew]

I'd be tempted to leave the folders themselves there in case a future installer looks for them being there).

What I did was just leave the factory stuff there and create/assign a second folder.

oops..

I meant to say, what I would have done is...

sickle, are you able to create scenes and not have samplers (kontakt!) reload samples? this is how forte does this and this is a must for fast scene changes.

forte lets you select all your samplers and sample based vstis in preferences, so that those particular vsti's are not slowing down the scene changing process. this is a must for live use. the trick is that you load your sampler with everything that you need for a set and have the host (kore?) reroute midi channels/ ports etc.


can you comment on this?

I'll comment instead- yeah, you can. You'll have to load up multiple instances, though. Using performance mode (which is what you'd be doing live), you can set everything up so your unused instances will shut off with program changes.

I'll second Sascha's comments about the audio interface. I was impressed by how well it works. A couple things to be aware of, though; make sure your USB hubs are putting out at least 500 mA per port, and try to have Kore on its own hub. On my machine, the interface sucks up just under 500 mA and consumes about 80% of the hub's total bandwidth.

ew

[seamoss]

I'll comment instead- yeah, you can. You'll have to load up multiple instances, though. Using performance mode (which is what you'd be doing live), you can set everything up so your unused instances will shut off with program changes.

So let me get this straight. I would have to load up a single instance of Kontakt for every instrument I use in Kontakt in order to have different Kontakt instruments per scene?

And what about .....say....Minimonsta. Would I have to load a separate instance of Minimonsta for every scene or do scenes contain information that would enable parameters of that particular vsti to be changed?

Also, what happens to the vstis that are not being used in the scene? Are they turned off? Muted? Do they have to be reloaded?

Thanks!

[Sickle]

oops..

I meant to say, what I would have done is...

fiend
and here i thought you only had inside info.


-ugo

I'm busted.

[ew]

First of all in Kore lingo, the different things happening in a performance are called presets- not scenes.

If you're using Kontakt multi-timbrally, no you wouldn't. Then you'd just load up one instance.

You can always use the realtime controllers to switch parameters or use program changes to change between patches. Otherwise it's the multiple instance route for the most part.

A performance consists of one or more presets changeable either through program changes or automatically by beat/bar or overall elapsed time. The preset consists of the on/off status of each .ksd (instrument), volume, pan, fx slots 1-4 on/off and send levels- that's all that's recalled in a preset. To not use an instrument in a particular preset, you turn it off and store the state of the performance as a preset of that performance. The instrument is shut off, so any inactive instruments don't contribute to CPU load. There's programmable fade in/out times so you have natural sounding transitions in between presets.

ew

[riley4reason]

How was your weekend...with Kore?