Re: [Bluemusic-users] killing csound/csoundAPI
Brought to you by:
kunstmusik
From: ebmtranceboy <ebm...@gm...> - 2012-09-22 16:56:25
|
Hi Steven, I've just compiled Csound version 5.18.03 beta (double samples) Here are my compiling options scons -j 3 buildDSSI=1 buildImageOpcodes=1 buildInterfaces=1 buildJavaWrapper=1 buildNewParser=1 buildPythonOpcodes=1 buildUtilities=1 buildVirtual=1 Lib64=0 useDouble=1 usePortAudio=1 usePortMidi=1 useALSA=1 useJack=1 useFLTK=1 Word64=1 buildPythonWrapper=1 smoothSort=1 buildCsoundAC=1 buildBeats=1 dynamicCsoundLibrary=1 buildOSC=1 useOSC=1 If I had understood all of these, I would probably have removed some other ones but I followed http://www.csounds.com/node/1373 and I removed only mp3 and stk since I know I don't need them. FYI, here is what I see now : * with blue2.2.2 : no change (no csoundAPI available + cpu-eater STOP button) * with blue2.3.0 : - with csoundAPI : all is fine - without : same behaviour as with blue2.2.2 -- View this message in context: http://csound.1045644.n5.nabble.com/killing-csound-csoundAPI-tp5715823p5716024.html Sent from the Csound - Blue - User mailing list archive at Nabble.com. |