Ernest

About 10 years ago, a blog site offered me a cheap copy of Max/MSP if I wrote an article comparing it to Reaktor. At the time, I favored Reaktor. This year, after some confusion about exactly why I designed a baby DAW, I wrote an explanation of why I believe MAX/MSP is now unquestionably superior, at this anchor: 

https://www.yofiel.com/downloads/audio-apps/remixquad-pro-audio-3d#power

About 10 years ago, a blog site offered me a cheap copy of Max/MSP if I wrote an article comparing it to Reaktor. At the time, I favored Reaktor. This year, after some confusion about exactly why I designed a baby DAW, I wrote an explanation of why I believe MAX/MSP is now unquestionably superior, at this anchor: 
https://www.yofiel.com/downloads/audio-apps/remixquad-pro-audio-3d#power 

About 10 years ago, a blog site offered me a cheap copy of Max/MSP if I wrote an article comparing it to Reaktor. At the time, I favored Rea

maxmsp-advantages-over-reaktor

the 'control latency' part got me interested, but i wonder if this applies to non-midi (ie. max control data) as well ? or is it just relevant for midi I/O latency ?

All control signals are limited by the Max queue, which cannot run faster than 1kHz, But if you keep the queue empty, you can be pretty sure that you will have 1ms latency worst case. The additional delay from the DSP block size only applies to audio signals.

All control signals are limited by the Max queue, which cannot run faster than 1kHz, But if you keep the queue empty, you can be pretty sure that you will have 1ms latency worst case.  The additional delay from the DSP block size only applies to audio signals. 

I don't understand the article or why Max is "unquestionably superior" to Reaktor. Certainly it's a pretty big jump to make such a claim based on one tiny aspect of the program. I have never had any significant problem with latency in Reaktor. It is "superior" to Max in many ways, so I am happy enough to work with both!

Well I will explain in simpler terms. It can only run on one processor core. That's it, eventually. Game over. The problem with Reaktor has nothing to do with latency and I never said that at all. Sorry to be blunt.

Well I will explain in simpler terms. It can only run on one processor core. That's it, eventually. Game over.  The problem with Reaktor has nothing to do with latency and I never said that at all.  Sorry to be blunt. 

No worries being blunt! I am glad to understand your point, and it is a good one. The part of the (overly long) page the link took me to was entitled "Latency Adjustments", hence my previous comment.

The limitation of Reaktor to a single core is indeed an issue, solved for some by hosting different Reaktor instruments in a DAW that can distribute them across a processor chip. More significant limitations of that program (for me) include the lack of scripting and the lack of a proper re-usable code model.

On the other hand, Reaktor has thousands of usable instruments to hack, right out of the box. Including good emulations of just about any classic synth or effect box. Max cannot compete with that library. Plus, Reaktor a better interface model. And sells for only 100 clams, if you wait for the annual sale. 

We could go on with pluses and minuses, but perhaps that wasn't your point.

No worries being blunt! I am glad to understand your point, and it is a good one.  The part of the (overly long)  page the link took me to was entitled "Latency Adjustments", hence my previous comment.

The limitation of Reaktor to a single core is indeed an issue, solved for some by hosting different Reaktor instruments in a DAW that can distribute them across a processor chip. More significant limitations of that program (for me) include the lack of scripting and the lack of a proper re-usable code model.

On the other hand, Reaktor has thousands of usable instruments to hack, right out of the box.  Including good emulations of just about any classic synth or effect box. Max cannot compete with that library.  Plus, Reaktor a better interface model. And sells for only 100 clams, if you wait for the annual sale. 

We could go on with pluses and minuses, but perhaps that wasn't your point.


There isn't much I can do about the length. I had to spell out alot of stuff. I could split it into several articles, but then people don't find them. I am working with a consumer market now, and I have to cope with quite a bit of laziness and stupidity. sorry about that.

You are right the link doesn't go to the right place on the page. Thank you for letting me know, or I wouldn't have checked it. On looking into it, due to page load ordering, when opening the anchor from a different site, it scrolls to a different place. To fix that will take a week or so of finding exactly what script and PGP is causing it, and fixing it properly, so please excuse me if I just provide the link to the page and let you jump to it--The jumplist at the top of the page works as expected.

https://www.yofiel.com/downloads/audio-apps/remixquad-pro-audio-3d

There isn't much I can do about the length. I had to spell out alot of stuff. I could split it into several articles, but then people don't find them. I am working with a consumer market now, and I have to cope with quite a bit of laziness and stupidity.  sorry about that.

You are right the link doesn't go to the right place on the page. Thank you for letting me know, or I wouldn't have checked it. On looking into it, due to page load ordering, when opening the anchor from a different site, it scrolls to a different place. To fix that will take a week or so of finding exactly what script and PGP is causing it, and fixing it properly, so please excuse me if I just provide the link to the page and let you jump to it--The jumplist at the top of the page works as expected. 

https://www.yofiel.com/downloads/audio-apps/remixquad-pro-audio-3d 

One of the metrics I'd be interested in seeing would be how many Reaktor users have made 

 changes to the instruments in the package. I'd also be interested to see what the stats on Reaktor Core (Kore?) use, too.

One of the metrics I'd be interested in seeing would be how many Reaktor users have made any changes to the instruments in the package. I'd also be interested to see what the stats on Reaktor Core (Kore?) use, too.

I think that Reaktor tends to attract people in the first place who want to hack. Otherwise they buy one of the many other products, even from NI own catalogue. Back when the forum was more active, this seemed to be the case. But of course with any product only a small percentage of people engage with it. Likely 1 in 100 people with Live use M4L, even though that's practically the only advantage of the DAW.

I think that Reaktor tends to attract people in the first place who want to hack. Otherwise they buy one of the many other products, even from NI own catalogue. Back when the forum was more active, this seemed to be the case.  But of course with any product only a small percentage of people engage with it.  Likely 1 in 100 people with Live use M4L, even though that's practically the only advantage of the DAW.


The page seems to not exist anymore, but it always get me sad to see that there's always something better than I have :^(

Im sorry about that, I had to stop working on audio software because I have lost my hearing. Beethoven may have been able to compose while deaf, but Its difficult to make audio software while deaf.

MAX/MSP Advantages over Reaktor