In my opinion this ridiculous EQ window should go away forever and leave its wasted space to something we really need: a trim knob.In fact the only thing I can really notice you missing is the green and black EQ window in the mixer.
In my opinion this ridiculous EQ window should go away forever and leave its wasted space to something we really need: a trim knob.In fact the only thing I can really notice you missing is the green and black EQ window in the mixer.
In my opinion this ridiculous EQ window should go away forever and leave its wasted space to something we really need: a trim knob.
To maintain the overall gain structure. I have a Gain plugin in the first slot of almost every channelstrip. And I know that I am not an exotic animal, many people do this.why would you need a trim knob in a software mixer?
To maintain the overall gain structure. I have a Gain plugin in the first slot of almost every channelstrip. And I know that I am not an exotic animal, many people do this.why would you need a trim knob in a software mixer?
I do it in any type of channelstrip. Not all plugins have adjustable inputs and outputs. Aux strips are usually fed by more than one channel. And a trim function comes handy for recorded tracks, to bring them to their desired level. Furthermore, if you use the -3 dB (uncompensated) pan law for whatever reason, you lose 3 dB of gain at every channelstrip in the chain.
To some extend yes. I like to have roughly the right levels without touching the volume faders. This is rather a personal obsession. But I know that some (or many?) mixing engineers trim all their channels before they start to mix.Is your reason here mainly to maintain visual consistency of the channel strip faders, so that a similar setting on each fader gives a similar volume output of the respective audio?
Only with plugins that are built to process audio within a certain range. Otherwise no, no impact on the audio fidelity.Or is there actually any difference in audio fidelity?
This is correct. Logic provides around 1,500 (onethousandfivehundred) dB of dynamic range and you cannot reach this limit accidently.I would have thought that with Logic's internal audio structure, the gain issues would not affect audio quality
I thought as much 🙂By the way, I love the miniature EQ view.
And - imagine 5 tracks feeding a bus that contains dynamic plugins like a compressor. Now you want to make one track louder or quieter. What now? This action may mess your settings in the bus. Adjusting the other 4 tracks just by guessing may change your overall mix. It is far more convenient to just trim the input of this bus.
But a trim knob would not work different from any other level control in a DAW. You are after the interface, after the A/D conversion. If you record noise, then it is here. A trim knob would do the same as the Gain plugin.A trim function would allow me to bring in the tape signal at a more optimal level without adding more noise.
But a trim knob would not work different from any other level control in a DAW. You are after the interface, after the A/D conversion. If you record noise, then it is here. A trim knob would do the same as the Gain plugin.A trim function would allow me to bring in the tape signal at a more optimal level without adding more noise.
...
The more we record various sources and the more we use subgroups and virtual instruments, the more we find ourselves adjusting the gain. Inserting plugins and open their GUI just for gain control is not comfortable. It's like having the pan control in a plugin.
Yes this depends on the recording path. For example, quiet sources through passive ribbon mics and a standard preamp will never deliver a "healthy" signal. In this cases it is a matter of trial and error to find out how much gain on the preamp and how much make up in the DAW gives the best sound and S/N ratio.If I've reached the point of no return on the interface but my input signal is still low, then a Trim function in the DAW would bring it up the signal to a healthy level.
Both have the same effect. It's just math. You add a certain number to the volume value of each individual sample. Increasing the gain in an input channelstrip can clip your track because it gets written to disk. I think you better use the Gain plugin on the track. Same result and safer.Right now to do that in Logic, I need to create an Input channel strip in the Environment, then insert a Gain plug-in ...
---
Or I can add the Gain plug-in after the signal is recorded.
Absolutely, we could set rough levels very quickly across many channelstrips and adjust the levels for correct plugin input at any time without inserting plugins just for gain control.Having a Trim function built right into the mixer channel strip would be a welcome addition as it would eliminate some set up time.
I just entered my request for a Trim knob on each channel strip.It's time to ask Apple for trim knobs again, right?
http://www.apple.com/feedback/logicpro.html
I think we need just a few thousand requests to get them
Yes this depends on the recording path. For example, quiet sources through passive ribbon mics and a standard preamp will never deliver a "healthy" signal. In this cases it is a matter of trial and error to find out how much gain on the preamp and how much make up in the DAW gives the best sound and S/N ratio.
Thank you!!! You comment here really makes sense. Adding the Gain afterwards is indeed safer and offers more flexibility in shaping the sound non-destructively.Both have the same effect. It's just math. You add a certain number to the volume value of each individual sample. Increasing the gain in an input channelstrip can clip your track because it gets written to disk. I think you better use the Gain plugin on the track. Same result and safer.
Interesting bit of Logic history. I'm ok with the illogical location of the I/O but having it in it's proper place in the first slot would be a strong visual reminder of signal flow.Therefore I usually have a Gain plugin in the top slot and don't touch the volume knob of the instrument itself. This might not sound logical to everybody but actually the instrument plugin is the first one in the chain. And it was originally at the top, before the I/O section got shifted down to a position in the channelstrip where it does not belong to.
We use essential cookies to make this site work, and optional cookies to enhance your experience.
Please note that in order to help fund the site we may serve ads by via Google AdSense, and cookies may be used for personalisation of these ads to make them more relevant. These are optional and you can choose to enable/disable any such cookies in your preferences:
Click here for further information and to configure your preferences