I also targeted the /Library/Audio folder which contains subfolders for VST, VST3, etc plugins, and copied those over, since my main, original issue is that opening up Logic projects that use Reaktor 5 is of course giving the dreaded error "The plugin 'Reaktor5' is not available on your system".(I'm giving enough info here to allow others to google for answers) "Mac SSD:Applications:Native Instruments:Reaktor 5") to "Macintosh HD". This made it possible to edit the plist file in a text editor and change any occurrences of "Mac SSD" (eg. To do that, I had to convert the plist file from 'binary1' format to XML format using a MacOS command-line utility called "pledit". plist file because my old mac's HDD is called "Mac SSD" whereas the new one is called "Macintosh HD". I searched in folders like /Library/Application Support, /Users//Application Support, etc. From Terminal I ran a "find" command which searched various folders for files with names starting with Reaktor5.Note that NI Support told me "Native Access will not show Reaktor 5 as an installable product because it's not compatible with your operating system Monterey" At this point Reaktor 5 opened up just fine on the new Mac, but it acted as though I hadn't activated it and didn't own the product.Copy the Reaktor 5 application from \Applications\Native Instruments to \Applications.But before I heard from NI Support that Reaktor 5 won't run on post-Catalina MacOS, I had spent quite a bit of time brute-force copying Reaktor 5 over from my old Mac (MacBook Pro Late 2013) to my new M1 MacBook Pro running Monterey. I have just discovered that I'm in the same situation as you. There has to be a better way of doing this, does anybody have any suggestions? This seems completely bananas and will have an impact on studio downtime, employing an assistant to do this work and I can see it taking multiple weeks and is very high risk in terms of maintaining project integrity. Surely there's a better way of upgrading from Reaktor 5 to 6. I work in a professional environment where there are vast archives of work from the last 10-15 years. You can't save out Reaktor ensembles from Reaktor 5 in a modern OS, so is it really the case that I have to:ġ) Locate a legacy machine capable of running Reaktor 5Ģ) Migrate all projects to a an external drive / NAS so they can be accessed by the legacy machineģ) Install both Reaktor 5 and Reaktor 6 on legacy machine (as well as any other dependant plugins that might exist on the track- this will require deactivation on the master machine in many instances)Ĥ) Duplicate each track containing a Reaktor 5 instanceĦ) Replace Reaktor 5 with Reaktor 6 on the duplicated trackħ) Manually connect automated / MIDI mapped parameters on the new Reaktor 6 instanceĨ) Render out a version of the Reaktor 5 and the Reaktor 6 trackĩ) Null test to ensure nothing has changedġ0) Fix / correct any human errors, or make notes on any changed incurred from the Reaktor 5-6 upgradeġ1) Replace projects in the master archive with these upgraded projects so they are now accessible and functioning again With Reaktor 5 no longer supported in modern operating systems, what is the workflow for upgrading these projects to be accessible on a modern OS? These all have rather complex MIDI mappings, routings and externally automated parameters. I have 100s (possibly 1000s with version control factored in) of projects using Reaktor 5. X-post from the NI forums, but interested in any thoughts here.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |