And this is done - can't find a way to usably map the dropdowns though - tried bumping up knob resolution, using relative learn mode, numerical input etc but they just tend to jump too much to be usable with knobs. https://dl.dropboxusercontent.com/u/5646041/Kore Templates/2016/Kore templates April 2016/Spire 1.ksd
oh thank god, everything still works fine in the serum factory library .ksd's with the old template in the new version, I was afraid it would screw everything up like what happened with Z3ta2. and yeah like I was saying, multi switches are desirable but only when the context allows it, it usually takes up a lot of button space, and normal buttons have priority obviously, though exceptions can be made with unimportant buttons, they can be put in a settings page instead if that works out... gonna go try out spire now. gotta love demos that use the same dll as full version. fun fact: the Tantra template (biggest FX one possibly) was done on the demo.
In PunchBox, you can't change modes from the controller (like in SDRR for example), which annoys me to no end. As d16 don't have a history of heeding my valuable advice about their incessant un-automatable buttons, I decided to make a different template for each of the modes. it does make for cleaner looking integrations at least. then you can isolate a mode from the browser. it won't save the browser selection with the patch, again, annoyingly.
Quick question guys, how do I use the template files? Just drop them in a user folder for Kore to scan? Or.. ?
yep, just put them in the User Folder. you can make other folders in there to categorize. then you set your browser to show Path, and you'll see User Sounds with your folder hierarchy in it.
Or you can add them to the database cache folder so they appear in the plugin menu https://www.native-instruments.com/...kore-templates-to-the-right-click-menu.77908/
I did that and the ones that worked are amazing ! thanks so much for all your work to all involved. i don't understand why some of them didn't work though. I have the plugins, but they just don't get picked up. Maybe I need to rescan?
if you have an AU plugin and the template was saved with the VST, it won't work. also it can't be vst3, 2.4 or below. there are also a few cases of incompatibilities due to version updates...
Thanks, there are no AU plugins or VST3 or 2.4 below,I think it must be down to version updates. Sorry to ask so many questions, but I love the reaktor KSD's that came from NI, is there a way to extract presets as KSDs automatically, as some of my ensembles have tons of presets.
right click on your Reaktor insert > Import Plugin Presets and yeah to be clear I meant that vst 2.4 is the latest supported version for plugins. from vst 3.0+, kore can't see them.
Before you do that, if there isn't one already, make sure you have mapped the ensemble knobs to the hardware and saved that as a template, that way all saved presets will be mapped for that ensemble.
Sorry guys, I must be missing something here. I load Reaktor into Kore, in the source area. I then add my ensemble to it, then I right click and choose (Import plugin presets) it whizzes through counting up to 128 (saying empty in each), but there are no presets afterward just 1 that says empty. The ensemble knobs seem to be mapped already when I add the ensemble in?
I have it now, sorry. The ensembles that don't show snapshot entries in the top bar, won't save presets (even though there are snapshots). The ones that do show snapshots in the top bar, work and save.
The ones that don't show them in the top bar need the ensemble snapshots to be set as snapshot master. That's because sometimes an ensemble will contain more than one set of snapshots (eg if it contains an instrument and effect each may have their own snapshots as well as snapshots on an ensemble level) so Kore needs to know which set of snapshots to import. Most recent ensembles will have this set but older ones don't always.
Thanks for the extra information, I wouldn't know how to make a snapshot as a master, but it doesn't matter too much, as most of the ensembles I'm getting the presets from are compatible. "saved that as a template, that way all saved presets will be mapped for that ensemble." how do I save as a template? I did read earlier here that you put template in the vendor field and have template as part of the title. Could you expand on this if that's ok ?
A template just means a Koresound setup with params mapped to the controller, that can then be used as a template for all other presets saved with it. It's not a special format, just set your first patch up as you want all subsequent patches to be mapped and save it (eg Carbon template etc) then do your batch import.
Thanks so much for your help Kymeia. I've got it working great now, is there an easy way to make the snapshot as a master? Might as well get fully organised I'm thinking. It's great being able to switch through (and categorise) so many sounds.
Yes you just go into the properties panel (while in edit mode) and select the snapshots list, then select 'set as master' as per this screenshot Then save it of course