Pro Tools harware insert wierdness

[Chinagraf]

Hi, I have a strange thing happening and was wondering if anyone has any ideas as to what's happening...?
I've posted on the DUC but thought maybe someone here working hybrid might have any sort of ideas?
My setup is Win 7 with SSL Alphalink converters. This is happening on both PT10 and 11 native. I have an SSL compressor on hardware inserts 1&2. I have a bunch of hardware.reverbs on inserts 25 - 32.
I use 17&18 to feed my monitor switcher.

1. I setup my Bricasti M7 on an aux track, it's on hardware inserts 27&28. All fine until I add a master fader and insert the SSL comp (on hardware inserts 1&2) on the master fader, then the reverb disappears. I can still see the reverb returns metering but no audible reverb.

2. However, if I setup an AUX input first, send all the channels to it and buss this to the master fader, everything works fine and I hear the reverb return BUT only if the SSL comp is inserted on the master fader. If I insert it on the AUX track everything is bussed to , the reverb return disappears again, but I can still see it metering on the channel again.

3. This is only happening with hardware insert 1&2. All the others work fine, but here is something else - Inserting the SSL comp that is on hardware inserts 1&2 only cuts off the other hardware inserts if they are on an aux track. If they are inserted over an audio track they keep working as normal.

4. I've checked all my default i/o for ins out busses, everything and nothing is set to output 1&2 as default. Is there any possibility ouputs 1&2 are reserved by the system for some purpose I'm not aware of. You are able to configure your i/o anyway you like aren't you?

Anybody got any hint as to what could be at the root of the issue?
Thanks for any insights.
Cheers.

[Ben M]

Have you tried in "I/O" (output) to make the audition paths "no output".

Trying to think of things....

[Chinagraf]

HI Ben, yep tried that. It's like I have 1&2 reserved for something that I can't find. What is bizarre is that is does work when I route to an aux then master fader and put it on the master fader insert. If 1&2 are tied up somewhere I would've thought it wouldn't work on the master fader insert either. I don't know for sure if it ever worked right because I'm usually using the MP after the SSL and doing it on the patchbay. I only noticed it in the last few weeks but it's only since then that I've been doing more intensive mixing on PT.

[Text_Edifice]

Is low latency monitoring turned on?

In the dim recesses of my brain there's something pinging.

[gigpiglet]

not something i usually use
so take this advice with a grain of salt
but first thing i would do - is use inserts 3 and 4, and go through all the steps again
does any/ all of the behaviour happen on this different pair of inserts?

if not - then like you say - there must be something about 1 and 2 (being reserved, being low latency, being… something)
but if it happens for ANY pair - then it could be an issue with what you are actually trying to achieve (or the way you are trying to achieve it)

I've had issues with things like that in banks of 8 (which is how the PT i/o defaults i guess) so maybe try using 9/10 or 21/22 rather than 3/4 for the test

[Chinagraf]

Dave! Yes!
Low latency monitoring was on and yes that seems to have been the cause. Your dim recesses are not so dim.
Thanks for the replies. It was only happening with outputs 1&2 so perhaps they are the ones that work as low latency monitoring? I'll have to switch the feed to my monitor switcher to find out.
Thanks TR brainstrust.

[Text_Edifice]

yeah it's the dumb workaround implemented in pt10 - from memory pt kills those outputs so you can route them through your hardware / software mixer. Kinda like the knob on the front of the m-boxes.