Re: System preparation for realtime audio
Re: System preparation for realtime audio
- Subject: Re: System preparation for realtime audio
- From: Stéphane Letz <email@hidden>
- Date: Thu, 6 Mar 2008 11:57:56 +0100
Message: 9
Date: Wed, 5 Mar 2008 22:28:18 -0800
From: Brian Willoughby <email@hidden>
Subject: Re: System preparation for realtime audio
To: alejandro <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
I am not entirely sure why you are using JACK. In my impression,
JACK is useful for users (not developers) who do not have the source
code available for their favorite playback application, but who still
want to manipulate (or record) that output.
In your case, you are developing a DAW, and it would seem that you
have full control of the audio data and processing. Why do you need
JACK? Can you not work directly with the audio output devices or
aggregates?
One reason for people wanting to port a Linux application on OSX use
JACK, is... because JACK is first an API for developers! So basically
the audio code can be used directly. Ardour (http://ardour.org/) is
an example of that approach. Then your application get JACK inter-
application audio for free.
I suppose that if your system involves integrating e.g. iTunes
playback, instead of simply opening the same file within your DAW and
playing it yourself, then you might need JACK to harvest the audio
streams of other applications. But it would still seem to me that
you would be better off implementing your own playback rather than
integrating the playback of an application for which you do not have
source into your DAW audio stream.
In other words, JACK might be making your problem more difficult than
it needs to be. I am merely suggesting that reworking your design to
use audio output units instead might get your product working
sooner. I have nothing against JACK for the problems it is designed
to solve, but it does seem to overly complicate your design.
P.S. I scanned your web site, but cannot determine from the
voluminous text whether JACK might be integral to your feature set
somehow. Where's the Executive Summary? ;-)
Brian Willoughby
Sound Consulting
I don't think the described problems have anything to do with using
JACK. Threads issues have to be solved first.
Regards
Stephane Letz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden