Author |
Topic: Running Status questions (Read 2247 times) |
|
Old Forum
New Member
Posts: 2
|
 |
Running Status questions
« on: Aug 17th, 2001, 11:56am » |
 Quote  Modify
|
This was posted in the old forum
From: Mats Andreasen
Date: 13 Aug 2001
Time: 01:49:38
Comments
As far as I understand, MIDI-OX handles Running Status in the following manners: 1. It can be configured to send Running Status. 2. When receiving R.S the last status byte can be showed.
But, when I configure MIDI-OX to send R.S, and then check with my receiving unit, Note on/off and all other messages are sent as normal. It does not seem to send them as R.S.?
And, when I try to show received R.S messages, a status line is written in the Monitor Output window. Not the In window as I expected. However, messages received are echoed to the output, so maybe that's the reason? But I think it should be more useful if recieved R.S messages was displayed as received, ie the status hex byte omitted in the Input monitor window, maybe with a plain text explanation at the end of the line.
Best regards.
|
| « Last Edit: Sep 10th, 2001, 9:17am by admin » |
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
 |
Re: Running Status questions
« Reply #1 on: Aug 17th, 2001, 12:00pm » |
Quote Modify
|
Under Windows, Running Status is something of a Red Herring. This is because, although an application is permitted to output data in Running Status form, the data must be first processed by a driver before being output from a MIDI interface. Multi-client drivers must merge data arriving at their 'outputs' (i.e. the input of the output port), so they will typically add the Status Byte before outputing the data to the interface. Furthermore, Running Status doesn't buy you much under Windows because each 'short message' is always passed as a series of 4 bytes stuffed into a DWORD, even if Running Status is enabled.
Under Windows, all input drivers must add the Status Byte before supplying the data to a client Application (this is a fixed rule). This means that if you are using MIDI Yoke to transfer data from one application to another (or one MIDI-OX instance to another), even if you supply Running Status enabled data to a MIDI Yoke Output port, MIDI Yoke must re-add the Status Byte to the data before outputing it (via the MIDI Yoke input port) to the next application.
In summary, MIDI-OX will never see Running Status enabled data at any of its inputs. If it enables and send Running Status enabled data, the output driver will likely re-add the status. Of course an output driver that communicates with a hardware interface may enable Running Status on its own, but this is up to the driver.
|
| « Last Edit: Sep 10th, 2001, 9:17am by admin » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print