FW: MPU-401 Module
Crain Greg <[email protected]> Thu, 30 Oct 2003 08:46:28 -0500
| Newsgroups | gmane.os.openbeos.midi |
|---|---|
| Message-ID | <59494E2589FBF14AB5BB0523274BC76801AB7482@abhe341a.abhe.ww011.siemens.net> |
Hello,=20 =20 Here is the link for my current work for submission:=20 http://mywebpages.comcast.net/gsc70/mpu401.zip=20 =20 I have the basic functionality working. The mpu401 part of it is =20 actually very simple. The stuff that is difficult for me was the =20 system integration type things. It's been a little slow for me, =20 because I've had to learn a lot along the way. Just when I think I'm =20 getting close, I realize there is something more I need to understand. =20 So it goes in software I suppose.=20 =20 The module, V1 ( with the published header), I believe is basically =20 working. The _problem_ is that I have found almost no midi drivers for =20 testing that use this V1 version except the Sonic Vibes (don't have =20 one), which is published. Midi out works, the interrupt stuff is in =20 place, and I think midi-in works, but is untested. I want to use the =20 Emuxki for both testing, and to get midi working on the driver. I =20 still need to do some work if there is more than one midi device using =20 the module. =20 =20 The unpublished(?) V2 module uses a different 'create_device_alt' hook. =20 =20 I'm not sure what is exactly happening, but I'm not really focusing on =20 it yet. It appears that it uses a global port for midi messages, =20 rather than passing a buffer pointer. All of my soundcards that have =20 Be Inc midi drivers use this V2. ( AWE64, ESS Solo, emu10k =3D no =20 midi, CT 5880 midi doesn't work, SB Vibra16 can't get midi to work even =20 with Be module ). =20 =20 Also in the archive is a midi port driver that assumes the standard =20 midi port address 0x330. I used this for some testing. I was able to =20 get midi-out working with my AWE64 using this. If I can get the =20 interrupts enabled, midi-in should work too.=20 =20 Even now, I know there are still a lot of things that can be cleaned =20 up, debug messages removed, code that needs to be done differently, =20 etc. It's a starting point though. I can go into more detail as to=20 what more is needed. =20 =20 Greg Crain=20 =20 =20 -----Original Message-----=20 Hello,=20 =20 That page can help us?=20 =20 http://www.borg.com/~jglatt/tech/mpu.htm=20 =20 For the softsynth some function are implemented,=20 todo implement reverb(0% done)=20 BSynth(50% done)=20 BMidiSynth(20% done)=20 BMidiSynthFile(20% done)=20 Write BSample(0% done)=20 correct bug......=20 =20 Have a nice day=20 =20 Jerome=20 =20