[Coco] MIDI with drivewire 4

[Bill Pierce]

Cool Aaron... But to test this before I sent the previous email, I listed a very complex midi to /midi and got more errors than midi. It made a big "bang" of notes then went into "lala" land till I hit break. I got quite a few "Unsupported Midi" messages on the DW console as well as a long list of 

Thu Oct 04 2012 01:46:58.087  WARN   DWVSerialPort       dwproto-0-11        MIDI: Invalid status byte: 0
Thu Oct 04 2012 01:46:58.091  WARN   DWVSerialPort       dwproto-0-11        MIDI: data2 out of range: 255

If I leave it alone, it hangs for a bit in silence, till the Coco ends with ERROR 244.
This file is valid as I play it with the midi player quite a bit.

So I guess my file was a little too complex and most likely chock full of sysex messages

Bill P

Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Bill Pierce
ooogalapasooo at aol.com




-----Original Message-----
From: Aaron Wolfe <aawolfe at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, Oct 4, 2012 1:42 am
Subject: Re: [Coco] MIDI with drivewire 4


On Thu, Oct 4, 2012 at 12:35 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> Gene,
>  In theory, that should work, but in reality it's a midi disaster. A midi file 
has no "clock" so therefore it will just "blast" the DW drive with data as fast 
as list can send it. There has to be software to send the bytes at proper 
intervals for it to be "musical". All midi timing is the job of the sender, the 
reciever just "plays it as it sees it" That's why there was so many requests for 
a "Standard Midi" player back in the old days.
>  I actually have one I'm going to release soon. Mike Knudson started it back 
in the 90s but it's a memory hog and needs to be tamed to play properly. A 
modified version of it is included with the latest release of Sound Chaser. It 
just stops loading tracks when memory is full and plays what it has. If the 
first track is too big for memory, it aborts.
>

Actually, with DW it will work to just dump a standard gm file to a /N
device, because DW notices its a gm file and sends it to the
sequencers rather than throwing it at the synth or output.  That's
probably what Gene was referring to.  However, that is also a dirty
hack and only exists because I wanted a simple way to test parts of
the MIDI system in the server :)  The feature may go away in some
future version, you really should do the sequencing on the coco side
like it was a normal midi port.

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco