Reaktor 6.5.0: Beta phase has started
Comments
-
I will send some complain to Ableton, but at the same time I never had any similar hassle with any other dev in order to migrate from old to new versions of a plugin.
I mean, I just need some numerical view of the Reaktor's output volume, exactly like in Guitar Rig 6 for exemple, and then I can manage the time passed on migration.
0 -
If you're a person who uses glasses, or who uses high-resolution screens, your priorities may update.
The US may have many shortcomings, but the Americans with Disabilities Act makes it the law that you should accommodate people with disabilities as a matter of course -- not as a second thought or an optional item. This really does improve the ability of the society to be good for everyone, not just those who haven't yet had some particular challenge pop up in their life.
The EU, as of 2022, has similar accessibility rules, too. In practice, it's not yet enforced. So, even if you think "I only aim for people who are 15-30 years old and in perfect health with no eye issues," the EU law thinks differently, and chances are, enforcement will step up.
So, step 1: Scale up (zoom) UIs/windows.
Step 2: Make those zoomed UIs/windows able to use sharp typography, line art, and images.
Step 3: Make the built-in widgets automatically do that.
ARM is good, too. Usually, though, the people who are actually good at UI/UX, aren't the same people who are actually good at JIT assembly code generation, so there's some chance they could work on both for whatever the next iteration is.
1 -
If you're a person who uses glasses, or who uses high-resolution screens, your priorities may update.
Yes I wear glasses at the screen, but don't work with high-resolution screens.
0 -
I’ve had the VST2 deleted for a while and they’ve been working like that.
The same line is in patch notes going back several months.
0 -
The point is the 9.2 release is the one that had the NKS VST3 fix. It wasn't in earlier releases. Before that you could load the VST3 from the plugin menu but not by clicking on NKS patches.
0 -
+ 1.billion
VST3 and scale" options in the preferences/menus by fixed amounts and up to 200%.
0 -
Reading all the excuses is tiring.
Resizable UI has been something that’s been asked for for years, yet it keeps falling on deaf ears. Yes, there are the gotchas that the people who made ensembles will need to update the UI elements for this to work properly. Personally, I don’t mind updating stuff that I’ve uploaded to the library. I am sure, many others would be ok with this too. But if the tools aren’t even there to support this, then that’s on NI.
And the entire hierarchy management system is still idiotic when it comes to having settings saved with a project within a DAW.
These are basic usability issues that need to be addressed, can be addressed, and should be addressed. We are not in the 90s anymore.
3 -
Is Reakor 6.5.0 (PC) only VST3 , or is there 64bit vst2.4 available ?
My favorite DAW not supporting VST3 yet.
0 -
For exactly reasons like the one you pointed to, we will provide a VST2 with the 6.5.0 release too.
2 -
I stopped buying Reason for years because the GUI was stuck at tiny 800x600 era resolution and hard to look at on displays released over the last ten years. They finally redid the GUI and I bought the upgrade happily, for that alone. It was great and that was not even on a Retina display… and now I have one of those too, and it looks spectacular. Everything at proper resolution looks spectacular. I don’t know how anyone can stand low resolution UIs and text, especially after using a mobile device with high-PPI displays. Blurry text and graphics have been bothering me for well over a decade and I was wondering about this issue LONG before Apple released their first Retina display device, so I’m not buying into “no one could’ve expected…”
I’m 47, I already wore glasses, and my eyes are getting worse at sitting close to things. Large SHARP UIs are extremely important to me and have been since before my eyes started getting middle aged. Even when I’m at proper distance for my eyes, non-retina resolution text hurts my eyes/head.
I can only assume all the people who proclaim how unimportant this is have never actually worked with a high-PPI setup. I didn’t want to look at text on anything else after I got my iPhone 4, and that was SO LONG AGO.
Also, yeah, get things working on Apple Silicon. That’s important too. But really, it’s the thing that should’ve come after high-PPI graphics, since high-PPI tech has been on the market since 2013.
2 -
I would like Reaktor to be able to have multi-instance communication. I will use multiple instances of an ensemble and when I save a snapshot, I will have to save the snapshot in one instance, and then reopen my project so the snaps are recognised in the other instances. This becomes tiresome and tricky when needing to save snapshots in the other open instances.
0 -
I’m 47, I already wore glasses, and my eyes are getting worse at sitting close to things...
I'm 52, I've worn glasses for many years. Support for high PPI displays is way down my list of priorities when it comes to Reaktor feature requests... WAAAAY down. Sure, it would be nice, definitely add it to the list, but there are so many more important things that still need fixing/adding that we've been asking for for a lot longer than folks have been asking for high PPI support!
1 -
I'm certainly not out to compete. If you have a list of priorities that doesn't include HD graphics, that's fine. Different people, different priorities. I just care for some of the "fancy graphics don't matter" comments I've seen around forums for years whenever someone brings up high-PPI support as a request.
3 -
With two months in the beta phase… how's it going?
0 -
Yes it is a comparatively long beta, but through centercode feedback we found some hard to fix issues. Some issues were actually even problems in Komplete Kontrol and Maschine related to VST2 - VST3 migration, that was the reason why we released our Beta 3 on Centercode together with beta versions of Maschine/Komplete Kontrol for combined testing.
Other bugs recently uncovered were related to, for example, missing examples when loading host projects, or cross-platform compatibility bugs.
Anyway, as far as we know at the moment, the last show-stopper bug has been fixed since the end of last week and we plan to do a final round of testing and then release it in the next days.
5
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 732 Tech Talks
- 3.8K Native Access
- 15.8K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 814 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 6.9K Traktor
- 6.9K 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