I seem to have solved this problem.
In the Settings dialogue of qjackctl I changed MIDI driver from "raw"
to "seq", and now I can connect the keyboard to tractor etc. It seems
to work, although I have not done very much with it yet.
I confess I hadn't tried messing about with this setting before
On Tue, 2016-12-27 at 17:57 +0100, Ralf Mardorf wrote:
> An example seems to work on my machine:
>
> $ amidi -l
> Dir DeviceName
> IO hw:0,0HDSPMx579bcc MIDI 1
> IO hw:3,0,0 nanoKONTROL MIDI 1
>
> $ pkill -9 jack; pkill a2j
>
> $ jackd -Xalsarawmidi -dalsa -r48000 -p256 &
An example seems to work on my machine:
$ amidi -l
Dir DeviceName
IO hw:0,0HDSPMx579bcc MIDI 1
IO hw:3,0,0 nanoKONTROL MIDI 1
$ pkill -9 jack; pkill a2j
$ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e & qjackctl
In QjackCtl's ALSA tab the device names are the sa
On Tue, 2016-12-27 at 16:20 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 15:06:03 +, David Sumbler wrote:
> >
> > As for audio related auto-starts, do you mean items in /etc/rcS.d ?
> > The only relevant item there is alsa-utils, which I assume I need.
> I'm thinking of pulseaudio, jackdb
On Tue, 27 Dec 2016 15:06:03 +, David Sumbler wrote:
>As for audio related auto-starts, do you mean items in /etc/rcS.d ?
> The only relevant item there is alsa-utils, which I assume I need.
I'm thinking of pulseaudio, jackdbus and what ever else could be
auto-started. I guess those auto-start
On Tue, 2016-12-27 at 15:01 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 13:40:15 +, David Sumbler wrote:
> >
> > david@eros:~$ killall -9 jackd a2jmidid qjackctl
> > jackd: no process found
> > a2jmidid: no process found
> > qjackctl: no process found
> This kill command doesn't terminate
On Tue, 27 Dec 2016 13:40:15 +, David Sumbler wrote:
>david@eros:~$ killall -9 jackd a2jmidid qjackctl
>jackd: no process found
>a2jmidid: no process found
>qjackctl: no process found
This kill command doesn't terminate what already might be running on
your install ;).
>ERROR: a2j_alsa_connec
On Mon, 2016-12-26 at 20:33 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 19:07:41 +, David Sumbler wrote:
> >
> > david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail
> > -50
> > [snip]
> > Mon Dec 26 17:09:43 2016: New client 'a2j' with PID 5142
> > Mon Dec 26 17:10:23 2016
On Mon, 26 Dec 2016 19:07:41 +, David Sumbler wrote:
>david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
>[snip]
>Mon Dec 26 17:09:43 2016: New client 'a2j' with PID 5142
>Mon Dec 26 17:10:23 2016: Client 'a2j' with PID 5142 is out
>Mon Dec 26 17:58:42 2016: Client 'qjackct
On Mon, 2016-12-26 at 19:26 +0100, Ralf Mardorf wrote:
> Is there anything useful in the log file?
>
> Please run
>
> grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
>
> and post the output.
Here goes - not sure that there's anything helpful there. The whole
section represents repe
On Mon, 26 Dec 2016 19:26:13 +0100, Ralf Mardorf wrote:
>Is there anything useful in the log file?
>
>Please run
>
> grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
>
>and post the output.
It might be that nothing ALSA MIDI related is part of a _jack_
log file ;).
--
ubuntu-studio-use
Is there anything useful in the log file?
Please run
grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
and post the output.
--
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-st
On Mon, 2016-12-26 at 18:32 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 17:05:08 +, David Sumbler wrote:
> >
> > On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> > >
> > > On Mon, 26 Dec 2016 15:40:00 +, David Sumbler wrote:
> > > >
> > > >
> > > > I click to connect the
On Mon, 26 Dec 2016 17:05:08 +, David Sumbler wrote:
>On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
>> On Mon, 26 Dec 2016 15:40:00 +, David Sumbler wrote:
>> >
>> > I click to connect the keyboard input (or output) to qTractor or
>> > something else, and the Messages window in
I've had a similar issue some time ago (trying to use midi in Pure Data) and my
workaround was to make the connections through Patchage. It just worked, don't
ask me why, and I've given it no thought ever since. But I think it would be
nice to post the output and see if there is anything to be f
On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 15:40:00 +, David Sumbler wrote:
> >
> > I click to connect the keyboard input (or output) to qTractor or
> > something else, and the Messages window in qJackCtl shows an ALSA
> > connection change.
> >
> > But no ch
On Mon, 26 Dec 2016 15:40:00 +, David Sumbler wrote:
>I click to connect the keyboard input (or output) to qTractor or
>something else, and the Messages window in qJackCtl shows an ALSA
>connection change.
>
>But no change is shown in the Connections window, and it seems that the
>connection is
It's a few months since I used my midi keyboard with the computer. I
want to get back to that project now, hence my email earlier today.
But now I have a bigger problem: I can't connect the keyboard to
qTractor (or anything else), although I had all of this working before.
In qJackCtl the keyboa
18 matches
Mail list logo
