Forums › Forums › SQ Forums › SQ general discussions › Reverb ducking…compressor on FX return
- This topic has 16 replies, 7 voices, and was last updated 3 years, 8 months ago by ioTon.
-
AuthorPosts
-
2021/03/17 at 8:19 pm #99899AndyParticipant
How can I put a compressor behind the FX return for the use of vocal effects ducking? I have an SQ5 board.
2021/03/18 at 12:14 am #99903ioTonParticipantYou can use an aux and insert the FX in the aux-bus. But then you have to use a matrix as main out, because auxes couldn’t be send to LR.
gg2021/03/18 at 12:56 am #99906MarkPAmanParticipantWould routing the effects return through a group get you what you need?
2021/03/18 at 10:49 am #99912SteffenRParticipantsimply use an input channel as return?
2021/03/19 at 12:15 pm #99935AndyParticipanthow do I set up using an input channel as a FX return?
2021/03/19 at 5:00 pm #99936SteffenRParticipantIs this not possible on SQ? Could be dLive only… wasn’t thinking about that…
2021/03/20 at 12:35 pm #99951AndyParticipantSo…can you route the effects return to a channel?
2021/03/20 at 1:14 pm #99952Andre SParticipantNo, sadly you can´t. Input channels can “only” be sourced from Local, SLink, USB Port, I/O Port and the Signal Generator.
Cheers,
André2021/03/20 at 4:19 pm #99963nutsusaParticipantI also agree with the ability to route effects to channels.
That’s because there are times when you want to narrow the PAN width of the effect return or make it MONO.
You just need to be able to narrow the width of the PAN for the effect return.2021/03/20 at 7:14 pm #99984Mfk0815ParticipantThese routing limitations (no routing of aux busses to main LR and no routing of FX returns to input channels) is really one of those hidden disadvantages not obviously mentioned in marketing documents. I am aware that A&H has some really special ideas of what to allow users and what not, no matter what is the standard in this market. I hope that A&H will rethink their strategies soon and add these routing possibilities to the SQ series.
2021/03/21 at 10:12 am #99997ioTonParticipant+1
but i can understand A&H – there must be a difference between dlive and SQ… sadly…
2021/03/21 at 10:58 am #99998AndyParticipantYes please
2021/03/21 at 11:12 am #100000Andre SParticipantWell, there might be some limiting factors, that have nothing to do with marketing (or add to it)
1.) The SQ has a less capable XCVI core than the Avantis or DLive. That means it can´t process as many audiopath and the processing that comes with it.
2.) That core needs to be programmed. The more complex the algorithms, the more programmers (or more workhours) you need. I think that adds a lot to the costs.
But of course I would also love to see many more routing options, more busses, more matrices, more effects, a USB interface that records 48 outputs,…
Cheers,
André2021/03/21 at 11:23 am #100001Mfk0815ParticipantHmm, for routing aux busses to main, what is there the essential difference to subgroups? Especially how much more processing is required to send the aux master signal to main in opposite to sending the subgroup to main?
And how much extra processing is required to pass the fx return to a input channel?
I would say nothing or very less, because imho there is no extra signal processing required. It only differs in the signal source and signal sink.
I even do not think that there is a real problem with latency or phase coherence for sending aux masters to main.
Imho this limitations are by organisational design and not caused by technical limitations. A& H simply do not want to allow such routings.2021/03/21 at 2:14 pm #100006Andre SParticipantA& H simply do not want to allow such routings.
How do come to that assumption?
-
AuthorPosts
- You must be logged in to reply to this topic.