[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#491963: jackd: Apps cannot access alsa MIDI ports, will not play MIDI events.



Package: jackd
Version: 0.109.2-3
Severity: important

First noticed this with qsynth. This will run very nicely with alsa. If
jackd is running, qsynth reported it cannot attach to any MIDI input port
(alsa-seq). No connection shows on the qjackctl connection pane and
trying to make the connection in there  has no effect and
repeated attempts can cause hangup.

This is apparently not a qsynth problem. Muse without jack so no audio can
handle MIDI in and out just fine. Muse with jack and audio cannot play MIDI
events to the MIDI out port chosen. No connection shows on the qjackctl pane
and attempts to make the connection there behave like the qsynth did.

These apps do not use jack-midi.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25.8-rt7-davidb (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages jackd depends on:
ii  libc6                         2.7-12     GNU C Library: Shared libraries
ii  libjack0                      0.109.2-3  JACK Audio Connection Kit (librari
ii  libreadline5                  5.2-3      GNU readline and history libraries
ii  libsndfile1                   1.0.17-4   Library for reading/writing audio 

Versions of packages jackd recommends:
ii  libpam-modules                0.79-4     Pluggable Authentication Modules f
ii  qjackctl                      0.3.3-1    JACK Audio Connection Kit Qt GUI I

Versions of packages jackd suggests:
ii  jack-tools                    0.0.2-5    various JACK tools: plumbing, play
ii  libjackasyn0                  0.11-2     The Asynchrounous JACK Library
pn  meterbridge                   <none>     (no description available)

-- no debconf information



Reply to: