Fader position determines the level added or subtracted from Unity as it's sent to the Main or Bus.See attached pic.
Notice the red circle which shows the track is at 0.0 and then look at the yellow circle which shows the fader is around 6.
Is there a fix or is this a bug?
Thanks
Me, in conversation with my wife at least twice a day.Forget it, I was wrong.
BRAHAHAHA, dude you're funny!Me, in conversation with my wife at least twice a day.
Yeah I do get that, not sure I totally understand either but as long as it's not an issue, and it seems it's not, I'm good!Hehe. ^^^^^
@topic: I'm not sure I understand what Drew is saying. Maybe one of the biggest mysteries for me is understanding parts of meters, I just make sure they don't clip and things sound as good as they can to my ears. The numbers don't really seem to mean much to me (other than like -6 db as an example where I like to start many things personally)
Thanks!!Fader position determines the level added or subtracted from Unity as it's sent to the Main or Bus.
The numeric readout is for the recorded level with Insert processing added.
Hmm... I've always seen that numeric readout change when moving the fader. It always corresponds to where the fader is (or moved to during automation).Fader position determines the level added or subtracted from Unity as it's sent to the Main or Bus.
The numeric readout is for the recorded level with Insert processing added.
LOL!! I had PT on the brain and no coffee yet!!! You are of course correct!! This is what I was referring to.Hmm... I've always seen that numeric readout change when moving the fader. It always corresponds to where the fader is (or moved to during automation).
I've never seen what the OP has in his photo (the numeric readout showing "0" when clearly the fader is well above that.
To the OP - might try a trash prefs/uninstall re-install?