![]() ![]() Replace projects in the master archive with these upgraded projects so they are now accessible and functioning again Render out a version of the Reaktor 5 and the Reaktor 6 trackįix / correct any human errors, or make notes on any changed incurred from the Reaktor 5-6 upgrade Manually connect automated / MIDI mapped parameters on the new Reaktor 6 instance Replace Reaktor 5 with Reaktor 6 on the duplicated track 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)ĭuplicate each track containing a Reaktor 5 instance Migrate all projects to a an external drive / NAS so they can be accessed by the legacy machine Locate a legacy machine capable of running Reaktor 5 You can't save out Reaktor ensembles from Reaktor 5 in a modern OS, so is it really the case that I have to: 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |