![]() ![]() Audio inputs, on the other hand, create a new value for every tick of the sample clock, regardless of whether a new value has arrived or not. Event inputs are simple to understand – a new event is created when one arrives at the cell input. ![]() Very briefly, it is important to cover the functional differences of audio and event inputs in Core. Reaktor styring code#If you can, it is best to contain all Core code for a project within a single cell. The takeaway from this is that translations from Core to Primary should be avoided as much as possible. This setup takes less than 1% of my CPU, a very substantial difference for two functionally identical designs. The following method is substantially more efficient: The result is that even this simple structure takes up 3.5% of my CPU. However, in between each cell, there is a translation from Core to Primary, then the signal is immediately translated back to core. Here, a simple Audio Core Cell is repeated 4 times. Reaktor styring how to#Take, for example, the following structure (which is not functionally useful, really, but just an illustration of how to use Core efficiently): While many tasks can be performed faster in Core than in Primary, there is some inefficiency caused by the need to translate from one to another. Core cells can be easily inserted inside a primary structure the same way any other module or macro would be. Visually, event inputs are marked red as in Primary, and audio inputs are marked black. Inputs to Audio Core Cells can be set to either event or audio rate in the FUNCTION tab of the properties: Audio Core Cells can receive both audio and event inputs, but can only use audio rate outputs, which can occasionally be rather frustrating when you want a cell that can receive audio and output events. Event Core Cells can only use event rate inputs and outputs. These modules behave very much like Primary macros, the difference being that the code contained within them is written in Core and not Primary. There are two modules that allow this: the Audio Core Cell, and the Event Core Cell. Since any Reaktor project must use Primary as a method to connect to audio ins and outs, and since panel elements such as knobs and switches only exist in Primary, it is necessary to interface any Core code inside a larger primary structure. Let’s get started! INTERFACING WITH PRIMARY The scope of this topic all but guarantees that this guide will be split into smaller sections. Core has many advantages over Primary mode, including improved CPU efficiency for many tasks, more data types, better data handling and manipulation, better handling of event streams, and more. In this tutorial, I’ll start going over the basics of programming in Reaktor Core. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |