On 03/16/2011 01:12 AM, Jack wrote:
Have you try [route gem_state] after your [gemhead 1] ?
Tell me if that work.
It doesn't.
I've also tried:
[route gem_state]
|
[list prepend gem_state]
|
[list trim]
which is, I guess, what you meant; but it works exactly as before (i.e.
suffers from the same issue). I wouldn't expect anything to change,
since gem_state should be the only message that comes out from gemhead
Your patch seems complex, I don't test it.
Obviously you don't have to.
I did take care to reduce the patch the bare minimum that I thought was
needed to reproduce the issue (but I was wrong about that), and in such
a way that only one click was needed to test it (I could have made it
simpler but then you would need to follow accurately a complex set of
instructions to reproduce it).
However I've found out I was wrong when I said:
I cannot reproduce the same problem with only one gemhead. With only one
gemhead, if I send pix_film a new number, and immediately turn on the
gemhead, as soon as the rectangle appears it already shows the new
frame, as I expect.
This is not true. The same issue DOES exist with only one gemhead. If
pix_film receives the frame number just before its gemhead is turned on,
it doesn't render the new frame untill one frame later.
If however the frame number is received more than one frame before the
gemhead is turned on, then the new frame is rendered as soon as expected.
I'll send a simplified test patch later.
Thanks
m.
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
