Chris, Your final mixes should follow the same principle. Ultimately, you need to create a final master where you bump up your levels, add final EQ and compression, in other words, mastering. That's beyond the scope of an email list. I'm simply telling you what the norm is for recording into a dAW. Keep your levels conservative and you'll be fine without worrying about clipping.
Slau On May 7, 2014, at 10:55 AM, Christopher-Mark Gilland <clgillan...@gmail.com> wrote: > OK, then, yeah, turn all that way way up on the monitor once I have Voiceover > on another device isolated, but that still doesn't tell me once all recorded > how to then get that volume back to its original level so it's equal with all > my other sound. Is that where a stereo master fader track comes into play? > I'd create one of them in the session, then bump that volume slider back up > to compensate, or is there actually a better way? > > Chris. > > ----- Original Message ----- > From: Slau Halatyn > To: ptaccess@googlegroups.com > Sent: Wednesday, May 07, 2014 10:38 AM > Subject: Re: Monitoring levels > > You have to figure out a way to keep VoiceOver and Pro Tools output separate. > Your just setting yourself up for a difficult time by trying to run things > the way you have them set up. > > Also, crank your vocal track up to the max on the fader. As you know, this > has no effect on recording levels, so boost it. Even a plug-in will have no > effect on the recorded track except while it's instantiated. The thing to > shoot for, really, is to keep the screen reader, system sounds, etc. (like > Chris Smart mentioned) separate from Pro Tools. > > Slau > > On May 7, 2014, at 9:11 AM, Christopher-Mark Gilland <clgillan...@gmail.com> > wrote: > >> Slau, >> >> I have a question then, >> >> I find that on my monitors, if I leave my volume slider in ProTools on a >> vocal track at 0%, then on my interface, I turn my gain dial way down to the >> point where in PT, on that track, it shows -18DB, that is so profusely >> quiet, that I literally almost cannot even hear it unless I turn my monitors >> almost 3 fourths the way up. Which of corse is way! way! quieter than >> Voiceover speech, or say my music instrument tracks etc. In order to get a >> good level that is audible, I'm having to way raise that gain. Even if I >> don't raise the gain on my interface, but pull the slider on the track in PT >> all the way to +12DB, which is practically all the way up, it only then >> starts! to become audible. I know you're probably saying, then, ok, Chris, >> you're music is way way way too hot. Crank it way the hell down! If I do >> that, then again, the over all level is very crisp and clean and doesn't >> clip, but at the same time, compared to my over all volume, PT not with >> standing, the recording volume is so pathetically low in comparison to >> everything else, that if I crank it up enough to hear it, any other sound >> that gets fed through like Alex from Voiceover etc. literally is deafening! >> I understand we're talking two different levels here. the one on my >> interface is the input volume, whilst the one on the track in PT is the >> output volume, I totally get that. I'm just not sure how to keep that input >> gain on my interface real real low, yet achieve the same level on the output >> volume without having to bring that input gain so hot. I do have an insert >> I sometimes pop on a vocal track, it's just one of the default pre-installed >> dynamic compression plugins, and yeah, if I set the preset to vocal leveler, >> it helps some, but I don't always want compression. All I need is an output >> volume only boost. I thought about using a Pre, if I could find a good >> hardware one that was accessible, but even that is gonna be for the input >> gain, not the output. >> >> So, if you have any suggestions, or think you may know what is going on, let >> me know. >> >> Chris. >> >> ----- Original Message ----- >> From: Slau Halatyn >> To: ptaccess@googlegroups.com >> Sent: Wednesday, May 07, 2014 8:35 AM >> Subject: Re: Monitoring levels >> >> Chris, >> >> If you're in danger of clipping, you're recording way too hot. With >> something like a vocal, your final peak should be -9 to -6 dB full scale. >> That means your average level should be in the range of -18 to -12 dB. >> That's what headroom is for. You're recording with 24 bits which give you a >> theoretical dynamic range of of 140 decibels. The sources you're recording >> are nowhere near 140 decibels, not even close. By pulling back your level, >> you'll eliminate any concern over clipping. Pro Tools is designed to have >> average levels at -18 dB. 18 decibels of headroom is plenty for just about >> anything you'll ever record. >> >> Slau >> >> On May 7, 2014, at 6:54 AM, Christopher-Mark Gilland <clgillan...@gmail.com> >> wrote: >> >>> I'm 100% perfectly aware that I can monitor the level of an individual >>> track by interacting with it, then finding the meter, and then, I can keep >>> hitting vo+F3 to read what's under the Voiceover cursor. what however I'm >>> looking for, is something slightly more robust. Is there a way, and if so, >>> how, that I could asign a hotspot or something similar then have it where >>> it won't read the meter automatically, no, however, if, and only! if, I >>> clip, it'll automatically trigger voiceover to say clipped, or to read the >>> meter in such of a way I'll know I'm clipping? Sometimes, with my hearing >>> loss, it's slightly tricky for me to know audibly, until it gets where it's >>> so badly clipping, that it's flat out disgusting. The issue is, yeah, I >>> could manually look, but what if I only clip on say, one note? If I sing >>> right over that note for instance then check the meter one or two notes >>> early/late, I might miss something very very important. I'm just >>> wonderring the best way to hit that meter dead spot on, so I know >>> instantly! that I'm clipping. >>> >>> Chris. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ptaccess+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ptaccess+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
