- This topic has 21 replies, 4 voices, and was last updated 9 years, 6 months ago by
.
-
Posts
-
No nothing like that exists.
The current method was working for me when i was working with TX7 but i imagine different hardware will react differently.
Also what do you mean by ticks, ticks of time, or a tick as a value difference in a modulator ?
by ticks i guess i meant an approximate number of times per second, for the purpose of sending a ‘snapshot’ of a single parameter that is being changed or has recently changed only that many times per second, rather than sending each and every increment to the device.
delay in milliseconds still sends an enormous amount of data, just slower. i’m talking about keeping things real time and chopping up the data flow to something like x “frames per second” from a parameter being changed, for when the hardware is ancient.
i suppose this would need its own class, useful for 1) old synths with this problem or 2) knobs with lots of increments where rapid movement might cause buffer problems.
maybe some old gear doesnt have the problem of the tx81z because they might have their own limitations as to how many values it can sense via its own counter?
- The forum ‘Using Ctrlr’ is closed to new topics and replies.