| Title: | * * Computer Music, MIDI, and Related Topics * * |
| Notice: | Conference has been write-locked. Use new version. |
| Moderator: | DYPSS1::SCHAFER |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 29 1994 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2852 |
| Total number of notes: | 33157 |
Anybody have any experience with the Yamaha MIDI Control Station
(MCS2)? It's purpose is to add additional "controllers" (pitch bend,
modulation, aftertouch, breath, etc.) to controller keyboards that
don't have those features -- like my Clavinova. The TX81Z has some
voices that use the breath controller, and I'd like to take advantage
of them; also, I'd like to be able to adjust volume, and send program
change instructions in performance situations.
As an alternative, I'm thinking about a computer interface with some
home-brew controls (pots and pedals and buttons and stuff) tacked on.
That leads me to a question about MIDI-merge theory...
When you have two controllers talking at once (in this case, a computer
and a keyboard), what sort of arbitration algorithms get used? My MIDI
terminology is a bit weak, but suppose for example that one controller
was in "running" mode -- sending data bytes, but no command bytes; and
then the other controller sends a different command; won't subsequent
data bytes from the first controller be mis-interpreted as "running"
mode data from the second controller?
Are there any limitations imposed by the use of a MIDI-merge? (Any
stuff you're not allowed to send from either controller, for example?)
I may not even be asking the right questions here, so any insights
that might clear up my confuddlement would be most welcome!
Thanks,
Kevin C.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1842.1 | If you find one, LET ME KNOW! | NRPUR::DEATON | Fri Jan 06 1989 15:37 | 33 | |
Hi Kevin, I have owned both a MIDI merge and the MCS2. First of all, I'll speculate about the way it works. I'd guess that there is some kind of a data buffer that stores ands spits out messages in proper protocol. The only messages that I'm SURE of that can't be merged like this are clock messages (like from a sequencer and a drum box at the same time). Now there seems to be on all mergers some allowance for a possible 'overflow'. Some mergers will 'lock up' and not send any data when this happens. The MCS2 and the Yamaha merge box will do this. Others will cause stuck notes. Most often, they will provide some kind of 'panic button' to send 'all notes off'. I would have really liked to keep the MCS2 box, but it seems that all it would do was lock up on me. Unacceptable. I had to return it. The Yamaha merge box did the same thing. I had to bring that back as well. The problem was even more confounding when the units went into overflow mode EVEN WHEN THERE WAS NO DATA GOING INTO THEM! Or, they would lock up when only one keyboard was plugged into it (and I'm no wonder-fingers!) I've begun to wonder if the power lines going into my studio were bad (?). So, before you write out a check on one of these units, try it out with your equipment - or get a guaranty that you can return it if the same thing happens to you. Just a word to the wise... If all you want is a merge box, the only one that seems to get rave reviews everywhere is the MX-8. It'll sink you in the excess of $300, though. I would personally love to find any other box that will do JUST merge and do it reliably! Dan | |||||