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

Gordon,
According to tech support at ADK, laptops just aren't well equipped to handle multiple firewire devices--at least not for audio. I tried every configuration of PCMCIA firewire adaptor withexternal hD and/or FA66. I even tried connecting the FA66 to the back of the HD. I worked on this with tech support from DancingDots, Edirol, Cakewalk, Glyph and ADK. all these configurations yielded less than acceptable results.
That's OK--at least I know its a limitation of the architecture itself. The solution I'm using is on the advice of ADK to either go with an external Esata drive or USB2.0, as both of these use a different buss entirely from the firewire device--eliminating the buss contention problems.
I went with the USB2.0 (Maxtor was recommended by ADK) and it seems to have solved the problem. As I understand it, USB2.0 has a bandwidth at least equal to Firewire400. I realize that their protocols and interface are quite different, But I don't know that that is going to be a significant factor here. by ADK tech supports standards, as long as the USB buss isn't heavily used by other devices, , USB should do the trick.
At any rate, I'm happy now to be able to make some music with my rig instead of continually chasing down hardware problems.
----- Original Message ----- From: "Gordon Kent" <dbmusic@xxxxxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, March 31, 2007 3:03 AM
Subject: [ddots-l] Re: I/O buffer size and latency



Phil:
Does your adk have the firewire integrated on it? If it does, you can get another firewire pcmcia card for your external drive. They really are not expensive. That being said, I really have gotten away with recording my audio on the drive in the adk with no problems. Make sure that you have the WiFi option turned off though, that will effect audio performance. If yours is like mine, press function f2 which will toggle it on and off. 
Gord
----- Original Message ----- From: "Phil Halton" <philhalt@xxxxxxxxxxx> 
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2007 7:02 PM
Subject: [ddots-l] Re: I/O buffer size and latency
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 



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