Re: Well, I was wrong.
And while not a technical book on recording, mixing and etc, The Daily Adventure of mixer man is worth the read from an entertainment stand point that also happens to have little audio nuggets in there. And if you get the Audio book a certain member of this mailing list makes a cameo. On Jul 11, 2014, at 3:30 PM, Chris Smart wrote: > I don't know about audio format for those. I got one as a pdf and bought and > scanned the other two. > > For Mixing Audio, Techniques Concepts and Tools, you definitely want the DVD > that goes with the book - everything in the bookas a wav file. > > Really what it comes down to is learning to identify narrower and narrower > bands of frequencies so you can set and adjust equalizers quickly, learning > what all the parameters of compressors, reverbs, delays etc. do, being able > to detect digital clipping, etc. A lot of just adjusting things, seeing what > they do, and trying to remember what it sounds like when you do this or that. > > Admittedly I had a bit of an advantage starting out. I'm one of those guys > with perfect pitch. So, while I can name notes by sound, imagine them, etc. I > couldn't name what frequency values various pitches are. But, I quickly > started learning that. 440 Hz is 4th octave A on a piano. double that to 880 > and you get a note an octave higher. Halve it to 220 and you get an octave > lower. Halve it a couple times and you're almost at 50 Hz, the hum of > electrical noise in Europe. You can map out the audible spectrum that way if > you want, if you're coming at this as a musician. The top note on a piano is > around 4K. The bottom note on a guitar in standard tuning is around 80 Hz. on > and on. find some frequencies you do know, and start doubling and halving > them, then cut those differences in half again, etc. > > You want to aim for being able to identify bands about a third of an octave > wide. > > At 02:42 PM 7/11/2014, you wrote: >> Chris, this is absolutely awesome! Thank you! I'm gonna save this e-mail >> in my archives, and will definitely check out these books. There is also >> some good resources that Chuck Reichel gave me a while back, and I have >> almost all of those tutorials at this point. I need to look again at what >> they're called, but they're excellent. Mayve chuck can chime in. >> >> Do you know if those books that you mentioned about are available in audio >> format anywhere? >> >> Chris. >> >> - Original Message - From: "Chris Smart" >> To: >> Sent: Friday, July 11, 2014 12:27 PM >> Subject: Re: Well, I was wrong. >> >> >>> Well, I was interested in mixing and mastering. For mixing, check out: >>> 1. Mike Senior - Mixing Secrets for the Small Studio >>> That one really illustrates what it takes to get a mix up to commercial >>> standards. >>> (and check out Mike's excelent website, including an enormous free >>> multitrack library of material to practice on!) >>> www.cambridge-mt.com >>> >>> and >>> 2. Roey Izhaki - Mixing Audio - Concepts Practices and Tools >>> http://www.mixingaudio.com/ >>> That one is extremely thorough, and every example in the book comes in >>> audio form on a data DVD. If something confuses you in the first book or >>> you want to learn a lot about a specific thing, such as compressors, >>> reverb, etc., check it out in the second book. >>> >>> Generally, Focal Press puts out a lot of great material. >>> >>> For mastering, the bible is: >>> Bob Katz - Mastering Audio; the Art and the Science. >>> His site is at: >>> http://www.digido.com >>> >>> Hopefully someone can recommend a good text on recording. >>> >>> At 12:11 PM 7/11/2014, you wrote: In your defense, Chris, you do have a very valid point about reading. That I'll give ya. Are there any good titles you'd recommend starting with? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 10:56 AM Subject: Re: Well, I was wrong. > if you can't afford school, you can still get and read lots of books on > recording, or producing, or mixing or mastering etc. > > The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) > > At 04:37 AM 7/11/2014, you wrote: >> You wrote: >> >> First of all, Chris, you probably shouldn't expect that people have the >> time to listen to an mp3 where you start going into your preference >> settings. That's just not reasonable for most people. >> >> And, I didn't! expect people to be required to listen. Why do you think >> I said, if you want! to listen to it, it may help explain things. >> Nowhere what so ever did I make mention that people absolutely just, >> had! to listen to it. If you don't wanna play it, or don't have the >> time, then, don't. Plain and simple. It's only an option I provided. >> >> Secondly, if you're close to clipping with y
Re: I can confirm Chris's meter problem.
They are, but entertaining all the same! Have fun. Sent from my iPhone > On 11 Jul 2014, at 21:52, Daniel Contreras wrote: > > I think we should take the list for what it's worth, a helpful source for > everybody, we are all on the same boat people. I hate to but in, but opening > these emails are a waste of my time in my opinion, if they're not pertaining > to the subject at hand. > > Daniel Contreras > >> On Jul 11, 2014, at 3:31 PM, Chris Smart wrote: >> >> sixth post. let me guess, not your fault? >> >> At 03:28 PM 7/11/2014, you wrote: >>> I'm sorry, as I said, I was just trying to help. Give me a break! >>> >>> Chris. >>> >>> - Original Message - From: "Chris Smart" >>> To: >>> Sent: Friday, July 11, 2014 3:22 PM >>> Subject: Re: I can confirm Chris's meter problem. >>> >>> Dude, I was kidding. Moving the decimal one place to the left or right is very basic! At 02:37 PM 7/11/2014, you wrote: > I admit, Chris, it was a little confusing at first when I heard his > explination. Basically, I am not sure if you were being sarcastic about > math being difficult, or if you were serious. I'm gonna assume the > ladder. > > So, look at t it this way... Let's say you have a double digit decimal DB > value. Let's use 12 just for example. So, forget for a minute it being > negative, or positive. Don't worry about that. Just for now look from > the bigger picture. Take the number 12, in general. 12 could also be > written as 12.0. > > So, 12.0 is no different than 12. Only thing is, with 12.0, we now have > a decimal place. So just move that decimal one place to the left. So > instead of 12, you now have 1.2. So think of it this way, and this is > what really helped me grasp it. The decimal needs to be in between the > two digits. So, say you needed -16DB. That's kind of low, but just > humor me here. So, what makes up 16? 1, and 6, right? 16's written as > 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 > meters would equal -1.6DB. Hopefully, that makes sense. > > Chris. > > - Original Message - From: "Chris Smart" > To: > Sent: Friday, July 11, 2014 12:15 PM > Subject: Re: I can confirm Chris's meter problem. > > >> But but, math is difficult. LOL >> >> At 11:56 AM 7/11/2014, you wrote: >>> Guys, >>> >>> As I mentioned a few days ago, it's an issue with the way the meter is >>> displaying only 14.4 dB of range. Between version 10 and 11, the meter >>> display changed and, as I mentioned before, it's something that needs >>> to be fixed. Think of everything as being one decimal spot off. In >>> other words, if you get a reading of -2 dB, what the meter is really >>> saying is -20 dB. If you're shooting for -15 dB, make sure your meter >>> reads -1.5 dB. Move the decimal one spot to the right in your mind. If >>> anybody wants to verify, create a track with a signal generator putting >>> out a tone at -20 dB and check the meter on the track and you'll see >>> that it displays -2.0. Adjust the output of the signal generator and >>> it'll follow the behavior I've outlined above. >>> >>> Slau >>> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: Hi. This *definitely!* must be a Voiceover issue. I don't recall the >>> exact model, as it was donated to me by a studio in my area which is >>> going out of business unfortunately, however I have some form of a >>> Scarlet. I think it's made by Focusright. Anyway, I can confirm with >>> this interface that like Christopher, I too am seeing the same problem >>> with my meters in PT11. I'm not getting identically the same readout as >>> he obviously, but it's definitely showing a much hotter signal than >>> what I know beyond a doubt is coming in. In PT10, like Christohper, I >>> do not have this situation either. My meters read fine over there. So, >>> Slau, with the utmost respect, I think you saying there are things >>> Christopher doesn't yet understand is a little bit harsh. I earnestly >>> don't think Chris is doing anything wrong. If he is, then why am I also >>> having the same problem with a completely different interface, not even >>> made by the same manufacturer? That just seems a bit odd to me that >>> this would be opporator error. I can't speak for Christopher, but I can >>> tell you from my part at least that I'm not doubting your experience >>> nor credibility, and if I implied in any way that I did, I apologize. I >>> just find it coencidental that he's having this issue, and that I am as >>> well. Thanks kindly, and make it a blessed day. Rosco. -- >>>
Re: I can confirm Chris's meter problem.
I think we should take the list for what it's worth, a helpful source for everybody, we are all on the same boat people. I hate to but in, but opening these emails are a waste of my time in my opinion, if they're not pertaining to the subject at hand. Daniel Contreras > On Jul 11, 2014, at 3:31 PM, Chris Smart wrote: > > sixth post. let me guess, not your fault? > > At 03:28 PM 7/11/2014, you wrote: >> I'm sorry, as I said, I was just trying to help. Give me a break! >> >> Chris. >> >> - Original Message - From: "Chris Smart" >> To: >> Sent: Friday, July 11, 2014 3:22 PM >> Subject: Re: I can confirm Chris's meter problem. >> >> >>> Dude, I was kidding. Moving the decimal one place to the left or right is >>> very basic! >>> >>> At 02:37 PM 7/11/2014, you wrote: I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. > But but, math is difficult. LOL > > At 11:56 AM 7/11/2014, you wrote: >> Guys, >> >> As I mentioned a few days ago, it's an issue with the way the meter is >> displaying only 14.4 dB of range. Between version 10 and 11, the meter >> display changed and, as I mentioned before, it's something that needs to >> be fixed. Think of everything as being one decimal spot off. In other >> words, if you get a reading of -2 dB, what the meter is really saying is >> -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 >> dB. Move the decimal one spot to the right in your mind. If anybody >> wants to verify, create a track with a signal generator putting out a >> tone at -20 dB and check the meter on the track and you'll see that it >> displays -2.0. Adjust the output of the signal generator and it'll >> follow the behavior I've outlined above. >> >> Slau >> >> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: >> >> > Hi. >> > >> > This *definitely!* must be a Voiceover issue. I don't recall the >> exact model, as it was donated to me by a studio in my area which is >> going out of business unfortunately, however I have some form of a >> Scarlet. I think it's made by Focusright. Anyway, I can confirm with >> this interface that like Christopher, I too am seeing the same problem >> with my meters in PT11. I'm not getting identically the same readout as >> he obviously, but it's definitely showing a much hotter signal than what >> I know beyond a doubt is coming in. In PT10, like Christohper, I do not >> have this situation either. My meters read fine over there. So, Slau, >> with the utmost respect, I think you saying there are things Christopher >> doesn't yet understand is a little bit harsh. I earnestly don't think >> Chris is doing anything wrong. If he is, then why am I also having the >> same problem with a completely different interface, not even made by the >> same manufacturer? That just seems a bit odd to me that this would be >> opporator error. I can't speak for Christopher, but I can tell you from >> my part at least that I'm not doubting your experience nor credibility, >> and if I implied in any way that I did, I apologize. I just find it >> coencidental that he's having this issue, and that I am as well. >> > >> > Thanks kindly, and make it a blessed day. >> > >> > Rosco. >> > -- >> > 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.
Re: I can confirm Chris's meter problem.
sixth post. let me guess, not your fault? At 03:28 PM 7/11/2014, you wrote: I'm sorry, as I said, I was just trying to help. Give me a break! Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 3:22 PM Subject: Re: I can confirm Chris's meter problem. Dude, I was kidding. Moving the decimal one place to the left or right is very basic! At 02:37 PM 7/11/2014, you wrote: I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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
Re: I can confirm Chris's meter problem.
where would you like your break? At 03:28 PM 7/11/2014, you wrote: I'm sorry, as I said, I was just trying to help. Give me a break! Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 3:22 PM Subject: Re: I can confirm Chris's meter problem. Dude, I was kidding. Moving the decimal one place to the left or right is very basic! At 02:37 PM 7/11/2014, you wrote: I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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
Re: Well, I was wrong.
I don't know about audio format for those. I got one as a pdf and bought and scanned the other two. For Mixing Audio, Techniques Concepts and Tools, you definitely want the DVD that goes with the book - everything in the bookas a wav file. Really what it comes down to is learning to identify narrower and narrower bands of frequencies so you can set and adjust equalizers quickly, learning what all the parameters of compressors, reverbs, delays etc. do, being able to detect digital clipping, etc. A lot of just adjusting things, seeing what they do, and trying to remember what it sounds like when you do this or that. Admittedly I had a bit of an advantage starting out. I'm one of those guys with perfect pitch. So, while I can name notes by sound, imagine them, etc. I couldn't name what frequency values various pitches are. But, I quickly started learning that. 440 Hz is 4th octave A on a piano. double that to 880 and you get a note an octave higher. Halve it to 220 and you get an octave lower. Halve it a couple times and you're almost at 50 Hz, the hum of electrical noise in Europe. You can map out the audible spectrum that way if you want, if you're coming at this as a musician. The top note on a piano is around 4K. The bottom note on a guitar in standard tuning is around 80 Hz. on and on. find some frequencies you do know, and start doubling and halving them, then cut those differences in half again, etc. You want to aim for being able to identify bands about a third of an octave wide. At 02:42 PM 7/11/2014, you wrote: Chris, this is absolutely awesome! Thank you! I'm gonna save this e-mail in my archives, and will definitely check out these books. There is also some good resources that Chuck Reichel gave me a while back, and I have almost all of those tutorials at this point. I need to look again at what they're called, but they're excellent. Mayve chuck can chime in. Do you know if those books that you mentioned about are available in audio format anywhere? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:27 PM Subject: Re: Well, I was wrong. Well, I was interested in mixing and mastering. For mixing, check out: 1. Mike Senior - Mixing Secrets for the Small Studio That one really illustrates what it takes to get a mix up to commercial standards. (and check out Mike's excelent website, including an enormous free multitrack library of material to practice on!) www.cambridge-mt.com and 2. Roey Izhaki - Mixing Audio - Concepts Practices and Tools http://www.mixingaudio.com/ That one is extremely thorough, and every example in the book comes in audio form on a data DVD. If something confuses you in the first book or you want to learn a lot about a specific thing, such as compressors, reverb, etc., check it out in the second book. Generally, Focal Press puts out a lot of great material. For mastering, the bible is: Bob Katz - Mastering Audio; the Art and the Science. His site is at: http://www.digido.com Hopefully someone can recommend a good text on recording. At 12:11 PM 7/11/2014, you wrote: In your defense, Chris, you do have a very valid point about reading. That I'll give ya. Are there any good titles you'd recommend starting with? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 10:56 AM Subject: Re: Well, I was wrong. if you can't afford school, you can still get and read lots of books on recording, or producing, or mixing or mastering etc. The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because yo
Re: I can confirm Chris's meter problem.
I'm sorry, as I said, I was just trying to help. Give me a break! Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 3:22 PM Subject: Re: I can confirm Chris's meter problem. Dude, I was kidding. Moving the decimal one place to the left or right is very basic! At 02:37 PM 7/11/2014, you wrote: I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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:/
Re: I can confirm Chris's meter problem.
Dude, I was kidding. Moving the decimal one place to the left or right is very basic! At 02:37 PM 7/11/2014, you wrote: I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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 e
Re: I can confirm Chris's meter problem.
Genuinely worrying about brother Chris of Norman. Thinking of staging an intervention. Is there something like Apple Script Anonymous he could attend? lol On 7/11/14, Chris Norman wrote: > Write an apple script to convert the value? :P > > > On 11 Jul 2014, at 17:15, Chris Smart wrote: > >> But but, math is difficult. LOL >> >> At 11:56 AM 7/11/2014, you wrote: >>> Guys, >>> >>> As I mentioned a few days ago, it's an issue with the way the meter is >>> displaying only 14.4 dB of range. Between version 10 and 11, the meter >>> display changed and, as I mentioned before, it's something that needs to >>> be fixed. Think of everything as being one decimal spot off. In other >>> words, if you get a reading of -2 dB, what the meter is really saying is >>> -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 >>> dB. Move the decimal one spot to the right in your mind. If anybody wants >>> to verify, create a track with a signal generator putting out a tone at >>> -20 dB and check the meter on the track and you'll see that it displays >>> -2.0. Adjust the output of the signal generator and it'll follow the >>> behavior I've outlined above. >>> >>> Slau >>> >>> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: >>> >>> > Hi. >>> > >>> > This *definitely!* must be a Voiceover issue. I don't recall the exact >>> > model, as it was donated to me by a studio in my area which is going >>> > out of business unfortunately, however I have some form of a Scarlet. I >>> > think it's made by Focusright. Anyway, I can confirm with this >>> > interface that like Christopher, I too am seeing the same problem with >>> > my meters in PT11. I'm not getting identically the same readout as he >>> > obviously, but it's definitely showing a much hotter signal than what I >>> > know beyond a doubt is coming in. In PT10, like Christohper, I do not >>> > have this situation either. My meters read fine over there. So, Slau, >>> > with the utmost respect, I think you saying there are things >>> > Christopher doesn't yet understand is a little bit harsh. I earnestly >>> > don't think Chris is doing anything wrong. If he is, then why am I also >>> > having the same problem with a completely different interface, not even >>> > made by the same manufacturer? That just seems a bit odd to me that >>> > this would be opporator error. I can't speak for Christopher, but I can >>> > tell you from my part at least that I'm not doubting your experience >>> > nor credibility, and if I implied in any way that I did, I apologize. I >>> > just find it coencidental that he's having this issue, and that I am as >>> > well. >>> > >>> > Thanks kindly, and make it a blessed day. >>> > >>> > Rosco. >>> > -- >>> > 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.
Re: I can confirm Chris's meter problem.
I figured that you were, but just in case, I thought I'd better explained. Hopefully, someone else who does! seriously find it hard may get some value out of this. Though I don't find it hard, I do! find it confusing, at best, and I hate that in my head I have to take time to convert. OK, I'll admit, I'm just lazy. guilty as charged. What I wonder is, and Slau, you or someone may have to confirm this, but did they visually change something with the meters? In other words, did they change the meters so that they read a little differently, or did the meters themselves not change as much as Voiceover changed the way it reads. In other words, for -12DBFS, is it really actually showing -1.2 visually, and a sighted person like us, just has to know to convert that, or is it something where visually it really indeed does! show -12, it's just that Voiceover doesn't know this. I'm just ultimately trying to pinpoint down if this is actually a bug, or if Voiceover's actually reporting it exactly as is; we just have to know that this is the case. I'm just glad that I'm nhot the only one on this list who saw this. I thought I was going crazy! Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:41 PM Subject: Re: I can confirm Chris's meter problem. I was kidding by the way. But yes, that's a simple solution. At 12:26 PM 7/11/2014, you wrote: Write an apple script to convert the value? :P On 11 Jul 2014, at 17:15, Chris Smart wrote: > But but, math is difficult. LOL > > At 11:56 AM 7/11/2014, you wrote: >> Guys, >> >> As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. >> >> Slau >> >> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: >> >> > Hi. >> > >> > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. >> > >> > Thanks kindly, and make it a blessed day. >> > >> > Rosco. >> > -- >> > 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://grou
Re: Well, I was wrong.
Chris, this is absolutely awesome! Thank you! I'm gonna save this e-mail in my archives, and will definitely check out these books. There is also some good resources that Chuck Reichel gave me a while back, and I have almost all of those tutorials at this point. I need to look again at what they're called, but they're excellent. Mayve chuck can chime in. Do you know if those books that you mentioned about are available in audio format anywhere? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:27 PM Subject: Re: Well, I was wrong. Well, I was interested in mixing and mastering. For mixing, check out: 1. Mike Senior - Mixing Secrets for the Small Studio That one really illustrates what it takes to get a mix up to commercial standards. (and check out Mike's excelent website, including an enormous free multitrack library of material to practice on!) www.cambridge-mt.com and 2. Roey Izhaki - Mixing Audio - Concepts Practices and Tools http://www.mixingaudio.com/ That one is extremely thorough, and every example in the book comes in audio form on a data DVD. If something confuses you in the first book or you want to learn a lot about a specific thing, such as compressors, reverb, etc., check it out in the second book. Generally, Focal Press puts out a lot of great material. For mastering, the bible is: Bob Katz - Mastering Audio; the Art and the Science. His site is at: http://www.digido.com Hopefully someone can recommend a good text on recording. At 12:11 PM 7/11/2014, you wrote: In your defense, Chris, you do have a very valid point about reading. That I'll give ya. Are there any good titles you'd recommend starting with? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 10:56 AM Subject: Re: Well, I was wrong. if you can't afford school, you can still get and read lots of books on recording, or producing, or mixing or mastering etc. The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools t
Re: I can confirm Chris's meter problem.
Ewww! God! Be my guest, pal! Hey, no seriously... if you do, I want it. I'll even pay you like 2 or 3 bucks via PayPal for it if you make it for us, and can tell us how to install and use it. And no, seriously, I'm not being sarcastic. I really will, if you can do it and get it consistently to work. Chris. - Original Message - From: "Chris Norman" To: "Pro Tools Access" Sent: Friday, July 11, 2014 12:26 PM Subject: Re: I can confirm Chris's meter problem. Write an apple script to convert the value? :P On 11 Jul 2014, at 17:15, Chris Smart wrote: But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact > model, as it was donated to me by a studio in my area which is going > out of business unfortunately, however I have some form of a Scarlet. I > think it's made by Focusright. Anyway, I can confirm with this > interface that like Christopher, I too am seeing the same problem with > my meters in PT11. I'm not getting identically the same readout as he > obviously, but it's definitely showing a much hotter signal than what I > know beyond a doubt is coming in. In PT10, like Christohper, I do not > have this situation either. My meters read fine over there. So, Slau, > with the utmost respect, I think you saying there are things > Christopher doesn't yet understand is a little bit harsh. I earnestly > don't think Chris is doing anything wrong. If he is, then why am I also > having the same problem with a completely different interface, not even > made by the same manufacturer? That just seems a bit odd to me that > this would be opporator error. I can't speak for Christopher, but I can > tell you from my part at least that I'm not doubting your experience > nor credibility, and if I implied in any way that I did, I apologize. I > just find it coencidental that he's having this issue, and that I am as > well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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.
Re: I can confirm Chris's meter problem.
I admit, Chris, it was a little confusing at first when I heard his explination. Basically, I am not sure if you were being sarcastic about math being difficult, or if you were serious. I'm gonna assume the ladder. So, look at t it this way... Let's say you have a double digit decimal DB value. Let's use 12 just for example. So, forget for a minute it being negative, or positive. Don't worry about that. Just for now look from the bigger picture. Take the number 12, in general. 12 could also be written as 12.0. So, 12.0 is no different than 12. Only thing is, with 12.0, we now have a decimal place. So just move that decimal one place to the left. So instead of 12, you now have 1.2. So think of it this way, and this is what really helped me grasp it. The decimal needs to be in between the two digits. So, say you needed -16DB. That's kind of low, but just humor me here. So, what makes up 16? 1, and 6, right? 16's written as 1 6. So, put a decimal between those two digits. So, -16DB on the PT 11 meters would equal -1.6DB. Hopefully, that makes sense. Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 12:15 PM Subject: Re: I can confirm Chris's meter problem. But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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.
Re: I can confirm Chris's meter problem.
I was kidding by the way. But yes, that's a simple solution. At 12:26 PM 7/11/2014, you wrote: Write an apple script to convert the value? :P On 11 Jul 2014, at 17:15, Chris Smart wrote: > But but, math is difficult. LOL > > At 11:56 AM 7/11/2014, you wrote: >> Guys, >> >> As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. >> >> Slau >> >> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: >> >> > Hi. >> > >> > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. >> > >> > Thanks kindly, and make it a blessed day. >> > >> > Rosco. >> > -- >> > 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.
Re: Well, I was wrong.
Cheers Chris, that's a really useful email. On 11 Jul 2014, at 17:27, Chris Smart wrote: > Well, I was interested in mixing and mastering. For mixing, check out: > 1. Mike Senior - Mixing Secrets for the Small Studio > That one really illustrates what it takes to get a mix up to commercial > standards. > (and check out Mike's excelent website, including an enormous free multitrack > library of material to practice on!) > www.cambridge-mt.com > > and > 2. Roey Izhaki - Mixing Audio - Concepts Practices and Tools > http://www.mixingaudio.com/ > That one is extremely thorough, and every example in the book comes in audio > form on a data DVD. If something confuses you in the first book or you want > to learn a lot about a specific thing, such as compressors, reverb, etc., > check it out in the second book. > > Generally, Focal Press puts out a lot of great material. > > For mastering, the bible is: > Bob Katz - Mastering Audio; the Art and the Science. > His site is at: > http://www.digido.com > > Hopefully someone can recommend a good text on recording. > > At 12:11 PM 7/11/2014, you wrote: >> In your defense, Chris, you do have a very valid point about reading. That >> I'll give ya. Are there any good titles you'd recommend starting with? >> >> Chris. >> >> - Original Message - From: "Chris Smart" >> To: >> Sent: Friday, July 11, 2014 10:56 AM >> Subject: Re: Well, I was wrong. >> >> >>> if you can't afford school, you can still get and read lots of books on >>> recording, or producing, or mixing or mastering etc. >>> >>> The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) >>> >>> At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools that teach audio engineering and production. OK, but if you can't afford to go to
Re: Well, I was wrong.
Well, I was interested in mixing and mastering. For mixing, check out: 1. Mike Senior - Mixing Secrets for the Small Studio That one really illustrates what it takes to get a mix up to commercial standards. (and check out Mike's excelent website, including an enormous free multitrack library of material to practice on!) www.cambridge-mt.com and 2. Roey Izhaki - Mixing Audio - Concepts Practices and Tools http://www.mixingaudio.com/ That one is extremely thorough, and every example in the book comes in audio form on a data DVD. If something confuses you in the first book or you want to learn a lot about a specific thing, such as compressors, reverb, etc., check it out in the second book. Generally, Focal Press puts out a lot of great material. For mastering, the bible is: Bob Katz - Mastering Audio; the Art and the Science. His site is at: http://www.digido.com Hopefully someone can recommend a good text on recording. At 12:11 PM 7/11/2014, you wrote: In your defense, Chris, you do have a very valid point about reading. That I'll give ya. Are there any good titles you'd recommend starting with? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 10:56 AM Subject: Re: Well, I was wrong. if you can't afford school, you can still get and read lots of books on recording, or producing, or mixing or mastering etc. The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools that teach audio engineering and production. OK, but if you can't afford to go to one of those schools... You wrote: Of course, it's possible to learn this on your own but it can take quite a long time. Understandable. You wrote: Bottom line is, if you have a microphone going into an interface and nothing else in between, there's no possible way your levels can be at -4 dB FS. For one thing, I know what -4DB means, but when you say DB FS, what do you mean by FS? Maybe we're talking two different levels here. Then again, nmaybe not? Secondly, let me go back to my initia
Re: I can confirm Chris's meter problem.
Write an apple script to convert the value? :P On 11 Jul 2014, at 17:15, Chris Smart wrote: > But but, math is difficult. LOL > > At 11:56 AM 7/11/2014, you wrote: >> Guys, >> >> As I mentioned a few days ago, it's an issue with the way the meter is >> displaying only 14.4 dB of range. Between version 10 and 11, the meter >> display changed and, as I mentioned before, it's something that needs to be >> fixed. Think of everything as being one decimal spot off. In other words, if >> you get a reading of -2 dB, what the meter is really saying is -20 dB. If >> you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the >> decimal one spot to the right in your mind. If anybody wants to verify, >> create a track with a signal generator putting out a tone at -20 dB and >> check the meter on the track and you'll see that it displays -2.0. Adjust >> the output of the signal generator and it'll follow the behavior I've >> outlined above. >> >> Slau >> >> On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: >> >> > Hi. >> > >> > This *definitely!* must be a Voiceover issue. I don't recall the exact >> > model, as it was donated to me by a studio in my area which is going out >> > of business unfortunately, however I have some form of a Scarlet. I think >> > it's made by Focusright. Anyway, I can confirm with this interface that >> > like Christopher, I too am seeing the same problem with my meters in PT11. >> > I'm not getting identically the same readout as he obviously, but it's >> > definitely showing a much hotter signal than what I know beyond a doubt is >> > coming in. In PT10, like Christohper, I do not have this situation either. >> > My meters read fine over there. So, Slau, with the utmost respect, I think >> > you saying there are things Christopher doesn't yet understand is a little >> > bit harsh. I earnestly don't think Chris is doing anything wrong. If he >> > is, then why am I also having the same problem with a completely different >> > interface, not even made by the same manufacturer? That just seems a bit >> > odd to me that this would be opporator error. I can't speak for >> > Christopher, but I can tell you from my part at least that I'm not >> > doubting your experience nor credibility, and if I implied in any way that >> > I did, I apologize. I just find it coencidental that he's having this >> > issue, and that I am as well. >> > >> > Thanks kindly, and make it a blessed day. >> > >> > Rosco. >> > -- >> > 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.
Re: I can confirm Chris's meter problem.
Slau, Thank you! This really puts a different perspective on things. The way that you explained makes way! more sense. Thanks again, and please again know from the beginning, there were absolutely no hard feelings. I just didn't realize that it was a decimal problem. Chris. - Original Message - From: "Slau Halatyn" To: Sent: Friday, July 11, 2014 11:56 AM Subject: Re: I can confirm Chris's meter problem. Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: Hi. This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. Thanks kindly, and make it a blessed day. Rosco. -- 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.
Re: I can confirm Chris's meter problem.
But but, math is difficult. LOL At 11:56 AM 7/11/2014, you wrote: Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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.
Re: Well, I was wrong.
In your defense, Chris, you do have a very valid point about reading. That I'll give ya. Are there any good titles you'd recommend starting with? Chris. - Original Message - From: "Chris Smart" To: Sent: Friday, July 11, 2014 10:56 AM Subject: Re: Well, I was wrong. if you can't afford school, you can still get and read lots of books on recording, or producing, or mixing or mastering etc. The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools that teach audio engineering and production. OK, but if you can't afford to go to one of those schools... You wrote: Of course, it's possible to learn this on your own but it can take quite a long time. Understandable. You wrote: Bottom line is, if you have a microphone going into an interface and nothing else in between, there's no possible way your levels can be at -4 dB FS. For one thing, I know what -4DB means, but when you say DB FS, what do you mean by FS? Maybe we're talking two different levels here. Then again, nmaybe not? Secondly, let me go back to my initial point. If indeed this is not ProTools related, and please know, this isn't in any way meant to challenge you nor to be rude/difficult, I'm just trying to understand your point from the bigger picture. So, keep that in mind when reading what I'm about to ask. If PT has nothing to do with it, which by the way, I'm in agreement with you on at this point in time until proven otherwise, then explain this to me... Why then is PT 10 with Voiceover showing me something totally different than PT 11, when my settings are absolutely 100% identical on both versions, I'm running both on the same mac computer, so it's not like I'm on a different workstation, same hardware, same interface, same drivers, same software, same hardware wiring, same hookup, and all my levels on PT, as well as on the interface itself haven't been touched with a 12 foot poll, sota speak, yet I'm getting totally completely different readouts between the two versions? That almost indicates
Re: I can confirm Chris's meter problem.
Guys, As I mentioned a few days ago, it's an issue with the way the meter is displaying only 14.4 dB of range. Between version 10 and 11, the meter display changed and, as I mentioned before, it's something that needs to be fixed. Think of everything as being one decimal spot off. In other words, if you get a reading of -2 dB, what the meter is really saying is -20 dB. If you're shooting for -15 dB, make sure your meter reads -1.5 dB. Move the decimal one spot to the right in your mind. If anybody wants to verify, create a track with a signal generator putting out a tone at -20 dB and check the meter on the track and you'll see that it displays -2.0. Adjust the output of the signal generator and it'll follow the behavior I've outlined above. Slau On Jul 11, 2014, at 10:38 AM, Rosco Vittore wrote: > Hi. > > This *definitely!* must be a Voiceover issue. I don't recall the exact model, > as it was donated to me by a studio in my area which is going out of business > unfortunately, however I have some form of a Scarlet. I think it's made by > Focusright. Anyway, I can confirm with this interface that like Christopher, > I too am seeing the same problem with my meters in PT11. I'm not getting > identically the same readout as he obviously, but it's definitely showing a > much hotter signal than what I know beyond a doubt is coming in. In PT10, > like Christohper, I do not have this situation either. My meters read fine > over there. So, Slau, with the utmost respect, I think you saying there are > things Christopher doesn't yet understand is a little bit harsh. I earnestly > don't think Chris is doing anything wrong. If he is, then why am I also > having the same problem with a completely different interface, not even made > by the same manufacturer? That just seems a bit odd to me that this would be > opporator error. I can't speak for Christopher, but I can tell you from my > part at least that I'm not doubting your experience nor credibility, and if I > implied in any way that I did, I apologize. I just find it coencidental that > he's having this issue, and that I am as well. > > Thanks kindly, and make it a blessed day. > > Rosco. > -- > 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.
Re: Well, I was wrong.
if you can't afford school, you can still get and read lots of books on recording, or producing, or mixing or mastering etc. The FS in dBFS means full scale. (not the same as dbV dBU dBSPL etc.) At 04:37 AM 7/11/2014, you wrote: You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools that teach audio engineering and production. OK, but if you can't afford to go to one of those schools... You wrote: Of course, it's possible to learn this on your own but it can take quite a long time. Understandable. You wrote: Bottom line is, if you have a microphone going into an interface and nothing else in between, there's no possible way your levels can be at -4 dB FS. For one thing, I know what -4DB means, but when you say DB FS, what do you mean by FS? Maybe we're talking two different levels here. Then again, nmaybe not? Secondly, let me go back to my initial point. If indeed this is not ProTools related, and please know, this isn't in any way meant to challenge you nor to be rude/difficult, I'm just trying to understand your point from the bigger picture. So, keep that in mind when reading what I'm about to ask. If PT has nothing to do with it, which by the way, I'm in agreement with you on at this point in time until proven otherwise, then explain this to me... Why then is PT 10 with Voiceover showing me something totally different than PT 11, when my settings are absolutely 100% identical on both versions, I'm running both on the same mac computer, so it's not like I'm on a different workstation, same hardware, same interface, same drivers, same software, same hardware wiring, same hookup, and all my levels on PT, as well as on the interface itself haven't been touched with a 12 foot poll, sota speak, yet I'm getting totally completely different readouts between the two versions? That almost indicates to me that there is an issue in PT 11.2 reading the meaters, vs. in 10.0. This is why I asked a few messages back in the thread if PT11 handled the meters a little differently, or if it was an issue of Voiceover itself doing something odd. You wrote: I guarantee that there's
I can confirm Chris's meter problem.
Hi. This *definitely!* must be a Voiceover issue. I don't recall the exact model, as it was donated to me by a studio in my area which is going out of business unfortunately, however I have some form of a Scarlet. I think it's made by Focusright. Anyway, I can confirm with this interface that like Christopher, I too am seeing the same problem with my meters in PT11. I'm not getting identically the same readout as he obviously, but it's definitely showing a much hotter signal than what I know beyond a doubt is coming in. In PT10, like Christohper, I do not have this situation either. My meters read fine over there. So, Slau, with the utmost respect, I think you saying there are things Christopher doesn't yet understand is a little bit harsh. I earnestly don't think Chris is doing anything wrong. If he is, then why am I also having the same problem with a completely different interface, not even made by the same manufacturer? That just seems a bit odd to me that this would be opporator error. I can't speak for Christopher, but I can tell you from my part at least that I'm not doubting your experience nor credibility, and if I implied in any way that I did, I apologize. I just find it coencidental that he's having this issue, and that I am as well. Thanks kindly, and make it a blessed day. Rosco. -- 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.
Re: recording issue with pt
Steve, Can you possibly write me off list? I need a little help trouble shooting something with my mac in general, which wouldn't probably be on topic completely for this list. I just wanna see if it's something I'm doing wrong or if my friend is correct on something he told me. my e-mail is: clgillan...@gmail.com Chris. - Original Message - From: "Steve Sparrow" To: Sent: Friday, July 11, 2014 9:04 AM Subject: Re: recording issue with pt Hey Chris. thanks for this. i'll go and give the i o set up thing a go again. i thought i did this correctly, how ever i did not hit default on the bus. so i'll give this a run, and see how i go. By the way, i'm using tools 11 steve . On 11 Jul 2014, at 10:54 pm, Christopher-Mark Gilland wrote: OK Steve, let's do a couple of things. First of all, let's make sure that your I/O settings are indeed set correctly. I'm not doubting you that you did nothing, so please know that upfront, but it may be worth us looking at. So bring up PT, but don't have a session opened, preferably, if you can help it. Now, go to your menu bar with vo+M and over to the setup menu. In here, go to I/O. Now, not knowing what version of PT you're using, it's going to be slightly more tricky to trouble shoot this, but I'll give it a go anyway. I'll start by saying the same thing I'd say to anyone on list. We're working with I O settings, and therefore, this can potentially make your audio completely stop working in PT if you do things wrong, so firstly, do exactly as I say, and B, know that you follow these directions at your own risk. They should be safe for the most part as we're not gonna be doing anything in here too distructive, and if you follow me to a T, you should be fine, but just out of the rare chance you're not, I have to CMA. OK, so in here, move to the input tab, and hit vo+command+F5 to select it. I'm not sure how your function keys are set up. You might have to do fn+vo+command+F5. The point is, you wanna route your mouse to your Voiceover cursor. Once done, hit vo+shift+space to click the input tab. Now, we want to select all paths. This isn't going to speak well, I promise you, so you're just gonna have to do it, and hear me out, trusting with faith that it's working. Press command+A to select all. Now, move down to the bottom of the window for convenience sake, then vo+left arrow until you find the delete paths button. It might just say delete, I don't recall the exact wording, but it'll be obvious. command+vo+F5, or whatever on it to route your mouse, then vo+shift+space to click it. You probably could just do vo+space, but I don't wanna chance it. Now, find the default button. Route your mouse, and click it with vo+shift+space. By the way Steve, if you don't see a delete button or a delete paths button, then skip that step and see if you see a default button. If so click it. If you don't see either, then, I don't know what to say, aside maybe reinstall the drivers for your interface. Anyway, next, we want to do exactly the same thing but this time, in the output tab. So go up to the top, click the output tab, just like we did the input tab. Now, hit command+A again to select all paths. Go down and hit delete if you can, then hit default. Finally, do it one more time on the bus tab. Then go down and click OK. Now, go to the setup menu, and then go to the playback engine. Make sure your interface is still correctly selected. If not, set it. Then close and reopen ProTools, even if not prompted to do so, just to be on the safe side. See if that fixes it. If not, someone else is gonna have to chime in. Before anyone else says, Whoa! Chris! Dude! That's w'w'w'w'w'way! overkill, maybe it was, but it's how I know to fix this problem when it occured for me a few times, and 9 outta 10 times, this fixed the issue. So, if I'm telling him something that over complicates things, I'm sorry, but realize I'm just genuinely trying to help. Chris. - Original Message - From: "Steve Sparrow" To: Sent: Friday, July 11, 2014 8:33 AM Subject: Re: recording issue with pt hi again, i did not copy this message from pro tools correctly. the message is this. the track can not be enabled because it does not have open active input and output assigned. this did not happen the other day when i started playing around with it. so i must be missing something. I have gone in to the set up window, and looked in the play back engine, and the motu is selected. but i've not made any recordings yet, and don't have any projects created with tools to prove the motu is working properly with pro tools. Steve On 11 Jul 2014, at 9:10 pm, Steve Sparrow wrote: Hi. having a recording issue with pt. when i hit the record enable button a track, i'm getting a message saying the track can not be enabled because active input and output have not been assigned. now, here is what i h
Re: recording issue with pt
hey again chris. Thanks for your help there mate. my only issue, is that i think i've gone through your instructions. but this damn thing does not want to play the game. i'm still getting the same message. I've set the default on the input, output, and bus in the i o set up. i've gone back in to set up and looked in the playback engine and the motu is there. I can go to a track, and all the inputs and outputs are there for the motu in the interface. It just will not let me arm a track. So i must have done something wrong. I can also play music through the motu using iTunes without an issue. so this is very odd. i am using tools 11. any thoughts guys. I can run this card fine with sonar on my pc machine. So it would seem that it's working. steve On 11 Jul 2014, at 10:54 pm, Christopher-Mark Gilland wrote: > OK Steve, let's do a couple of things. > > First of all, let's make sure that your I/O settings are indeed set > correctly. I'm not doubting you that you did nothing, so please know that > upfront, but it may be worth us looking at. > > So bring up PT, but don't have a session opened, preferably, if you can help > it. > > Now, go to your menu bar with vo+M and over to the setup menu. In here, go > to I/O. > > Now, not knowing what version of PT you're using, it's going to be slightly > more tricky to trouble shoot this, but I'll give it a go anyway. I'll start > by saying the same thing I'd say to anyone on list. We're working with I O > settings, and therefore, this can potentially make your audio completely stop > working in PT if you do things wrong, so firstly, do exactly as I say, and B, > know that you follow these directions at your own risk. They should be safe > for the most part as we're not gonna be doing anything in here too > distructive, and if you follow me to a T, you should be fine, but just out of > the rare chance you're not, I have to CMA. > > OK, so in here, move to the input tab, and hit vo+command+F5 to select it. > I'm not sure how your function keys are set up. You might have to do > fn+vo+command+F5. The point is, you wanna route your mouse to your Voiceover > cursor. Once done, hit vo+shift+space to click the input tab. > > Now, we want to select all paths. This isn't going to speak well, I promise > you, so you're just gonna have to do it, and hear me out, trusting with faith > that it's working. Press command+A to select all. > > Now, move down to the bottom of the window for convenience sake, then vo+left > arrow until you find the delete paths button. It might just say delete, I > don't recall the exact wording, but it'll be obvious. command+vo+F5, or > whatever on it to route your mouse, then vo+shift+space to click it. You > probably could just do vo+space, but I don't wanna chance it. > > Now, find the default button. Route your mouse, and click it with > vo+shift+space. > > By the way Steve, if you don't see a delete button or a delete paths button, > then skip that step and see if you see a default button. If so click it. If > you don't see either, then, I don't know what to say, aside maybe reinstall > the drivers for your interface. > > Anyway, next, we want to do exactly the same thing but this time, in the > output tab. So go up to the top, click the output tab, just like we did the > input tab. Now, hit command+A again to select all paths. Go down and hit > delete if you can, then hit default. > > Finally, do it one more time on the bus tab. > > Then go down and click OK. > > Now, go to the setup menu, and then go to the playback engine. Make sure > your interface is still correctly selected. If not, set it. > > Then close and reopen ProTools, even if not prompted to do so, just to be on > the safe side. > > See if that fixes it. > > If not, someone else is gonna have to chime in. Before anyone else says, > Whoa! Chris! Dude! That's w'w'w'w'w'way! overkill, maybe it was, but > it's how I know to fix this problem when it occured for me a few times, and 9 > outta 10 times, this fixed the issue. So, if I'm telling him something that > over complicates things, I'm sorry, but realize I'm just genuinely trying to > help. > > Chris. > > - Original Message - From: "Steve Sparrow" > To: > Sent: Friday, July 11, 2014 8:33 AM > Subject: Re: recording issue with pt > > > hi again, i did not copy this message from pro tools correctly. the message > is this. > the track can not be enabled because it does not have open active input and > output assigned. > this did not happen the other day when i started playing around with it. so i > must be missing something. > I have gone in to the set up window, and looked in the play back engine, and > the motu is selected. but i've not made any recordings yet, and don't have > any projects created with tools to prove the motu is working properly with > pro tools. > Steve > On 11 Jul 2014, at 9:10 pm, Steve Sparrow wrote: > >>
Re: recording issue with pt
Hey Chris. thanks for this. i'll go and give the i o set up thing a go again. i thought i did this correctly, how ever i did not hit default on the bus. so i'll give this a run, and see how i go. By the way, i'm using tools 11 steve . On 11 Jul 2014, at 10:54 pm, Christopher-Mark Gilland wrote: > OK Steve, let's do a couple of things. > > First of all, let's make sure that your I/O settings are indeed set > correctly. I'm not doubting you that you did nothing, so please know that > upfront, but it may be worth us looking at. > > So bring up PT, but don't have a session opened, preferably, if you can help > it. > > Now, go to your menu bar with vo+M and over to the setup menu. In here, go > to I/O. > > Now, not knowing what version of PT you're using, it's going to be slightly > more tricky to trouble shoot this, but I'll give it a go anyway. I'll start > by saying the same thing I'd say to anyone on list. We're working with I O > settings, and therefore, this can potentially make your audio completely stop > working in PT if you do things wrong, so firstly, do exactly as I say, and B, > know that you follow these directions at your own risk. They should be safe > for the most part as we're not gonna be doing anything in here too > distructive, and if you follow me to a T, you should be fine, but just out of > the rare chance you're not, I have to CMA. > > OK, so in here, move to the input tab, and hit vo+command+F5 to select it. > I'm not sure how your function keys are set up. You might have to do > fn+vo+command+F5. The point is, you wanna route your mouse to your Voiceover > cursor. Once done, hit vo+shift+space to click the input tab. > > Now, we want to select all paths. This isn't going to speak well, I promise > you, so you're just gonna have to do it, and hear me out, trusting with faith > that it's working. Press command+A to select all. > > Now, move down to the bottom of the window for convenience sake, then vo+left > arrow until you find the delete paths button. It might just say delete, I > don't recall the exact wording, but it'll be obvious. command+vo+F5, or > whatever on it to route your mouse, then vo+shift+space to click it. You > probably could just do vo+space, but I don't wanna chance it. > > Now, find the default button. Route your mouse, and click it with > vo+shift+space. > > By the way Steve, if you don't see a delete button or a delete paths button, > then skip that step and see if you see a default button. If so click it. If > you don't see either, then, I don't know what to say, aside maybe reinstall > the drivers for your interface. > > Anyway, next, we want to do exactly the same thing but this time, in the > output tab. So go up to the top, click the output tab, just like we did the > input tab. Now, hit command+A again to select all paths. Go down and hit > delete if you can, then hit default. > > Finally, do it one more time on the bus tab. > > Then go down and click OK. > > Now, go to the setup menu, and then go to the playback engine. Make sure > your interface is still correctly selected. If not, set it. > > Then close and reopen ProTools, even if not prompted to do so, just to be on > the safe side. > > See if that fixes it. > > If not, someone else is gonna have to chime in. Before anyone else says, > Whoa! Chris! Dude! That's w'w'w'w'w'way! overkill, maybe it was, but > it's how I know to fix this problem when it occured for me a few times, and 9 > outta 10 times, this fixed the issue. So, if I'm telling him something that > over complicates things, I'm sorry, but realize I'm just genuinely trying to > help. > > Chris. > > - Original Message - From: "Steve Sparrow" > To: > Sent: Friday, July 11, 2014 8:33 AM > Subject: Re: recording issue with pt > > > hi again, i did not copy this message from pro tools correctly. the message > is this. > the track can not be enabled because it does not have open active input and > output assigned. > this did not happen the other day when i started playing around with it. so i > must be missing something. > I have gone in to the set up window, and looked in the play back engine, and > the motu is selected. but i've not made any recordings yet, and don't have > any projects created with tools to prove the motu is working properly with > pro tools. > Steve > On 11 Jul 2014, at 9:10 pm, Steve Sparrow wrote: > >> Hi. having a recording issue with pt. >> when i hit the record enable button a track, i'm getting a message saying >> the track can not be enabled because active input and output have not been >> assigned. >> now, here is what i have set up. I have the track selected. on the input i >> have gone to the interface, and selected analogue 1 from my motu 869. the >> output is assigned to main out 1 and 2 on the motu. from what i can see, >> i've set up the i.o. so not sure what this message means. Is there something >>
Re: recording issue with pt
OK Steve, let's do a couple of things. First of all, let's make sure that your I/O settings are indeed set correctly. I'm not doubting you that you did nothing, so please know that upfront, but it may be worth us looking at. So bring up PT, but don't have a session opened, preferably, if you can help it. Now, go to your menu bar with vo+M and over to the setup menu. In here, go to I/O. Now, not knowing what version of PT you're using, it's going to be slightly more tricky to trouble shoot this, but I'll give it a go anyway. I'll start by saying the same thing I'd say to anyone on list. We're working with I O settings, and therefore, this can potentially make your audio completely stop working in PT if you do things wrong, so firstly, do exactly as I say, and B, know that you follow these directions at your own risk. They should be safe for the most part as we're not gonna be doing anything in here too distructive, and if you follow me to a T, you should be fine, but just out of the rare chance you're not, I have to CMA. OK, so in here, move to the input tab, and hit vo+command+F5 to select it. I'm not sure how your function keys are set up. You might have to do fn+vo+command+F5. The point is, you wanna route your mouse to your Voiceover cursor. Once done, hit vo+shift+space to click the input tab. Now, we want to select all paths. This isn't going to speak well, I promise you, so you're just gonna have to do it, and hear me out, trusting with faith that it's working. Press command+A to select all. Now, move down to the bottom of the window for convenience sake, then vo+left arrow until you find the delete paths button. It might just say delete, I don't recall the exact wording, but it'll be obvious. command+vo+F5, or whatever on it to route your mouse, then vo+shift+space to click it. You probably could just do vo+space, but I don't wanna chance it. Now, find the default button. Route your mouse, and click it with vo+shift+space. By the way Steve, if you don't see a delete button or a delete paths button, then skip that step and see if you see a default button. If so click it. If you don't see either, then, I don't know what to say, aside maybe reinstall the drivers for your interface. Anyway, next, we want to do exactly the same thing but this time, in the output tab. So go up to the top, click the output tab, just like we did the input tab. Now, hit command+A again to select all paths. Go down and hit delete if you can, then hit default. Finally, do it one more time on the bus tab. Then go down and click OK. Now, go to the setup menu, and then go to the playback engine. Make sure your interface is still correctly selected. If not, set it. Then close and reopen ProTools, even if not prompted to do so, just to be on the safe side. See if that fixes it. If not, someone else is gonna have to chime in. Before anyone else says, Whoa! Chris! Dude! That's w'w'w'w'w'way! overkill, maybe it was, but it's how I know to fix this problem when it occured for me a few times, and 9 outta 10 times, this fixed the issue. So, if I'm telling him something that over complicates things, I'm sorry, but realize I'm just genuinely trying to help. Chris. - Original Message - From: "Steve Sparrow" To: Sent: Friday, July 11, 2014 8:33 AM Subject: Re: recording issue with pt hi again, i did not copy this message from pro tools correctly. the message is this. the track can not be enabled because it does not have open active input and output assigned. this did not happen the other day when i started playing around with it. so i must be missing something. I have gone in to the set up window, and looked in the play back engine, and the motu is selected. but i've not made any recordings yet, and don't have any projects created with tools to prove the motu is working properly with pro tools. Steve On 11 Jul 2014, at 9:10 pm, Steve Sparrow wrote: Hi. having a recording issue with pt. when i hit the record enable button a track, i'm getting a message saying the track can not be enabled because active input and output have not been assigned. now, here is what i have set up. I have the track selected. on the input i have gone to the interface, and selected analogue 1 from my motu 869. the output is assigned to main out 1 and 2 on the motu. from what i can see, i've set up the i.o. so not sure what this message means. Is there something else i need to set up. cheers Steve -- 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 recei
Re: recording issue with pt
hi again, i did not copy this message from pro tools correctly. the message is this. the track can not be enabled because it does not have open active input and output assigned. this did not happen the other day when i started playing around with it. so i must be missing something. I have gone in to the set up window, and looked in the play back engine, and the motu is selected. but i've not made any recordings yet, and don't have any projects created with tools to prove the motu is working properly with pro tools. Steve On 11 Jul 2014, at 9:10 pm, Steve Sparrow wrote: > Hi. having a recording issue with pt. > when i hit the record enable button a track, i'm getting a message saying the > track can not be enabled because active input and output have not been > assigned. > now, here is what i have set up. I have the track selected. on the input i > have gone to the interface, and selected analogue 1 from my motu 869. the > output is assigned to main out 1 and 2 on the motu. from what i can see, i've > set up the i.o. so not sure what this message means. Is there something else > i need to set up. > cheers Steve > > -- > 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.
recording issue with pt
Hi. having a recording issue with pt. when i hit the record enable button a track, i'm getting a message saying the track can not be enabled because active input and output have not been assigned. now, here is what i have set up. I have the track selected. on the input i have gone to the interface, and selected analogue 1 from my motu 869. the output is assigned to main out 1 and 2 on the motu. from what i can see, i've set up the i.o. so not sure what this message means. Is there something else i need to set up. cheers Steve -- 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.
Re: Well, I was wrong.
You wrote: First of all, Chris, you probably shouldn't expect that people have the time to listen to an mp3 where you start going into your preference settings. That's just not reasonable for most people. And, I didn't! expect people to be required to listen. Why do you think I said, if you want! to listen to it, it may help explain things. Nowhere what so ever did I make mention that people absolutely just, had! to listen to it. If you don't wanna play it, or don't have the time, then, don't. Plain and simple. It's only an option I provided. Secondly, if you're close to clipping with your preamps all the way down, then there's another issue here that you need to address and I'm not sure what that is but I can assure you that no microphone's own output signal is hot enough to hit line level without a preamp of some sort. The issue is Slau, it's apparently not hitting that hot, you're correct. Even when Sweetwater went in and looked, it shows I'm hitting at a decent level. I think it's more a Voiceover thing than anything. It appears based on all the testing I've done with an experienced sighted person who knows a ton about audio production, that it's Voiceover being dumb and not correctly announcing the meter levels. You wrote: You clearly don't have the answer because you're searching for it and it would take some deeper examination of what's going on to figure out your issue. OK that made no sense. If something is going wrong, isn't that what one should do?... search and try to figure out the answer? How can you examine anything to start with if you don't search nor ask for what may be the cause? You wrote: I assure you that it has absolutely zero to do with Pro Tools itself. I now agree. I think it's more a bug with Voiceover. When sighted people have looked at my levels, I'm coming in around -14 to -12, which is absolutely perfect. However, on the actual mono audio track itself which the mike is being recorded, when I sing into the mike, as I'm doing so looking at the meter, according to Voiceover, I'm peeking around -5 to -4 DB. So, at this time, the only explaination that I have is Voiceover is being dumb. When I used PT 10, I didn't change a single thing in my interface software, nor did I change anything with the physical hardware gain input dial on the channel through my interface, yet, in PT 10, the meter shows correctly. You wrote: It's software and has no bearing on your recording volume. The problem is that you're dealing with some stuff that you don't understand and you'll need to get a handle on it in order to solve the problem. OK, what stuff then don't I understand? What stuff do I need to research more thoroughly? You wrote: The quagmire is that it takes a lot of time to understand the various aspects of the myriad of equipment and that's why there are schools that teach audio engineering and production. OK, but if you can't afford to go to one of those schools... You wrote: Of course, it's possible to learn this on your own but it can take quite a long time. Understandable. You wrote: Bottom line is, if you have a microphone going into an interface and nothing else in between, there's no possible way your levels can be at -4 dB FS. For one thing, I know what -4DB means, but when you say DB FS, what do you mean by FS? Maybe we're talking two different levels here. Then again, nmaybe not? Secondly, let me go back to my initial point. If indeed this is not ProTools related, and please know, this isn't in any way meant to challenge you nor to be rude/difficult, I'm just trying to understand your point from the bigger picture. So, keep that in mind when reading what I'm about to ask. If PT has nothing to do with it, which by the way, I'm in agreement with you on at this point in time until proven otherwise, then explain this to me... Why then is PT 10 with Voiceover showing me something totally different than PT 11, when my settings are absolutely 100% identical on both versions, I'm running both on the same mac computer, so it's not like I'm on a different workstation, same hardware, same interface, same drivers, same software, same hardware wiring, same hookup, and all my levels on PT, as well as on the interface itself haven't been touched with a 12 foot poll, sota speak, yet I'm getting totally completely different readouts between the two versions? That almost indicates to me that there is an issue in PT 11.2 reading the meaters, vs. in 10.0. This is why I asked a few messages back in the thread if PT11 handled the meters a little differently, or if it was an issue of Voiceover itself doing something odd. You wrote: I guarantee that there's another piece of gear that's causing you to see levels that hot. I suggest you eliminate the variables and figure the problem out that way. All I have is my keyboard which is only running into the interface via midi, so it can't be ca
