From: "Sean M. Pappalardo - D.J. Pegasus" <spappalardo@mixxx.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net
Subject: Re: Help requested: new HSS1394 MIDI back-end
Date: Fri, 01 Jun 2012 00:04:49 +0200 [thread overview]
Message-ID: <4FC7EB01.1070306@mixxx.org> (raw)
In-Reply-To: <4FC5C9C8.1000604@ladisch.de>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
On 05/30/2012 09:18 AM, Clemens Ladisch wrote:
> As it happens, the actual SysEx commands use the wrong manufacturer ID
> ("00 01 02" is Crystal Semiconductor); I could just use the real ID
> (Stanton is "00 01 60") to escape non-MIDI HSS1394 messages. Let's add
> "HSS" to identify this, and to allow the full byte range, each HSS1394
> byte is split into two nibbles.
That all sounds good, but that now means that applications that want to
use these device features must have different code for Linux than they
do for Windows or OSX. In the case of Mixxx, that also means a different
controller preset. But I guess that's not the end of the world if it's a
choice between this and no support at all.
Sigh...
Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4545 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-05-31 22:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94aa86f3-5257-402a-a094-f58fccdeb846@email.android.com>
2012-05-30 4:51 ` Help requested: new HSS1394 MIDI back-end Clemens Ladisch
2012-05-30 5:12 ` [alsa-devel] " Sean M. Pappalardo - D.J. Pegasus
2012-05-30 7:18 ` Clemens Ladisch
2012-05-31 20:00 ` Clemens Ladisch
2012-06-09 6:54 ` Sean M. Pappalardo - D.J. Pegasus
2012-06-09 11:07 ` Clemens Ladisch
2012-06-09 12:41 ` Sean M. Pappalardo - D.J. Pegasus
2012-06-10 13:00 ` Clemens Ladisch
2012-10-24 11:49 ` Sean M. Pappalardo - D.J. Pegasus
2012-10-25 19:23 ` Clemens Ladisch
2012-10-25 20:26 ` Sean M. Pappalardo - D.J. Pegasus
2012-10-26 7:48 ` Clemens Ladisch
2012-10-31 10:00 ` Sean M. Pappalardo - D.J. Pegasus
2012-11-11 21:34 ` [git pull] " Clemens Ladisch
2012-11-09 6:41 ` Help requested: " Sean M. Pappalardo - D.J. Pegasus
2012-11-12 9:45 ` Takashi Iwai
2012-11-12 11:33 ` Clemens Ladisch
2012-11-12 11:40 ` Takashi Iwai
2012-11-12 11:45 ` [alsa-devel] " Clemens Ladisch
2012-11-12 14:26 ` Takashi Iwai
2012-06-09 8:42 ` Sean M. Pappalardo - D.J. Pegasus
2012-06-09 10:12 ` Sean M. Pappalardo - D.J. Pegasus
2012-05-31 22:04 ` Sean M. Pappalardo - D.J. Pegasus [this message]
2012-06-01 8:22 ` Clemens Ladisch
2012-06-01 13:40 ` [alsa-devel] " Stefan Richter
[not found] <mailman.786.1339244201.2490.alsa-devel@alsa-project.org>
2012-06-09 12:56 ` Jonathan Woithe
2012-05-25 19:43 Sean M. Pappalardo - D.J. Pegasus
2012-05-27 13:50 ` Clemens Ladisch
2012-05-27 20:59 ` Sean M. Pappalardo - D.J. Pegasus
2012-05-28 14:58 ` Clemens Ladisch
2012-05-28 20:40 ` Sean M. Pappalardo - D.J. Pegasus
2012-05-29 17:05 ` Clemens Ladisch
2012-05-29 21:52 ` Sean M. Pappalardo - D.J. Pegasus
2012-07-24 11:44 ` Clemens Ladisch
2012-08-01 17:16 ` Sean M. Pappalardo - D.J. Pegasus
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=4FC7EB01.1070306@mixxx.org \
--to=spappalardo@mixxx.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=linux1394-devel@lists.sourceforge.net \
/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.