From: "Clemens Ladisch" <clemens@ladisch.de>
To: "David Griffith" <dgriffi@cs.csubak.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MOTU Fastlane USB MIDI interface
Date: Mon, 20 Aug 2007 08:37:22 +0200 [thread overview]
Message-ID: <1187591842.11769.1206227263@webmail.messagingengine.com> (raw)
In-Reply-To: <Pine.GSO.4.55.0708170202270.26403@helios.cs.csubak.edu>
David Griffith wrote:
> On Fri, 17 Aug 2007, Clemens Ladisch wrote:
> > David Griffith wrote:
> > > On Thu, 16 Aug 2007, Clemens Ladisch wrote:
> > > > Please try "amidi -d -p virtual" and playing a .mid file to this port with
> > > > aplaymidi.
> > >
> > > $ aplaymidi -p "virtual" castle2.mid
> > > Invalid port virtual - No such file or directory
> >
> > Sorry, the name of the correspondig sequencer port is different,
> > probably "128:0"; see the output of "aplaymidi -l".
>
> $ aplaymidi -l
> Port Client name Port name
> 14:0 Midi Through Midi Through Port-0
> 16:0 Ensoniq AudioPCI ES1371
> 20:0 Fastlane Fastlane MIDI A
> 20:1 Fastlane Fastlane MIDI B
>
> $ aplaymidi -p 20:0 casablan.mid
>
> Nothing is written to the Fastlane. No lights. Nothing.
Please run "amidi -d -p virtual" and then play to the virtual port
created by amidi, to see if MIDI playback works even without hardware.
Regards,
Clemens
next prev parent reply other threads:[~2007-08-20 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 9:42 MOTU Fastlane USB MIDI interface David Griffith
2007-08-16 7:37 ` Clemens Ladisch
2007-08-16 10:16 ` David Griffith
2007-08-16 15:45 ` Clemens Ladisch
2007-08-16 21:18 ` David Griffith
2007-08-17 6:17 ` Clemens Ladisch
2007-08-20 0:23 ` David Griffith
2007-08-20 6:37 ` Clemens Ladisch [this message]
2007-08-20 7:45 ` David Griffith
2007-08-20 8:11 ` MIDI-related oops (was MOTU Fastlane USB MIDI interface) David Griffith
2007-08-24 15:02 ` MOTU Fastlane USB MIDI interface Clemens Ladisch
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=1187591842.11769.1206227263@webmail.messagingengine.com \
--to=clemens@ladisch.de \
--cc=dgriffi@cs.csubak.edu \
--cc=linux-kernel@vger.kernel.org \
/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