Re: [PD] Patchmatrix Execution Order Issues

2007-01-19 Thread Luke Iannini (pd)
Frank – sorry I didn't get a chance to respond earlier; I found a solution and have been coding that instead of reading the list in my free time : ). First, your patch is reversed from what you explained, no? M inlets by N outlets? Anyhow, only a technicality. My patch was indeed intended to

Re: [PD] Patchmatrix Execution Order Issues

2007-01-18 Thread Phil Stone
Luke Iannini writes: Sorry if I'm losing everyone : ), hopefully at least the idea of a Pd-Message-Patchmatrix makes sense to everyone and I'm just losing everyone with my implementation and explanation thereof! I don't yet understand the details of what you propose, but I certainly see the

[PD] Patchmatrix Execution Order Issues

2007-01-17 Thread Luke Iannini (pd)
OK, this is about the 16th hour (2 nights now) I've spent attempting to debug this, so I'm capitulating and asking for help : ). There was a discussion of a signal patchmatrix a while back. I'm attempting to make a message-based version of the same thing. Attached is a version completely

Re: [PD] Patchmatrix Execution Order Issues

2007-01-17 Thread Luke Iannini (pd)
I am aware of the stack overflow possibility, and I'll probably block out routings that would cause that. The intent is for the input to reach all outputs before any new input is processed (i.e. before any new input changes the routing configuration of the spigots). I see my mistake more