Slashdot thread on Sound, Flash etc Highlights a Focus need

2009-07-10 Thread brian mullan
A recent Slashdot thread had resonance with my own work in promoting use of Linux in a very large educational project and problems I'm facing. http://linux.slashdot.org/story/09/06/19/1937210/State-of-Sound-Development-On-Linux-Not-So-Sorry-After-All Quite a fe

Possible problems in your Debian packages

2009-07-10 Thread DDPOMail robot
This is an automated mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === aeolus: = Lintian reports 2 error(s) and 3 warning(s), you should consider fixing them. See http://lintian.debian.org/maintainer/deb

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Adrian Knoth
On Fri, Jul 10, 2009 at 05:43:18PM +0100, Daniel James wrote: > Hi Adrian, Hi! >> Are you sure your jack2 package is in good shape? ;) > I just did a source build of 1.9.2 in /usr/local using waf, it works > fine for Hydrogen, but neither amsynth or mx44 packages work. Did you > build your a

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Daniel James
Hi Adrian, Are you sure your jack2 package is in good shape? ;) I just did a source build of 1.9.2 in /usr/local using waf, it works fine for Hydrogen, but neither amsynth or mx44 packages work. Did you build your amsynth and mx44 from source? Cheers! Daniel -- To UNSUBSCRIBE, email to

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Daniel James
Hi Adrian, No problems over here with plain jack2-1.9.2. Works out of the box. Same is true for amsynth: works like a charm with jack2. Are you sure your jack2 package is in good shape? ;) Possibly an update to 1.9.2 would fix this, perhaps upstream have put in some backwards compatibility o

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Adrian Knoth
On Fri, Jul 10, 2009 at 01:49:58PM +0100, Daniel James wrote: > Hi Adrian, Hi! >> int >> JackOutput::process (jack_nframes_t nframes) >> [..] >> - return 0; >> + return 1; > > If that's all it needs, that would be awesome! Thanks :-) Sorry, it's exactly the other way round: retur

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Reinhard Tartler
Daniel James writes: >>> # ldconfig -p | grep jack >>> libjackserver.so.0 (libc6,x86-64) => /usr/lib/libjackserver.so.0 >>> libjack.so.0 (libc6,x86-64) => /usr/lib/libjack.so.0 >>> libjack.so.0 (libc6) => /usr/lib32/libjack.so.0 >>> libjack.so (libc6) => /usr/lib32/libjack.so >> >

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Daniel James
Hi Adrian, Cannot connect ports owned by inactive clients: "amSynth" is not active This is simple to fix. The process callback return value was ignored in jack1, so everybody returned 0. In jack2, returning 0 means "problems", so you just return 1 (true) and everything is fine. The patch I se

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Adrian Knoth
On Fri, Jul 10, 2009 at 10:00:54AM +0100, Daniel James wrote: >>> # ldconfig -p | grep jack >>> libjackserver.so.0 (libc6,x86-64) => /usr/lib/libjackserver.so.0 >>> libjack.so.0 (libc6,x86-64) => /usr/lib/libjack.so.0 >>> libjack.so.0 (libc6) => /usr/lib32/libjack.so.0 >>> libjack.

Re: Bug#536061: amsynth: failed to initialise JACK... aborting

2009-07-10 Thread Daniel James
Hi Reinhard, # ldconfig -p | grep jack libjackserver.so.0 (libc6,x86-64) => /usr/lib/libjackserver.so.0 libjack.so.0 (libc6,x86-64) => /usr/lib/libjack.so.0 libjack.so.0 (libc6) => /usr/lib32/libjack.so.0 libjack.so (libc6) => /usr/lib32/libjack.so this looks pr