I did havePF_OutFlag_WIDE_TIME_INPUT set, but for a while I had it under second list of "out_flags" as opposed to "out_flags2" ... definitely confused me for a bit trying to interpret all the PiPL flag errors I was getting.
GuidMixInPtr() fixed all the render glitches for me, thanks for that suggestion! It also forced me to learn how to implement the smart render system, which I can see having huge benefits as I get deeper into this.
Something I ran into was a whole bunch of memory write access errors...it took me a while before I realized it would only happen when I tried to write to a pixel outside the render area..(this would happen if I 'wiggled' my point parameter off the screen) To fix this I have started passing the "input_world->extent_hint" to all of my PF_Pixel functions and running a check to see if my pixel is within the PF_Rect before it writes it to the output_world at that point....sometimes I have to pass it a few layers deep ( SmartRender() > MyLineAlgorithm() > PF_Pixel() ) is there a better way to do this? Not sure if it's a common enough problem for you guys to run into.
One other little question is about calculating parameter values between frames...currently I use "current_time - 1 * time_step" to get the value of a parameter at the previous frame. If instead I multiply a fraction of time_step, would I get in-between values?
Thanks!!