Vincent Burel wrote:sure, when we say "Pre-Fader" , it means before Intellipan, Comp, Gate...
![Arrow :arrow:](./images/smilies/icon_arrow.gif)
![Image](https://cdn1.imggmi.com/uploads/2019/1/16/3b8b9d75fd0fe2f17b73d3216c4b7594-full.png)
![Exclamation :!:](./images/smilies/icon_exclaim.gif)
Quod erat demonstrandum!
Besides Intellipan, Comp, Gate the ASIO PATCH INSERT is also affected by this glitch!
What do we do now?
I have a high latency workaround with VB CABLE.
And I have a ultra low latency workaround by using a modular host for PATCH INSERT to clone HW inputs.
I hesitate to give you detailed instructions, because I think it would be easier to fix that glitch in an update to keep the level of confusion for normal users as low as possible.
For advanced users only:
![Image](https://cdn1.imggmi.com/uploads/2019/1/16/f500a0e21b19f5e98b783d34add4b502-full.png)
Though we have not selected a device for Hardware Input 2 it shows an input signal! This is the untouched input signal of Hardware Input 1 that we have cloned in our ASIO (VST) host app by connecting Patch Insert In#1 stereo input with Patch Insert In#2 stereo output.
I hope that besides PRE-FADER fix an update would change the routing.
The ASIO PATCH INSERT should be first post input pin (pre-fader pin) followed by INTELLIPAN, Comp. and Gate.
At the moment ASIO PATCH INSERT is post INTELLIPAN, Comp. and Gate and this way it is really a waste of opportunities.