I know, but I can't get anywhere with external firewire drives and the FA66
on the ADK laptop
Why do you say 256Kb? Is that just a guess, or do you have some
experience and/or information to justify it?
----- Original Message -----
From: "Omar Binno" <omarbinno@xxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 6:12 PM
Subject: [ddots-l] Re: I/O buffer size and latency
Try 256. Also, it's strongly recommended not to use your main comp
harddrive for audio data storage.
Omar Binno
Phone: (248) 444-9699
Email: omarbinno@xxxxxxxxx
My Space:
www.myspace.com/omarbinno
----- Original Message -----
From: "Phil Halton" <philhalt@xxxxxxxxxxx>
To: "ddots-l" <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 6: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
