Tepeix wrote:I suppose 10ms must never miss a sample.
The approximate rule is this: Green value changes (not triggers, strictly speaking) at blue/white inputs can be missed whenever the time interval between changes is smaller than the audio latency time (DS/ASIO buffer size). Below this time, shorter intervals make misses more likely, though exactly what (if anything) gets missed is subject to 'green' timing randomness. As you found, "splitting" and "merging" a trigger, so that it hits the same component more than once, is the worst - in effect, that's no delay at all, so can cause misses on any system.
Explanation: Audio drivers and VST hosts always request whole buffers full of samples, and it's essential that these are delivered as quickly as possible to avoid nasty audio snap, crackle, pop! So audio is deemed "high priority" and 'green' is deemed "low priority". But this raises a problem - how can a "low priority" triggered green event (or worse, an unpredictably branching cascade of triggers) affect a specific sample within a "high priority" buffer-filling routine? Either the "low priority" work must interrupt and slow down the "high priority" work (snap, crackle, pop!), or the sharing of data between them must be limited somehow (sacrifice timing precision).
So, the FS "one sample at a time" ethos is only really a facade for coding convenience. When the soundcard/host wants a new buffer full of samples; green processing is stopped; a new buffer is filled with audio samples and delivered; and then 'green' processing resumes. This has two main consequences**...
1) All of the audio samples in the same soundcard buffer will "see" the same 'green' input values.
2) 'Green' values can change multiple times in-between buffer requests, so that the audio streams miss them.
Note that this is certainly a huge simplification: for example; sample-accurate MIDI events (e.g. poly notes) are treated differently (also some Ruby stuff, maybe?). No doubt only MyCo and Malc know all of the finer details.
Tepeix wrote:But who know.
Grizzled old-timers like me, mostly!
In ye olden days of SynthMaker, soundcard latencies were often HUGE compared to nowadays, so; (a) misses were a much bigger problem back then, and (b) it was much easier to diagnose.
Tepeix wrote:the modified version will always be true for 1 sample.
You discovered the perfect solution in any case!
** There are actually three main consequences: The third is that many sensible persons (and some insensible ones like me) might now finally be freed from the perennial quest for the much-sought and long-fabled Sample-Accurate Kilohertz Green Super-Trigger. I have so much more time for my unicorn hunting now!
