![]() ![]() Within Core (the lower level programming area), the biggest change is that there is no more distinction between event or audio cells, which means you can use audio rate signals for control, a feature useful for all kinds of advanced synthesis. Table Framework data is stored with snapshots as well, which makes it much more convenient to associate audio samples with Reaktor presets. This allows you to do things like drag-and-drop a sample from the browser into Reaktor and make that sample data available to any macro or core module in your ensemble. Within the Primary patching area, the biggest change is probably the Table Framework, which is essentially just a new way for Reaktor 6 to handle sample data. There are some important changes hiding beneath the surface as well. Renaming modules is much easier now as well, as it no longer has to be done via the properties view-simply double click the module name in the structure view to change it. (If you're partial to the old colors, you have the option to switch back.) Instruments and macros now have two possible view options in the structure view: Compact, the same view as in previous versions, and Flexible, a larger option allowing for more descriptive naming of ports and modules. The most obvious is the new color scheme, which I found to be much more attractive. The structure view also received a number of helpful visual updates. The properties view and browser both received major attention, with the latter following the recent browser standards set by other Native Instruments products like Maschine and Komplete Kontrol. Many of the changes focused on improving the visual aesthetic and workflow of the patching environment. Among its many updates was a new modular instrument format called Blocks. The wait for a new version was still a topic of conversation for many, but that all ended this past September when Native Instruments announced Reaktor 6. Products like Monark, Razor, Skanner XT, Prism and the excellent Molekular kept the world of Reaktor feeling fresh and provided repeated opportunities for producers to make the jump into designing their own instruments. Version 5 of Native Instruments Reaktor managed the feat quite well due to a number of factors, namely the combination of a robust library of user creations and a steady stream of impressive commercial instruments designed for the platform. There aren't many examples of music software that can survive for ten years without a major version upgrade and still stay relevant with an engaged user base.Plus, new features like Table Framework, Bundles, and Scoped Buses unlock a new level of power for REAKTOR builders. Workflows are now more efficient thanks to a modernized interface, improved structure editing, and a revised property and navigation. Primary and Core Macro libraries are refined for ease of use with new categories and intuitive folder structure. Whether used as an instrument or hardware control device, standalone REAKTOR 6.1 with Link offers hassle-free timing sync with one or more devices and apps, including MASCHINE, TRAKTOR, iOS apps, and Ableton Live. Twisted Tools, Tim Exile, Heavyocity, Blinksonic, and Tonsturm were the first wave of partners. REAKTOR 6.2 introduced third-party instruments for REAKTOR and REAKTOR Player. The REAKTOR 6.3 update featured Patch’n’Play functionality, allowing front panel patching to completely overhaul the experience of virtual modular synthesis, as well as introducing BLOCKS BASE and BLOCKS PRIMES and bringing leading instrument makers including Unfiltered Audio, Holonic Systems, Toy Box and ACL into the Blocks ecosystem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |