Dear Roman, Frank, List
Roman Haefeli wrote:
while not being 100% sure, what frank meant with the other timing domain, i guess, he meant all the messages, that are not initiated by [metro]/[delay]/[pipe] and co. this would be messages from:
- the guis and clicks on message boxes
- networking objects [netreceive]/[tcpreceive] etc.
- [hid] / [comport] / [arduino] / [wiimote]
- [cltin] / [notein] / [midiin] etc.
- probably more
all those messages lack the extra timing information and thus are executed only at block boundaries.
I'm just interested, how would you argue that the logical timing of the following is sub-adc/dac-block (which it is)?
[t b b]
|
|
|
|
[t b b] [random 100]
| |
| [/ 100]
| /
| /
| /
[delay]
|
[t b b]
| |
[timer]
|
[print]
Clearly we all agree that [del] follows Pd's time tagged execution. So this time tag must be set with respect to the whole logical tree, including the new value given by the [random] object, right?
cheers,
Peter