30 Aug
2008
30 Aug
'08
6 p.m.
First thought it was a qsynth problem but it his everything, across the board!
I fire up a program, qsynth, qtractor, etc. I simply cannot connect (in
qjackctl or qtractor's or qsynth's connection pane) to a MIDI output device.
Repeated tries will eventually crash out.
Qsynth will run OK with jack not running (latency not all that bad, either!).
Qtractor would not connect, even without jack running, but the first try with
jack might has locked out further tries.
The MIDI will connect up fine "locally" with no such program running, i.e., I
can connect the keyboard to an output device and play it.
I have no .asoundrc or conf file. Any help appreciated because I am eager to
try the new qtractor!
30 Aug
30 Aug
6:35 p.m.
Hello David!
Did you try starting just fluidsynth like this:
fluidsynth -a jack -j [-r samplerate] soundfont_file
aconnect soundcard-port fluid-port
i.e.
aconnect 16 128 or 20 128
try:
aconnect -li
and
aconnect -lo
for port lists.
Did you update your kernel/JACK lately?
uname -r
will show the kernel version, if you're unsure.
If you got all packages from your distro try to update kernel and JACKD
again.
If you build your jack and/or kernel yourself, rebuild both.
If the fluidsynth fails. Try this:
fluidsynth -a jack [-r samplerate] soundfont_file
Now you have to connect the jack-ports as well. Do it like this:
jack_connect fluidsynth:left system:playback_1
jack_connect fluidsynth:right system:playback_2
Does this work? See the jack-output. If your system starts jack
automatically look at your "kernel console" TTY10 (ctrl+alt+F10). If you start
JACK yourself look at the terminal/window, where you started jack for error
messages.
How about your QTractor? Did you build this one yourself. Try to rebuild as
well and don't use qjackctl for connecting but use aconnect and jack_connect
as well. Look for error messages in the shell, where you ran
aconnect/jack_connect, then again check TTY10.
If this works, have a look at qjackctl. The old rebuild or update advice
applies as well.
If all that fails, I'm out of it.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
8:02 p.m.
David Baron wrote:
First thought it was a qsynth problem but it his
everything, across the board!
I fire up a program, qsynth, qtractor, etc. I simply cannot connect (in
qjackctl or qtractor's or qsynth's connection pane) to a MIDI output device.
Repeated tries will eventually crash out.
Qsynth will run OK with jack not running (latency not all that bad, either!).
Qtractor would not connect, even without jack running, but the first try with
jack might has locked out further tries.
The MIDI will connect up fine "locally" with no such program running, i.e., I
can connect the keyboard to an output device and play it.
I have no .asoundrc or conf file. Any help appreciated because I am eager to
try the new qtractor!
awe. you seem to have a strange problem with (all) my apps and midi
(alsa-seq) stuff i presume?
complete details about your setup might help, specially everything
regarding the kernel, dmesg, modprobe.conf, lsmod output, limits.conf,
root or a regular user, whether you're trying to run any of the jackd
midi backends, anything...
did you try with aconnect?
seeya
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
5983
days inactive
5983
days old
linux-audio-user@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
David Baron -
Julien Claassen -
Rui Nuno Capela