Hello 111,
The issue with the previous code was that we were passing the frames in to the render call of the wedge node. So frameTuple was ( start,end,step ), for some reason Wedge nodes interpret this as render the output driver ( for all frames it is set up for ) once per frame in the range.
What this meant in our case was that if a task was frames 1-5 it would render frames 1-5 5 times each. We fixed this by not passing a frame range into the render call ( setting frameTuple to an empty set ).
Grant