I found an old version of the MIDI tracker software I wrote in VB6. Trouble is this was part of a s/w suite I wrote years ago and which the damned upgrade wizard didn't like. However, I did create a new VB6 project and just put in it the forms of the MIDI tracker and MIDI recorder - which only used standard MS controls that ship with VB6 and which still worked fine in VB6 as a standalone project - thank God.
Then I tried upgrading it via the damn wizard -which still choked. But the wizard reminded me of how much work I originally put into the damn thing. There are around 500 graphical objects (picture boxes) - mostly for the keys (white key up, white key down, black key up, black ket down) and the 88 keys etc. and still there was stuff that VB.Net didn't like. One of VB6's most useful features - 'control groups' - is missing in VB.Net hence the main reason the wizard choked and has messed up the code soething chronic. But at least it did get my class (for controlling short MIDI in and short MIDI out messages with mm dll calls and the graphics for the keyboard, etc. I'm going to have to recode it from scratch but at least I have something I can work with/from now (especially helpful since I don't have the MIDI documentation anymore and the General MIDI 1.0 specification is harder to find than it should be - thanks to MMA copyright ownership and their strict enforcement of it). Now since the API calls should still work I am pretty confident I will be able to write my MIDI tracker in VB.Net now. OMG, it felt really, really weird being back in Vb6 for a moment - I am getting used to being in VB.Net lol
Thursday, July 17, 2008 10:49 PM
- Edited by bigamee Thursday, July 17, 2008 10:57 PM spelling mistakes
The MIDI code module seems to have escaped/survived VB.Net's butchering wizard reasonably intact (yaaaaaaay):
ModuleMidiModule Public Const MAXPNAMELEN As Short = 32 ' Maximum product name length ' Error values for functions used in this sample. See the function for more information Public Const MMSYSERR_BASE As Short = 0 Public Const MMSYSERR_BADDEVICEID As Integer = (MMSYSERR_BASE + 2) ' device ID out of range Public Const MMSYSERR_INVALPARAM As Integer = (MMSYSERR_BASE + 11) ' invalid parameter passed Public Const MMSYSERR_NODRIVER As Integer = (MMSYSERR_BASE + 6) ' no device driver present Public Const MMSYSERR_NOMEM As Integer = (MMSYSERR_BASE + 7) ' memory allocation error Public Const MMSYSERR_INVALHANDLE As Integer = (MMSYSERR_BASE + 5) ' device handle is invalid Public Const MIDIERR_BASE As Short = 64 Public Const MIDIERR_STILLPLAYING As Integer = (MIDIERR_BASE + 1) ' still something playing Public Const MIDIERR_NOTREADY As Integer = (MIDIERR_BASE + 3) ' hardware is still busy Public Const MIDIERR_BADOPENMODE As Integer = (MIDIERR_BASE + 6) ' operation unsupported w/ open mode 'User-defined variable the stores information about the MIDI output device. Structure MIDIOUTCAPS Dim wMid As Short ' Manufacturer identifier of the device driver for the MIDI output device ' For a list of identifiers, see the Manufacturer Indentifier topic in the ' Multimedia Reference of the Platform SDK. Dim wPid As Short ' Product Identifier Product of the MIDI output device. For a list of ' product identifiers, see the Product Identifiers topic in the Multimedia ' Reference of the Platform SDK. Dim vDriverVersion As Integer ' Version number of the device driver for the MIDI output device. ' The high-order byte is the major version number, and the low-order byte is ' the minor version number. 'UPGRADE_WARNING: Fixed-length string size must fit in the buffer. Click for more: 'ms-help://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="3C1E4426-0B80-443E-B943-0627CD55D48B"'
<VBFixedString(MAXPNAMELEN),System.Runtime.InteropServices.MarshalAs(System.Runtime.InteropServices.UnmanagedType.ByValArray,SizeConst:=MAXPNAMELEN)>Public szPname() As Char ' Product name in a null-terminated string. Dim wTechnology As Short ' One of the following that describes the MIDI output device: ' MOD_FMSYNTH-The device is an FM synthesizer. ' MOD_MAPPER-The device is the Microsoft MIDI mapper. ' MOD_MIDIPORT-The device is a MIDI hardware port. ' MOD_SQSYNTH-The device is a square wave synthesizer. ' MOD_SYNTH-The device is a synthesizer. Dim wVoices As Short ' Number of voices supported by an internal synthesizer device. If the ' device is a port, this member is not meaningful and is set to 0. Dim wNotes As Short ' Maximum number of simultaneous notes that can be played by an internal ' synthesizer device. If the device is a port, this member is not meaningful ' and is set to 0. Dim wChannelMask As Short ' Channels that an internal synthesizer device responds to, where the least ' significant bit refers to channel 0 and the most significant bit to channel ' 15. Port devices that transmit on all channels set this member to 0xFFFF. Dim dwSupport As Integer ' One of the following describes the optional functionality supported by ' the device: ' MIDICAPS_CACHE-Supports patch caching. ' MIDICAPS_LRVOLUME-Supports separate left and right volume control. ' MIDICAPS_STREAM-Provides direct support for the midiStreamOut function. ' MIDICAPS_VOLUME-Supports volume control. ' ' If a device supports volume changes, the MIDICAPS_VOLUME flag will be set ' for the dwSupport member. If a device supports separate volume changes on ' the left and right channels, both the MIDICAPS_VOLUME and the ' MIDICAPS_LRVOLUME flags will be set for this member. End Structure Declare Function midiOutGetNumDevs Lib "winmm" () As Short ' This function retrieves the number of MIDI output devices present in the system. ' The function returns the number of MIDI output devices. A zero return value means ' there are no MIDI devices in the system. 'UPGRADE_WARNING: Structure MIDIOUTCAPS may require marshalling attributes to be passed as an argument in this Declare statement. Click for more: 'ms-help://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="C429C3A5-5D47-4CD9-8F51-74A1616405DC"' Declare Function midiOutGetDevCaps Lib "winmm.dll" Alias "midiOutGetDevCapsA"(ByVal uDeviceID As Integer, ByRef lpCaps As MIDIOUTCAPS, ByVal uSize As Integer) As Integer ' This function queries a specified MIDI output device to determine its capabilities. ' The function requires the following parameters; ' uDeviceID- unsigned integer variable identifying of the MIDI output device. The ' device identifier specified by this parameter varies from zero to one ' less than the number of devices present. This parameter can also be a ' properly cast device handle. ' lpMidiOutCaps- address of a MIDIOUTCAPS structure. This structure is filled with ' information about the capabilities of the device. ' cbMidiOutCaps- the size, in bytes, of the MIDIOUTCAPS structure. Use the Len ' function with the MIDIOUTCAPS variable as the argument to get ' this value. ' ' The function returns MMSYSERR_NOERROR if successful or one of the following error values: ' MMSYSERR_BADDEVICEID The specified device identifier is out of range. ' MMSYSERR_INVALPARAM The specified pointer or structure is invalid. ' MMSYSERR_NODRIVER The driver is not installed. ' MMSYSERR_NOMEM The system is unable to load mapper string description. Declare Function midiOutClose Lib "winmm.dll" (ByVal hMidiOut As Integer) As Integer ' The function closes the specified MIDI output device. The function requires a ' handle to the MIDI output device. If the function is successful, the handle is no ' longer valid after the call to this function. A successful function call returns ' MMSYSERR_NOERROR. ' A failure returns one of the following: ' MIDIERR_STILLPLAYING Buffers are still in the queue. ' MMSYSERR_INVALHANDLE The specified device handle is invalid. ' MMSYSERR_NOMEM The system is unable to load mapper string description. Declare Function midiOutOpen Lib "winmm.dll" (ByRef lphMidiOut As Integer, ByVal uDeviceID As Integer, ByVal dwCallback As Integer, ByVal dwInstance As Integer, ByVal dwFlags As Integer) As Integer ' The function opens a MIDI output device for playback. The function requires the ' following parameters ' lphmo- Address of an HMIDIOUT handle. This location is filled with a ' handle identifying the opened MIDI output device. The handle ' is used to identify the device in calls to other MIDI output ' functions. ' uDeviceID- Identifier of the MIDI output device that is to be opened. ' dwCallback- Address of a callback function, an event handle, a thread ' identifier, or a handle of a window or thread called during ' MIDI playback to process messages related to the progress of ' the playback. If no callback is desired, set this value to 0. ' dwCallbackInstance- User instance data passed to the callback. Set this value to 0. ' dwFlags-Callback flag for opening the device. Set this value to 0. ' ' The function returns MMSYSERR_NOERROR if successful or one of the following error values: ' MIDIERR_NODEVICE- No MIDI port was found. This error occurs only when the mapper is opened. ' MMSYSERR_ALLOCATED- The specified resource is already allocated. ' MMSYSERR_BADDEVICEID- The specified device identifier is out of range. ' MMSYSERR_INVALPARAM- The specified pointer or structure is invalid. ' MMSYSERR_NOMEM- The system is unable to allocate or lock memory. Declare Function midiOutShortMsg Lib "winmm.dll" (ByVal hMidiOut As Integer, ByVal dwMsg As Integer) As Integer ' This function sends a short MIDI message to the specified MIDI output device. The function ' requires the handle to the MIDI output device and a message is packed into a doubleword ' value with the first byte of the message in the low-order byte. See the code sample for ' how to create this value. ' ' The function returns MMSYSERR_NOERROR if successful or one of the following error values: ' MIDIERR_BADOPENMODE- The application sent a message without a status byte to a stream handle. ' MIDIERR_NOTREADY- The hardware is busy with other data. ' MMSYSERR_INVALHANDLE- The specified device handle is invalid.
EndModuleThursday, July 17, 2008 11:09 PM
Just looking through the code in th module - much of it I plagarised from an old MS SDK for muiltimedia some years ago - hence many of the REMs are from the writers of the SDK. Iknow the wizard butchered my code in the forms - not sure just how badly yet - but I should be able to write the thing in VB.Net ok now tg.
AllanThursday, July 17, 2008 11:21 PM