What's the general status of Reaktor?
Comments
-
Reaktor is not running on M1 natively or under Rosetta. And it will probably take time. Maybe long time. Maybe even longer time....
0 -
I have Reaktor 6 running fine on a new M1 Mac Mini (Monterey) both in standalone and as a plugin in Logic, both under Rosetta. Way better performance than my 2015 iMac i7 Quad Core. The single core is being pushed as I can see in Activity Monitor, for example in HQ and multi-voice patches in Razor- I can run a bunch of them in Logic on different tracks, but the darn machine is dead silent, when before my iMac's fan would kick in and loud!
2 -
Hi all. Thanks a lot for the answers/testimonies. I'm relieved because I use Reakor quite a lot on stage, and I just bought an M1pro to replace my old mid-2012 i7 macbook pro. Then I just thought about NI plugins and while reading this thread I was a bit scared that Reaktor was not very stable on the new ARM macs under Rosetta/Monterey.
I understand the native version will come in a long time, but I guess even under Rosetta my new machine will be like day & night compared to my good old macbook (pretty nice machine actually, specially when I read the issues people have with more recent ones, but the 16gb RAM limit and the CPU start to show their age when using a Live set on stage with 20 songs, many virtual synths and some kontakt instruments. Form is the worst offender for my present machine and my set uses more than 20gb of RAM so I get a lot of instability).
Anyway, thanks for the answers...
0 -
Yeah, you’ll most certainly be ok. I made the jump from a 2013 i5 MBP, and the difference is like night and day indeed. I’ve yet to come across a Reaktor instrument or ensemble which didn’t run, and it’s not even close (bar some wild Blocks racks I’ve made). Form barely leaves a dent in this machine — I’m just realizing I’ve gotten used to this kind of performance 😁 Form used to be a problem in the past. Also, no problems with stability here. Long live Reaktor!
1 -
And I'm no Apple lover - can't stand their 'ecosystem', their shady customer support, bad styling, forced obsolescence, unrepairables, fanboy army... just doesn't work for me, but I'm not a fantasist,
Can I add Im not a fanatisist (if thats a word)? - and yet here I am a Mac user because way back when I migrated from the Atari it made sense to move in the Apple/Logic direction and there's too much water gone under the bridge to "wean" off Apple now. I would if I could for the above reasons and more. It would be nice if people here could see there are actually some Mac users who see's their Macs as a tool, not a religion. I also cant stand their marketing mystery hype that has people on the edge of their seat. So much I despise about Apple. As for M$ I could argue they're anything but squeaky clean. In the end you just have to say it is what it is.
This time last year NI was just a name Id heard of many years ago like many others. Id only used stock Logic stuff. Long story short, I went totally out and got K13 UCE. I haven't even really scratched the surface of whats possible. When I came to Reaktor I didn't even know how to get around the interface. As Ive poked around I've found there's some stuff I really love in this thing. I really hope Reaktor lives on, even if I never get into the depths, theres sounds ready made that are great just as they are or with a little tweaking. I hope some noob questions are OK on this Forum.
Its really encouraging to hear others say Reaktors working on Monterey, but I don't want to update until Reaktors officially supported. Im not on AS and can afford to wait as I find my 8core 2019 iMac 40GB RAM pretty capable at this point for what Im doing.
0 -
My Mac host is Cubase, which has an M1 version, but that can't load Rosetta plugins, only native plugins (which is understandable.)
I could run Cubase entirely under Rosetta, but then there's no point -- I have Windows for that, and despite Apple cherry-picking benchmarks, even their $5k ultra package doesn't quite match the latest from AMD and NVIDIA in blended workloads, especially when you also do GPU stuff.
Anyway -- no announcement regarding potential ARM version of Reaktor, means they send the "we don't know if this has a future" message, which is apparently exactly what they intend. (On another note, I was also sad that the Maschine+ hardware, which I also have, used an Atom chip, not an ARM of some sort, but this now makes more sense.)
0 -
My short couple of cents:
x86 is an ugly, legacy architecture. I think ARM is way better, but ARM processors are still behind, not only x86, even ARM itself. For example, no mainstream ARM processor implements SVE, which means porting from AVX is a performance disgrace.
This is a slowly, peacefully sinking ship. Sometimes I feel like complaining, but there's no point. It is what it is...
1 -
x86 has survived 45 years, or so. And it is backward compatible with x80, which will celebrate 50 in few years.
Platform that has survived so long in IT will most probably live as long as silicon will be used. No real need for change.
I keep finger crossed for Apple to be able to produce strong ARM chips, but I strongly doubt they will be able to keep pace with AMD and Intel.
0 -
x86 has survived 45 years, or so.
And that makes it good for us, now in 2022, because... ?
And it is backward compatible with x80, which will celebrate 50 in few years.
Which is useful for us, now in 2022 because... ?
x86 is a significant part of IT history, and like the dinosaur it is, belongs in a history museum!
Unfortunately, it's very difficult to replace a dominant technology, because change is painful and expensive. Old habits die hard and all that... That's where Apple's own dominance is for once a benefit - maybe they are big enough to be able to force the change through.
It is a worry though, it's really important that PCs don't die out and instead change with the times! Maybe needs one of the big Chip makers (or a new one?) to embrace ARM (or some new ARM competitor that is not x86...). Imagine what Apple would be like if they had a monopoly on desktop/laptop computing!
It's also really important that old software companies don't die, and instead embrace change and put resources into research and development to keep their great products relevant and successful!
1 -
I'll ask again for examples of LLVM being used as part of the compiler toolchain for Dataflow languages.
It's the back-end for Rustc, and Rust is very much a data flow language (with the whole ownership/borrow checker paradigm.) It might not have boxes-and-arrows, but that's more of an interface choice.
Also: I weaned myself off of Apple a long time ago; my main workstation is a Threadripper, but my laptop is an M1 for "it's good to test everything everywhere" reasons. And it's handier on the couch than the Maschine+ (which has no battery) and the Threadripper (which ... really ... doesn't move at all!)
1 -
Verified technolody, lots of SW, lots of HW. Lots of experience design such CPUs. Good compilers. Not many CPUs survived that long, if any.
Yes, it may be difficult to replace x86. But mainly, there is no real reason to do so.....
Apple makes 4 different CPUs (for PC) and that's it. Take it or leave it. x86 platform has hundred or so differently scaled CPUs. Everyone will find what suits. More or less.
And Apple does not sell its CPUs, so it cannot penetrate outside.
Intel and AMD are able switch to ARM if needed. They already produce ARMs. But there would have to be a demand. Why would users want to switch to ARM? AMD notebook CPUs, if produced on the same process like M1 would consume about the same, while being stronger. So, the only advantage of AS are specialized coprocessors and faster access to memory. x86 may extend instruction set or coprocessors may be external addon. And DDR5, bigger cache and possibly more memory banks will solve most of AS advantages....
And by the way, x86 procesors are internally sort of RISC. Each x86 instruction is internally translated to internal almost RISC like code.... There is sort of HW Rosetta.
0 -
Rust is very much a data flow language
Most of my searches on "dataflow programming in Rust" lead back to these two projects "timely dataflow" and "differential_dataflow" both related, from the same team, and from a quick look they seem to be dataflow frameworks written using Rust, rather than the rust language itself being a dataflow language?
Although they might be implementations of a virtual 'dataflow architecture' model - which is not the same as dataflow programming paradigm it would seem (discovered this distinction just now... on Wikipedia, so it must be true!).
Various info on the Rust language mention many different paradigms. Here's an example from an intro tutorial: "Rust is a multi-paradigm programming language, which supports imperative procedural, concurrent actor, object-oriented and pure functional styles. It also supports generic programming and metaprogramming, in both static and dynamic styles."
'The Book' linked from the main rust language site doesn't contain the word 'dataflow'.
None of the resources I can find on Dataflow programming languages mention Rust (Wikipedia, Stack overflow, various papers)
Definitely need to read more about Rust though, so thanks for that - every day's a school day :)
0 -
Let NI finish making Massive X working on x86 first.. :)
/uj
0 -
My suggestion is that *the rust compiler* is a dataflow application.
The reason for this is that Rust tracks object ownership at compile time, and must account for single ownership at all times, so the graph it builds to do this internally, is a data flow graph of ownership, which in turn determines when the Rust compiler emits "destroy this object" code. (As well as give error messages to programmers who write improperly constructed programs.)
Maybe this is too "conceptually dataflow" rather than, like, "these boxes and arrows show how data flows," or some data processing language or library like Pandas or Flink or whatever, compared to what you're looking for?
Anyway, I have very high confidence LLVM would generate well optimized code (including SIMD) for audio DSP, for a variety of architectures. The most important of which are x64, ARMv8, and CUDA/PTX.
Which brings me to ANOTHER crazy Reaktor-adjacent idea I want to see realized, which is: wouldn't it be cool to multiply the throughput of Reaktor by a hundred X by running it on a high-end GPU? Latencies would be higher (probably no better than 400 Hz control rate at best, and double-buffered 64-sample buffers or bigger,) but the throughput could be absolutely astounding. One of those little NVIDIA Jetson modules could probably be used to build a hardware-based synth that did the same thing, too.
Uh, anyway.
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 66 NI News
- 859 Tech Talks
- 4.4K Native Access
- 17.6K Komplete
- 2.1K Komplete General
- 4.6K Komplete Kontrol
- 6.1K Kontakt
- 1.6K Reaktor
- 398 Battery 4
- 888 Guitar Rig & FX
- 453 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 7.8K Traktor
- 7.8K 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