From: Colin Fletcher <colinf@axicon.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: UA-1000 MIDI control port (was - Re: [linux-usb-devel] [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface)
Date: Fri, 08 Jul 2005 17:37:49 +0100 [thread overview]
Message-ID: <42CEABDD.60700@axicon.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0507071305230.21603-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> Do you (or the manual) know what the control port is good for?
No, I was wondering that myself. I assume it's for controlling the
internal patchbay, monitoring and so forth by sending it magic SysExes,
but there's no mention of how to do this in the Owner's Manual.
I posted a message on the edirol.co.uk web site asking if they can send
me some documentation: if they come back with anything useful I'll let
you know.
Colin Fletcher
--
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
prev parent reply other threads:[~2005-07-08 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050623024635.5b873305.akpm@osdl.org>
2005-06-23 11:45 ` [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface Clemens Ladisch
2005-06-24 9:35 ` [linux-usb-devel] " Colin Fletcher
2005-06-24 10:28 ` Clemens Ladisch
2005-06-24 13:39 ` [alsa-devel] " Colin Fletcher
2005-06-27 15:05 ` [linux-usb-devel] " Clemens Ladisch
2005-06-27 21:32 ` [alsa-devel] " Colin Fletcher
2005-06-28 2:03 ` david-b
2005-06-28 2:30 ` Lee Revell
2005-06-28 3:31 ` [linux-usb-devel] " david-b
2005-06-28 4:10 ` [alsa-devel] " Lee Revell
2005-06-28 10:19 ` Colin Fletcher
2005-06-28 13:39 ` Clemens Ladisch
2005-06-28 6:56 ` Clemens Ladisch
2005-06-28 10:23 ` Colin Fletcher
2005-07-06 18:24 ` [linux-usb-devel] " Colin Fletcher
2005-07-07 11:07 ` Clemens Ladisch
2005-07-08 16:37 ` Colin Fletcher [this message]
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=42CEABDD.60700@axicon.com \
--to=colinf@axicon.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.