I'd just like a nice simple interface that says Monark, Razor, Skanner XT, where I find also find the snapshots / presets, and can quickly click go. It did at least give me a hazy notion of some of the fundamentals, even though today 99.5% of the time I open Kontakt it's to use someone else's libraries. I did have a brief spell many years ago of trying to make a proper instrument, and it took me far too long to realise this was a foolish and ridiculous use of my time. I do occasionally make simple instruments in Kontakt. Reaktor, for almost all of us, is merely the host, so it just needs to be an efficient and easy to use one. Usually I just find weird stuff I like and commit it to audio.
Reaktor library mod#
Stuff like Steampipe is awesome, with a mod wheel controlled chiff. The mechanized electronic drums have huge amounts of bleeps and bloops and endless patterns. Oh, I can’t program the freaking thing, but it’s great fun to load some various crazinesses and as I said, just muck about. Separately, NI are discontinuing the short-lived stand-alone version of Super 8, though FM8 lives for now. Therefore, we would like to motivate you to participate in the testing as well, so that together we can make this version a success and a valuable asset for you and all other users. What we are trying to achieve is to deliver this version with high quality and a good base for the future. But at this stage, we as a team will not be able to change this situation.
Our team is aware that the lack of more features will lead to frustration. Still: to make this a quality release we think that having a good test coverage in day by day user situations is absolutely essential. includes saving a file on Windows, then loading-testing and re-saving on Mac, and again loading-testing on Windows.
We tested this area a lot, also using cross platform testing which e.g. for non-embedded Sample files, references to ensembles in preset files or in host projects, references to Blocks in Rack files and so on. A prominent area is persistence where external file references were stored in content files, e.g.
Reaktor library code#
As I mentioned in a previous post, the Apple Silicon port implied that we had to replace an important internal code object, and this replacement needed to be done with extreme care to not introduce serious errors. While this may sound like fishing for compliments, I'm writing this to share a bit of our motivations and why we need the Reaktor community's support, because the rebuild effort has been extensive and despite our diligence, internal testing has already revealed some unexpected bugs. I'm actually quite proud of what we've accomplished so far under the circumstances, how thoroughly and prudently we've invested our resources to move forward, taking great care to avoid bugs like incorrectly loading old content. To make this happen, our very small team has put some effort into writing new code or reworking existing code.
Reaktor library update#
Apple abolishes Rosetta with an OSX update or some DAWs decide to stop VST2 support. We also open a path for a possible use of Reaktor for a future where e.g.
Reaktor library upgrade#
When the user wants to upgrade to the currently latest Windows or Apple OS versions, but is currently unable to do so due to existing deficiencies. Again, if the DAW supports the VST2 -> VST3 migration feature, you will be able to load project files which were created using the VST2 version of Reaktor. When using a DAW that no longer has VST2 support. In this case, if the DAW is supporting the VST2 -> VST3 migration feature, you will be able to load project files which were created using the VST2 version of Reaktor. when a DAW is running in native Apple Silicon mode.
0 kommentar(er)
