Studio One’s Splitter creates parallel signal paths and automatically compensates for plug-in delay between its branches before they recombine. You can build the same basic setup with a send feeding a separate Bus or FX Channel, which gives the compressed copy its own Console fader.
Both methods keep an untreated path audible while a second copy gets hit harder. Crushing the duplicate is only half the job. The useful part is knowing which control changes compressor drive and which one changes the final blend.
The setup is easier to manage once your Studio One bus and effect returns are already organized. A send-based setup makes sense when several channels need the same parallel compressor, while the Splitter is cleaner when one channel or submix needs parallel processing inside its own insert chain.
For one drum bus, bass, vocal, or instrument group, this can be cleaner than adding another mixer channel. The dry and compressed paths sit beside each other in the same effects chain, so you can see the routing without chasing sends across the Console.
Timing is handled inside the Splitter too. Studio One compensates for plug-in delay between its branches, which matters when a compressor uses look-ahead or another processor adds latency. The same dry-and-compressed summing problem appears in parallel compression signal-path design, where phase alignment between correlated paths matters before they are combined.
The branch level is not a replacement for the compressor controls. Threshold, input level, ratio, attack, release, and makeup gain shape the compressed copy. The branch level decides how much of that finished result gets mixed with the dry path.
The send amount controls how hard the compressor is fed. The return fader controls how loudly the processed result joins the mix. Raising the send can create more gain reduction, different envelope movement, and more saturation in compressors that add it, while raising only the return leaves the detector behavior alone.
Both moves can make the parallel path sound louder, which is why they get confused. They are not interchangeable. Once the compressor is reacting the way you want, use the return fader for the wet-to-dry balance instead of pushing the send and quietly changing the compression.
Sending from an existing drum bus also gives the compressor the balance already built inside that submix. Feeding kick, snare, toms, and rooms separately lets you bias the parallel path toward selected pieces of the kit instead. Neither routing is universally better, but they solve different problems.
A post-fader send lets source-fader moves alter the compressor feed, while a pre-fader send can keep that feed independent. Pick deliberately. If the detector response is already right and you only want more or less parallel weight during a section, automate the return fader rather than the send.
This matters when the compressor should react to a different tonal balance from the dry path. Rolling some low end out of only the compressed branch can stop a kick from dominating gain reduction, while the untouched branch keeps its original weight. A bright parallel vocal can get its own EQ without forcing the dry vocal through the same curve.
You can also place processing after the branches recombine when both paths need the same final treatment. The routing view makes these distinctions visible, which is a real advantage over building a maze of duplicate channels for every version of New York compression.
Gain-match before judging the result. A louder parallel return often wins an instant comparison even when it has softened the attack or exaggerated room noise. Bring the compressed path down, then raise it until the extra body, sustain, or density becomes useful without burying the transient the dry path was kept to preserve.
Both methods keep an untreated path audible while a second copy gets hit harder. Crushing the duplicate is only half the job. The useful part is knowing which control changes compressor drive and which one changes the final blend.
The setup is easier to manage once your Studio One bus and effect returns are already organized. A send-based setup makes sense when several channels need the same parallel compressor, while the Splitter is cleaner when one channel or submix needs parallel processing inside its own insert chain.
The Splitter keeps both paths inside one channel
Open the Channel Editor, add a Splitter, choose Normal mode, and create two identical branches. Leave one path clean and put the compressor on the other. Studio One mixes the branches back together after the split, and each branch gets its own level control.For one drum bus, bass, vocal, or instrument group, this can be cleaner than adding another mixer channel. The dry and compressed paths sit beside each other in the same effects chain, so you can see the routing without chasing sends across the Console.
Timing is handled inside the Splitter too. Studio One compensates for plug-in delay between its branches, which matters when a compressor uses look-ahead or another processor adds latency. The same dry-and-compressed summing problem appears in parallel compression signal-path design, where phase alignment between correlated paths matters before they are combined.
The branch level is not a replacement for the compressor controls. Threshold, input level, ratio, attack, release, and makeup gain shape the compressed copy. The branch level decides how much of that finished result gets mixed with the dry path.
Send level and return level do different jobs
A send-based parallel compression setup gives you two gain decisions before the sound reaches Main. Send a drum bus or source channel to a separate compression Bus, insert the compressor there, keep the normal dry route intact, then blend the compressed return underneath it.The send amount controls how hard the compressor is fed. The return fader controls how loudly the processed result joins the mix. Raising the send can create more gain reduction, different envelope movement, and more saturation in compressors that add it, while raising only the return leaves the detector behavior alone.
Both moves can make the parallel path sound louder, which is why they get confused. They are not interchangeable. Once the compressor is reacting the way you want, use the return fader for the wet-to-dry balance instead of pushing the send and quietly changing the compression.
Sending from an existing drum bus also gives the compressor the balance already built inside that submix. Feeding kick, snare, toms, and rooms separately lets you bias the parallel path toward selected pieces of the kit instead. Neither routing is universally better, but they solve different problems.
A post-fader send lets source-fader moves alter the compressor feed, while a pre-fader send can keep that feed independent. Pick deliberately. If the detector response is already right and you only want more or less parallel weight during a section, automate the return fader rather than the send.
Splitter placement changes what the branches inherit
The Splitter can sit at different points in a Studio One effects chain, and its position decides what happens before the signal divides. Put corrective EQ before the Splitter and both the dry and compressed branches inherit that EQ. Move the EQ inside the compressed branch and only the parallel copy gets it.This matters when the compressor should react to a different tonal balance from the dry path. Rolling some low end out of only the compressed branch can stop a kick from dominating gain reduction, while the untouched branch keeps its original weight. A bright parallel vocal can get its own EQ without forcing the dry vocal through the same curve.
You can also place processing after the branches recombine when both paths need the same final treatment. The routing view makes these distinctions visible, which is a real advantage over building a maze of duplicate channels for every version of New York compression.
Gain-match before judging the result. A louder parallel return often wins an instant comparison even when it has softened the attack or exaggerated room noise. Bring the compressed path down, then raise it until the extra body, sustain, or density becomes useful without burying the transient the dry path was kept to preserve.
