Reaktor 6.3 - Blocks and Front Patching
HTML-код
- Опубликовано: 15 сен 2024
- Getting into the new front patching Blocks in Reaktor 6.3 with Julian and Phillipe from Native Instruments.
#TSR19 - Thomann took a bunch of RUclipsrs to their shop and told us to go play and make videos. So we did. This is straight to camera, one take, off-the-cuff, honest and fabulous. Thanks to Thomann for the opportunity and thanks to Julian and Phillipe from NI for spending some time with me. Search for #TSR19 for more fantastic videos from fabulous synthesizer RUclipsrs.
Thomann Store - www.thomann.de/...
Molten Music Technology - moltenmusictech...
Native Instruments - www.native-inst...
Patreon - / robinvincent
That was very helpful for me as well - and I've been doing synths since 1970. I really love the new interface! Thanks to Julian and Phillipe and the Reaktor team, and of course to Robin for asking all the best questions!! :-)
Man something like a combinator for Reaktor would be a MAJOR streamline! There’s so many times when I have an exact structure that I am comfortable with, and would perhaps like to push the boundaries of. However it gets cumbersome (in a very first world crisis sort of way) to have to reconstruct every time, or have to rely on loading a full rack to play around with. I’d love to take say a bass line configuration and another I’ve made for drum patterns and just drag and drop them from a browser to use quickly or just expand off that configuration
Option overload 🤣🤘🏽is better than no options
Great to put some faces to those N.I. peeps :)
Just like how in Ableton you can save clips and ALC files, Reaktor would really thrive from the "subpatches" you mentioned.
This is what it should have been from the beginning, can't wait until more modules come out that support racks.
Really useful stuff. Thank you so much!
Front panel patching is great - I would love to see that we can do both patchings also independently, iow create a kind of "Bus"-Patching in the connection window that can be overwritten by the front panel patching!
Cool stuff!
Thanks for being a tad cranky and pushing them on some features and workflow items. I spent a few hours with the new version after seeing this and still came away a bit frustrated. I think my eurorack and Arturia synths are still the more approachable options.
Just to speak to the LED jack thing ... the sockets like Expert Sleepers and on the Make Noise Shared System bus don't effect the signal in anyway. The LED cables from Mushi.one (and anyone else) does, because it pulls current from the signal/socket to power that LED as it's in the cable itself. It's not an issue for most things, but for sensitive pitch information etc you will notice a difference.
Cool! We need to design a new patch socket that has additional internal connections for LED powering and DMX control.
Thanks for the great questions!
The main gap that exists is that NI and its team assume a higher level of synthesis on the part of people (owners or not) than currently exists.
I have had Reaktor from Komplete 7 and going under the hood beyond presets was always a road never taken beyond the menu lol
More tutorials are needed in order to know what connections can be made and why.
The new front side patching is a paradigm shift better than what existed before but to assume that we are conscious scientists of music technology is a gross overstatement.
Did I hear them say that a recommendation engine for the patching was too difficult or not desired?
Thanks again for this video!
there are more than enough tutorials on modular synthesis out there. it works pretty much the same in blocks as it would with eurorack modules, that's the whole point.
feel free to educate yourself or stick to presets.
12:14 pop up. . . shortcut keys plzzzz
It's a huge letdown that the new patch saving system doesn't work for every part of Reaktor. Please make it work with ensembles as well.. it's so incredibly annoying to keep saving whole ensembles per song project.
that probably won't happen, Ensembles are just too big and complicated to save with DAW project chunk data.
You only need to save new Ensembles if you are 'editing" the ensemble or adding samples though... are you using the new (version 6) preset saving system, I read this article recently and realized i wasn't understanding it fully myself.
support.native-instruments.com/hc/en-us/articles/209722789-Using-and-Managing-Presets-in-REAKTOR-6
I tried to get into blocks but the CPU use is just insane, I use a mix of older and newer hardware. newer hardware runs it smooth but still. whats up with the bloat? Is this a javascript thing so the interface can look nicer and be easier to skin? I have used reaktor 5 for years and still love it it runs well on Linux under wine without any issue whatsoever and allowed me to make custom headless "instruments" out of older laptops where the hardware's only programming or function is to run a single patch. Reaktor 6 bums me out this is no longer possible. comparing to VCV rack in terms of resource usage i can say VCV is less intensive even being an un optimized beta with known issues around CPU use. I am able to create more complex patches without spiking to 100%. I hope this improves I have loved using reaktor for many years, for now i will be sticking with older reaktor versions along with newer open source alternatives.
fair enough - i guess it's complex stuff
@@MoltenMusicTech I think the overhead is mainly due to the complexity but more so in making it more friendly and approachable for everyone. Older versions of reaktor were very daunting to approach while this version is very welcoming not only for users but also developers. this comes with a price of higher overhead. Newer machines are affordable though still too expensive to cart around to shows or hardcode a patch into an interactive art exhibit. Still i want to love it :D
Much of the cpu hit is due to the high quality DSP algorithms and the important requirement of all signals to be running at at least audio rate. Another chunk of it is due to highly technical reasons caused in part by limitations of the Reaktor core language. The builder community has been asking for related updates for years, but the community is very small compared to the general user-base, so it's hard to get these requests prioritised.
Ich wollte kaufen von Thomann.de Reaktor 6 ich finde nicht auf dem Webseiten
A bit confused here, but it looks like this new interface works with "racks". If you try to introduce one of the blocks from the user database it refuses and says : "cannot load user content into rack". So are NI turning this into a closed system where you have to purchase all new content? Kerching!!
Seems that way so far, it’s a new format, don’t know if it will start adapting previous blocks
What button to see patching???? 3.28....I have ver 6.30
You have to be using Blocks Base or Blocks Primes to see the front patching - it doesn’t work for previous block patches as far as I can tell
it is Kinda Like Propellerhead Reason Software
Reaktor 6.3 is not working well Many Users Have Problems. I wished i never updated .
I'm sorry to hear that.
I’m always paranoid about updating 🤪
I noticed the Kyra synth next to the speaker. A review is being baked ??
I didn't get the chance to try the Kyra - i don't know how likely it is to ever make it my way.
Right? just chilling in the corner, not like a production run is waiting to be released or anything.
So wait. Do I have to pay for Euroreakt now? Two days ago, before updating, I was using it for free
No... not sure what you mean? Reaktor 6.3 which includes the Blocks updates is free to current users of Reaktor 6 as far as I know. Are you having a problem running it?
You can keep using the version you have for free in ensembles without front patching. Keep jamming. If you want the front patching, pony up and throw the creators some coin. Euro Reakt is fantastic.
but did they add multi-touch yet?
no, they didn't. Works well on single touch though
Dude seems pretty easily intimidated for someone who spends time with music tech. I thought the NI folks did a good job of not rolling their eyes.
I was really surprised also. I have watched a lot of his videos before maybe he was stoned haha
The problem with Reaktor which they still haven't addressed with Blocks is the high CPU load they bring which makes them pretty useless to use within DAWs, for musical purposes and the fact they are still monophonic. The other is that there is no image thumbnails of the ensembles or that of the Blocks which can be taken like can be done in DAWs like Presonus Studio One or the latest version of Cubase, so they are viewable in a browser. The year might as well be 2001, when Reason made it's entrance to the world of DAWs....but even then... Reason had image thumbnails of the instruments and effects. I just wish Native Instruments would stop pissing about with Blocks and bring Reaktor up to date, integrating new and innovative things other than trying to make a quick buck and being a me too application. They need to get the old developers back, those who developed ensembles like Razor to show these developers how to be innovative and be forward thinking.... not backward thinking.
skyhawk77 razor is so badass
What high CPU load? Time to upgrade your 10-year-old Mac Pro, gramps.
the problem is that reaktor is a clusterfuck of who knows what's going to happen, sometimes amazing most times fml.
I use reaktor for some years and I.m.o. It's great. Read the manual helps.
@@rmanpojo8485 I do every day otherwise I get lost in it.. but thanks
software is boring. i'm sorry. :/
You are boring - I'm not sorry ;)
Dualtrx yep