[Clam-devel] problems with LADSPA on Intel Mac

[Pau Arumi]

En/na Greg Kellum ha escrit:
> Hi Andreas,
> 
> I had the same problems installing libsndfile and maybe cppunit on my 
> Intel mac.  I can remember having to compile and install both of those 
> libraries from their sources.  I would suggest you do the same.

That info should be in the wiki then...
However I still hope we'll manage to fix the macport install.
Andreas just reported success with cppunit and qt4(!) on irc, 
some hours ago.

> With regards to jackOSX, why are you trying to use this in the first 
> place?  I gave up on using jack on OS-X a number of years ago, because 
> the latency that jack added to the audio stream, basically meant that 
> you couldn't do anything in real-time any more.  In my own experience 
> only having my code loaded as a vst plugin or connected via rewire kept 
> the latency small enough for real-time applications.

ATM, jack is the clam preferred back-end. Our PortAudio backend
is not stable and doesn't allow doing things like choosing the
driver and hardware device.

Your comment about vst and low-latency I think is a bit
misleading. Vst, or any other plugin standard by the matter,
basically defines a callback schema.
It is the host implementation the responsible for choosing the
callback buffer sizes, dealing with the back-end/driver, and at
the end, keeping the latency low.
In other words, any vst plugin wont play in low-latency in a
badly implemented host. Furthermore, there are vst hosts that
uses jack as back-end in mac osx (ardour compiled with vst).

About jack in mac osx, I think it's time you give it a second try 
;). In my macbook, I get very reasonable (low)
latencies. I'm saying it by heart but I think that works reliably
with 256 buffer size (48KHz) which is not bad for a poor intel
onboard sound chip. In short, your jack app performs as good as 
CoreAudio can. From http://jackaudio.org/faq

"There is NO extra latency caused by using JACK for audio input
and output. When we say none, we mean absolutely zero. The only
impact of using JACK is a slight increase in the amount of work
done by the CPU to process a given chunk of audio, which means
that in theory you could not get 100% of the processing power
that you might get it if your application(s) used ALSA or
CoreAudio directly. However, given that the difference is less
than 1%, and that your system will be unstable before you get
close to 80% of the theoretical processing power, the effect is
completely disregardable."

Cheers!
Pau


> Best,
> Greg
> 
> 
> 
> On 8/15/07, *Andreas Calvo* <flipy.bcn at gmail.com 
> <mailto:flipy.bcn at gmail.com>> wrote:
> 
>     I've been trying to install CLAM[1] under mac os X, but it turns out
>     that the wiki was a little bit obsolet and some steps are broken.
>     First, I couldn't install the "libsndfile", it reports this error:
>     Command output: sndfile-play.c:489: error: 'time_in' undeclared
>     (first use in this function)
>     Then, I've tried to install all other dependencies, but "cppunit" is
>     not available neither.
> 
>     I've also installed jackOSX, and Qjackctl for mac os x, but it
>     crashes when I try to run it after configuring.
>     (Following some instructions from the Ardour Mac OS X team [3])
> 
>     So I've moved into trying to install LADSPA[2], so I've needed to
>     hack the makefile a little bit.
>     But now, trying to compile, it gaves me errors about the " stdio.h"
>     [4] file:
>     In file included from listplugins.c:10:
>     /usr/include/stdio.h:84: error: parse error before 'fpos_t'
> 
>     Does anyone have any hint about this problems?
> 
> 
>     [1] http://clam.iua.upf.edu/wikis/clam/index.php/Devel/Mac_OSX_build
>     [2] http://www.ladspa.org/download/ <http://www.ladspa.org/download/>
>     [3] http://ardour.org/requirements_osx
>     <http://ardour.org/requirements_osx>
>     [4] http://lalists.stanford.edu/lad/2005/04/0162.html
> 
> 
>     _______________________________________________
>     Clam-devel mailing list
>     Clam-devel at llistes.projectes.lafarga.org
>     <mailto:Clam-devel at llistes.projectes.lafarga.org>
>     https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
>     <https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel