16 Mar
2011
16 Mar
'11
2:05 a.m.
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.
Sorry, not quite exact yet.
It seems that:
- if I send the frame number to pix_film just before (in zero logical
time) I turn on its gemhead, then it works fine (renders the new frame immediately
- if I send the frame number to pix_film just before I send it the
gemlist (i.e., triggered by a [t a b] fed with the gemhead), then it doesn't generate the new image until the next frame.
This MAY be expected behavior. Can anyone confirm?
thanks m.