From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Janssen Subject: Application development Date: Tue, 29 Apr 2014 09:40:37 +0200 Message-ID: <535F5775.7080504@amsat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from pe1chl.nl.eu.org (pe1chl.nl.eu.org [89.18.172.156]) by alsa0.perex.cz (Postfix) with ESMTP id 0FE262625F3 for ; Tue, 29 Apr 2014 09:40:39 +0200 (CEST) Received: from linux.pe1chl.ampr.org (linux.pe1chl.ampr.org [44.137.41.97]) by sys2.pe1chl.ampr.org (8.14.4/8.14.4/Debian-4) with ESMTP id s3T7ec0s028908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 29 Apr 2014 09:40:39 +0200 Received: from [127.0.0.1] (localhost [127.0.0.1]) by linux.pe1chl.ampr.org (8.14.7/8.14.7) with ESMTP id s3T7ebl7008700 for ; Tue, 29 Apr 2014 09:40:37 +0200 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org A week and a half ago I asked some questions about application development using alsa ("Control the exact moment of output"), but it appears this list is more about development of alsa itself. Is there another place where discussions about using alsa are more appropriate, and/or a place where documentation can be found that goes a bit further than a plain list of function names and parameter lists? I.e. a more general description about how one structures an application that uses alsa, and how timing fits in that picture. Rob