From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Date: Tue, 11 Aug 2009 22:25:38 -0700 From: Roman Shaposhnik In-reply-to: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: References: <263c72eb8fb54e742882b53d6183f71b@quanstro.net> <414BCD8C-1138-4A9E-AF40-D4022A2FA223@sun.com> Subject: Re: [9fans] audio standards -- too many to choose from Topicbox-Message-UUID: 43ae1ee4-ead5-11e9-9d60-3106f5b1d025 On Aug 11, 2009, at 10:10 PM, Tim Newsham wrote: >> I'm not sure either latency or RT is proper terminology here. But >> I believe what I meant was clear: when you need overall latency >> to be around 5ms you start to notice 9P. > > It sounds like you have a specific app in mind, and a real-time > one at that. If you're using your audio device for live audio > (ie. adding effects to audio from your guitar) > you need pretty small latency. You can go a bit higher than > 5ms without noticing, though. Not so much a special application (although I was doing VJing at the time) but rather [multitrack] recording. > Most apps dont require realtime. For example, streaming a song. > You dont care if the samples show up at year ear 2seconds > after they were sent from your hard drive, so long as all the > samples are delayed by the same amount.. You can stream this > clear across the country over all kinds of cut rate ISPs and > still get satisfactory results with enough buffering.. Sure. But if all you're aiming at with this thread is a driver that supports simple audio playback, I guess I misread the subject line. Thanks, Roman.