I have 100s (possibly 1000s with version control factored in) of projects using Reaktor 5. These all have rather complex MIDI mappings, routings and externally automated parameters.
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?
You can't save out Reaktor ensembles from Reaktor 5 in a modern OS, so is it really the case that I have to:
1) Locate a legacy machine capable of running Reaktor 5
2) Migrate all projects to a an external drive / NAS so they can be accessed by the legacy machine
3) 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)
4) Duplicate each track containing a Reaktor 5 instance
5) Save the ensemble from Reaktor 5
6) Replace Reaktor 5 with Reaktor 6 on the duplicated track
7) Manually connect automated / MIDI mapped parameters on the new Reaktor 6 instance
8) Render out a version of the Reaktor 5 and the Reaktor 6 track
9) Null test to ensure nothing has changed
10) Fix / correct any human errors, or make notes on any changed incurred from the Reaktor 5-6 upgrade
11) Replace projects in the master archive with these upgraded projects so they are now accessible and functioning again
I work in a professional environment where there are vast archives of work from the last 10-15 years. Surely there's a better way of upgrading from Reaktor 5 to 6. 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. There has to be a better way of doing this, does anybody have any suggestions?