hi there, I hope this is the right category...
it would be great if all data inside a 32b table could be 'cleared'
programatically.
for example,the 'table 32b' could have a 'trigger' input for clearing.
I'm working on a multitrack looper,it would make things a lot easier...
cheers, rbrt
hmm depending on the size of the table, clearing a table is likely to cause buffer underruns.
Perhaps you could use table/record to record silence into the table? Or mute the playback of that table?
Perhaps you could use table/record to record silence into the table?
that's going to work for sure,but it will make the actual looper-objects more heavy...
so in general,it's not easy to clear or re-initialize a table in real-time?
(I'll take the record-silence approach then...)
It is better to spread operations over time, rather than clearing a table at once.
Real time depends on the worst case, not the average or best case. Clearing a table at once 'd cause a surge in the workload, spreading that workload is a better strategy.
..thanks for the info,
I'll do it like that then..
the first sketch of a looper-object should be on git in not-too-long...
Wouldn't the time needed to zero the table be predictable? So maybe it could be split over a few samples/ticks with a static variable in the object, so you'd zero the first part first and then during the calculation of the next sample start where you left off? Or maybe with firmware support you could use a DMA channel to do it...