Hi Nick,
If all's well I'll put out a new release of the code in the next few
days, of course it would be very reassuring to know that what's now in
svn compiles and works on someone else's machine before doing so :-)
I just built today's SVN against a locally built JACK 1.9.2 on 64 Studio
3.
Hi Adrian,
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?
Yup.
Then I guess amsynth and mx44 will work with JACK 2 if built locally
against a compatible ve
On Sat, Jul 11, 2009 at 06:31:50PM +0100, Nick wrote:
> Hi,
Hi!
> If all's well I'll put out a new release of the code in the next few
> days, of course it would be very reassuring to know that what's now in
> svn compiles and works on someone else's machine before doing so :-)
Compiles and wor
Hi,
I've incorporated those patches (thanks!), and also made a few other
improvements to the way audio / midi devices are chosen, and errors
are handled - amsynth will now display a gtk error dialog if the
start-up fails.
If all's well I'll put out a new release of the code in the next few
days,
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
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
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
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
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
>>
>
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
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.
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
Vladimir Komendantsky 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.
Hi Adrian!
2009/7/9 Adrian Knoth :
amsynth cannot be used with jack.
>>> This cannot be true. I just tried it on two different machines
>>
>> To clarify, amsynth works with original JACK but not JACK 2, a.k.a
>> jackdmp. This is because amsynth's JACK connection code is a little
>> non-standa
On Tue, Jul 07, 2009 at 02:51:13PM +0100, Daniel James wrote:
> Hi Adrian,
Hi!
>>> amsynth cannot be used with jack.
>> This cannot be true. I just tried it on two different machines
>
> To clarify, amsynth works with original JACK but not JACK 2, a.k.a
> jackdmp. This is because amsynth's JAC
Hi Adrian,
amsynth cannot be used with jack.
This cannot be true. I just tried it on two different machines
To clarify, amsynth works with original JACK but not JACK 2, a.k.a
jackdmp. This is because amsynth's JACK connection code is a little
non-standard, and needs a rewrite to bring it u
Hi,
2009/7/7 Adrian Knoth :
> I wonder how dlopen() to libjack.so should fail if you have jackd
> installed. You also have the libjack0 package.
In fact amsynth appears to depend on libjack0. So, having libjack0
wasn't an option.
> Does libjack.so show up
> on "ldconfig -p"?
It does:
# ldconfi
On Tue, Jul 07, 2009 at 10:32:59AM +0100, Vladimir Komendantsky wrote:
Hi!
> amsynth cannot be used with jack.
This cannot be true. I just tried it on two different machines, no
problems at all:
a...@hex:~$ amsynth
amSynth 1.2.0
Copyright 2001-2006 Nick Dowell and others.
amSynth comes with AB
Package: amsynth
Version: 1.2.0-4
Severity: important
amsynth cannot be used with jack.
Configured as (MIDI: auto, Audio: auto), amsynth does not load jack
library. The console message in this case is "cannot load JACK
library". Changing configuration to (MIDI: alsa, Audio: jack) in
amsynth yield
19 matches
Mail list logo
