From alsa-devel-owner@alsa.jcu.cz  Fri Oct  9 19:49:14 1998
Received: from lbox1.burly.com (lbox1.burly.com [208.12.9.18])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id TAA18240
	for <alsa-devel@jcu.cz>; Fri, 9 Oct 1998 19:49:07 +0200
Received: from chili.burly.com (chili.burly.com [208.12.9.20])
	by lbox1.burly.com (8.8.7/8.8.7) with SMTP id KAA14774
	for <alsa-devel@jcu.cz>; Fri, 9 Oct 1998 10:42:32 -0700
Date: Fri, 9 Oct 1998 10:46:58 -0700 (PDT)
From: Mike Lewis <mlewis@burly.com>
To: alsa-devel@jcu.cz
Subject: newbie questions about dsp api
In-Reply-To: <Pine.SOL.3.96.981009105041.182A-100000@kotilo>
Message-ID: <Pine.LNX.3.96.981009100658.8032N-100000@chili.burly.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Hi.  I've got a few questions about the dsp interface.  If anyone has
answers, or source code that use these features, I'd be most appreciative.

For snd_pcm_block_mode(void *handle, int enable), does the enable
arg take a 0 for disable and 1 for enable?  I tried both values and found
no difference in blocking.

For snd_pcm_playback/record_info, what are fragments?  What is the
relationship between min_fragment_size, max_fragment_size and
fragment_align?  On my sb16, I get min=32, max=32768 and align=0.

Related to prev question: what is the strategy for using
snd_pcm_playback/record_params?  My guess it's for tuning the buffer, but
don't know.  Could someone explain?

snd_pcm_playback/record_status seems like more info for tuning
buffer/playback/record and synchronization.  What is the strategy for
using this?

Thanks.
Mike



