02.02.2013 Views

1. First steps in Reaktor Core - Native Instruments

1. First steps in Reaktor Core - Native Instruments

1. First steps in Reaktor Core - Native Instruments

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9.2. Rout<strong>in</strong>g and merg<strong>in</strong>g<br />

Rout<strong>in</strong>g can be more or less CPU <strong>in</strong>tensive depend<strong>in</strong>g on the situation and<br />

the platform. If you can avoid rout<strong>in</strong>g without add<strong>in</strong>g other CPU-<strong>in</strong>tensive<br />

operations to your structure, do so.<br />

Sometimes ES Ctl rout<strong>in</strong>g can be replaced by us<strong>in</strong>g Latches. If possible, do so.<br />

If you split the event path <strong>in</strong>to two branches us<strong>in</strong>g a Router, it’s a good idea<br />

to merge the branches generated by the outputs of the Router:<br />

It’s also a good idea to merge to the <strong>in</strong>com<strong>in</strong>g (unsplit) event to the Router:<br />

Merg<strong>in</strong>g is not necessarily done by us<strong>in</strong>g a Merge module. Any arithmetic or<br />

a similar module will do the job:<br />

Merg<strong>in</strong>g can also happen <strong>in</strong>side a macro (depend<strong>in</strong>g on its <strong>in</strong>ternal structure):<br />

It may be reasonable or necessary to merge the branches generated by different<br />

Routers, but beware of higher CPU loads <strong>in</strong> that case.<br />

140 – REAKTOR CORE

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!