Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Schweer <ws@seh.de>
To: alsa-devel@lists.sourceforge.net
Cc: Martin Langer <martin-langer@gmx.de>
Subject: Re: tascam us-122 midi in does not work
Date: Wed, 16 Jun 2004 19:25:26 +0200	[thread overview]
Message-ID: <200406161925.26126.ws@seh.de> (raw)
In-Reply-To: <20040614224314.GA625@tuba.home>

On Tuesday 15 June 2004 00:43, Martin Langer wrote:
> On Sun, Jun 13, 2004 at 01:07:20PM +0200, Werner Schweer wrote:
> > Hello,
> >
> > Some strange effect occurs on my tascam us-122 audio/midi usb
> > device:
> >    After starting JACK the midi input does not work anymore. Not even
> > the midi in led on the us-122 flashes. Midi output is always fine.
> > After stopping JACK midi input still does not work. Midi input works
> > again after disconnect/reconnect the usb cable.
> > I'm using current ALSA cvs and kernel 2.6.7rc3.
> >
> > Can anyone confirm this to work on a normal system?
>
> Hmm. US122, 2.6.6 with ALSA 1.0.5 and jack works here. Another machine with
> us122 and ALSA CVS on 2.4.25rc1 is also fine.
>
> What about reconnecting midi clients without removing usb cable?

does not work either.

/Werner



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-16 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 11:07 tascam us-122 midi in does not work Werner Schweer
2004-06-14 22:43 ` Martin Langer
2004-06-16 17:25   ` Werner Schweer [this message]
2004-06-14 23:10 ` Karsten Wiese
2004-06-16 17:20   ` Werner Schweer
2004-06-18  4:09     ` Karsten Wiese
2004-06-18 18:51       ` Werner Schweer
  -- strict thread matches above, loose matches on Subject: below --
2004-06-12  9:23 Werner Schweer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406161925.26126.ws@seh.de \
    --to=ws@seh.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=martin-langer@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox