Yes, that is correct, the only benefit would be noticed during the time index parameter is an integer.(0,1,2,3,…)
But as this is quite often the case (when you’re finished doing a crossover between inputs and have chosen the input you want to see), I thought it would be a useful enhancement to stop unnecessary cooking in your network.
Somehow when I open your file in 2017.1900 (or 088) all nodes have all parameter modes set to Constant instead of Export, so it took me a while to see what you meant. But yes, when i enable all exports your chop network simulates the requested behaviour, in turning blend mode off when index==integer.
I saw that too… not sure what happened to my exports.
Seems like you might loose a frame in transition when you started crossing between inputs again - and therefore had to start up cooking on the next input. Does that seem okay to you?
In building out that little tester I also noticed that those index can be very fincky… 0.9999999 is still input 0 when blend between is off. Do you think a part of this would be some indication of a rounding tolerance around those values?