nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to change the sample rate of individual instruments within an ensemble.

Studiowaves

I made a little 4 channel recorder using multiple audio tables. It works but the audio tables always seem to follow the master sample rate for the ensemble. I assumed the tables would react to an address changes and read or write to a specific memory located within the table and stop using cpu until the next address change. However even if you stop the address changes and use a duplicate filter to block successive clocking the audio tables continue running at full speed. Apparently the only way to reduce the cpu usage is to change the master clock of the whole ensemble but I only want to change the sample rate on one of the instruments which is the recorder.

Not sure why the audio tables continue running at full speed when the address doesn't move, but maybe there's a way to stop that. Any ideas?

Find more posts tagged with

Reaktor 6

Comments

Chet Singer

Audio tables always run at full speed because they have audio inputs. They're like filters, in that they're always operating.

If you want to clock a table at something other than the audio rate, use an event table. But running event tables at high clock rates might cost more CPU than using an audio table itself.

Studiowaves

https://community.native-instruments.com/discussion/comment/263988#Comment_263988

Too bad the tables run all of the time, they don't really need to continue running unless the address changes for another read or write to a memory. I can pause the location address and they keep running. That cpu adds up when you use a lot of them. I made an 8 channel 5.5 second recorder if the sr is 48k. At the most it reads or writes to a max of 8 memory locations at a time. Yet it uses a tremendous amount of CPU compared to what it's actually accomplishing. We need an event driven system that responds to a new address , or a read write change. Then just set there doing nothing until a new event hits it. I really don't get it. My guess its doing other thing for the other features it has. I wish had a simple version.

silvermoats

my hot tip of the week for saving CPU is that you can deactivate any Reaktor element by running it through a Switch module and shutting that off, which you can do through an IC send so that it happens automatically on receiving certain values elsewhere in the signal chain, no need to click it off manually :)

Quick links

Unanswered questions