Actually you would not have been happy when we’ve disabled this in a connected Hydra as well?
Yes, we’ve decided to allow this with Hydra at the end, cause its too much fun. But its indeed still a problem:
Connecting a SF to something thats left from it, track wise, will introduce latency in the transferred envelope. Not just that, it will introduce a kinda random amount of latency, that is differnet on every setup - depending on the buffer settings you’ve set up for your sound card. Sidelick and other plugins do actually have more or less the same problems.
Thats the reason why you can not route a SF to previous tracks. If you do bypass with a hydra, we think you know what you do (Hydra is for nerds only), and can live with that latency.
There were other situations where it was a lot. Some VST effects might feel real sluggish.
The worst part is the random latency and if you are doing live stuff, you are not going to like that you have to scratch your head every time that you have posted your setup on stage and have to figure out which device was connected how to fix it, but it is Beta, so ofcourse the best time to test if the latency really is causing problems if various devices are hooked differently in the same setup.
What you also don’t know was that there were issues with Multiple CPU environments (crackling and that sorts of things). Appearantly, the Hydra does not seem affected by these issues (anylonger)…
It won’t break anything, thats right, but the problem is that this latency, even though its often small, is not fixed. It will be different every time you’ve changed your soundcards latency settings, or play the song on a differenet setup.