This one is beyond me -- can anybody help??<div><br></div><div>Thanks!</div><div>Niels.</div><div><a href="http://nielsmayer.com">http://nielsmayer.com</a></div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Simon Lewis</b><br>Date: Mon, Apr 26, 2010 at 1:45 PM<br>Subject: Re: [PlanetCCRMA] CLAM on CCRMA or Fedora please??<br>To: Niels Mayer <br>Cc: PlanetCCRMA mailinglist <<a href="mailto:planetccrma@ccrma.stanford.edu">planetccrma@ccrma.stanford.edu</a>>, <a href="mailto:music@lists.fedoraproject.org">music@lists.fedoraproject.org</a><br>
<br>Hi Niels<br><div bgcolor="#ffffff" text="#000000">
<br>
Can you help?<big><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>I am trying to build clam 1.4.0 on Fedora 12 x86_64</big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>Using the attached rpm spec file I can
successfully build libclam.</big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>However, the build stops when trying to build the
plug-ins... See
Konsole output below...</big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>The CLAM source code is not particularly lib64
savy -
clam_build_helpers.py has to be modified to build libclam.</big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>How to build the plug-ins on 64bit linux systems? </big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>Simon</big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big></big></font><br>
<font size="-1"><big>+ for i in Filters GuitarEffects MIDI resampling
samplebysample sndfile
spacialization speech osc</big></font><br>
<font size="-1"><big>+ pushd plugins/Filters</big></font><br>
<font size="-1"><big>~/rpmbuild/BUILD/CLAM-1.4.0/plugins/Filters
~/rpmbuild/BUILD/CLAM-1.4.0</big></font><br>
<font size="-1"><big>+ export
PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib64/pkgconfig</big></font><br>
<font size="-1"><big>+
PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib64/pkgconfig</big></font><br>
<font size="-1"><big>+ scons
clam_prefix=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr
prefix=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr</big></font><br>
<font size="-1"><big>scons: Reading SConscript files ...</big></font><br>
<font size="-1"><big>Package clam_core was not found in the pkg-config
search path.</big></font><br>
<font size="-1"><big>Perhaps you should add the directory containing
`clam_core.pc'</big></font><br>
<font size="-1"><big>to the PKG_CONFIG_PATH environment variable</big></font><br>
<font size="-1"><big>No package 'clam_core' found</big></font><br>
<font size="-1"><big>OSError:
'PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib/pkgconfig
pkg-config
clam_core --libs --cflags' exited 1:</big></font><br>
<font size="-1"><big> File
"/home/simon/rpmbuild/BUILD/CLAM-1.4.0/plugins/Filters/SConstruct",
line 36:</big></font><br>
<font size="-1"><big> env.EnableClamModules(clamDependencies,
CLAMInstallDir)</big></font><br>
<font size="-1"><big> File "/usr/lib/scons/SCons/Environment.py", line
217:</big></font><br>
<font size="-1"><big> return apply(self.method, nargs, kwargs)</big></font><br>
<font size="-1"><big> File
"/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/share/clam/sconstools/clam.py",
line
166:</big></font><br>
<font size="-1"><big> ' '.join(libs)))</big></font><br>
<font size="-1"><big> File "/usr/lib/scons/SCons/Environment.py", line
1447:</big></font><br>
<font size="-1"><big> return function(self, self.backtick(command))</big></font><br>
<font size="-1"><big> File "/usr/lib/scons/SCons/Environment.py", line
585:</big></font><br>
<font size="-1"><big> raise OSError("'%s' exited %d" % (command,
status))</big></font></big><br>
<font size="-1"><font face="sans-serif"></font></font><br>
<br>
Am 26.04.2010 18:32, schrieb Niels Mayer:
<blockquote type="cite"><div><div></div><div class="h5">I noticed that CLAM stopped being supported by PlanetCCRMA
around F8 timeframe.
<div><br>
</div>
<div>It looks like a lot of new and cool stuff is available. Any
interest in getting this added?</div>
<div><br>
</div>
<div><a href="http://clam-project.org/" target="_blank">http://clam-project.org/</a></div>
<div><br>
</div>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">CLAM
1.4.0, 3D molluscs in the space</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex"><br>
</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">The
CLAM project is delighted to announce the long awaited 1.4.0 release
of CLAM, the C++ framework for audio and music, code name 3D molluscs
in the space.</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex"><br>
</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">In
summary, this long term release includes a lot of new spacialization
modules for 3D audio; MIDI, OSC and guitar effectsmodules;
architectural enhancements such as typed controls; nice
usability features for the NetworkEditor interface; convenience tools
and scripts to make CLAM experience better; enhanced building of LADSPA
plugins and new support for LV2 and VST plugin building; a new easy to
use application to explore songs chords called Chordata; many
optimizations, bug fixing and code clean ups.</blockquote>
<div><br>
</div>
<div>It looks great and easy to use: <a href="http://clam-project.org/wiki/Development_screenshots" target="_blank">http://clam-project.org/wiki/Development_screenshots</a></div>
<div><br>
</div>
<div>See also:</div>
<div><br>
</div>
<div><a href="http://vokicodder.blogspot.com/2007/04/educational-vowel-synth-and.html" target="_blank">http://vokicodder.blogspot.com/2007/04/educational-vowel-synth-and.html</a></div>
<div><a href="http://vokicodder.blogspot.com/2007/04/realtime-mfcc-and-lpc-analysis.html" target="_blank">http://vokicodder.blogspot.com/2007/04/realtime-mfcc-and-lpc-analysis.html</a></div>
<div><a href="http://vokicodder.blogspot.com/2007/04/realtime-voice-gender-change.html" target="_blank">http://vokicodder.blogspot.com/2007/04/realtime-voice-gender-change.html</a></div>
<div><a href="http://vokicodder.blogspot.com/2009/04/vst-plugins-with-qt-user-interface.html" target="_blank">http://vokicodder.blogspot.com/2009/04/vst-plugins-with-qt-user-interface.html</a></div>
<div><br>
</div>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">...
CLAM allows to visually build JACK and PortAudio based applications
with Qt interfaces as well as GUI-less VST and LADSPA plugins. The more
flashy feature of VST is user interfaces that are mostly built
using VSTGUI. We are using Qt as interface for JACK and Portaudio based
apps because we are using the nice features of Qt toolkit to
dynamically bind the UI elements and the underlaying processing.
Moreover, Qt styling features enables shinning designer-made
interfaces. Why not being able to reuse the same interface for VST and
JACK? That has been a long standing TODO in CLAM so now is time to
address it.</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">
<br>
</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">In
summary, we fully solved croscompiling vst's from linux and we even
started using qt interfaces as vst gui. In that last point, there still
is a lot of work to do, but the basic question on whether you can use
qt to edit a vst plugin is now out of any doubt.</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">
<br>
</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">To
make the spike simpler, and in order not to collide with other CLAM
developers, currently working on it, i just left apart all the CLAM
wrapping part, just addressing vst crosscompiling and Qt with the sdk
examples.</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">
<br>
</blockquote>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0px 0px 0px 0.8ex;padding-left:1ex">Cross
compilation was pretty easy. This time I found lot more documentation
on mingw and even scons. Just by adding the crossmingw scons tool we
are already using for the apps and i managed to get Linux
cross-compiled plugins running on Wine. </blockquote>
<div><br>
<font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre;"><br></span></font>
</div>
</div></div></blockquote><br>
</div>
</div><br></div>