Multiple synth timers

[d.healey]

I remember @Lindon ran into this issue a while ago and I can't remember if we found a solution for it. But is there a way to use multiple synth timers?

I'm working on a polyphonic legato thing where I need to run individual timers for sets of notes. My current thinking is I could use a separate MIDI processor for each note group, but I'd prefer to have everything in a single module.

Ideally I'd like to be able to create audio thread timer objects just like we can currently for message thread timers. Is it possible to use a background task for this purpose?

[Christoph Hart]

@d-healey you have 4 timers per container. Do you need more?

[d.healey]

@Christoph-Hart I don't get it, I thought I just have a single synth timer in a script??? In my current project I need 6, I'm working on a guitar and need one timer per string.

I actually wrote the whole thing a few years ago and it worked perfectly, now I'm coming back to finish the project and I realise I'm using timer objects so it won't work when the UI is closed.

[Christoph Hart]

@d-healey ah yes, one per script and 4 scripts per container can have a non-deferred synth callback.

[d.healey]

@Christoph-Hart oh why the limit of 4? Maybe I can sub divide the timer callback to handle all note groups.

[aaronventure]

@d-healey is there a particular reason why you can't just have the timer running while you have sound playing, and where it serves as an engine running at a specific resolution in which you do any and all logic by saving engine uptime for important events and querying deltas in the timer?

that way you can have... as many as you want.

[d.healey]

@aaronventure Yeah that's what I meant by subdivide it. Have it running at a fixed interval and use counters to track the amount of time for each task.