Maddogg6

Ok so I finally figured out how to do something a few others seemed to have interest in also, here it is:

http://fileanchor.com/23746-d


Anyway - its a small little app (25KB) that you can send the following command line arguments:

KX_SENDMIDI.EXE PORT CHANNEL CONTROLLER VALUE

So if you make a batch file:
KX_SENDMIDI.EXE 0 0 10 100

And you have KX automation set like: MX6 Line1 LEVEL - CC10 CH1

The above bat file would set that MX6 input to 100.

This would be usefull for scripting languages like AUTOHOTKEY, AUTOIT, WSH etc or even a complex bat file I suppose.. to map KEY presses (or mouse, joystick etc) - to control KX plugin sliders and switches.

I wrote it in freebasic (I gave up on *trying* to learn C/++) and it uses WinAPI - so there shouldn't be any need for any external DLL's or anything and should run from anywhere you decide to keep it. It will work even if you dont use KX btw.

Im considering making a TRS type thing that will read a config file, and does all the keymapping its self - but this so far works for me, and thought maybe others can make use of it as well.

Feel free to post questions, comments or nasty remarks...

Chester01

it would be cool (my vision) if you could map keyboard keys (like on the keyboard im typing this on right now) to different levels/options witihin plugins. for example, i never use the number pad therefore if i were to map my gain hq sliders so taht pressing 8 would increase the gain and 2 would decrease it, i would have a volume control... pressing 1 could mute or w/e just a thought... your plugin sounds very interesting, i dont have a musical keyboard to test it but good luck!

__________________
COMP: Dual Intel PIII 733 Mhz; GeForce 4 Ti 4600; 1.128 Gb RAM; SB0350 (Audigy 2 ZS Platnium)
STEREO(I UPGRADED):Crown Audio K1 and K2 amplifiers (4000 watts at .1% THD ), JL 13w7 Subwoofer (6.5 CF) (2) 18" PR's, Klipsch SB-1's, some cement blocks for speaker stands...

Maddogg6

Well - thats sort of what this will do - when used with something like WinLIR - or AUTOIT..

Suppose you have WINLIR RUN (or execute) a program based on the remotes button pressed.

OR - Say with AUTOHOTKEY - runs this program when a PC Keyboard keystroke is detected.. so it actually is pretty flexible - but admitted - using with other software will make it 'less' user friendly.

If theres more interest maybe Ill continue improving this... ?? But it'll never be anything with a GUI or anything as it would just bloat it up to much, not to mention GUI programming is way beyond my abilities.

Russ

Good idea Maddogg6.
I like this idea better than scripting kX Console commands, because it allows the plugin itself to handle setting the registers correctly, etc (rather than the uses having to do it themselves).

-Russ

Maddogg6

At least some stuff can be done with PC Keys/WinLIR or whetver they may use for their remote control.

Its speed (opening the midiport) is kinda slow, thus - Im working on a way to have a TRS - keep the midi port open - and allow faster 'slider' motion - but It seems hooking the keyboard is needed (simple keyscans in FB require the app to have focus).. ??

Maybe I'll figure it out - Ill post here If I do..

But - if anyone needs to know what midi ports they have in stalled - this will show the DEVICEID for each one:
http://fileanchor.com/23820-d

Russ

That is normal for regular keyboard processing for any application.
If you can access the WinAPI directly with FB, you can use the RegisterHotKey WinAPI function to do it, or you could use hooks.

Maddogg6

Ahh thanks for the hint - those keywords to google by are invaluable when you see all the funcs found in winAPI...