Send midi shortMsg hMO, midiMsg(pointer) `MidiTHRU the message to the output portĬlear midiIn buffer `Purge the midiIN buffer to make room for further messages MidiMsg(pointer) = midiIn buffer(msg) `Store the actual message (the midiIN message is temporarily stored in the midiIN buffer) MidiStamp(pointer) = timer() - time `Sava a (poor) timestamp for the midi event If dev = 0 `Loop through the items in the midiIN buffer Sleep 90 `Ensure that the cursor doesn't scroll too fast Text 22, 22 * dev, get midiIn device name(dev) `Display the name of the current deviceĭev = 0 `Since this is used for the selection below, it should start at the first item (id 0) Text screen width() - text width(".:Choose an midiIN device."), 0, ".:Choose an midiIN device." We start by allowing the user to choose his midiIN device: `unneccessary memory by creating arrays etc. `First out, we need to tell the midi plugin that it will be used otherwise it wouldn't take up Set display mode 1024, 768, 32 : set window on : set window title "MIDI Recording & Playback" : maximize window : disable escapekey `The escapekey will be used later on Global time as integer `Used with timer() to determine *really* simple timestampsĭim midiMsg (65535) `The program will be able to store 65535 separate midiMessagesĭim midiStamp (65535) `Timestamps between each midi message. Global pointer as integer `Points to the current midiMessage (its ID, that is) Global hMI as dword `Handle to opened midiIN port I hope that someone will find this useful merry holidays Midi.html should be placed in DBPRO_ROOTHelpcommands.įinally, copy the midi folder to DBPRO_ROOTHelpcommands. MidiKeywords.ini are headed for DBPRO_ROOTEditorKeywords, Midi_includes.dba to whereever you'd like to have it (the installer puts it in DBPRO_ROOTProjects), Midi_Plugin.dll goes into DBPRO_ROOTCompilerplugins_user, If you don't dare to use the installer (maybe I've been isolated in my basement with a german, a taliban, two japaneses and a cat, writing the most vile malware ever seen to this day and now decided to spread it - in the perfect disguise a midi-plugin installer! - after two years of febrile development), you could just move the files yourself. It could turn out to be of use in some app/game you'll write, who knows?Īttached is the plugin, helpfiles, the keyword files and a program that gets everything set up for you (it even appends the commands.html file, adding Midi-commands to it's end), while you play the banjo using your midi-controller. ♦Possibility to trigger the computers built-in oscillatorĪllright, this might not be all that usefull in the sequencing terms, but I threw in the Beep-function from kernel32 as well. Retrieve midiIn ports (adresses and names), collect midiIn events as shortMessages (3-byte words) - you can then parse theese however you like, and so on. has separate, easy to use commands (saves you some time from having to write your own shortMsg's for it). Port listings, volume control, instrument selection, etc. Send midiOut data over any available port on your system. Most things you would need to do can be done directly by using your own midi messages (which are usually words consisting of 3 bytes) use the command SEND MIDI SHORTMSG and get most info you'd need here. Not to worry it is fully functional - the only things I might have done about it otherwise would have been to add some additional "for convenience"-commands, maybe enhance the helpfiles a bit and tried to optimize the code. Therefore, I decided to realease the plugin as-is, with removed restrictions. However, my demo version was time limited and set to expire in the middle of December. I posted a demo of this before the interrest wasn't very big though (not that you could really expect it for such a thing as this either) and hence I haven't really done anything more about this the last months, as it does all that my needs require of it allready. The installer is still the same though, so the files might need to be moved manually. I've shaped up the helpfiles a bit and added a new command set sustain pedal. Slightly updated version attached due to SMD_3D_Interactive's QMidi project.
The midiIn buffer purging has been updated in order to deal with the issue of certain messages getting lost during processing.
#Code qmidi download
See further info in post 37 and download the update. I've also fixed a few bugs and shaped up the documentation again.Īlso, for the first time ever, I have supplied a proper, commented demonstration source. I've also added a new "parsing" system, complete with an include file, which allows you to easily extract any kind of information from an midi message.
The midiIn seems to finally work properly no more lost messages judging by my tests.
0 kommentar(er)
