Hi, Well, no, CLAM isn't depending on Jack, but as port audio also isn't working correctly on my system (or so it seems), I thought I'd try it, but I couldn't get it to link correctly. So, I also just turned it off by setting with_jack=no.
Best, Greg On Thu, Apr 17, 2008 at 3:06 PM, Han, Yushen <[EMAIL PROTECTED]> wrote: > Hi, Greg > > Thank you for this report and the progress! > > I have problem with Jack for Mac in my 10.5.2. The jack lib is in my > /usr/local/lib. > > But when I use it to play anything, I got something like > > ConnectPort: can't find mach server port name = jackdmp_entry_default > err = unknown error code > Cannot connect to server Mach port > jack server is not running or cannot be started > JAR: Blacklisted client Xquartz > JAR: Blacklisted client Terminal > JAR: Blacklisted client loginwindow > JAR: Blacklisted client Xcode > JAR: Blacklisted client SystemUIServer > JAR: jack server not running? > > Actually I changed the Sconstruct file turn off the Jack by > with_jack = False > Then I compiled CLAM. > > I am not sure if CLAM is really depending on Jack. > It seems to work without it. Does anybody know about this? > > Best regards, > Han, Yushen > > > > > On Thu, Apr 17, 2008 at 8:58 AM, Greg Kellum <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I did some debugging last night to see why the NetworkEditor's plugins > > weren't loading correctly on my system, and I realized that I had been > > linking against an older version of clam that somehow ended up in my > > /opt/local directory. Don't ask me how. Anyway, I deleted those > > binaries, and after relinking against the actual CLAM libraries, I did > > get all of the plugins in the Network Editor. > > > > So, I loaded up the SDIFDatabaseProcessing to see if it was working, > > but I had some issues with port audio. First, port audio tried to use > > a sample rate of 48000 which the built in audio card on my laptop > > doesn't support. So, I recompiled the port audio processing code to > > use 44100 instead. But then port audio complained about a buffer > > overrun problem when I tried to turn on the audio. I'm not sure why > > this happened. Anyone have any ideas? > > > > Then, I tried to install jack and use that instead, but after > > installing the standard jack distribution for OS-X, scons complained > > that jack wasn't registed with pck-config or something like that, and > > it wouldn't let me compile against jack even though the jack library > > was in /usr/local... > > > > So, some progress was made, but it's still not working yet... > > > > Greg > > > > > > > > On Wed, Apr 16, 2008 at 6:44 PM, Han, Yushen <[EMAIL PROTECTED]> wrote: > > > Hi, Pau > > > > > > Now I can see only 1 processing - VectorBasedArrayPanning in the list > :-( > > > > > > I can see "parumi|home" in the chatroom. It you prefer, I am happy to > > > continue our discussion there. > > > > > > Did you see my response (as comments to my GSoC proposal ) to your > question? > > > Let me know if you need more information from me. > > > > > > Best regards, > > > Han, Yushen > > > > > > > > > > > > > > > > > > On Wed, Apr 16, 2008 at 11:47 AM, Pau Arumí Albó <[EMAIL PROTECTED]> > wrote: > > > > > > > > El dc 16 de 04 del 2008 a les 11:36 -0400, en/na Han, Yushen va > > > > escriure: > > > > > > > > > Pau, > > > > > I see. This is a good point. > > > > > > > > > > I went to my CLAM_PLUGIN_PATH > > > > > There are two files now: > > > > > libplugins_continuous_excitation_synth.dylib > > > > > libplugins_spacialization.dylib > > > > > > > > > > Can I know the files that you have to make the SDIF work in your > > > > > CLAM_PLUGIN_PATH? > > > > > > > > Yes, you have it: libplugins_continuous_excitation_synth.dylib > > > > each plugins sub dir compiles a libplugins_*.dylib > > > > > > > > The fact you pointed on the previous mail (you see 3D audio plugin > > > > category but not New Spectral Processing) is interesting, because > both > > > > categories are from plugins in the libplugins_spacialization.dylib. > > > > > > > > It seems your OS is not loading some of the processings. To confirm > > > > this: how many processings do you have in the 3D Audio category? > > > > You should see 14. > > > > > > > > (BTW, we would be more efficient discussing over irc, come by if you > > > > can) > > > > > > > > > > > > > > > > P > > > > > > > > > Previously , you suggested that I could print out the loaded > libraries in > > > > > > > > > > void RunTimeLibraryLoader::LoadLibrariesFromPath(const > std::string & > > > > > path) const > > > > > CLAM/src/Processing/Plugins/RunTimeLibraryLoader.cxx line 30 > > > > > > > > > > This is a good idea and I can try that later. > > > > > > > > > > Best regards, > > > > > Han, Yushen > > > > > > > > > > On Wed, Apr 16, 2008 at 11:19 AM, Pau Arumí Albó <[EMAIL > PROTECTED]> wrote: > > > > > > > > > > > > A related issue: our current plugin loading strategy is quite > "raw" in > > > > > > the sense that we dynamically load *every* file in the plugin > directory > > > > > > list. While this works in Linux and Windows, in Mac (10.4.9) i > get a > > > > > > crash each time i provide a directory with binaries that are > not clam > > > > > > plugins. > > > > > > > > > > > > For example if i point CLAM_PLUGIN_PATH to > > > > > > plugins/continuousExcitationSynthesizer, and start > NetworkEditor it > > > > > > crashes when trying to load the binaries (executables, not > plugins) in > > > > > > that dir. The same happens if the clam_plugin_path points to > somewhere > > > > > > else like /usr/bin. > > > > > > > > > > > > So this is a (not really annoying) bug, that should be fixed by > > > > > > filtering the files we dynamically load. > > > > > > > > > > > > P > > > > > > > > > > > > > > > > > > > > > > > > El dc 16 de 04 del 2008 a les 17:10 +0200, en/na Pau Arumí > Albó va > > > > > > escriure: > > > > > > > > > > > > > > > > > > > > Hi, Pau > > > > > > > > > > > > > > > > No, it does not appear in the processing tree ( unlike > what you had in > > > > > > > > your snapshot). > > > > > > > > By "use", I mean that > > > > > > > > (1) I could not add it to the processing tree. (neither > SDIFDatabaseReader) > > > > > > > > (2) In SMSTools, I could do SMS analysis but could not > save the > > > > > > > > result in SDIF (all SDIF related operation could not be > done). > > > > > > > > > > > > > > > > Han, Yushen > > > > > > > > > > > > > > I've checked again now in my Mac OS 10.4.9. And it loads > here. > > > > > > > It could be some issure related on how dynamic libs are > loaded in 10.5. > > > > > > > We need some debuggin from you guys (as described in > previous responses) > > > > > > > to find out the problem. > > > > > > > > > > > > > > But to be sure we about the current status, could you (or > Greg) confirm > > > > > > > if other plugins are loading? > > > > > > > > > > > > > > To be specific, do you see the categories "[plugin] 3D > Audio" and > > > > > > > "[plugin] New Spectral Processing"? > > > > > > > You should see them after having issued "scons install" in > > > > > > > plugins/spacialization. And having done "export > > > > > > > CLAM_PLUGIN_PATH=/your/prefix/lib/clam/" > > > > > > > > > > > > > > P > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Apr 16, 2008 at 4:20 AM, Pau Arumí Albó <[EMAIL > PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > El dt 15 de 04 del 2008 a les 16:35 -0400, en/na Han, > Yushen va > > > > > > > > > escriure: > > > > > > > > > > > > > > > > > > > Hi, Pau and Greg > > > > > > > > > > > > > > > > > > > > Thank you for your information with the snapshot, Pau. > > > > > > > > > > > > > > > > > > > > I checked out r11310 and just compiled both the CLAM > and the plugin in > > > > > > > > > > my Mac OS X 10.5.2 again. > > > > > > > > > > Still, it gave the same error when I use the > SDIFDatabaseProcessing. > > > > > > > > > > > > > > > > > > What do you mean "use"? Does SDIFDatabaseReader appears > in the > > > > > > > > > processing tree?? (else what kind of use?) > > > > > > > > > > > > > > > > > > Note that the "SDIFDatabaseReader" entry in the > processing tree (as > > > > > > > > > shown in the snapshot) corresponds to the > "SDIFDatabseProcessing" > > > > > > > > > > > > > > > > > > BTW, those comparison warnings seems totally > inoffensive. > > > > > > > > > > > > > > > > > > Pau > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Clam-devel mailing list > > > > > > > Clam-devel@llistes.projectes.lafarga.org > > > > > > > > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Clam-devel mailing list > > Clam-devel@llistes.projectes.lafarga.org > > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel > > > > _______________________________________________ > Clam-devel mailing list > Clam-devel@llistes.projectes.lafarga.org > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel > _______________________________________________ Clam-devel mailing list Clam-devel@llistes.projectes.lafarga.org https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
