From owner-freebsd-ports@FreeBSD.ORG Thu Jul 24 03:22:18 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52BDE37B401 for ; Thu, 24 Jul 2003 03:22:18 -0700 (PDT) Received: from komposti.turkuamk.fi (komposti.turkuamk.fi [195.148.208.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4728043F93 for ; Thu, 24 Jul 2003 03:22:17 -0700 (PDT) (envelope-from Lauri.Jarvenpaa@students.turkuamk.fi) MIME-Version: 1.0 To: freebsd-ports@freebsd.org From: "Lauri J =?iso-8859-1?Q?J=E4rvenp=E4=E4?=" Date: Thu, 24 Jul 2003 13:28:28 +0300 Message-ID: X-MIMETrack: Serialize by Router on lisa/AmkOp(Release 5.0.12 |February 13, 2003) at 24.07.2003 13:28:30 Content-type: text/plain; charset=us-ascii Subject: Ardour/JACK port and low-latency FreeBSD audio? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 10:22:18 -0000 Hello. Is anybody planning to port JACK and Ardour to FreeBSD? I asked the author about the requirements on the kernel side and he replied: "it requires: a) SCHED_FIFO scheduling to be fully implemented, or something equivalent. b) at least as much of P.1003 (pthreads) to be fully and correctly implemented as linuxthreads takes care of c) very fast FIFOs for interprocess cooperative scheduling (this is critical)" I guess these do exist on FBSD but some light into subject would be nice. And more requirements: "JACK currently requires ALSA support to do anything useful, although someone has written a wrapper for PortAudio for the OS-X port, and there is also a patch to run JACK on top of a homegrown audio device driver." Any additional ideas? How is low-latency audio usually handled in FreeBSD? Finally, interesting sidenote: "btw, JACK stress tests OS scheduling in a way and to a degree that no other software does. it has revealed several problems with the linux scheduler, and can easily cause system lockups if kernel level locking protocols have even the tiniest weakness to them." If nobody is alredy doing this I could try to give it a mentally challenged shot.