reaktor 5.7 questions

Maybe.
It's also possible that some of this stuff is being handed down from R6 development. If they are using the current version as a platform for R6, then some of the new features will translate with little or no extra work - maybe they are just giving us some of these early?
Alternatively, maybe some of these features were slated for R6, but R6 has moved on to become a more fundamental update. So the work they had done on the R5 engine has been bundled up and released as an incremental update.
Or, maybe they've been using R5 to test ideas for R6, and giving us some of the ones that work well.

Whatever, it's good to be getting updates and bug fixes.
Personally, I'm happy to get smaller free updates, as I'm not sure that I will upgrade when I have to pay for it. I may decide to move on and try something else. It really depends on what the R6 feature set turns out to be.

 

i guess the point is i wouldn't pay for 5.7, and was hoping for a more substantive update.
it's been 7 years, i don't think asking a question about the future versions is that crazy. and given how many times you've asked about maschine's future in the last week you'd be the last person i'd expect to give me a hard time about it, really.

 

I'm not asking for an update, I'm asking for Infoemation, some signs of progress, like with reaktor currently.

But fair enough, also I find 5.6 and x64 was a big step, at least overdue.

 

personally i could really care less if most of the software i own gets updated. i'm really happy the last two propellerheads updates have been free for me (wouldn't have bought them) and reasonably pleased with the last few years of reaktor updates... so don't take my posts as complaint.

on the other hand, i've reached a point in reaktor where the things i want to do are constantly pushing up against what is possible to do. without an update coming, i might as well move onto another platform or just go back to c++ and start writing vsts. to be clear, i *really* don't want to do that. i've grown to kind of hate text-based programming after using reaktor.

ableton, i don't care if it ever gets updated. i'm still on v7 and it still does everything i want. (OMG no bezier curves lol)

 

Its weird that the Reaktor team would change the look and layout twice and so close together for 5.5 and 5.7 and maybe that is an indicator that those R6 hamster wheel's are turning.

 

For me, this is exactly why NI should update Reaktor; 2 of the best builders of recent times & most consistantly helpful forum members are considering moving away from the platform. NI should be killing themselves to keep people like them, especially given the way Reaktor is presented (User Library, forum as learning/support resource etc).

Just my $0.02

 

User Library, yeah, that's another story, tale if you will...

 

agreed 100%

sowari

 

+10000000

on the matter of 5.7 vs 6, I don't care, as long as it gets some worthy updates, and, if it's 6, the updates are worth the money for upgrade.

The way I see it now is that something's happening. Whether it really is an improvement of Reaktor for the users, time will tell. (of course, if NI showed this to be so without any doubts, that would be most awesome)

 

...
keir? you planning on responding to this thread?

 

herw has asked if he can respond to the points with some more information. He has a response ready and I think he'll be posting it shortly.

 

thanks - keir. I have asked before i send this because i don't want to get in conflict with NDA.

Loading time optimization (CompiledCoreCellCodeCaching)
a feature for ensembles with large core structures; when storing an ensemble it is compiled. In play-mode you can load the ensemble very fast. If you change to edit-mode the compiler for core cells is working again, so you have the normal loading time like in R5.6.2; usefull for preset users
Screensets added
like in R5.5(R5.1.5 ?) with windows; you can add up to 20 screensets (means structure, panel or splitted view of any macro(s) and change by button or shortkey)
Explicit edit mode added
see first point
Redesigned header and layout
small design changes (transport button etc.)
Global debug mode added
good point, there is a global button for primary AND core showing the values of the wires in all screensets. You can jump from screenset to srceenset and compare the values.
Old info button (primary) is for hints only.
Feel of wire dragging improved
feeling of connecting and catching inputs and outputs of macros is very smooth now (well done)
fixes
R5.70 is very stable although there are still some bugs to be fixed but i bet that you wouldn't recognize them. The team has done a very good job!

ciao herw

 

thanks herw.
do you know if global debug mode fixes the problems with debug in core (that is, switching to structure view resets the ensemble, making it very difficult to set a state and check the core cell) ?

 

it's not a simple problem (toggling between the screensets in debug mode always results in a re-init of the opened structure), but i don't have more information about it.
You have to discuss it when the update is published.
From my experiments with RUHR i have learned that you have to know about initialization outside and inside of core.

ciao herw