Reaktor 6.5.0: Announcing start of Beta phase for January 2023
Comments
-
Good news ! How do we eventually invited ?
0 -
Reaktor lives on!!! Sounds a bit cinematic there but I was beginning to worry it was being slowly dropped.
0 -
Just to doublecheck, will folks who are already betatesters be able to just log in as usual and click through for the new beta, or will they have to re-register?
0 -
If there is no Apple Silicon SDK for VST2, why do 99% of my plugins (and I speak about hundred of them) are running native on my M1 pro in their VST2 version ?
And why most of them did offer a native Apple Silicon VST2 version only few months after the release of the new Mac chips ?
I understand the simple fact NI doesn't want to allocate ressources (i.e. money) in updating VST2 versions of their plugins, especially when I see how much time they need to update anything, but this is a lie to suggest it's because VST2 is no more supported by Apple and so "most plugin that updates are dropping VST2 on MacOs"...
Regarding the reasons users should need VST2 Apple Silicon support, there is a very simple reason that comes directly to mind : recall of old sessions !
I've got hundreds of sessions with hundreds of NI plugins in their VST2 form that lie in my hard drive. NI is the most painful company when it comes to recalls : at least on Ableton Live, you can't open Kontakt 5 instances with Kontakt 6. You can't open Reaktor 5 or Guitar Rig 5 instances with R6 or GR6, so you need to keep all these versions in your drive, export a preset for each instance and open it with the new version (praying so it sounds the same) if you want to "update" your sessions so it may open in the future. And in a very close future (when Apple will drop Rosetta), I'll will not even be able to recall any session containing VST2 instances of NI plugins because after years not even caring about VST3, they decided baldly to abandon VST2 and only take care about VST3...
How is that way of updating things help us, pro users, in our daily work ?
So I don't want to spoil the party regarding Reaktor 6 native Apple Silicon version (I'm pretty damn happy about that), but please don't tell NI users it's because of Apple SDK we don't get a VST2 native Apple Silicon version (when 99% of the plugins I use offer that). It's just because NI doesn't want to allocate ressources they don't have (or prefer to give away to shareholders)...
2 -
"Sample accurate" in case of VST3 pertains to host automation (and even then, plugin specifically needs to support that feature), it's not related to plugin induced latency.
0 -
Hi Chet!
Is this issue with Reaktor Standalone on your Win11 still happening each time you open it ?
Did you check for the same "Service Host: Capability Access Manager Service" in task manager while running any other Standalone Applications. Maybe it happens there too, but is not as prominent to the performance.
Is your Win11 and all drivers up to date ? Also please check this possible fix for it out https://www.youtube.com/watch?v=LPu-fqg51kM , might actually help and the only side effect might be loading time increased a bit.
Cheers
Sufox
0 -
Sorry, but besides the addition of native Apple Silicon support and the new VST3 plugin there will be no new features implemented.
At this point, perhaps it is time to comment on the situation. For a variety of reasons, NI is not in a position to invest major resources in this product, which has not been news for some time. I'm not going to comment on the details, nor on whether or not I personally think all of these reasons are indisputable. What I will get into is the value of the upcoming release and why we are asking the Reaktor community to support it to get the best result:
- The 6.5.0 release will ensure that Reaktor and with it all existing content such as Reaktor Player products, Factory Library, Reaktor User Library content and personal user files are usable in existing and new DAW projects and standalone use cases. Including situations like
- where there is no OSX Rosetta support, e.g. when a DAW is running in native Apple Silicon mode. 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 using a DAW that no longer has VST2 support. 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 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.
- We also open a path for a possible use of Reaktor for a future where e.g. Apple abolishes Rosetta with an OSX update or some DAWs decide to stop VST2 support.
To make this happen, our very small team has put some effort into writing new code or reworking existing code. 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. 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. 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. A prominent area is persistence where external file references were stored in content files, 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. We tested this area a lot, also using cross platform testing which e.g. includes saving a file on Windows, then loading-testing and re-saving on Mac, and again loading-testing on Windows. Still: to make this a quality release we think that having a good test coverage in day by day user situations is absolutely essential.
Our team is aware that the lack of more features will lead to frustration. But at this stage, we as a team will not be able to change this situation. What we are trying to achieve is to deliver this version with high quality and a good base for the future. 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.
Best
Georg and the REAKTOR team
13 - The 6.5.0 release will ensure that Reaktor and with it all existing content such as Reaktor Player products, Factory Library, Reaktor User Library content and personal user files are usable in existing and new DAW projects and standalone use cases. Including situations like
-
Always nice to hear directly from the Reaktor team.
"For a variety of reasons, NI is not in a position to invest more resources into this product, which hasn't been news for some time"
I first reacted thinking it meant the end of Reaktor "good thing i didn't start ranting" but rereading it just means the team will stay small right?
"What we are trying to achieve is to deliver this version with high quality and a good base for the future."
That can be seen as a positive thing as well.
0 -
Thanks for pointing out the misleading wording, i have corrected it.
0 -
I hope what it means is just in relation to the current update, I would hope Reaktor continues to be a viable product, NI would be beyond stupid to drop or stop developing Reaktor too.
1 -
One can only hope, but we already have a history of things that have happened. We're still bemoaning discontinuation of Pro-53, Spektral Delay, Kore, Service Center...
It is very very clear which product(s) are keeping NI alive financially (and also consider NI/Soundwide has to respond to venture capital stakeholders)...
3 -
Catering to the hip hop/trap mass seems to be more viable yes,quite sad to me but well...i will refrain from derailing the thread too much.
We have an update coming and a word from the coders...all is good for now.
1 -
'A prominent area is persistence where external file references were stored in content files, 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. We tested this area a lot, also using cross platform testing which e.g. includes saving a file on Windows, then loading-testing and re-saving on Mac, and again loading-testing on Windows. Still: to make this a quality release we think that having a good test coverage in day by day user situations is absolutely essential.'
This is worrying because at the moment one area where Reaktor (and all NI plugins tbh) struggles is in accurately guiding users to relocate missing resources. The problem is the dialogue boxes that report missing files are too small and do not always show the full path for the missing resource. If you want to have a positive bug squashing process, given this is a likely issue, it would be great if you could ensure firstly that Reaktor correctly reports missing resources.
3 -
Because DAWs like Logic Pro and Bitwig will run Intel plug-ins sandboxed or out-of-process, and in the case of Logic lots of Intel Plug-ins are very buggy/glitchy when used that way. Depending on that is a support nightmare due to the issues users face with it, as well as the fact that we are past the two year period after M1's release, so we cannot expect Rosetta 2 to remain forever. We have to assume it is on the chopping block, because we are going past the time frame that Apple expected it to serve a purpose.
No VST2 plug-ins exist that are Native ARM, because Steinberg has never ported the VST2 SDK to ARM and they aren't licensing it out anymore. It's been deprecated for almost a decade and it has been out of development for years.
1 -
The VST2 SDK doesn't have to be ported to ARM, actually. Some plugin developers actually made VST2 work on Apple Silicon and it wasn't that compliacted, apparently. It's just that Steinberg doesn't want to support that scenario (well, VST2 in its entirety, really). But it can and did work.
3
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 695 Tech Talks
- 3.6K Native Access
- 15K Komplete
- 1.8K Komplete General
- 3.9K Komplete Kontrol
- 5.2K Kontakt
- 1.5K Reaktor
- 351 Battery 4
- 778 Guitar Rig & FX
- 400 Massive X & Synths
- 1.1K Other Software & Hardware
- 5.2K Maschine
- 6.6K Traktor
- 6.6K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators