And they do!Įxpecting 'forwards compatibility' in any software development environment is unrealistic. This is a problem in a way because NI's prioritisation of backwards compatibility slows down development and means that radical improvements to the application are much less likely.īut it's obviously important in a studio context that old projects will load and work in newer versions. The vast majority of ensembles, instruments and macros made on older versions will all work on 6.4. Very occasionally, much older ensembles need some tweaking, or just don't work, but this is rare, and there are usually workarounds of you engage with the community. Reaktor 6.4 is fully backwards compatible with older versions (dating right back over 20 years in some cases). I’m still on 6.3 and can not load ensembles made with 6.4. Reaktor 6.4 is not compatible to prior versions. 100% agree with the op and also the 6.1 to 6.4 improvements are well worth checking out if someone was not impressed by 6.0 which is 5 years back (lot of people don't realize all the impovents in 6.1-6.4 because the major version number is 6). The 6.4 granular stuff can easily integrate with the 6.x analog stuff, so it's also nice an uniform (vs me patching between eu samplers/granular to 5u then to record in protools/cubase). now i work out the "theory" on the hardware, but can redo the circuits and stuff in NI so I can save a session and also don't need to go through the huge hassle of sampling then integrating the samples in NI.
If i have to tweak the samples though, it's a week to get the entire system back to where it was and its never exactly the same.
problem i have is i would need two more walls to do a complete queue, so i do samples. I am slowly moving things back to Reaktor, as an example i have a eu rack for granular which i connect to my 5u rack. The most recent 6.4 is amazing, also i like how they have kept it compatible to 6.0.
0 kommentar(er)
