From: Dave Phillips <dlphillips@woh.rr.com>
To: x.zupftom@web.de
Cc: linux-msdos@vger.kernel.org
Subject: Re: MIDI input
Date: Thu, 19 Jun 2008 08:11:20 -0400 [thread overview]
Message-ID: <485A4CE8.5070301@woh.rr.com> (raw)
In-Reply-To: <172036971@web.de>
x.zupftom@web.de wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: "Dave Phillips" <dlphillips@woh.rr.com>
>> I believe that SPG filters running status bytes, perhaps Score doesn't ?
>>
>
> Sorry, but what does filtering status bytes mean? Can it possibly be done before feeding the MIDI input to Score?
>
Running Status is a MIDI message, usually encountered in long strings of
messages with the same status. According to the MIDI Programmer's
Handbook, "It is the receiver's responsibility to identify and process
Running Status transmissions."
The more I consider the problem, the more I think it may have something
to do with Active Sensing bytes. An Active Sensing byte (hex FE) is sent
every 300 ms if an instrument is idle, perhaps the message timing in
your examples should be checked for their incidence ?
>
>> How do you
>> configure Score for MIDI input, do you select a driver or does it have a
>> default internal driver or ... ?
>>
>>
>
> It must have an internal driver. There are three configuration options: The type of MIDI interface (you can chose between None, MPU-401 or compatible, Passport MIDI-Transport, IBM Music Feature and Yamaha C1), the IRQ level and the port address.
>
DOSemu is likely to support only the MPU driver. Is that what you're using ?
Best,
dp
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-19 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 22:41 MIDI input x.zupftom
2008-06-19 12:11 ` Dave Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-12 13:38 x.zupftom
2008-06-18 20:47 x.zupftom
2008-06-18 22:09 ` Dave Phillips
2008-06-18 13:09 x.zupftom
2008-06-18 13:37 ` Dave Phillips
2008-06-16 21:22 x.zupftom
2008-06-16 23:23 ` Dave Phillips
2008-06-15 9:42 x.zupftom
2008-06-16 16:38 ` Dave Phillips
2008-06-13 21:54 x.zupftom
2008-06-13 18:09 x.zupftom
2008-06-12 23:47 x.zupftom
2008-06-13 0:50 ` Dave Phillips
2008-06-12 22:12 x.zupftom
2008-06-12 22:57 ` Tony Borras
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=485A4CE8.5070301@woh.rr.com \
--to=dlphillips@woh.rr.com \
--cc=linux-msdos@vger.kernel.org \
--cc=x.zupftom@web.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