What do you think of Kore 2?

[ew]

I actually reported this on the NI forums a while ago. The presets all import but they are one off - the name doesn't match the actual preset. Seems to be something with Albino though and not Kore.

Oh yeah- I remember that. It's a case of 0-127 vs 1-128. Thanks for the memory jog

Is it working in Pro-Tools 8 yet ?

PC or Mac? Most of the issues I've heard with PT are on the Mac side. If you're running PT8 and Leopard, the upcoming 2.1 update should fix any issues there.

ew

[koalaboy]

As a VST automation based controller Kore has higher resolution than Nocturn for stuff opened in Kore and the knobs have a better feel. The next update will also enable it to function as a midi controller for devices without them needing to be wrapped in Kore but then of course the resolution would be the same as Nocturn or any other midi controller

Ah, useful to know. I must admit, I'd be concerned if the knobs felt worse than the Nocturn though

[auricle]

Whether it's better than the Nocturn as a controller I can't say- I've never used a Nocturn.
However, with Kore you don't have the wrapped .dlls that you do with Automap, which can be a plus depending on the host, etc.

ew

Very true - I guess though, I could map the Nocturn via MIDI to Kore, and ignore all the automap stuff ?

I've also used an Automapped VSTi (using a Remote SL keyboard) inside of Kore 2 and everything worked Not sure how useful it would be but at least it's possible.

[Gribs]

I have Komplete 6 already.

Doh! I meant 5 of course. Note time of my post. Note complete lack of coffee in veins...

[Gribs]

I am much more interested in loading, using, and organizing presets that I have made or modified. Outside of NI's stuff I happen to like Blue, CronoX, and Alchemy a lot. It would be nice to have Omnisphere linked up too but it is out there in its own universe (Omniverse? Unisphere?).

[ew]

I am much more interested in loading, using, and organizing presets that I have made or modified. Outside of NI's stuff I happen to like Blue, CronoX, and Alchemy a lot. It would be nice to have Omnisphere linked up too but it is out there in its own universe (Omniverse? Unisphere?).

You can load, save and organize presets for all of those (including Omnisphere); Blue's the only one that you'll be able to batch import, though. The rest would be one at a time.

ew

[placeboemotion]

Whether it's better than the Nocturn as a controller I can't say- I've never used a Nocturn.
However, with Kore you don't have the wrapped .dlls that you do with Automap, which can be a plus depending on the host, etc.

ew

Very true - I guess though, I could map the Nocturn via MIDI to Kore, and ignore all the automap stuff ?

I've also used an Automapped VSTi (using a Remote SL keyboard) inside of Kore 2 and everything worked Not sure how useful it would be but at least it's possible.

Grrrr. Maybe I should not have bought that Novation Remote (in lovely green no less). The Kore2 deal with the included electronic experience is indeed a big teaser, but I have still not understood what I am missing by not using the Kore2 physical controller? (Apart from the fact that the knobs and buttons on the screen would match the layout on the controller) - or is there that much info on the controller's screen

[ew]

Grrrr. Maybe I should not have bought that Novation Remote (in lovely green no less). The Kore2 deal with the included electronic experience is indeed a big teaser, but I have still not understood what I am missing by not using the Kore2 physical controller? (Apart from the fact that the knobs and buttons on the screen would match the layout on the controller) - or is there that much info on the controller's screen

Higher resolution- 512 steps vs the 128 of MIDI automation. Browsing the selected sounds folder from the controller- unfortunately, you can't browse between locations from the controller as you could with Kore 1.

The controller shows the 16 controls for the selected page (8 knobs and 8 buttons) with a semi-descriptive abbreviation depending on the parameter's name (or what you renamed it). Touching a control gives you the full name of the parameter and the value.

ew

[idobs]

Batch import is over rated anyway. The whole point of Kore is to act as a Sound design platform enabling you to create complex multi layered Sounds from a Library of smaller building blocks and to search for the right sounds to use for this based on attributes. If you batch import how could you have attributes for what you import? - to create those you would still have to go through each and tag them afterwards which would be as time consuming as doing it one-by-one anyway. Best process is to only import your favourite patches - tag them in great detail (to create rich, searchable data) and add controller mappings to them as well (to use with the Kore hardware).

You're scaring me away from Kore2! This sounds like a homework project


Actually, your comment is very useful for me - I thought that using Kore2 for other synths would be my main usage, but maybe I should look at the other aspects of Kore2 more...

Thanks,
-Ido

[aMUSEd]

Batch import is over rated anyway. The whole point of Kore is to act as a Sound design platform enabling you to create complex multi layered Sounds from a Library of smaller building blocks and to search for the right sounds to use for this based on attributes. If you batch import how could you have attributes for what you import? - to create those you would still have to go through each and tag them afterwards which would be as time consuming as doing it one-by-one anyway. Best process is to only import your favourite patches - tag them in great detail (to create rich, searchable data) and add controller mappings to them as well (to use with the Kore hardware).

You're scaring me away from Kore2! This sounds like a homework project


Actually, your comment is very useful for me - I thought that using Kore2 for other synths would be my main usage, but maybe I should look at the other aspects of Kore2 more...

Thanks,
-Ido

Lets just say I've moved away from seeing it as a preset librarian for all my presets (all those many thousands potentially) to being a librarian for sounds I actually want to use and a way of having them literally at my fingertips for use in sound design and performance.

[ew]

Batch import is over rated anyway. The whole point of Kore is to act as a Sound design platform enabling you to create complex multi layered Sounds from a Library of smaller building blocks and to search for the right sounds to use for this based on attributes. If you batch import how could you have attributes for what you import? - to create those you would still have to go through each and tag them afterwards which would be as time consuming as doing it one-by-one anyway. Best process is to only import your favourite patches - tag them in great detail (to create rich, searchable data) and add controller mappings to them as well (to use with the Kore hardware).

You're scaring me away from Kore2! This sounds like a homework project

It is. Tagging and batch import are the things I use the least in Kore.

Actually, your comment is very useful for me - I thought that using Kore2 for other synths would be my main usage, but maybe I should look at the other aspects of Kore2 more...

?

Who says that because you don't do attribute tagging and batch import, you can't use Kore with other synths? What both aMUSEd and I do is use template .ksds for each plugin, and load the patch from the plugin. You've mapped the controllers out with the template; that's the important part IMO.

Why I like Kore are such things as 512 step resolution, multiple scalable targets for the same controller, a unified controller layout and things like that.

ew

[aMUSEd]

Yeah it's a great central place from which to work with all your synths and effects. In fact in several of my hosts I have dispensed entirely with scanning in my whole VST folder and just load Kore to play my VSTs with - I have templates for nearly all my synths and effects with controller mappings set up for playability. That's good for stability and faster loading in the host, and it means most synths can be played with the same common controls and a common interface (and if you have the controller largely without even needing to look at the screen).

My points were just in relation to the "librarian" side of things where I think it pays to be more selective about what one imports rather than importing whole soundbanks with hundreds of presets - that is largely unnecessary from a performance perspective and even if you do want to use it as a librarian a good library should be filled with good books you mean to read and use and that you can find easily, not any old crap bunged on shelves without any sorting or organisation.

[Echoes in the Attic]

Why I like Kore are such things as 512 step resolution, multiple scalable targets for the same controller, a unified controller layout and things like that.

ew

Don't forget the morphing and layering!

[koalaboy]

So more questions then.

Does this mean, I can install VSTs all over the hard disk without caring, and Kore into it's own directory... then, just let my host find Kore, and I load the other VSTs into Kore (which remembers where they came from), setup the sounds (from multiple VSTs), FX and controller mappings, and save all this as a preset in Kore ?

If I don't save it as a preset in Kore, is it stored in the 'preset' my host will see Kore as having, so when I reload the project this will just work ?

If I have a kore preset and one of the VSTs I was referencing has moved, does Kore prompt me to point to it's new location ?

Does Kore support OSC ?

I'm getting worried for my wallet right now...

[ew]

Does this mean, I can install VSTs all over the hard disk without caring, and Kore into it's own directory... then, just let my host find Kore, and I load the other VSTs into Kore (which remembers where they came from), setup the sounds (from multiple VSTs), FX and controller mappings, and save all this as a preset in Kore ?

Nope. Kore only allows for one plugin folder on Windows; on a Mac, there's only a couple places it can be, so all of them are included.

If I don't save it as a preset in Kore, is it stored in the 'preset' my host will see Kore as having, so when I reload the project this will just work ?

Yep

If I have a kore preset and one of the VSTs I was referencing has moved, does Kore prompt me to point to it's new location ?

See above. Where are you going to move it to?

Does Kore support OSC ?

Not at the present. That was supposed to be part of a v1 update, but it hasn't happened yet

ew