PluginQL -- A kX Addon

Maddogg6 · Dec 7, 2005, 10:07 AM

Quote:

Originally Posted by Russ

@Maddogg6
Are you using epilog? If you look at kX mixer when you press the volume keys, you see that it adjusts the master volume sliders, and if you unload epilog, the master volume sliders are no longer visible in kX mixer. Also, if you look at the microcode for epilog, you will see the control registers that are used for that (MasterL and MasterR). Other plugins could use them (the volume keys), but it is a little more complicated because plugins do not have a window of thier own (other than the tweak window, which basically does not exist when it is closed).

So, its Epilog.. ok - but theres a way for this to function. What trick does epilog do to bypass the 'missing' window problem you describe?

Quote:

Originally Posted by Russ

BTW: KX Console can be used to (among other things) change the value of any register in the DSP, and thus can be used to modify volumes, etc. This means that you do not necessarly need a plugin to respond to keypresses itself. i.e. You can create a Windows shortcut (with it's own shortcut keys) to call kX Console functions, and thus create your own volume keys, etc. It is a little messy, as the console window would pop up every time you press the key, but it is workable (without having to be a programmer). Also, you can using scripting languages such as VBSCRIPT to script the actions (and start kX Console hidden), and do it that way. I actually did this once for the heck of it. I probably still have the script around here somewhere... And of course, if you have VC++, you can use the kX API, and control all that stuff directly.

Is it possible to make use of the KX API with other compilers or is this a just 'VC++/req. MFC' thing also (like for plug-ins) ?

Not that Im even near capable - But Id like to understand better.

I read in other posts you had some success in converting headers or something (maybe just relating to plug-ins..??) - can you better explain the difference using VC++ 2005 (express??) - is it just a matter of converting the format of function calls (something find/replace-able) or is it more complex.

Russ · Dec 7, 2005, 10:33 AM

Quote:

Originally Posted by Maddogg6

So, its Epilog.. ok - but theres a way for this to function. What trick does epilog do to bypass the 'missing' window problem you describe?

It uses kx mixer to do it. i.e. Eugene made that plugin and kX, so he can do things that we can not do. That is not to say that it is not possible, I only said it is more complicated. We can create out own invisible window to use to receive messages from the Windows Mixer. I had to do a similair thing with this addon, so that I could receive the messages from the hotkeys.

Quote:

Is it possible to make use of the KX API with other compilers or is this a just 'VC++/req. MFC' thing also (like for plug-ins) ?

Not that Im even near capable - But Id like to understand better.

I read in other posts you had some success in converting headers or something (maybe just relating to plug-ins..??) - can you better explain the difference using VC++ 2005 (express??) - is it just a matter of converting the format of function calls (something find/replace-able) or is it more complex.

That is a complicated subject, as you probably have read in other threads. MFC is a requirement. The stuff I mentioned in the other threads was regarding the version of MFC and not necessarliy the version of VC++.

Russ · Dec 7, 2005, 08:20 PM

I removed the test version and just added the changes to the other versions (both 3538i and 3538h) as it shouldn't cause anybody any problems. It really should not effect anybody that does not have multiple cards under kX, so if you only have 1 card, and allready installed this addon, then you do not need to update it to this version (although you can if you want to). Remember that you have to quit kX Mixer in order to be able to replace the file (otherwise you will get an error about it being in use), and you do not have to re-register it, if you registered the previous version. If anyone with multiple cards tries it, please let me know if it works right.

-Russ

PITmaster · Dec 8, 2005, 06:30 PM

@Russ

3538h version works with multiple cards now

But I didn't complex test, I just tryed.
Do you know how to change plugin's id? I have more than 19 plugins on my kxdsp window and some of them has numbers above 20 or 30.

PITmaster

Russ · Dec 8, 2005, 09:17 PM

Thanks PITmaster. As far as the id's go, kX just basically numbers them using the loweset available id at the time it was loaded. The only way to re-order them, would be to either clear the DSP, and load the plugins in the order that you want them to be in (as far as the id's go), or a series of unloading individual plugins, and then reloading them (i.e. if you free up a lower id, the next plugin loaded will use it).

Russ · Dec 8, 2005, 09:59 PM

BTW: I am still open to suggestions...

i.e.
Possibly adding more hotkeys to access higher plugin numbers. The issue with that is that I do not want to use too many (and not common one's) as they are global, if another program wants to use one of the hotkeys assigned here, it will not be able to do so.

Another option is that it could be modified to use a multiplier in order to access the higher numbers using the same keystrokes.
i.e.
ALT-SHIFT-KEY_NUMBER could be used to set a multipler, and then CTRL-SHIFT-KEY_NUMBER would open the plugin for that KEY_NUMBER, plus ten times the multipler.
i.e.
(the mutiplier remains in effect until you change it).
ALT-SHIFT-0 = multiplier 0.
CTRL-SHIFT-2 = plugin #2
ALT-SHIFT-1 = multiplier 1.
CTRL-SHIFT-2 = plugin #12
ALT-SHIFT-2 = multiplier 2.
CTRL-SHIFT-2 = plugin #22
, etc.

The advantage here would be that you could access numbers up to 100, without needing additonal hotkeys, but the disadvantage would be that it would require 2 sets of keystrokes if you want to open a plugin using a different multiplier. 100 is probably way more than would ever be needed, so maybe use a subset of the above (30,40,50, whatever), and use the additional ALT_SHIFT-KEY_NUMBER combos to do other things (i.e. open the DSP Window itself, or other kX windows, etc).

What do you guys think? Any other ideas?

-Russ

Russ · Dec 9, 2005, 12:08 AM

@Maddogg6,
Just to let you know, when I first made my sb022x test plugin, I did include support for the multimedia keyboard volume keys, (because I wanted to be able to control the Master Volume using them, and that plugin replaced epilog and thus that ability). If you read the thread about that, you will see that I had mentioned it there. It worked, but on occasion kX mixer would crash, and I was never able to figure out why, so I removed that option when I released that plugin. Maybe when I have the time I will look into that again, and see if I can figure out what the problem was, and add it to a simple volume control plugin or something. In any case, I just thought I would let you know one of the reasons why I said that it is a little more complicated with plugins.

Maddogg6 · Dec 9, 2005, 09:57 AM

Thanks Russ,

It makes sense that its possible and I was pretty certain C++ was gonna be needed for the plug-in -

For now I will use epilog instead of Kxlt - which is ok really.
But a Vol would be nice too - Ill do some searching..

Thanks Again.

PITmaster · Dec 9, 2005, 10:43 AM

Quote:

Originally Posted by Russ

BTW: I am still open to suggestions...
(the mutiplier remains in effect until you change it).
ALT-SHIFT-0 = multiplier 0.
CTRL-SHIFT-2 = plugin #2
ALT-SHIFT-1 = multiplier 1.
CTRL-SHIFT-2 = plugin #12
ALT-SHIFT-2 = multiplier 2.
CTRL-SHIFT-2 = plugin #22
, etc.

What do you guys think? Any other ideas?
-Russ

I think it "sounds" good.
Of course I wouldn't repeat multiplier selection every time before open plugins with the same multiplier, right?

One thing, I guess it would be good ability to activate/deactivate add-on or it's already possible and I just don't know how.

PITmaster

Marki · Dec 9, 2005, 04:56 PM

Quote:

Originally Posted by Maddogg6

The idea behind this could actually get complex for some advanced things like A PC KB Midi Keyboard - play KX synth with PC KB and no other SW needed)

or - recorded automation via midi file playback initiated by a single keystroke - all within KX ... just starts blowing my mind. (merged of course)

We are thinking about something similar - kX "automation" using external components. Now we use PC with Audigy connected to old external audio analog mixer, which is connected to 1000W power amp and speakers. But the idea is to get as much as possible into PC. But "normal" hardware mixer has advantage of real sliders. In PC, you have buch of them on screen and it's not so easy to instantly modify the one that is needed.
So the idea is audigy would act also as mixer with output directly to power amp. And using some home-made external sliders to adjust mixer "volumes". I think MIDI interface would be easy to implement...

Russ · Dec 10, 2005, 03:29 AM

Quote:

Originally Posted by PITmaster

I think it "sounds" good.
Of course I wouldn't repeat multiplier selection every time before open plugins with the same multiplier, right?

One thing, I guess it would be good ability to activate/deactivate add-on or it's already possible and I just don't know how.

PITmaster

Right, the multiplier would stay in effect until you change it.
As for deactivating the addon (or actually just deactivating the hotkeys), I was thinking that would be a good idea as well, just in case you need to use of the hotkeys in another application, etc.

Russ · Dec 13, 2005, 11:19 PM

I think 100 is probably way more than is needed for the plugins, so here is my latest thinking.
The ALT-SHIFT-KEY_NUMBER hotkeys are used to set the current mode (out of 10 modes).
The CTRL-SHIFT-KEY_NUMBER hotkeys will have different assignements in each mode.
This will allow for 100 different hotkeys to be used.
I am thinking of using an .ini file to be able to customize the hotkeys for each mode.
Possibilities include:
Opening the tweak window for a plugin.
Opening kx's 'about' window.
Opening kx Mixer to a specific page.
Opening the DSP window.
Opening the kX Router window.
Opening the Speaker Test window.
Opening the kX Editor.
Opening the Setup Buffers window.
Opening the kX Automation window.
Opening the Asio Control Panel window.
Opening the OSD Notifications window.
Opening the Synth Compatibility window.
Opening the Driver Compatibillity window.
Opening the SPDIF/I2S Status window.
Opening the kX 24/96 Router window.
Opening kX help.

There are lots of possibilities beyond the above, I am just not sure how much would be useful. Even with the above options, 100 is probably still much more than is needed, so I may cut down on the number of modes.

What do you think?

thomasabarnes · Dec 14, 2005, 04:46 AM

Sounds cool. Do whatever you want to do.

**dj_stick** · Dec 14, 2005, 09:23 AM

Quote:

Originally Posted by Russ

There are lots of possibilities beyond the above, I am just not sure how much would be useful. Even with the above options, 100 is probably still much more than is needed, so I may cut down on the number of modes.

What do you think?

how about the number of modes can be set by the user? maybe an .inf file, or ui batch script?

Russ · Dec 14, 2005, 10:32 AM

Yeah, that is a good idea, that way people can decide for themselves how many they want to use.

TheKezReturns · Dec 17, 2005, 08:31 AM

Any chance of midi messages triggering these events as well as keys?
...once you get problems to hand sorted of course

Russ · Dec 17, 2005, 09:14 PM

I think it should be possible, but I am not quite sure how, and I am not quite sure such a thing would be practicle. I do not have any midi hardware (nor that type of midi software) to test such a thing out (I do not use midi all that much), nor do I know what midi messages would be good to use for this purpose. We are talking about over 100 different mappings. For the PC keyboard that is OK, because there are many possible key combinations, but I am not sure that would be so good with midi messages. Again, I do not use midi all that much and do not know a whole lot about it.

Russ · Dec 17, 2005, 11:42 PM

err, scratch that... Actually it would only be 20 different mappings needed.
Maybe I could add a plugin interface to it, to take advantage of the plugin API's automation stuff. It could be a plugin that uses no resources, and uses dummy parameters just to allow you to use kX Automation to map messages to simulate the PC keyboard keys, etc. That shouldn't be difficult to do. I will look into it.

-Russ

TheKezReturns · Dec 19, 2005, 07:04 AM

Awesome, I have a live setup with Ableton Live & Lemury's MX6 both hooked up to a BCF2000 midi controller which works great. I hate using the mouse on stage as it's not very visually appealing, and I have replaced mouse actions with midi wherever possible. There is no keyboard coz I don't need one. In fact the only time I ever really have to use the mouse is when I have to bring up dsp plugins windows to do some tweaking which i find a real pain in the a***. A simple press of a button on the BCF2000 would be alot easier, especially when your drunk and there's some big red light in your eyes and you can hardly make out the text on the screen thru the smoke

Anway, love your work, rock on!

...ohh and the button normally send midi note on/off msgs.

/Kez.

Russ · Jan 10, 2006, 06:25 AM

Does anyone know of a way to test kX's Automation without external midi devices? (i.e. a way to simulate it through software so that you can trigger kX Automation events).

I added a plugin interface which is used for kX Automation, and as a GUI for configuring the hotkeys, and I am looking for a way to test the automation stuff.

**dj_stick** · Jan 10, 2006, 08:01 AM

try using a sequencer with midi output/midi yoke

Russ · Jan 10, 2006, 09:04 AM

Ok, I see how it works. All I have to do is set the midi output port to kX Control.

Lex Nahumury · Jan 10, 2006, 09:27 AM

Also; Try use MIDI OX instead of a sequencer.
It's free, light weight and has a control panel/msg monitor
The ideal tool for quick MIDI msg generation/testing/development etc.

Russ · Jan 10, 2006, 11:25 AM

I will check it out. Thanks for the info.

Russ · Jan 10, 2006, 11:03 PM

I added a new test version (currently 3538i only) to the second download site (link in first post of this thread).
The zip file contains the addon and the plugin (as well as the unregister reg script, in case of problems, use the reg script to unregister the addon, the plugin, and delete the settings).
This versions works as follows:
ALT-SHIFT-NUM_KEY sets the mode (1-10)
CTRL-SHIFT-NUM_KEY performs the actions assigned to that key for the current mode.
This gives 100 hotkeys.
The addon can now be used not only for tweak windows but also for opening various kX windows, and toggling/changing a few kX hardware parameters.

The addon menu item can be used to enable/disable the hotkeys (also indicates the current mode). If the menu item is checked (the default state), it means that it is enabled.

The plugin part is used for kX Automation and for configuring the key assignments.
If you do not use kX Automation, then you do not need to load the plugin (except if you want to re-assign the keys, after which you can unload the plugin again if you want).
Changes made to key assignments are not saved until you click on the save button (including setting the defaults (i.e. to set defaults, click Set Defaults, and then click Save Settings, etc).
The mode combo box selects the configuration page for the mode selected. You can modify individual pages without saving (i.e. you will not lose changes to a page by changing to another page, the settings are held, they are just not saved/used until the Save Settings button is clicked).
Setting defaults, resets all pages (again not saved until you manually save).
Closing the plugin window will cause any unsaved changes to be lost (this way whenever you open the tweak window, you know that the settings listed are always the current settings).
The addon does not need to be loaded or enabled to make changes to the settings.

Installation is the same as it was with the previous versions (see previous posts).

Again, this is a test version. I could not test everything out myself (i.e. mutiple card seups under kX, and I only did some basic testing with the kX Automation, etc), so there may be some bugs.

Russ · Jan 11, 2006, 01:08 AM

I added the 3538h version for testing as well (also only available from the secondary download link).

Maddogg6 · Jan 11, 2006, 02:42 AM

@Russ - Ive been playing with this (finally - I had it loaded and forgot about it - ?? :S)

It works well and IS quite handy - Another fine release from 'RussWare'

KX V3538h - Audigy 2ZS Platinum SB0350

Kudos...

Did you figure on which way to handle #'s > 10 ?

No rush, just curious...

Russ · Jan 11, 2006, 04:12 AM

Quote:

Originally Posted by Maddogg6

Did you figure on which way to handle #'s > 10 ?

Which version are you using (I think maybe you are still using the very first version)?
In that last release, ALT-SHIFT-KEY_NUM was used for plugin #'s 11-20.

In the new test version, ALT-SHIFT-KEY_NUM is used to change modes, with each mode having 10 keys which can be assigned to any plugin # (among other things) that you want (up to 99 as it stands now).

Under the default settings, Modes 1-4 are for plugin #'s 1-40.
i.e.
(MODES stay in effect until you change them)
ALT-SHIFT-1 = MODE 1
In Mode 1:
CTRL-SHIFT-1 = plugin #1
CTRL-SHIFT-2 = plugin #2
.. etc.

ALT-SHIFT-2 = MODE 2
In Mode 2:
CTRL-SHIFT-1 = plugin #11
CTRL-SHIFT-2 = plugin #12
.. etc.

Again, that is with the default settings... You can change the key assignments for each mode using the GUI.

Maddogg6 · Jan 11, 2006, 04:23 AM

Yeah - I figurued it out right after post.. .doh! I first read it as ALT+SHIFT+CTRL - sheesh! IT WORKS GREAT! Whoo hoo!
Damn 'online speed reading' course was a waste :S.

Russ · Jan 11, 2006, 04:33 AM

BTW: I forgot to mention something:
I am not sure what will happen if you try to use a feature not supported by your card, so be wary of any such features.

i.e.
If your card is a 4.0 card, I am not sure what might happen if you use the 'Toggle Route HP To Center/Sub' option, etc. Hopefully it will do nothing, but I cannot be sure, so be careful with such options.

Dec 7, 2005, 08:20 PM	Thread Starter #33
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I removed the test version and just added the changes to the other versions (both 3538i and 3538h) as it shouldn't cause anybody any problems. It really should not effect anybody that does not have multiple cards under kX, so if you only have 1 card, and allready installed this addon, then you do not need to update it to this version (although you can if you want to). Remember that you have to quit kX Mixer in order to be able to replace the file (otherwise you will get an error about it being in use), and you do not have to re-register it, if you registered the previous version. If anyone with multiple cards tries it, please let me know if it works right. -Russ Last edited by Russ; Dec 7, 2005 at 08:41 PM. Reason: spelling :)

Dec 8, 2005, 09:59 PM	Thread Starter #36
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	BTW: I am still open to suggestions... i.e. Possibly adding more hotkeys to access higher plugin numbers. The issue with that is that I do not want to use too many (and not common one's) as they are global, if another program wants to use one of the hotkeys assigned here, it will not be able to do so. Another option is that it could be modified to use a multiplier in order to access the higher numbers using the same keystrokes. i.e. ALT-SHIFT-KEY_NUMBER could be used to set a multipler, and then CTRL-SHIFT-KEY_NUMBER would open the plugin for that KEY_NUMBER, plus ten times the multipler. i.e. (the mutiplier remains in effect until you change it). ALT-SHIFT-0 = multiplier 0. CTRL-SHIFT-2 = plugin #2 ALT-SHIFT-1 = multiplier 1. CTRL-SHIFT-2 = plugin #12 ALT-SHIFT-2 = multiplier 2. CTRL-SHIFT-2 = plugin #22 , etc. The advantage here would be that you could access numbers up to 100, without needing additonal hotkeys, but the disadvantage would be that it would require 2 sets of keystrokes if you want to open a plugin using a different multiplier. 100 is probably way more than would ever be needed, so maybe use a subset of the above (30,40,50, whatever), and use the additional ALT_SHIFT-KEY_NUMBER combos to do other things (i.e. open the DSP Window itself, or other kX windows, etc). What do you guys think? Any other ideas? -Russ Last edited by Russ; Dec 8, 2005 at 11:18 PM.

Dec 14, 2005, 04:46 AM	#43
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	Sounds cool. Do whatever you want to do. __________________ May a song always touch you in a positive way. Sonar 8.5.3 PE, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB HDD 7200 rpm, My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Dec 8, 2005, 06:30 PM	#34
PITmaster DriverHeaven Addict Join Date: Sep 2003 Posts: 266 Rep Power: 0	@Russ 3538h version works with multiple cards now But I didn't complex test, I just tryed. Do you know how to change plugin's id? I have more than 19 plugins on my kxdsp window and some of them has numbers above 20 or 30. PITmaster

Dec 8, 2005, 09:17 PM	Thread Starter #35
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Thanks PITmaster. As far as the id's go, kX just basically numbers them using the loweset available id at the time it was loaded. The only way to re-order them, would be to either clear the DSP, and load the plugins in the order that you want them to be in (as far as the id's go), or a series of unloading individual plugins, and then reloading them (i.e. if you free up a lower id, the next plugin loaded will use it).

Dec 9, 2005, 12:08 AM	Thread Starter #37
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	@Maddogg6, Just to let you know, when I first made my sb022x test plugin, I did include support for the multimedia keyboard volume keys, (because I wanted to be able to control the Master Volume using them, and that plugin replaced epilog and thus that ability). If you read the thread about that, you will see that I had mentioned it there. It worked, but on occasion kX mixer would crash, and I was never able to figure out why, so I removed that option when I released that plugin. Maybe when I have the time I will look into that again, and see if I can figure out what the problem was, and add it to a simple volume control plugin or something. In any case, I just thought I would let you know one of the reasons why I said that it is a little more complicated with plugins.

Dec 9, 2005, 09:57 AM	#38
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	Thanks Russ, It makes sense that its possible and I was pretty certain C++ was gonna be needed for the plug-in - For now I will use epilog instead of Kxlt - which is ok really. But a Vol would be nice too - Ill do some searching.. Thanks Again.

Dec 13, 2005, 11:19 PM	Thread Starter #42
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I think 100 is probably way more than is needed for the plugins, so here is my latest thinking. The ALT-SHIFT-KEY_NUMBER hotkeys are used to set the current mode (out of 10 modes). The CTRL-SHIFT-KEY_NUMBER hotkeys will have different assignements in each mode. This will allow for 100 different hotkeys to be used. I am thinking of using an .ini file to be able to customize the hotkeys for each mode. Possibilities include: Opening the tweak window for a plugin. Opening kx's 'about' window. Opening kx Mixer to a specific page. Opening the DSP window. Opening the kX Router window. Opening the Speaker Test window. Opening the kX Editor. Opening the Setup Buffers window. Opening the kX Automation window. Opening the Asio Control Panel window. Opening the OSD Notifications window. Opening the Synth Compatibility window. Opening the Driver Compatibillity window. Opening the SPDIF/I2S Status window. Opening the kX 24/96 Router window. Opening kX help. There are lots of possibilities beyond the above, I am just not sure how much would be useful. Even with the above options, 100 is probably still much more than is needed, so I may cut down on the number of modes. What do you think?

Dec 14, 2005, 10:32 AM	Thread Starter #45
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Yeah, that is a good idea, that way people can decide for themselves how many they want to use.

Dec 17, 2005, 08:31 AM	#46
TheKezReturns HardwareHeaven Lover Join Date: Apr 2005 Location: Gold Coast Australia Posts: 118 Rep Power: 42	Any chance of midi messages triggering these events as well as keys? ...once you get problems to hand sorted of course

Dec 17, 2005, 09:14 PM	Thread Starter #47
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I think it should be possible, but I am not quite sure how, and I am not quite sure such a thing would be practicle. I do not have any midi hardware (nor that type of midi software) to test such a thing out (I do not use midi all that much), nor do I know what midi messages would be good to use for this purpose. We are talking about over 100 different mappings. For the PC keyboard that is OK, because there are many possible key combinations, but I am not sure that would be so good with midi messages. Again, I do not use midi all that much and do not know a whole lot about it.

Dec 17, 2005, 11:42 PM	Thread Starter #48
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	err, scratch that... Actually it would only be 20 different mappings needed. Maybe I could add a plugin interface to it, to take advantage of the plugin API's automation stuff. It could be a plugin that uses no resources, and uses dummy parameters just to allow you to use kX Automation to map messages to simulate the PC keyboard keys, etc. That shouldn't be difficult to do. I will look into it. -Russ

Dec 19, 2005, 07:04 AM	#49
TheKezReturns HardwareHeaven Lover Join Date: Apr 2005 Location: Gold Coast Australia Posts: 118 Rep Power: 42	Awesome, I have a live setup with Ableton Live & Lemury's MX6 both hooked up to a BCF2000 midi controller which works great. I hate using the mouse on stage as it's not very visually appealing, and I have replaced mouse actions with midi wherever possible. There is no keyboard coz I don't need one. In fact the only time I ever really have to use the mouse is when I have to bring up dsp plugins windows to do some tweaking which i find a real pain in the a***. A simple press of a button on the BCF2000 would be alot easier, especially when your drunk and there's some big red light in your eyes and you can hardly make out the text on the screen thru the smoke Anway, love your work, rock on! ...ohh and the button normally send midi note on/off msgs. /Kez.

Jan 10, 2006, 06:25 AM	Thread Starter #50
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Does anyone know of a way to test kX's Automation without external midi devices? (i.e. a way to simulate it through software so that you can trigger kX Automation events). I added a plugin interface which is used for kX Automation, and as a GUI for configuring the hotkeys, and I am looking for a way to test the automation stuff.

Jan 10, 2006, 09:04 AM	Thread Starter #52
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Ok, I see how it works. All I have to do is set the midi output port to kX Control.

Jan 10, 2006, 09:27 AM	#53
Lex Nahumury DH Senior Member Join Date: Jan 2003 Location: The Netherlands Posts: 1,930 Rep Power: 62	Also; Try use MIDI OX instead of a sequencer. It's free, light weight and has a control panel/msg monitor The ideal tool for quick MIDI msg generation/testing/development etc.

Jan 10, 2006, 11:25 AM	Thread Starter #54
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I will check it out. Thanks for the info.

Jan 10, 2006, 11:03 PM	Thread Starter #55
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I added a new test version (currently 3538i only) to the second download site (link in first post of this thread). The zip file contains the addon and the plugin (as well as the unregister reg script, in case of problems, use the reg script to unregister the addon, the plugin, and delete the settings). This versions works as follows: ALT-SHIFT-NUM_KEY sets the mode (1-10) CTRL-SHIFT-NUM_KEY performs the actions assigned to that key for the current mode. This gives 100 hotkeys. The addon can now be used not only for tweak windows but also for opening various kX windows, and toggling/changing a few kX hardware parameters. The addon menu item can be used to enable/disable the hotkeys (also indicates the current mode). If the menu item is checked (the default state), it means that it is enabled. The plugin part is used for kX Automation and for configuring the key assignments. If you do not use kX Automation, then you do not need to load the plugin (except if you want to re-assign the keys, after which you can unload the plugin again if you want). Changes made to key assignments are not saved until you click on the save button (including setting the defaults (i.e. to set defaults, click Set Defaults, and then click Save Settings, etc). The mode combo box selects the configuration page for the mode selected. You can modify individual pages without saving (i.e. you will not lose changes to a page by changing to another page, the settings are held, they are just not saved/used until the Save Settings button is clicked). Setting defaults, resets all pages (again not saved until you manually save). Closing the plugin window will cause any unsaved changes to be lost (this way whenever you open the tweak window, you know that the settings listed are always the current settings). The addon does not need to be loaded or enabled to make changes to the settings. Installation is the same as it was with the previous versions (see previous posts). Again, this is a test version. I could not test everything out myself (i.e. mutiple card seups under kX, and I only did some basic testing with the kX Automation, etc), so there may be some bugs.

Jan 11, 2006, 01:08 AM	Thread Starter #56
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I added the 3538h version for testing as well (also only available from the secondary download link).

Jan 11, 2006, 02:42 AM	#57
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	@Russ - Ive been playing with this (finally - I had it loaded and forgot about it - ?? :S) It works well and IS quite handy - Another fine release from 'RussWare' KX V3538h - Audigy 2ZS Platinum SB0350 Kudos... Did you figure on which way to handle #'s > 10 ? No rush, just curious...

Jan 11, 2006, 04:23 AM	#59
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	Yeah - I figurued it out right after post.. .doh! I first read it as ALT+SHIFT+CTRL - sheesh! IT WORKS GREAT! Whoo hoo! Damn 'online speed reading' course was a waste :S.

Jan 11, 2006, 04:33 AM	Thread Starter #60
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	BTW: I forgot to mention something: I am not sure what will happen if you try to use a feature not supported by your card, so be wary of any such features. i.e. If your card is a 4.0 card, I am not sure what might happen if you use the 'Toggle Route HP To Center/Sub' option, etc. Hopefully it will do nothing, but I cannot be sure, so be careful with such options.