Author |
Topic: Midi Replicator necessary for Multi-client? (Read 1148 times) |
|
gabriel
Member
MIDI-OX Rules!
Posts: 14
|
 |
Midi Replicator necessary for Multi-client?
« on: Jul 26th, 2002, 1:13pm » |
 Quote  Modify
|
Jamie,
Thanks for your help with my last question. I have another for you.
I'm using my M-Audio 2496 as a midi input, and ran into a problem because it's drivers aren't multiclient. I solved this by buying Midi Replicator. I'm using Gigastudio with a home-brew Woodwind controller. For the record, the woodwind controller doesn't use up any of the resources of the computer running Giga and MidiOx. It's output is processed by a separate computer and then sent as midi to the synths it controls and to Gigastudio.
MidiOx helps me in some of the more intricate midi routing and processing aspects of this setup. It's hard for me to get a grasp on the problems I sometimes have in running Gigastudio, which is unstable to say the least (and this has nothing to do with MidiOx). There is the occasional crash, and sometimes, though Gigastudio is still alive (it still reacts to use of it's internal virtual keyboard), it no longer responds to midi.
When I look more carefully at what's happening, I notice that MidiOx is showing me that it's no longer receiving midi from the M-Audio 2496. In fact, sometimes it doesn't respond to input from my controller even though it spits out midi messages at regular intervals (maybe 7 or 8 seconds apart), that seem to be a very very slowed down record of what I had been doing on the controller before the breakdown occurred (not verified, but likely). When this happens, I am forced to exit MidiOx to fix the problem. This isn't so easy,however, since EVERYTHING running on my computer slows down incredibly, and it takes a half minute or more for the computer to respond to any of my keystrokes. Eventually, I can get things working again after exiting and then restarting MidiOx.
I don't have any problems like this with my hardware synths, so my controller isn't at fault. In terms of the Giga computer, I believe the problem didn't exist before I started using Midi Replicator.
So, finally, to the crux of the question. Is it possible to simplify, and somehow use MidiOx or MidiYoke to make a multiclient device out of the M-audio card. I have a feeling that it is Midi Replicator that may be causing the problem. If I simplify, and use fewer programs to achieve my goals, it might help. Yeow, I didn't think I had it in me to be so convoluted in explaining something. Sorry, but please do let me know if you have any thoughts about how I might be able to divide and conquer my problem to get more insight into it.
Gabriel
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Midi Replicator necessary for Multi-client?
« Reply #1 on: Jul 26th, 2002, 9:28pm » |
Quote Modify
|
The system may be slowing down because when GigaStudio crashes, it doesn't (can't) properly cleanup open MIDI drivers. These may be left in an active state, and need to be closed and reopened, at least, and possibly the system might need rebooting to fully re-initialize everything. It's very unfortunate that Giga is crashing on you, but I think you're not alone there.
It should be possible to use just MIDI-OX, MIDI Yoke and GigaStudio to obtain a multiclient solution. But if Giga crashes, MIDI Yoke may have the same trouble as MIDI Replicator.
I'm not familiar with how you have your system routed now, but a simple one port solution might be:
[M-Audio 2496]->[MIDI-OX]->[MIDI Yoke 1]->[GigaStudio]
|
| « Last Edit: Jul 26th, 2002, 9:29pm by Jamie OConnell » |
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