Date: Tue, 09 Mar 2004 09:02:43 -0600 From: Jim Ramsay <i.am@jimramsay.com> To: freebsd-multimedia@freebsd.org Subject: Re: calling all audio ports maintainers -- ardour and jack Message-ID: <c2kmaj$u5o$2@sea.gmane.org> In-Reply-To: <20040309112430.GA93365@huckfinn.arved.de> References: <20040309032501.32f5995c@localhost> <20040309112430.GA93365@huckfinn.arved.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Tilman Linneweh wrote: > * epilogue@allstream.net [Di, 09 Mär 2004 at 09:25 GMT]: > >>just dropping a line to see whether anyone is working on porting >>ardour (ardour.org) and jack (jackit.sf.net) over to freebsd? >> >> >>does anyone know if there are OS architectural issues preventing this >>software from being ported? or is it mostly a matter of finding someone >>willing to contribute their time and effort? >> > > > You need to port ALSA to FreeBSD. > Maybe it is possible to write an OSS output driver for jack, but I think you > still need the ALSA userspace library. Apparently there's a portaudio backend for Jack, and I'm pretty sure portaudio works with FreeBSD as that's what Audacity uses (and that works okay on FreeBSD). I'm afraid there may be scheduler latency issues with FreeBSD, though. For example, when I'm recording a second track with Audacity in full-duplex mode, I get an audible drop every 12 seconds or so (I suspect that's when audacity flashes its buffer to disk, but have been unable to confirm this). For now I've actually moved back to Linux for my one desktop system with the nice soundcard, just for the low-latency kernel patch and jack/ardour. If this starts working well, I'll be back to FreeBSD for everything again. -- Jim Ramsay "Me fail English? That's unpossible!"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c2kmaj$u5o$2>