PluginQL -- A kX Addon

PITmaster · Jan 12, 2006, 03:27 PM

Hmm, I just successfully simulate this behaviour of combobox in Delphi. It happens when Constraints.MaxHeight property is not EQ 0 and LT 42.

So how it looks in your sources of PluginQL, Russ?

PITmaster

Russ · Jan 13, 2006, 12:09 AM

I do not use Delphi and it does things a little differently.
In any case I updated the plugin code to give it a larger dropdown height. Give it a try and see if it makes a difference for you. Everything else is the same, so you only need to replace the plugin with the newer one. When you download the zip file, make sure that you do not get a cached version of the older one (since it is the same name, etc), the date on the plugin should be todays date.

BTW: Regarding the number order, did you want both the keys and the modes to be 0-9, or just the modes (remember that there is no plugin number 0)?

thomasabarnes · Jan 13, 2006, 03:40 AM

Ah Russ the update is nice! Working great here. No problems. Thanks for the work.

Maddogg6 · Jan 13, 2006, 07:40 AM

I missed this one too - seems like we post at same times and gets mish-mashed somehow.. hehe.

Quote:

Originally Posted by Russ

If it is just a matter of closing the window after accidentally opening the wrong one, ALT-F4 should work for any window (and ALT-TAB to switch between open windows).

This is true - but it is faster if keeping fingers on same key to close the window just opened - I guess I figure many use multiple DSPs - I have a DSP for a sonar project alone - memorizing keys may not be possible. So 'guessing' keys for tweak windows is qute convenient.
I find I end up with 6-7 open windows and end up clicking on all - thus the 'close all KX; would be nice - just assign it to the same 'key#' in all modes.
This would definitly help when using multiple DSPs.

Quote:

Originally Posted by Russ

As for the open/close toggle, another possible option is to have that as a seperate item in the ComboBoxes. i.e. Have one option work as it does now, and a seperate one that is an open/close toggle. That way people could decide for themselves which way they prefer.

As for closing all kX Windows, I did see a close_all_windows function in there, so that might be possible.

Im not understanding the idea here...

BUT...
If toggle is too much pain for partial implementation - the 'close all' is a very near second. . IMHO . It adds great convenience when using multiple dsps -
How about 'close ALL KX' with an 'except' dropdown.

'Except' drop down List contents:
Kx Mixer - any
Kx Mixer - Ins & Outs
..
..
KX Mixer - Kx Console
KX DSP

This would add some flexibility - even if just by default 'close all KX except DSP' window - which, if using multiple dsp's, and this window may be open/minimized frequently, leaving the DSP window opened/minimized would be very helpful.
But - if not, just close all would be great also...

PITmaster · Jan 13, 2006, 08:22 AM

@Russ

Thanks! Now all comboboxes works fine

So I have a little ask, to Eugene I guess, to check comboboxes in Synth Comparibility window and in kX Router 24/96 window and fix this issue with final version.

I can agree with your mode order, I think. I've just got I can define any plugin ID for every shortkey

About card ID. I've just thought out better solution - to assign card ID for every mode. Then, for ex. modes 1-5 may works with card1 and modes 6-0 with card2. Has card ID to be changed in Device setings before opening right plugin?

PITmaster

Maddogg6 · Jan 13, 2006, 10:27 AM

Also..

I prolly sound soooo needy or something, I'm not really - like I said before, I have no expectations - but I do have tons of ideas/suggestions...

Soo..

PRESET! - ability to save key maps is a definite need.

This must be a bug - as, not that Im playing with it - my changes arent saved in DSP config... and now I notice theres no presets for the plugin to save.

Russ · Jan 14, 2006, 12:42 AM

Quote:

Originally Posted by PITmaster

I can agree with your mode order, I think. I've just got I can define any plugin ID for every shortkey

About card ID. I've just thought out better solution - to assign card ID for every mode. Then, for ex. modes 1-5 may works with card1 and modes 6-0 with card2. Has card ID to be changed in Device setings before opening right plugin?

Right, we are really only talking about what the default settings are (and which number appears next to the menu item to indicate the mode, 0 or 10), as you can configure the modes (and the keys for that matter) as if they are numbered 0-9 if you like.

Regarding the card ID, basically the way it works now, is that everyrthing is done using the currently selected device. Of course I can select the device number programmatically, but as not everyone has mutiple card setups, I am not sure how I would want to handle that (different devcies for different keys. I will have to think about it.

BTW: Can you work with different devices at the same time? i.e. Can you have a tweak window opened for a plugin used with one device, and a tweak window opened for a plugin used with another device at the same time?

Russ · Jan 14, 2006, 12:44 AM

Quote:

Originally Posted by thomasabarnes

Ah Russ the update is nice! Working great here. No problems. Thanks for the work.

Thanks, Glad to hear it

Russ · Jan 14, 2006, 01:19 AM

@Maddogg6,

What I meant is, possibly having one item in the comboboxes be "Open Plugin#", and another option being "Toggle Open/Close Plugin#", that way people can choose which way they would like it to work.

Technically, I really should not be opening the tweak windowss for plugins like FxBus, epilog, etc, as technically they do not have tweak windows. That is a bad thing that I am doing, but currently kX doesn't complain about it, and it does not seem to cause problems (currently), but I really should not be doing that, so I may change that behavior anyway.

As for the close all windows thing... Adding an exception would be more difficult to do. I would be using the close_all_windows() API function, so it would work based on how that function works (which I have not even tried as of yet, so at the moment I cannot even be completely sure that it really means all windows).

As for presets, I intentionally left that out as I did not think that it really made sense for this (it is really an addon and not a plugin.). The plugin part was really just to make automation easy, and since it had GUI stuff built in, I decided to use it as a configuration GUI too, but it does not work like a regular plugin. The settings are currently global settings (as the addon is a global addon). You would not have 2 instances of the plugin loaded, each using different presets. I think if anything, that maybe being able to save different settings along with the kX configs might make sense, but I am not sure that presets make sense here.

Maddogg6 · Jan 14, 2006, 03:32 AM

Ah ok - the OPEN or OPEN/CLOSE choice seems best way - yeah - that should be good too.

Well - I can understand that, if the kx mixer windows would change - ie, a user making a 'fix' to the dsp, can throw off all the factory 'preset' key map.

I was just presenting 2 possible directions to accomplish same 'convenience' in such instances. So if close all with exception is not practical - the above way is a winner, ..

But saving as globals / config is whats desired anyway - I wasnt thinking of the addon thing - it makes sense thst its different.

Edit: I was trippin...

Its an awesome addon already - [Raises Mug of Beer]

Russ · Jan 14, 2006, 04:05 AM

Regarding saving different settings with different configs... I am not sure how that works with Addons, so I will have to look into it. I have not seen any addon settings in any of the config files as of yet, so I am not completely sure it is possible to do it like that.

Maddogg6 · Jan 14, 2006, 06:22 AM

Quote:

Originally Posted by Russ

Regarding saving different settings with different configs... I am not sure how that works with Addons, so I will have to look into it. I have not seen any addon settings in any of the config files as of yet, so I am not completely sure it is possible to do it like that.

This is easy to live without - the open - open/close window thing is much more desirable.

Russ · Jan 14, 2006, 07:52 AM

Ok, It was a good thing to look into anyway, as that is what led to figuring out the 3538i drum thing. I was reading the config file looking for any sections that might contain addon data, and saw the midi drum channel setting, and that got me thinking about that issue again.

I will add the open/close toggle in one way or another. I am not sure as of yet if I will do it for all kX windows or just plugins, or what, but I will at least do it for plugins that have a tweak window ( plugins that return something other than "None" for get_user_interface() ).

PITmaster · Jan 14, 2006, 11:11 AM

Quote:

Originally Posted by Russ

BTW: Can you work with different devices at the same time? i.e. Can you have a tweak window opened for a plugin used with one device, and a tweak window opened for a plugin used with another device at the same time?

Yes, it's possible.

PITmaster

Russ · Jan 14, 2006, 11:33 AM

Quote:

Originally Posted by PITmaster

Yes, it's possible.

PITmaster

Ok, thanks for the info.

Russ · Jan 21, 2006, 04:10 PM

BTW: You should uninstall this addon (using the .reg file) before installing any kX updates as it may not be compatible with newer kX versions.

The .reg file also removes the settings, so if you want to save the settings, back up the following registry key (before using the .reg file): HKEY_CURRENT_USER\Software\kX\PluginQL_Addon

Smiro · Feb 25, 2006, 08:51 PM

How bout a version for the 3538j ?

I tried the latest beta from your site but doesn't seem to work.

Russ · Feb 25, 2006, 11:08 PM

I have been busy testing some other things out, so I haven't had a chance to work on this lately. I think it should work with 3538j, as the kX API did not change much from 3538i (3538i plugins work in 3538j), but have not tested it as of yet. In any case, I will update it when I have a chance.

thomasabarnes · Feb 26, 2006, 08:11 AM

The .3538i version doesnt seem to work with .3538j. There are 2 files in the .zip, do we need to move one or both anywhere?

Russ · Feb 26, 2006, 08:51 AM

Ok, I tested the 3538i version and it does not work with 3538j. I will have to go through the SDK code and run some tests to see what changed.

Russ · Feb 26, 2006, 10:52 AM

I figured out what is going on with 3538j.
It appears that init() is fixed for addons, but now load_settings() does not get called automatically, and that is why is is not working. In any case, I can call load_settings() manually, and it works.

Last time I was working on this, I was playing around with the open/close plugin window toggle, but then I stopped to wait and see if there was going to be any changes in 3538j that would affect this, so I have not implemented some of the things I wanted to, as of yet.

For the time being, I can either make the 3538j version the same as the 3538i version, or I can make it so that the tweak_plugin option is a toggle (which means that it will only open/close plugin windows that have a real tweak window (i.e. it will not open the tweak window for plugins like epilog, FxBus, Prolog, etc, but those windows can still be opened using the other options), and it will work as an open/close toggle (again the toggle is only for plugin tweak windows)). Which way would you guys prefer it to be for now?

BTW: Regarding the 3538h and 3538i versions, is there any reason to keep those versions around?

thomasabarnes · Feb 26, 2006, 05:28 PM

Anyway is good Russ, and I think it's a good idea to keep 3538h around. hehe 3538h is the best 3538 driver version that windows 98 users can use.

Smiro · Feb 26, 2006, 06:02 PM

Quote:

Originally Posted by Russ

For the time being, I can either make the 3538j version the same as the 3538i version, or I can make it so that the tweak_plugin option is a toggle (which means that it will only open/close plugin windows that have a real tweak window (i.e. it will not open the tweak window for plugins like epilog, FxBus, Prolog, etc, but those windows can still be opened using the other options), and it will work as an open/close toggle (again the toggle is only for plugin tweak windows)). Which way would you guys prefer it to be for now?

Personally i want this plugin so that i open my MX6 without right click on task bar, dsp, ecc.

So either way would work for me

Russ · Feb 26, 2006, 06:41 PM

Quote:

Originally Posted by thomasabarnes

Anyway is good Russ, and I think it's a good idea to keep 3538h around. hehe 3538h is the best 3538 driver version that windows 98 users can use.

I am not sure that is true. I tried 3538h on Windows ME and it wasn't reliable. I couldn't load the majority of the plugins, because the effects menu would crash kX when trying to display any submenu's (for plugin categories like Default, Basic, ..., ProFX, EFX, etc). IIRC, Max M. stated that any 3538 version has significant incompabilities with Win98SE / WinME, and that 3537 is the lastest version that should be used with those OS's. With that in mind, the only reason I could think to use 3538h, is if you have Win98SE / WinME , and your card doesn't work in 3537 (but does in 3538h). In any case, I guess, I will keep the 3538h version around for a while but I am pretty sure that there is no need for the 3538i version, so I will probably get rid of that.

thomasabarnes · Feb 26, 2006, 07:48 PM

Quote:

Originally Posted by Eugene Gavrilov

hello, guys

a small poll: how about removing win98se support from the drivers?
this will make the final package appr. 1Mb smaller and will simplify certain parts of the driver as well... of course, any pre-3538i versions will keep working fine

E.

That's a quote from this thread: http://driverheaven.net/showthread.p...ht=win+support

I'm saying 3538h is the best version for win 98 support because technically it's the last version (and best ASIO performance) release that is suppose to work with Win 98. Chit man, people encounter bugs every now and then. But, tecnically, 3538h is the last kx version that Win 98 users should be able to use.

Just trying to look out for thos Win 98 users. But this addon is your creation. Do what you want to do.

Russ · Feb 26, 2006, 08:42 PM

I added the 3538j version to the download pages. I went for the version with the open/close toggle for now (otherwise it should be the same as the previous version). I haven't done a lot of testing with it as of yet, so as usual, there may be some bugs.

Again, to install:
Place the plugin and addon wherever you want them to stay on your hard drive.
Install the plugin as with any other plugin.
For the addon, regisiter the addon, and then restart kX mixer (if you are overwirting a previous version, make sure kx mixer is closed first, as it cannot overwrite the file while it is in use).

The addon does the actual handling of the hotkeys, so it needs to be loaded (and enabled) for the hotkeys to work.
The plugin serves as a GUI to configure the addon, and is used for kX automation. It only needs to be loaded when you want to change the settings, or use kX automation to control the addon.

thomasabarnes · Feb 26, 2006, 09:41 PM

Thank you Russ. It's working good here.

Russ · Feb 26, 2006, 09:43 PM

Quote:

Originally Posted by thomasabarnes

Thank you Russ. It's working good here.

Thanks

Let me know if you have any problems, etc.

thomasabarnes · Feb 26, 2006, 09:58 PM

BTW, it's great how the Plugin works so we can have Ctrl Shift# to open any Object number in the DSP. This is a great job you have done. Really thanks!

Russ · Feb 26, 2006, 11:17 PM

BTW: I haven't forgotten about people's suggestions, etc.
I still have a bunch of things on the TODO list for this.
i.e.
Open/Close toggle as an option.
A close all kX windows option (still need to test this).
Card selection option for multicard setups.
Saving different settings for different configs.
etc.

Jan 13, 2006, 12:09 AM	Thread Starter #92
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I do not use Delphi and it does things a little differently. In any case I updated the plugin code to give it a larger dropdown height. Give it a try and see if it makes a difference for you. Everything else is the same, so you only need to replace the plugin with the newer one. When you download the zip file, make sure that you do not get a cached version of the older one (since it is the same name, etc), the date on the plugin should be todays date. BTW: Regarding the number order, did you want both the keys and the modes to be 0-9, or just the modes (remember that there is no plugin number 0)? Last edited by Russ; Jan 13, 2006 at 12:18 AM.

Jan 13, 2006, 03:40 AM	#93
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	Ah Russ the update is nice! Working great here. No problems. Thanks for the work. __________________ 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

Jan 13, 2006, 08:22 AM	#95
PITmaster DriverHeaven Addict Join Date: Sep 2003 Posts: 266 Rep Power: 0	@Russ Thanks! Now all comboboxes works fine So I have a little ask, to Eugene I guess, to check comboboxes in Synth Comparibility window and in kX Router 24/96 window and fix this issue with final version. I can agree with your mode order, I think. I've just got I can define any plugin ID for every shortkey About card ID. I've just thought out better solution - to assign card ID for every mode. Then, for ex. modes 1-5 may works with card1 and modes 6-0 with card2. Has card ID to be changed in Device setings before opening right plugin? PITmaster Last edited by PITmaster; Jan 13, 2006 at 09:53 AM.

Jan 14, 2006, 03:32 AM	#100
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	Ah ok - the OPEN or OPEN/CLOSE choice seems best way - yeah - that should be good too. Well - I can understand that, if the kx mixer windows would change - ie, a user making a 'fix' to the dsp, can throw off all the factory 'preset' key map. I was just presenting 2 possible directions to accomplish same 'convenience' in such instances. So if close all with exception is not practical - the above way is a winner, .. But saving as globals / config is whats desired anyway - I wasnt thinking of the addon thing - it makes sense thst its different. Edit: I was trippin... Its an awesome addon already - [Raises Mug of Beer] Last edited by Maddogg6; Jan 14, 2006 at 04:02 AM.

Jan 14, 2006, 04:05 AM	Thread Starter #101
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Regarding saving different settings with different configs... I am not sure how that works with Addons, so I will have to look into it. I have not seen any addon settings in any of the config files as of yet, so I am not completely sure it is possible to do it like that. Last edited by Russ; Jan 14, 2006 at 04:45 AM.

Jan 12, 2006, 03:27 PM	#91
PITmaster DriverHeaven Addict Join Date: Sep 2003 Posts: 266 Rep Power: 0	Hmm, I just successfully simulate this behaviour of combobox in Delphi. It happens when Constraints.MaxHeight property is not EQ 0 and LT 42. So how it looks in your sources of PluginQL, Russ? PITmaster

Jan 13, 2006, 10:27 AM	#96
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	Also.. I prolly sound soooo needy or something, I'm not really - like I said before, I have no expectations - but I do have tons of ideas/suggestions... Soo.. PRESET! - ability to save key maps is a definite need. This must be a bug - as, not that Im playing with it - my changes arent saved in DSP config... and now I notice theres no presets for the plugin to save.

Jan 14, 2006, 01:19 AM	Thread Starter #99
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	@Maddogg6, What I meant is, possibly having one item in the comboboxes be "Open Plugin#", and another option being "Toggle Open/Close Plugin#", that way people can choose which way they would like it to work. Technically, I really should not be opening the tweak windowss for plugins like FxBus, epilog, etc, as technically they do not have tweak windows. That is a bad thing that I am doing, but currently kX doesn't complain about it, and it does not seem to cause problems (currently), but I really should not be doing that, so I may change that behavior anyway. As for the close all windows thing... Adding an exception would be more difficult to do. I would be using the close_all_windows() API function, so it would work based on how that function works (which I have not even tried as of yet, so at the moment I cannot even be completely sure that it really means all windows). As for presets, I intentionally left that out as I did not think that it really made sense for this (it is really an addon and not a plugin.). The plugin part was really just to make automation easy, and since it had GUI stuff built in, I decided to use it as a configuration GUI too, but it does not work like a regular plugin. The settings are currently global settings (as the addon is a global addon). You would not have 2 instances of the plugin loaded, each using different presets. I think if anything, that maybe being able to save different settings along with the kX configs might make sense, but I am not sure that presets make sense here.

Jan 14, 2006, 07:52 AM	Thread Starter #103
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Ok, It was a good thing to look into anyway, as that is what led to figuring out the 3538i drum thing. I was reading the config file looking for any sections that might contain addon data, and saw the midi drum channel setting, and that got me thinking about that issue again. I will add the open/close toggle in one way or another. I am not sure as of yet if I will do it for all kX windows or just plugins, or what, but I will at least do it for plugins that have a tweak window ( plugins that return something other than "None" for get_user_interface() ).

Jan 21, 2006, 04:10 PM	Thread Starter #106
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	BTW: You should uninstall this addon (using the .reg file) before installing any kX updates as it may not be compatible with newer kX versions. The .reg file also removes the settings, so if you want to save the settings, back up the following registry key (before using the .reg file): HKEY_CURRENT_USER\Software\kX\PluginQL_Addon

Feb 25, 2006, 08:51 PM	#107
Smiro DriverHeaven Junior Member Join Date: Feb 2003 Posts: 31 Rep Power: 0	How bout a version for the 3538j ? I tried the latest beta from your site but doesn't seem to work.

Feb 25, 2006, 11:08 PM	Thread Starter #108
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I have been busy testing some other things out, so I haven't had a chance to work on this lately. I think it should work with 3538j, as the kX API did not change much from 3538i (3538i plugins work in 3538j), but have not tested it as of yet. In any case, I will update it when I have a chance.

Feb 26, 2006, 08:11 AM	#109
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	The .3538i version doesnt seem to work with .3538j. There are 2 files in the .zip, do we need to move one or both anywhere? __________________ 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

Feb 26, 2006, 08:51 AM	Thread Starter #110
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Ok, I tested the 3538i version and it does not work with 3538j. I will have to go through the SDK code and run some tests to see what changed.

Feb 26, 2006, 10:52 AM	Thread Starter #111
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I figured out what is going on with 3538j. It appears that init() is fixed for addons, but now load_settings() does not get called automatically, and that is why is is not working. In any case, I can call load_settings() manually, and it works. Last time I was working on this, I was playing around with the open/close plugin window toggle, but then I stopped to wait and see if there was going to be any changes in 3538j that would affect this, so I have not implemented some of the things I wanted to, as of yet. For the time being, I can either make the 3538j version the same as the 3538i version, or I can make it so that the tweak_plugin option is a toggle (which means that it will only open/close plugin windows that have a real tweak window (i.e. it will not open the tweak window for plugins like epilog, FxBus, Prolog, etc, but those windows can still be opened using the other options), and it will work as an open/close toggle (again the toggle is only for plugin tweak windows)). Which way would you guys prefer it to be for now? BTW: Regarding the 3538h and 3538i versions, is there any reason to keep those versions around?

Feb 26, 2006, 05:28 PM	#112
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	Anyway is good Russ, and I think it's a good idea to keep 3538h around. hehe 3538h is the best 3538 driver version that windows 98 users can use. __________________ 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

Feb 26, 2006, 08:42 PM	Thread Starter #116
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	I added the 3538j version to the download pages. I went for the version with the open/close toggle for now (otherwise it should be the same as the previous version). I haven't done a lot of testing with it as of yet, so as usual, there may be some bugs. Again, to install: Place the plugin and addon wherever you want them to stay on your hard drive. Install the plugin as with any other plugin. For the addon, regisiter the addon, and then restart kX mixer (if you are overwirting a previous version, make sure kx mixer is closed first, as it cannot overwrite the file while it is in use). The addon does the actual handling of the hotkeys, so it needs to be loaded (and enabled) for the hotkeys to work. The plugin serves as a GUI to configure the addon, and is used for kX automation. It only needs to be loaded when you want to change the settings, or use kX automation to control the addon.

Feb 26, 2006, 09:41 PM	#117
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	Thank you Russ. It's working good here. __________________ 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

Feb 26, 2006, 09:58 PM	#119
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,373 Rep Power: 58 System Specs	BTW, it's great how the Plugin works so we can have Ctrl Shift# to open any Object number in the DSP. This is a great job you have done. Really thanks! __________________ 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

Feb 26, 2006, 11:17 PM	Thread Starter #120
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	BTW: I haven't forgotten about people's suggestions, etc. I still have a bunch of things on the TODO list for this. i.e. Open/Close toggle as an option. A close all kX windows option (still need to test this). Card selection option for multicard setups. Saving different settings for different configs. etc.