I'm wondering if anyone is experiencing problems doing batch imports for mostly Reaktor user ensembles, but some factory ensembles as well? I know I have more than 1 problem, I'm not sure if they are related. I'm using Kore 2.1.4 -64 Bypass Integrated Engines is OFF. I can use the older Reaktor .dll that was included with the last Kore update if necessary but currently I'm using the reaktor 5.9.3 .dll in the Kore internal engine. By default, and I don't understand why, the installer places the 64 bit files in C/program files x86/common files /ni/kore2/plug-in when it seems like they should be placed in C/program files/...NOT program files x86. Is this by design? After a fresh Windows 7 install this February, I decided to change the directory of my Reaktor ensembles. That was probably a mistake. Using Reaktor 5.9.3 stand alone in the Reaktor Preferences the FACTORY content location is C/program files/NI/Reaktor 5. Using Reaktor 5.9.3 stand alone in the Reaktor Preferences the USER content location is D/patches/VSTI/NI/Reaktor 5 Using Kore2, most of my Reaktor sounds are in the Kore user folder, D/kore/shared content/sounds/reaktor ensembles I also have Kore>factory sounds>reaktor at c/program files x86/common files/NI/shared content/sounds/reaktor 5. To my knowledge everything works fine using Reaktor stand-alone and Reaktor inside Cubase. But integrating Reaktor with Kore2 stand-alone is now giving me headaches. The integration to my knowledge worked perfect prior to my Windows 7 re-install where I changed the Reaktor ensemble locations. I could batch import any user ensemble I wanted including the very old original reaktor ensembles created around 1999. I also notice to add to confusion I have IE ensembles (Integrated engine?) I think certain ensembles such as Uranus have a new GUI. Was this created because the very old ensembles were not expected to work any longer? My first problem is double clicking on any kore2>sounds>reaktor>ensemble from the Kore browser. In Kore2 new Performance, the name of the patch is loaded, but when I click on EDIT to open Reaktor I get the dreaded "Reaktor Ensemble not found" If I locate the ensemble I'm successful, but only when that ensemble is open. Once I close it in Kore then try to load it again, I get the same error. I believe I understand the problem is that each .ksd includes directory information therefore my only solution since I have changed ensemble locations is to completely delete all my .ksd's for each Reaktor ensemble and then in Kore right click on the Performance Source, load reaktor, press EDIT then the Reaktor shell opens where I can then locate the user or factory ensemble? But unfortunately if I load the user ensemble...for example 3x-v1.6 (james walker halls) I get "EMPTY" in the Kore2 source box! Is this because I need to install a older Reaktor .dll?, What is EMPTY in new performance.source indicating? I know I have successfully batch imported the ensemble 3x and dozens of other ensembles prior to my February OS re-install. Secondly, In Kore2 factory sounds>Reaktor5 choose any ensemble...for example Carbon, then double click a .ksd and in the source box it shows "not found." Thirdly, and I'm not sure if its related to the above problems, but I used to be pretty affluent at changing the automation parameters for any Reaktor ensemble so everything would be good in Kore. That was a few years ago so when I did it recently, I'm not sure if I'm doing everything correctly. I use Reaktor for mostly a huge preset library so forgive me for not knowing Reaktor very well. Also, reading old threads, many by EW here, I see some conflicting instructions. Hopefully things will be made more clear. In Reaktor stand-alone 1. toggle edit mode if necessary 2.press connect tab 3. make sure the focus is on Instrument and not ensemble 4. in automation section, press the ID's tab, sort and compress ID's. 5. in the old Kore manual it said make sure Max ID is the same as Max ID in use. But others in this forum have said make sure Max ID is 1 more than Max ID in use. I'm not sure if that really matters, but I always add 1. 6. Then use instrument up/down. Since I'm only using Reaktor for presets, I'm not sure what I'm doing! I usually press instrument UP, but any help to a casual Reaktor user would be appreciated. 7. After this, press the function tab (located in same area as connection tab) And I'm almost positive I used to UNCHECK recall by midi. However EW and some others are saying make sure it's checked. Can anyone verify if it should be checked or unchecked? I swear I used to have to uncheck to make this work. After this, file>save ensemble. ( unless I'm omitting something?) Apologies for tossing out so many problems but I know my Kore2 configuration can work better than it is currently. Other than Kore, life is good.
i have the most recent version of Reaktor inside my Kore plugins folder & do not check the bypass box. i've had a similar issue w/Reaktor presets & kinda gave up on trying to fix it by putting all my ensembles in all the locations Kore was prone to seeking them out, so i have 4 locations with all of them. i realize this isn't great for disc space but that isn't an issue for me. another thing i have done is . . . since i have spent a lot of time tagging & color-coding & giving stars to all my presets, i keep all the NI ksd files & my library of ksds from non-NI plugins ALL in my personal file (My Documents/Native Instruments/Shared Content/Sounds) & have deleted all the ksd files from where NI puts them (usually in the Common Files folder in both x86 & 64 bit Program Files folders) using an application called Take Ownership, which allows me to do what i want with program files certain companies don't want me touching. this process allows me to get rid of all those stupid duplicates that always plagued my library. also, there was a thread on the Kore forums that detailed how to set up categories in Kore (5 Star, 4 Star, 3 Star, 2 Star, 1 Star) & i also have categories named after the colors for color-coding; these are for being able to save the new library & make it transferable to another computer, but i am sure the options here are pretty limitless . . . once i got my library the exact way i wanted it & located all the Kore database files (there is a whole folder of them in AppData/.../Native Instruments/Kore 2. i applied the TakeOwnership app to that folder so that i could copy & paste it to backup drives & usb stick. then i also took the Sounds file in My Documents/Native Instruments/Shared Content/ & saved that folder as well to my usb stick, so that i could then transfer my library of sounds & database to my upstairs computer, where everything also works (granted, i have to have all my Reaktor ensembles installed in all the same locations). this set up makes me very happy even though i just got the Komplete 10 update a few weeks ago because now i have the option of using Kore 2 & its automation capabilities while in my DAW (because of all my .ksd files from Komplete 7) or i can use the Komplete 10 presets & its file format for use & automation inside of Maschine. the downside of all of what i have done is that i have lost the ability to open up many of Kore 2's ksd files due to the fact that i have chosen to use the most recent version of Reaktor in my plugin folder & not the version that is necessary to open up those Kore-specific ksd files, but that was a sacrifice i was willing to make. it took me a few years to figure all this out, and one time i lost my entire library's worth of tags, colors & stars, but now that i have things set up the way i do now, i have never been happier with my studio i realize a lot of this info may not be directly related to your issues, but maybe it will help in some way
Thanks. I gave up on color codes back when NI offered Kore support for the reasons you mention. One of the major drawbacks of Kore is that you don't want to spend too much time tagging sounds because the way it is designed, there isn't much long term permanency. Today I'm going to put the Reaktor.dll that came with the very last Kore2 update back with the Kore2 integrated engines and remove the newest Reaktor.dll to see if that makes a difference.
that's one way of looking at it. i have found long-term permanency w/my database, though (as i said, it took a while, but it was worth it). i am just hoping the Kore 2 hardware works with Windows 10, so i am holding off on the free update for now.
that's good. so i take it it works with Windows 8 then? i have never left the comfort & stability of Windows 7 after i got it
I put the 64 bit files back in C/program files x86 and that solves the problem of missing Kore2 missing factory .ksd's. I don't understand the logic of placing a 64 bit .dll in the C/program files x86, but whatever...that is how the NI installer did it originally. Now going to put an older Reaktor .dll in the Kore engines folder and see if there is a difference between that and the current Reaktor .dll for the purpose of recognizing Reaktor ensembles.
I put the old reaktor.dll's in (the ones that came with the last Kore update) and no luck. With the old reaktor .dll's almost every patch I click on in the Kore2 browser says this file was saved by a newer Reaktor version and I need to install the newer version. So I have put the newest Reaktor.dll's back in the Kore engine file.
I'm going to shorten my question. When I load Reaktor in Kore2, then click on edit that brings up the GUI, I am then given the opportunity to navigate to any Reaktor ensemble I wish. My problem is that for some Reaktor ensembles,such as James Walker Halls JX-v1.6, I drag or double click on the ensemble which shows up in the GUI, but in Kore2 under the "source" it shows the Reaktor symbol but reads <empty> when it should show the name of the patch loaded in the ensemble. Therefore I can't do a batch import until I figure out why it shows <empty>. If I select a different snap-shot (patch) in the Reaktor GUI that has JX-v1.6, I get a message that says "Change alert. You have made changes that can not be saved in the host application. If you want to use this edited version next time when loading this song please use "create local copy"in order to save it in a file and to enable automatic savings of future changes to this file." Then it gives me the chance to create a local copy by pressing the auto save button.
It sounds like with the ensembles that are showing 'empty' you have not got the top level ensemble (ie the one with the snaps) set as snapshot master. Kore will only show the snapshots names and import them if they are also showing in the main dropdown preset menu. What you need to do (I had to do this myself for 3X1.6) is enter edit mode, select the ensemble that has the snapshots, open the properties panel and go to 'function' 'snapshot' and select the button 'set as master'. You should now see the snapshots in the main Reaktor dropdown and the snapshot name should show in Kore. Save the ensemble and import (after setting up your controlled params).
Thank you!!! I wish I could buy you a beer. I have been messing with this for days, reading posts here usually dating back several years, plus the Kore manual part titled "automation of Reaktor in Kore." I can't find where the manual even mentioned checking to make sure the top level is checked as snapshot master. It gives good steps while on the Connect tab (sorting compressing), but I didn't know about the snapshot master. For anyone else reading this, I think Kymeia meant "properties" tab, not preferences. Can you answer the following: 1. Apparently I was wrong. It doesn't matter if "Recall by midi" is checked or unchecked? 2. Does it really matter if Max ID is one more than Max ID in use? 3. After sorting and compressing the instrument, not the ensemble of course, it says to use the instrument up/down. Can you explain this for someone who uses Reaktor only for snap-shots and doesn't get under the hood of Reaktor? Should the Ensemble be highest, followed by the instrument? 4. Why are the Kore 64 bit .dll's installed by default in the Programs x86 file when it seems like they should be placed in the 64 bit programs file? I moved them to the 64 bit programs file, and then none of the factory .ksd's showed up. So the .dll's have to be where they are installed by default however this didn't make sense to me. Anyway, thank you! Greg
That's because it changed in Reaktor well after the Kore manual would have been written, I think around 5.6 ish?? Which is why older ensembles like 3X need editing. You don't need to do anything to automation for batch import to work. Changing automation settings may be necessary though in order to map params to Kore knobs and that gets a bit complicated. Problem is there are some Reaktor ensembles that have ridiculous automation ID numbers well into the thousands, Kore just can't handle those, it seems to need numbers under 128 so you have to be selective and prioritise. Even sorting and compressing won't be much help if there are hundreds of IDs. In some cases I have had to edit ensembles pragmatically, just manually adding low number IDs to the params I want to map (and remembering to avoid dupes) and forgetting trying to map everything. And yes I meant 'properties' not prefs (I've edited it now so as not to confuse anyone).
Yes. Thank you again! My way too long post could have been summarized with 2 separate issues. 1. Don't ever move the location of Reaktor ensembles without the expectation that you will have to batch import every Reaktor ensemble that you moved, because the Kore .ksd contains information on the location of the Kore ensemble. 2. When doing Reaktor batch imports remember the button "set as master." This did not exist in older Reaktor versions. Kore is such a wonderful sound design tool despite it's few short-comings. It's very sad to realize Native Instruments abandoned such a powerful tool, but you can't blame them for wanting to make a quick buck with Maschine and now Komplete Kontrol. I can only hope someday in the future NI will revive it or revive the concept with something similar.
Yeah I tend to file that one under the "Kore can't work miracles' category - a ksd is essentially just a Kore project file - if you saved say a Cubase or any other DAW project file containing an ensemble and then moved the ensemble the same would occur. At least for now batch import from Reaktor is still possible, I worry that this is something we would lose if Reaktor 6 even comes out but we are lucky this is so far one Kore related area NI have not messed up.
Thank you for this thread. So on this new machine installation should I install Reaktor 5.9.4 from K10 over the Reaktor 5.5.0 from K7 or just skip to installing Reaktor 6. Will I lose or gain anything from skipping the latest version of Reaktor 5?
You will still need Reaktor 5.9.4 to load any Koresounds that were made with Reaktor 5 (which is a lot) since R6 is a separate plugin. Unless they have specifically been resaved using Reaktor 6 or are new ensembles (eg Blocks)