Re: [Bluemusic-users] Blue 2.5.1
Brought to you by:
kunstmusik
From: Steven Yi <ste...@gm...> - 2013-08-20 22:29:29
|
Hi Menno, For #1, I just tried here on OSX and got a crash. The crash report though doesn't seem to help much as it shows all native code calls in the stack of the thread that crashed. However, the issue is tricky. If I start a jack server (i.e. "jackd -d coreaudio") then blue will not crash if I try multiple times. If I do not jack already started, then I think Csound tries to launch one and in that case, I am getting crashes. Do you have jack server already started and running when you try this in Blue? I'm wondering if the behavior is different on OSX than it is on Linux. As for #2, unfortunately something like is not possible. I agree that some kind of configuration dialog would be great, but the problem is that lib_jcsound6.so is a native library. This pretty much needs to be loaded and known about during Blue's startup. The worst case scenario is one version of the library is loaded, and then another version is tried to load. This could cause library functions with the same names but from different libraries to be in the same loader and then things go haywire and usually ends in a crash. This is also the reason I had to go with either loading CS5 API or CS6 API, but not both, as it would cause crashes. A solution might be for me to release a 3rd release artifact for Linux, one that has some sensible default paths setup (i.e. /usr/lib/jni, /usr/local/lib/, etc.). I can't set that as it is now as the same conf file gets used if running on Windows from that zip build. I'd love to see if there are easier solutions. If you would, file a feature request for having Blue pre-setup for Linux paths for loading Csound API. I'll look at it for one of the next few releases. Thanks! steven On Tue, Aug 20, 2013 at 1:56 PM, menno <nab...@ya...> wrote: > Hi Steven, > > nearly there! The jack output is found, also the Portmidi midi and out. But > it crashes when i push the button to find the Jack In. I have tried with > Blue running in terminal AND doubleclick. Same result: crash, and no errors > are shown. > > Just an idea: when one opens Blue for the first time and one wants to make > Blue ready for use with the Csound6 API, perhaps a window could open that > lets you point to lib_jcsound6.so - or, perhaps, even better, in the Options > menu? > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Blue-2-5-1-tp5726896p5726926.html > Sent from the Csound - Blue - User mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users |