Write an apple script to convert the value? :P

On 11 Jul 2014, at 17:15, Chris Smart <[email protected]> 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 <[email protected]> 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 [email protected].
>> > 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 [email protected].
>> 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 [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to