rlang

7. USB= 100 mA initial, 500 mA max at 5 volts Rob

Thorsten has said with regeditor "Search for AUDIO DEVICE, and change to MBHP_USB" If I do this I find many occurances of USB AUDIO DEVICE in the registry. Some are connected with the proper VID and PID, others appear to have no relation. The regeditor prevents me from changing the ones related to the proper VID and PID as shown below. The device is not plugged in. I can not edit the line that says: "DeviceDesc"="USB Audio Device" Does anyone know how to change the device name for a device using the generic audio driver in XP. [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_04d8&Pid_000a\5&4f71199&0& 1] "DeviceDesc"="USB Audio Device" "LocationInformation"="Pic18F2455 MIDI V2.1" "Capabilities"=dword:000000a4 "UINumber"=dword:00000000 "HardwareID"=hex(7):55,00,53,00,42,00,5c,00,56,00,69,00,64,00,5f,00,30,00,34,\  00,64,00,38,00,26,00,50,00,69,00,64,00,5f,00,30,00,30,00,30,00,61,00,26,00,\  52,00,65,00,76,00,5f,00,30,00,31,00,30,00,30,00,00,00,55,00,53,00,42,00,5c,\  00,56,00,69,00,64,00,5f,00,30,00,34,00,64,00,38,00,26,00,50,00,69,00,64,00,\  5f,00,30,00,30,00,30,00,61,00,00,00,00,00 "CompatibleIDs"=hex(7):55,00,53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,\  5f,00,30,00,31,00,26,00,53,00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,\  00,30,00,33,00,26,00,50,00,72,00,6f,00,74,00,5f,00,30,00,30,00,00,00,55,00,\  53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,31,00,26,00,53,\  00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,33,00,00,00,55,00,\  53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,31,00,00,00,00,\  00 "ClassGUID"="{4D36E96C-E325-11CE-BFC1-08002BE10318}" "Class"="MEDIA" "Driver"="{4D36E96C-E325-11CE-BFC1-08002BE10318}\\0008" "Mfg"="(Generic USB Audio)" "Service"="usbaudio" "ConfigFlags"=dword:00000000

I will send you the coding, probably around week's end after I have another stab at it. On the writing your own WDM driver, that was my original thought. After reading Walter Oney's 600 page opus called Programming the Microsoft Windows Driver Model, I was discouraged. Edition 1 of this book had over 24 pages of errata, which says to me that even if you are an expert, it is easy to make mistakes building a windows driver. Even so, I ordered the Windows Server 2003 Driver development kit from Microsoft. There are some USB examples and it also includes the following audio driver examples: ac97 - A sample audio driver that runs on an Intel motherboard with an integrated AC97 controller. This sample shows how to write a WDM audio adapter driver that implements WavePci support for a PCI add-in card with scatter/gather DMA capabilities. Included with this sample driver are additional subdirectories containing sample code that works in conjunction with the driver. ddksynth - Kernel-mode DLS synthesizer. This sample can be adapted for a MIDI output device as well. dmusuart - MPU-401 miniport driver for processing DirectMusic and MIDI input and output streams. This is the source code for the built-in DMusUART miniport driver in portcls.sys. Hardware vendors can adapt this sample to write their own custom miniport drivers. fmsynth - FM-synth miniport driver for MIDI. This sample driver provides an interface to a device that implements OPL3-style synthesis. This is the source code for the built-in FMSynth miniport driver in portcls.sys. Hardware vendors can adapt this sample to write their own custom miniport drivers. gfx - The two GFX samples appear in the DDK for Windows XP SP1, Windows Server 2003, and later. These samples implement support for a simple GFX (global effects) filter: mpu401 - Stand-alone sample adapter driver. This adapter driver implements standard functionality for an MPU-401 MIDI interface device. The source code for this sample is quite small because it uses only the system-supplied miniport drivers that are implemented in portcls.sys. msvad - Microsoft Virtual Audio Device. This is a collection of samples that all use the same "virtual audio device" in lieu of an actual hardware-based adapter driver. Each of these samples highlights a different facet of the WDM audio driver architecture: ac3 - Demonstrates support for a non-PCM audio data format. drmmult - Demonstrates support for multiple-stream audio with SAP-protected content. For information about SAP (secure audio path), see the Platform SDK documentation. drmsimp - Demonstrates support for a single audio stream with SAP-protected content. ds2dhw - Demonstrates support for hardware-accelerated two-dimensional mixing for DirectSound. multstr - Demonstrates support for playback of multiple streams of PCM audio data. pcmex - Demonstrates support for a PCM audio format that is defined by the WAVEFORMATEXTENSIBLE structure. simple - A skeleton reference implementation of an audio adapter driver upon which the other msvad sample drivers are built. sb16 - Sound Blaster 16 sample. This sample implements an audio adapter driver for an SB-compatible adapter card on an ISA bus. I have not had a chance to look at or compile any of these examples. Rob

Like you I also had problems with the audio control device so I used your descriptors as a guide and just reduced the number of serial ports. My problem now is trying to squeze everything I need into one serial port. I may have to implement an additional serial port as a "bit blaster" since I really think I need a serial port for debugging at this stage. Currrently I am trying to use one port for debugging and midi output, but sometimes a character is displayed out of sequence. Of course I can't use the serial port for debugging once a real midi device is plugged in. The out of character sequence probably has something to do with the way I manage the serial buffer. Note the following output USB MIDI Interface V2.1 Full speed USB I D>H GD device 12 01 08 d8 04 08 H>D SA 01 D>H GD device 12 01 08 d8 04 08 00 01 02 D>H GD config 09 02 08 32 02 01 D>H GD config 09 02 08 32 09 08 00 00 08 00 06 08 24 02 08 01 03 08 03 02 08 05 01 08 05 25 08 02 04 08 01 01 03 D>H GD stall IN Unstall D>H GD string 04 03 04 D>H GD string 2a 03 08 31 00 08 34 00 08 4d 0008 20 00 08 30 00 02 D>rH <= note the out of place r from string below GD sting 04 03 04 ... Do es anyone have any thoughts on what takes priority in the interrupts - serial or usb? ;) Thanks, Rob

I have developed a PIC18F2455 based USB MIDI interface and am currently in the testing of the software written in BOOSTC. I like the chip because it does not require a software download like the cypress chip and has a PDIP form factor for easy soldering. I was interested in your USB module software because of the problems you found with the MICROSOFT driver. The software currently enumerates correctly at full speed as an audio device. Any advice you have would be appreciated. http://www2.netdoor.com/~rlang/usbmidi.jpg for photo

I am trying to use the FTDI232BM USB to serial chip in a MIDI application. The FT232BM chip comes with a WDM usb driver and API (FT_Write(lngHandle, strWriteBuffer, LENGTH_MESSAGE, lngBytesWritten))that I can use to send midi data to the chip and it will convert to MIDI serial output. I would like to use the windows MIDI API functions like IRET = midiOutShortMsg(MIDI_OUT_HANDLE, MIDIMSG). My question is what do I have to do to have the FT232BM chip recognized as a MIDI device? Why do I want it to be recognized as a MIDI device when I can already send midi data to it? So that CAKEWALK and other musical applications can use it directly. Any guidance is greatly appreciated. Thanks in advance. Bob Lang

I think the drivers are dependent on the chipset in your USB device. A free driver if you use the FT232BM chip is available at http://www.ftdichip.com/FTDriver.htm