This seems to be the "workaround" for now...
I think I have been able to locate and fix this bug. Until it is released
the workaround I can think of is to never change the routing
so that a new output becomes used when using a sample rate
other than 44k1. So, when you change your routing you go:
-temporarily set sample rate to 44.1
-change routing
-bring sample rate back to whatever it was