PreSonus Forums

My setup is
dbx 160A. Output 4 Input 4
dbx 160XT Output 5 Input 5
VLA II. Output 6 Input 6
Pultec Clone Output 7 Input 7
1176 Clone Output 8 Input 8

Part way through the mix session my dbx Compressors stop working and eventually the other gear goes out too.
Sometimes I can restart the song and everything is good but this isn’t working as much anymore.

What happens is the pipeline XT shows signal on the SEND meter but nothing on the RETURN meter.

PS
I render each track using pipeline XT before moving onto the next track.

Have you checked with Focusrite Support on this issue?

That never occurred to me. I didn’t see how this would have anything to do with my interface.

Do you think the glitch might be there?

I was trying to set up my presets today so I ran the tone generator through pipeline and finally into the VU meter to calibrate everything.

It’s working great. Both send & return meters are functional and now calibrated to -18dB.

It’s got to be like something super simple I’m missing.

At the risk of sounding like a me too I also have seen this problem.

The reason I think it’s worth mentioning is that I’m using a dbx compressor and also a Focusrite 18i20 interface.

Perhaps there is something in these combinations of hardware that is causing a problem. I’ve never been able to pin it down. A restart of the software is my usual solution.

Cheers Jason

It can be really hard to diagnose if a problem is hardware or software.

My the headphone amp on my 1820m quit and I bought a headphone amplifier.

Year later I redid the computer and it was back working. I thought that was hardware for sure.

Have you got a small mixer with headphones? I would wait until it fails then check the outputs and see if signal is getting to the ports.

Maybe, troubleshooting is hard. Maybe set up a track and send it to that output and see if signals can get there when Pipeline can not.

There are rules though:

1. TRY EVERYTHING!

2. Only do one thing at a time.

Tuoni64 wroteAt the risk of sounding like a me too I also have seen this problem.

The reason I think it’s worth mentioning is that I’m using a dbx compressor and also a Focusrite 18i20 interface.

Perhaps there is something in these combinations of hardware that is causing a problem. I’ve never been able to pin it down. A restart of the software is my usual solution.

Cheers Jason

Thanks so much

So does restarting give you a lasting fix. If not how much time does it typically buy you before it goes down again?

Hi Frank,

Apologies fort he gap - I've been offline a bit. Generally it works for the rest of the session (I think). I tend to print the tracks as soon as I'm happy with them to free the compressors up for other work (I only have a pair of them) so probably wouldn't notice if it had stopped again.

I'll keep a closer eye on things now and see if I can see any kind of pattern. I am at a loss to explain it as all the indicators are that sound is going places except that there is no return signal in the plugin. That is, I can see the output metering on the compressor and I can see the input levels on the Focusrite mix software both indicating a signal. I can't recall checking the input matrix in S1 to see if there was a signal in the little meter it displays against each input - I'll look at that next time I encounter the problem.

I just chalked it up to a glitch and live with it. I spent years working in analogue/24 track studios where generally one or more bits of outboard gear were considered 'dodgier' than others and dead channels on the desk were common so I'm perhaps tolerant of just living with the problems! Of course we're not talking Abbey Road quality here

Cheers,
Jason.

Trucky wroteHave you checked with Focusrite Support on this issue?

I just did a short while ago. The representative is going to do some research and get back to me.

Tuoni64 wroteAt the risk of sounding like a me too I also have seen this problem.

The reason I think it’s worth mentioning is that I’m using a dbx compressor and also a Focusrite 18i20 interface.

Perhaps there is something in these combinations of hardware that is causing a problem. I’ve never been able to pin it down. A restart of the software is my usual solution.

Cheers Jason

I was able to chat with a focusrite representative. He is going to do some research and get back to me.

Anyone figured out a solution for this Pipeline XT issue. Mine was working fine, now when I open a project in the latest Studio One 4.5 I have the same issue as listed in the original post. The plugin shows the input, but no output. I know my hardware (Symphony I/O MKII with 16x16 and 2x6se cards) is all connected correctly because I can open a project in both Logic Pro X and Pro Tools 2019.6 and the I/O hardware inserts work perfectly. I'm really wanting to transition to Studio One but hardware inserts are a large part of my workflow. Anyone else using the latest Pipeline XT without problems? I've uninstalled Studio One and re-installed, but still no go.

I get the same behaviour but when in solo. I have made a post and just posted a video

Mine works now and it was a super simple fix. I’m trying really hard to remember what it was though.

I think it was as simple as deselecting and re selecting the track after instantiating pipeline xt.

I seem to remember trying every possible fix and contacting support and researching posts etc. I might have even contemplated buying a more powerful interface.

Trucky wroteHave you checked with Focusrite Support on this issue?

Yup
No other documented cases.

Finally figured out my Pipeline issue. I recently upgraded to Mojave and had not gone in to my security settings and given Studio One access to my microphone since I'm thinking "I don't use the internal mic." Doh...Apple considers whatever you are using as your interface your microphone. It was just a simple click and now everything is working great.

Did someone find a solution for windows?

I switched to the Quantum interface and everything works fantastic.
I’m inclined to believe that in some way it was related to the Mix Control software.
I’m not saying that the software is bad only that maybe it’s not optimized for pipeline use.

If you decide to record more tracks and happen to use the same inputs and/or outputs that pipeline is using then it can cut-off audio to an external unit.

vahevahe wroteIf you decide to record more tracks and happen to use the same inputs and/or outputs that pipeline is using then it can cut-off audio to an external unit.

I primarily use pipeline for mixing, specifically adding outboard compression. I render the track then instantiate another pipeline on the next track. What typically happens is that the signal is interrupted and the ping is useless. I’ve found that I just need to click on any adjacent track then click back and re ping and I’m good to go. I have no explanation as to why this works, it just does😁

Frank Crow