Kontakt and Reaktor are worthless in this regard, unless you're okay with losing your sanity. Sure, you can download a module that shoehorns in some kind of un-controllable polyphony, create a small level of inter-modularity, and truly badass gate patterns, but you will quickly reach the limit in terms of what is possible.Ĭontrol and interface wise. I have an 8 core i9, and the most modules I've been able to concurrently run at a stable buffer (because when it's set too high, the clocks and sound quality become a jumbled mess indistinguishable from the offline render) are maybe 35-45, however this number is actually far less than what you would get out of the average eurorack module, both in terms of functionality, power, and cv. The stories of pain and suffering using it aren't to be taken for granted ultimately it is a pile of shit. After spending a lot of time with it though, I came to the conclusion that that is all it's is good for (learning). Downloading the Rob Hordijk modules are a requirement for this though – as far as utilities, logic, and a few modulators are concerned. I think of reaktor 6 as a tool for understanding what it is you want/can get out of modular within a narrow scope. If an older version allowed you to load new files, it would have to have a complex process of error reporting which would just tell you that it's not going to work, and give you a long list of reasons that you can't do anything about anyway, because you would need the latest version to access them. The old version can't know about features and changes that exist in the newer files. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |