Sorry for the delayed response.
Jack messages output, from hydrogen startup till after I've clicked away all
the dialogs (sorry to digest subscribers!) -
----
p, li { white-space: pre-wrap; } 15:24:58.242 Statistics reset.
15:25:02.557 JACK connection graph change.
15:25:02.597 JACK connection change.
15:25:02.619 JACK connection graph change.
15:25:02.655 ALSA connection graph change.
Unknown destination port in attempted (dis)connection src_name
[Hydrogen:out_L] dst_name [alsa_pcm:playback_1]
port created: Hydrogen [130] (playback): Hydrogen Midi-In
port created: Hydrogen [130] (capture): Hydrogen Midi-Out
15:25:02.800 JACK connection change.
15:25:02.804 ALSA connection change.
JackEngine::XRun: client = Hydrogen was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
15:25:03.028 XRUN callback (1).
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
15:25:06.256 JACK connection graph change.
15:25:06.433 JACK connection change.
15:25:06.441 JACK connection graph change.
15:25:06.641 JACK connection change.
15:25:06.651 JACK connection graph change.
15:25:06.860 JACK connection change.
15:25:06.872 JACK connection graph change.
15:25:07.089 JACK connection change.
15:25:07.106 JACK connection graph change.
15:25:07.329 JACK connection change.
15:25:07.352 JACK connection graph change.
15:25:07.571 JACK connection change.
15:25:07.587 JACK connection graph change.
15:25:07.823 JACK connection change.
15:25:07.827 JACK connection graph change.
15:25:08.048 JACK connection change.
JackEngine::XRun: client = Hydrogen was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
15:25:20.788 XRUN callback (2).
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
----
My jackd call from jack control looks like this -
/usr/bin/jackd -p128 -t5000 -dalsa -r48000 -p128 -n2 -S -D -Chw:Audiophile192
-Phw:Audiophile192
So the port-max isn't being set - could I be exceeding whatever the default is?
The kit has 64 multi-layered instruments.
The drumkit is downloaded from the official server, "MC-307_TR-606". Here is
the song file, excuse the bad patterns - luckily the track has evolved beyond
these now!
https://mega.co.nz/#!icIEHRjR!gjruGN_BrZBiq1kCdsXGtU-QxmRhS0xhh5f8lH2wj_g
Thanks for the help
Oliver
Message: 4
Date: Fri, 08 Aug 2014 12:44:47 +0200
From: Sebastian Moors <mau...@smoors.de>
Subject: Re: [Hydrogen-devel] Annoying dialog box
To: hydrogen-devel@lists.sourceforge.net
Message-ID: <53e4aa1f.8060...@smoors.de>
Content-Type: text/plain; charset="iso-8859-1"
Hi Oli,
there is no fixed limit of instruments in hydrogen. Your error is caused
by "jack_port_register", not hydrogen itself. The method belongs to the
jack api and fails to register a new port.
So at the moment i see two possible reasons for this behaviour:
1. Hydrogen provides the call to "jack_port_register" with
wrong/malformed data
2. "jack_port_register" fails because of some reason on your side, maybe
not enough (shared) memory to create a new buffer for the port. But i'm
not familiar enough with jack to help you there.. What you can try is to
have a look at the jack log files (or the messages window from qjackctl)
to see if there is some obvious error.
Btw., is someone else able to reproduce this problem?
@Oli: Maybe you could provide us a song file where this happens (with
some drumkits from the official repository)?
Best regards,
Sebastian
Message: 5
Date: Fri, 8 Aug 2014 11:47:59 +0100
From: Harry van Haaren <harryhaa...@gmail.com>
Subject: Re: [Hydrogen-devel] Annoying dialog box
To: hydrogen-devel@lists.sourceforge.net
Message-ID:
<CAKudYbMeO09tfK_NOn0jnczUASLi5Z6cah3pps8xeiyJcO=c...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Jack has a maximum port variable, see jackd -h or set with jackd
--port-max
That's generally the cause of port-registration failures. I think having
two ports with identical names might cause port_register() to fail too.
HTH, -Harry
------------------------------------------------------------------------------
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
