Midi Yoke Drivers For Mac
Brie Hoffler
My SC-8820 has dead MIDI ports so I am thinking about a software signal reroute. Is it possible, using MIDIOX and MIDI Yoke, to redirect MIDI signals from the soundcard's gameport to the SC-8820 that is connected to the computer via USB cable?
My SC-8820 has dead MIDI ports so I am thinking about a software signal reroute. Is it possible, using MIDIOX and MIDI Yoke, to redirect MIDI signals from the soundcard's gameport to an the SC-8820 that is connected to the computer via USB cable?
Are you sure that the SC-8820 'computer' switch is set to MIDI and that a Win98 MIDI application can send MIDI data the Win98 MIDI redirector when it is pointed to the Roland SC-8820 driver provided "SC-8820 synth part A"? IF the physical DIN-5 MIDI ports are "broken", then try the USB port connection method (and switching the 'computer' switch to USB) to see if any Windows MIDI program can produce MIDI output.
Unlike Win2K and WinXP which can redirect the MIDI I/O ports at 0x330 for the NTVDM DOS emulation, Win98 itself does not not hook the MIDI I/O ports at 0x330 for its DOS 'emulation' mode via a system VxD. In its Win98 VxD SoundBlaster drivers for 16-bit ISA sound-cards, Creative did hook the MIDI I/O ports at 0x330 (or 0x300) to allow MIDI data redirection/conversion to the E-mu 8000 I/O ports for the AWE32/64 E-mu 8000 based engine for the Win98 DOS mode, or it allowed direct MIDI I/O AWE32/64 game port pass-thru (buggy) to an external MIDI device.
If your sound-card is a Creative SB32/AWE32/AWE64 with the correct drivers and the AWE32 Control Panel applet then DOS mode MIDI I/O port re-direction is possible. Otherwise, you are dependent on another ISA sound-card's driver support for MIDI I/O port re-direction for the Win98 DOS 'emulation' mode. Of course, if your SC-8820 MIDI ports are truly hosed, then you are out of luck.
Using the USB connection method, the module plays midi files fine with Winamp or any other player.
There is no MIDI sound output under pure DOS with any of these cards (they should work, according to other people on this forum): Vortex 2, SB Live, AudioPCI
So only the DIN IN and OUT are fried. (Well, possibly the serial PC/MAC, too. But that is not important for me.)
the unit I own probably has multiple defects then. It should work on USB power under Windows, but regardless of the switch position, none of the computers I tried with detects it until I plugin in the 9V adapter as well. So it needs more juice than a standard US 2.0 hub can provide.
USB is only rated to provide 5v at 500ma, so I'm surprised it works at all actually. Do you have any other MIDI devices that you could use to chain their output to the 8820 input? Perhaps try to get hold of a cheap USB to MIDI port to see if the MIDI DIN ports are really toast or not.
If it helps any, I have an SC-8820 as well, and it works fine here when connected USB-only, including the MIDI out (to which i've connected an sc-55).
However, I remember having it hooked up on another PC once, and although it seemed to work, when playing a 'complex' midi file, it would stop producing sound sooner or later and would only come back up when rebooting the whole computer because it couldn't be recognized as a MIDI device anymore.
Long shot, but easy to check just in case: Did your MIDI Driver Mode change (MME v. UWP)? I had something similar with nanoKontrols not being seen in Cakewalk after I had switched to UWP. Hope your solution is that simple to fix.
- The "Nuclear Option": I haven't seen this issue in a while, but on occasion USB devices would stop working and the only fix was clearing out USB traces from the registry with a utility like USB Oblivion. Then re-attach the USB device and have it "recognized" by Windows again. Of course after doing this you'll need to reinstall all of your USB devices.
I have reinstalled the drivers, moved ports and even sent MOTU to the shop to check. I think it is a corrupted branch of the registry where Cakewalk stores the midi info. I have older backups I could copy that branch from, but I don't know where it is located.
a few things:
the midicontroler will only listen to Ctrl Change type messages.
the midinote will only listen to Key On type messages.
you need also to select wich hardware or virtual midi port to listen (right en pin)
you need a midi splitter named midi yoke, that is ( youpee ) part of mid ox.
so if you want to monitor your IN signal from midi Ox, you take the hook on the device, and you cant normally get it in vvvv.
You need to route the output in midi OX to a Midi Yoke port. This is this midi port you need to listen in vvvv.
I understand that perhaps MIDI-XO is taking the input away from vvvv. However it is strange that vvvv MidiClock still works, even if MIDI-XO is running, though the other modules do not. I tried playing with MidiNote again without MIDI-XO running, but had the same result, nothing on the output pin.
7fc3f7cf58