[gmpi] Re: 3.15 MIDI
- From: "Jeff McClintock" <jeffmcc@xxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Thu, 17 Jun 2004 11:34:46 +1200
>> the more it seems
> > impossible... to have one GMPI message per MIDI message without losing
> > MIDI stream byte-exactness.
> If you convert MIDI to GMPI then back to MIDI, the converter may use
> running status when the original stream did not (or vica versa).
Therefore
> is is not exactly the original byte stream.
Now that I think about it, The Windows mutimedia API discards running
status, before my application sees it. So does the VST API.
Running status isn't important.
Jeff
----- Original Message -----
From: "Jeff McClintock" <jeffmcc@xxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Thursday, June 17, 2004 11:06 AM
Subject: [gmpi] Re: 3.15 MIDI
> OK, That's an interesting point.
>
> If you convert MIDI to GMPI then back to MIDI, the converter may use
> running status when the original stream did not (or vica versa).
Therefore
> is is not exactly the original byte stream.
>
> Hmm...
>
> Both streams represent the same performance, both will 'render' the same
> music.
>
> Is that a genuine problem, I don't know....
>
> Jeff
>
> ----- Original Message -----
> From: "Chris Grigg" <gmpi-public@xxxxxxxxxxxxxx>
> To: <gmpi@xxxxxxxxxxxxx>
> Sent: Thursday, June 17, 2004 10:41 AM
> Subject: [gmpi] Re: 3.15 MIDI
>
>
> > 1. OK, in this model how would the following be handled?:
> >
> > - Sys ex
> > - MIDI out from plugs
> > - GMPI/MIDI transcoding side effects including:
> > > Message execution time shifts
> > > Running Status handling
> > > (N)RPN parameter number tracking
> >
> > 2. On that last category,the more I think about it, the more it seems
> > impossible, or at least it that it would be somewhat to very
> > complicated, to have one GMPI message per MIDI message without losing
> > MIDI stream byte-exactness.
> >
> > Consider running status, for example in the context of an ordinary
> > 7-bit controller message. MIDI device sends a full 2-byte
> > status+data message, waits a minute, then sends another controller
> > message but this time it's a 1-byte message, relying on running
> > status to imply/repeat/insert the previous status byte. The host
> > turns the first MIDI msg into a GMPI set-parameter message, the plug
> > converts it back to MIDI, and sees a 2-byte msg; so far, so good.
> > Then the plug gets a second GMPI message corresponding to the 2nd
> > MIDI message, converts it back to MIDI... but now you've got another
> > 2-byte message instead of a 1-byte message. MIDI received at the
> > plug not exact with MIDI received at the host.
> >
>
>
>
> ----------------------------------------------------------------------
> Generalized Music Plugin Interface (GMPI) public discussion list
> Participation in this list is contingent upon your abiding by the
> following rules: Please stay on topic. You are responsible for your own
> words. Please respect your fellow subscribers. Please do not
> redistribute anyone else's words without their permission.
>
> Archive: //www.freelists.org/archives/gmpi
> Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
>
>
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
