Originally mentioned the thought of this over in this request.
Essentially, it would be nice if the 16 dedicated stereo RackFX returns could be reworked as a class of patchable generic input channels with limited processing (PEQ only, as it currently stands). The use case would be for inputs that don’t require much, if any processing, and thus are “wasting” the DSP allocated to a standard input channel.
This would be particularly convenient for me, because I use standard AUX buses for my sends and full input channels for my returns, in order to get the extra processing available with those components. Unfortunately, that leaves me with 16 stereo channels that are effectively being wasted.
An example of how I would take advantage of input channels with limited processing is drum triggers that are being used for the side chain of a gate on your drum mic inputs. The triggers don’t need any real processing because they’re simply capturing a transient that informs the gating of the corresponding mic channel.
You could also use these as the return channels for an external processing solution, like Waves SuperRack.
Ok, I know there can be reasons to do things that way, but you are using input channels as returns, and then ask to repurpose the fx returns as channels. It seems a bit backwards. You can still use normal the auxes for the RackFX while using the dedicated return channels. Most people would just do that and save the regular channels for…channels.
Yep, I’m aware you can use a standard AUX along with the built in FX returns. For many people that’s absolutely sufficient and in many cases, maybe even the best solution.
However, I like to being able to leverage dynamics processing on my FX returns which the dedicated returns do not have. In that case, it’s not by any means unreasonable to use a standard input channel to get that processing.
Another reason I run standard input channels for my FX returns is because it allows me to use ABCD inputs to switch between the onboard FX racks and outboard FX plugins in Waves SuperRack Performer with an Action. If I used the dedicated FX returns, I wouldn’t be able to do this.
I’m not saying everyone should run their shows my way. That would be silly. My workflow is just one of many. I have no idea how technically feasible the suggestion is, but that’s not really the point. The dLive is Allen&Heath’s flagship console. If implemented, the suggestion really just makes the console more versatile and thus more suitable for a variety of workflow needs.