[ddots-l] Re: metering discrepancies
What happened is: I was recording an audio stream from the internet which played through my jaws soundcard. I routed the jaws soundcard into the sonar soundcard--so far so good. When testing the input level, I mistakenly got the spike in level when jaws announced the meter level-not the level of the streamed program. So, jaws level was around -5db, and that's what I mistakenly read as the level for the stream. Fooled myself pretty good with that one!
----- Original Message ----- From: "Mike Christer" <m-christer@xxxxxxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, January 27, 2007 11:59 AM
Subject: [ddots-l] Re: metering discrepancies
Try pushing the input level until it distorts, then back it off a little, and see what the post meter reading is!
It might do the trick, possibly showing that Sonar isn't seeing the input properly? 

I dunno, might work...

Alternatively, have you reset and refreshed the meters etc?
----- Original Message ----- From: "Phil Halton" <philhalt@xxxxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, January 27, 2007 4:39 PM
Subject: [ddots-l] Re: metering discrepancies
that's what I did, I armed track, and read meter with f2 after first resetting the meter with triple f2. it read approx -5 DB, then on playback with track unarmed, meter read approx -17 db. I changed no settings--I just loaded the normal template into a new session of sonar, and began recording after checking input level. I haven't really given much attention to this aspect of sonar(digital audio recording), and I'll have to investigate it a little more with an eye towards this problem. 


.
----- Original Message ----- From: "Mike Christer" <m-christer@xxxxxxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, January 27, 2007 9:11 AM
Subject: [ddots-l] Re: metering discrepancies



Phil!
When looking at the input level, make sure the feedback you get from JAWS says, "input", and not "output"?
I guess you know that you should take the meter level when the track is actually armed? 

Mike

Mike
----- Original Message ----- From: "Luis Elorza" <luiselorza@xxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, January 27, 2007 4:18 AM
Subject: [ddots-l] Re: metering discrepancies
maybe you lowered the volume for that track. the meter shows the output level not your wave file level.
----- Original Message ----- From: "Phil Halton" <philhalt@xxxxxxxxxxx> 
To: "ddots-l" <ddots-l@xxxxxxxxxxxxx>
Sent: Friday, January 26, 2007 4:43 PM
Subject: [ddots-l] metering discrepancies
When I check meter levels with an audio track armed, then record on that track, and then check my levels on playback, there is a big discrepancy. For example, I had an input level of around -5 DB with an armed track, then on playback, the meters read around -17 DB. Why the big discrepancy?
Is this a sonar thing, or something to do with my hardware? I'm using an Echo Indigo I/O laptop soundcard with sonar 5.2 

** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq 



** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq 



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.12/653 - Release Date: 26/01/2007 




** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq 




** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq 



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.12/653 - Release Date: 26/01/2007 



** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq 




** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: