From mboxrd@z Thu Jan 1 00:00:00 1970 From: torbenh Subject: alsa jack plugin Date: Mon, 8 Nov 2010 10:26:47 +0100 Message-ID: <20101108092647.GS4410@siel.b> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by alsa0.perex.cz (Postfix) with SMTP id 2B3622438C for ; Mon, 8 Nov 2010 10:26:49 +0100 (CET) Received: from torbenh by siel.b with local (Exim 4.72) (envelope-from ) id 1PFNzz-0004AL-UB for alsa-devel@alsa-project.org; Mon, 08 Nov 2010 10:26:47 +0100 Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org the alsa jack plugin has quite some problems: a) does not work correctly with mplayers alsa output. (and quite a few others) b) it includes the pid in its clientname. c) it requires port connections. d) jack client is deactivated when alsa stream is not active. e) no way to set the jack clientname the master branch on git://hochstrom.endofinternet.org/alsa-plugins carries fixes for a, b and e. c and d have their own branches. i have seen a few problems with making the write end of the fd non-blocking. would it be possible to use eventfd(2) for this ? -- torben Hohn