[ddots-l] Re: I/O buffer size and latency

Omar,
On the FA66, the monitor mix knob(its described in those faceplate descriptor files I sent you) mixes the signal coming from both the inputs and the signal going to the outputs from sonar. Center position gives equal volume to both. Far left gives exclusive access to the signal at the input jacks. And far right (clockwise) gives exclusive access to the signal coming back from sonar. And, obviously, settings inbetween the extremes is a weighted mix of the two.
So, to hear sonar's input echo alone, turn the input echo on in the sonar track, and turn the monitor mix knob fully counterclockwise. To eliminate signal from sonar(in the monitor only), and hear only the dry signal at the input jacks, turn the monitor mix knob fully clockwise.
Unless you're using headphones, watch out for feedback if you've got open mics while monitoring the input signal.
----- Original Message ----- From: "Omar Binno" <omarbinno@xxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 7:43 PM
Subject: [ddots-l] Re: I/O buffer size and latency



How do you change the input monitoring to go through the soundcard?

Omar Binno
Phone: (248) 444-9699
Email: omarbinno@xxxxxxxxx
My Space: www.myspace.com/omarbinno
----- Original Message ----- From: "Luis Elorza" <luiselorza@xxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 7:37 PM
Subject: [ddots-l] Re: I/O buffer size and latency
i recommend you use 64 because it will give you enough power to record a huge project, and i also recommend instead of using input monitor in your sonar tracks, try using an input monitor in your soundcard, most have this function that is a direct dry signal routed from your inputs to your outputs. and this way you can have whatever latency setting in sonar. any ways you can notice that even at minimum latency your monitoring will sound as a doubler and to me it's very anoying. 
this way you only need low latency  when playing soft synths.
----- Original Message ----- From: "Phil Halton" <philhalt@xxxxxxxxxxx> 
To: "ddots-l" <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 2:06 PM
Subject: [ddots-l] I/O buffer size and latency
my sonar6 producer installation on an ADK laptop is set to a I/O buffer size of 128(advanced page of audio options). The sonar default is (according to the help files) 64.
I'm using the internal system drive for audio data(7200 rpm drive). I'm wondering what the best setting for the I/O buffer size would be to maximize latency and minimize dropouts. How does this variable affect disk throughput, and with this kind of system drive, what might be a better setting than 128KB?
Currently, I can record at 24 bits with minimally perceptable latency with input echo on. Naturally, I'm trying for zero latency while recording audio, but I start getting dropouts when I start cutting the latency slider any further than 50% for the Edirol FA66(ASIO). Wouldn't recording at 16 bits improve latency(50%less data throughput involved with 16bits from 24bits).
I like the headroom and quality that comes from 24bits, but I want that zero latency for obvious reasons. That's why I'm considering changing the disk I/O buffer size--it seems to be the only variable left that might improve performance. 
.


** 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 



** 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: