MIDI drums DO work in 3538i !!!

Russ · Jan 14, 2006, 03:36 AM

I have just discovered that you can get midi drums to work with 3538i and the kX Synths.

If you read my post in the 3538i bug thread, you are aware that there is a new kX Hardware Setting for setting the drum channel (that unfortunatley seems to keep resetting to 0).

Well I decided to see what would happen if I edited one of the config files (must be a config file that had 'Hardware' checked when it was saved) and manually set the drum channel to 10 (0xA), and then load that config. I did this and then re-selected the kX Synth as my midi port in my midi software, and guess what, the drums worked!!!

I then tried rebooting and unfortuantley it did not last through a reboot (kX re-saves the settings to the registry and unfortunatley seems to write back 0 again).

I then tried another go at using kX Console to set the drum channel to 10, and realized that it was working (somewhat).

If you set the drum channel to 10, and re-select the midi port in your software it works. The keys here are that you should not read back (-ghw) the value, as that seems to break it, and to re-select the midi port in your midi software. Also, this seems to only need to be done once, so long as you do not do something to break it, it seems to stick (i.e. close and re-open the midi software, it still works without having to re-select the midi port each time).

So, after booting, you should be able to use kX Console (kxctrl -shw 21 0xA), or load a saved config (and then re-select the midi port in the midi software once), and have working midi drums with the kX Synth's in kX 3538i.

I still have to do some more testing to try and get a setup that does some of this automatically (i.e. I have not tried using a batch file, or modifying the kx startup command line arguments as of yet to see if I can get it to work automatically, nor have I found a way that does not require re-selecting the midi port at least once), but I want to share this info as soon as possible, as I think this should make some people happy.

Maddogg6 · Jan 14, 2006, 03:48 AM

well, hell Russ -you figured out the hard part -- seems liek a bat file in the startup start menu - that calls a .reg file - and 'kxctrl -shw 21 0xA' - all at boot up..
No?

Russ · Jan 14, 2006, 03:51 AM

Yup, a simple batch file should work (no .reg file necessary), I just haven't tested it as of yet.

Russ · Jan 14, 2006, 04:10 AM

BTW: The 're-selecting the MIDI port' thing may not always be necessary. I just tried doing the following from the 'RUN' line.

kxctrl.exe -shw 21 0x0

I then opened the midi software and tested it and had no drums.

Then I tried setting the drum channel to 10 (again from the 'RUN' line).

kxctrl.exe -shw 21 0xA

I again opened the midi software and tested it, and had working drums, without having to re-select the midi port.

So it seems that the thing with having to re-select the midi port may depend on the midi software itself (i.e. how it initializes the midi port when it first opens), and the method that you use to set the drum channel to 10.

So it seems that it may be possible using batch files to get it work with minimum hassle.

Russ · Jan 14, 2006, 04:56 AM

Ok, I tried using a simple bat file in the startup folder and it did not work. Unfortunatley, I cannot make sure that it executes only after kxmixer has finsished loading and restored settings (I could probably add a bunch of pauses, etc, but that is not a great solution). I am thinking that maybe a simple addon or plugin, that does nothing more than set the drum channel to 10 might work better (as it should only execute it's code after kxmixer has finished loading), I will have to give it a try.

BTW: With mutiple card setups, you proabably would have to set the drum channel to 10 for each device.

Maddogg6 · Jan 14, 2006, 05:07 AM

Maybe... .. This command CAN ONLY be sent after FIRST attempting to open the midi port? Is this possibly the case? - I dunno - just throwing out ideas...

Russ · Jan 14, 2006, 05:26 AM

Quote:

Originally Posted by Maddogg6

Maybe... .. This command CAN ONLY be sent after FIRST attempting to open the midi port? Is this possibly the case? - I dunno - just throwing out ideas...

I do not think so, but I am still figuring out the details. I think that reselecting the midi port is only necessary if the midi software was open when you tried changing the drum channels (in which case closing/reopening the midi software should have the same effect). That is what my current testing is pointing towards anyway...

I tried making a simple plugin to do this, but again it did not work after booting, so I think kxmixer loads the plugin before it finishes restoring settings. I will try some more things out, but you may just have to execute a simple kxctrl command after kxmixer finishes it startup process, which really is not a big deal to do.

Maddogg6 · Jan 14, 2006, 05:30 AM

I will install i and see how it is - doesnt sound too painful to get drums working again..

Maddogg6 · Jan 14, 2006, 05:32 AM

WHAT IF - you replace the kx mixer registery entry for startup with a bat file that first loads KX mixer THEN the KXCTRL command.. thats should work no?

thomasabarnes · Jan 14, 2006, 05:33 AM

Good news Russ! Us not to sharp kX users will need some kind of Getting MIDI Drums To Work Using 3538i For Dummies fix.

So I'll keep following this thread to see what you end up with.

Thanks for the info!

Russ · Jan 14, 2006, 05:39 AM

Quote:

Originally Posted by Maddogg6

WHAT IF - you replace the kx mixer registery entry for startup with a bat file that first loads KX mixer THEN the KXCTRL command.. thats should work no?

No, you run into the same problem.

There are 2 ways you can execute a program from a cmd bat file:

1)
The program will run, and the bat file will not execute the next command until the program exits. This method will not help at all.

2) The program will run, and the bat file will immediatley execute the next command (i.e. multiple threads). This method will work to execute kxctrl after kxmixer, but there is no way to wait until kxmixer finishes loading and restoring settings, before moving to the next command, so kxctrl will start too quickly. Again, adding a bunch of pauses may work, but it may not be the best solution.

Russ · Jan 14, 2006, 05:46 AM

Quote:

Originally Posted by thomasabarnes

Good news Russ! Us not to sharp kX users will need some kind of Getting MIDI Drums To Work Using 3538i For Dummies fix.

So I'll keep following this thread to see what you end up with.

Thanks for the info!

It is pretty easy, and it would be good if other people could verify my results.

I think the easist method would be as follows:

Close any applications that might be using the midi port.
Execute the following from the 'Run' line on the 'Start' menu:
kxctrl.exe -shw 21 0xA

Open your midi software and play a song that has a drum track (on channel 10) and see if it works. If for some reason it does not work, try re-choosing which port the midi software uses for output (should be one of the kX Synth's), and then start the song again, and see if it works this time.

That is about all there is to it.

Maddogg6 · Jan 14, 2006, 05:52 AM

Well. maybe no sense banging head against brick wall when Eugene indicated a new release soon.. ?? But kudos on finding the problem...

Russ · Jan 14, 2006, 06:13 AM

Yes that is true, but you can never be sure how soon is soon (there was an indication about sometime in January, but you never know what problems he might run into that may push off the target date).

I only wish I figured it out sooner, as I did test the drum channel thing before, but I guess I kept making the same mistakes in my initial testing. I either, read back the value (which seems to make it not work), or I had my MIDI software open when trying (and did not try reselecting the port or closing/re-opening the program) or some combination of both. During my initial testing this time, I did the same thing, I had my MIDI program open during the test, but I happened to have the MS Synth selected for the drums, so I had to select the kX Synth, and that made it work (otherwise I may have missed it again), and after some more quick tests to ensure that I could consistantly get it to work, I posted the message to let others know.

Maddogg6 · Jan 14, 2006, 06:22 AM

I just tried to D/L 3538i - and DH wants me to DISABLE MY FIREWALL - um.. WTF!
I dont think so. Ill need to find my archive - I know I have it on a disk somewhere.. but DAMN! get real, turn off your firewall - This seems VERY UN-NECESSARY. - Anti-leach or not..

thomasabarnes · Jan 14, 2006, 06:25 AM

Russ:

The kxctrl.exe -shw 21 0xA command run from the Run box did it, but it has to be done again after a PC restart. Oh yeah, I didnt have to reselect the MIDI port either.

I'm glad you figured this out, and I think it's good for us to know this because as you say Eugene may get busy and the release date for the new driver version may be delayed.

Thanks, and it would be even better if you can figure out a way so this command can be run auotmatically at restart (after the kX Mixer loads right?).

Russ · Jan 14, 2006, 06:26 AM

Quote:

Originally Posted by Maddogg6

I just tried to D/L 3538i - and DH wants me to DISABLE MY FIREWALL - um.. WTF!
I dont think so. Ill need to find my archive - I know I have it on a disk somewhere.. but DAMN! get real, turn off your firewall - This seems VERY UN-NECESSARY. - Anti-leach or not..

Hmm, I wonder what firewall setting triggers that. I have no such problem. In any case, do not feel that you have to install it for my sake, I am sure other people will test it out.

Quote:

Originally Posted by Maddogg6

I will install i and see how it is - doesnt sound too painful to get drums working again..

Doh, missed another post... I hate when that happens

In any case, I would have replied with the same answer as above anyway...

Russ · Jan 14, 2006, 06:33 AM

Quote:

Originally Posted by thomasabarnes

Russ:

The kxctrl.exe -shw 21 0xA command run from the Run box did it, but it has to be done again after a PC restart. Oh yeah, I didnt have to reselect the MIDI port either.

I'm glad you figured this out, and I think it's good for us to know this because as you say Eugene may get busy and the release date for the new driver version may be delayed.

Thanks, and it would be even better if you can figure out a way so this command can be run auotmatically at restart (after the kX Mixer loads right?).

Yes, after kX Mixer loads...

Good stuff, thanks for verifying my results.
I will keep trying to see if I can figure something out (I still have some ideas that might do the trick..).

BTW:
Other times where you may have to repeat the command is, when loading a saved config that saved the hardware setiings (although if you edit it and change it to use channel 10, than I think it will work), or possibly when changing devices when using multi-card setups, etc.

Maddogg6 · Jan 14, 2006, 06:46 AM

DAMN! - what about re-compiling KX MIXER - to send that command in its code... ?? I know- I'm strecthing...

Maddogg6 · Jan 14, 2006, 06:49 AM

OR is there a cmd line param for KX Mixer to send that command also.. ??

Maddogg6 · Jan 14, 2006, 06:55 AM

OK - ALSO - the reason I thought of the REG file - is to PUT that setting into the registery if the kxctrl ran before mixer finishes loading - I assumed those settings was being read from the registry - and turning off ch10 drums also from those settings... ??

I thought would cover both bases running kxctrl AND changing registry - depending on if kx mixer finished loading or not - no matter - the right setting would have been read from the registry - but I now assume this setting is not stored in the registry.. .

Im dumb with this stuff... but I try.. lol

Russ · Jan 14, 2006, 07:00 AM

Well we cannot recompile kxmixer (we do not have the source code), and I do not know of any startup commands to do it.

One possiblilty might be, to not have kxmixer restore the settings from the rsgistry at all, and to just load an edited config file instead. I do not know, there are lots of things to try. I was also trying to see if changing the setting in the registry would help (as that is what kxmixer uses at startup), but I did not have any luck, but I will have to redo some of my testing anyway, to be sure I did not make any mistakes in my testing (as we have allready figured out some more things since I originally posted the message, and did some of my initial testing).

Russ · Jan 14, 2006, 07:03 AM

Quote:

Originally Posted by Maddogg6

OK - ALSO - the reason I thought of the REG file - is to PUT that setting into the registery if the kxctrl ran before mixer finishes loading - I assumed those settings was being read from the registry - and turning off ch10 drums also from those settings... ??

I thought would cover both bases running kxctrl AND changing registry - depending on if kx mixer finished loading or not - no matter - the right setting would have been read from the registry - but I now assume this setting is not stored in the registry.. .

Im dumb with this stuff... but I try.. lol

You typed this while I was responding to your previous messages, and I answered some of this in that reply, but...

That is not dumb, it is a good idea, and it is (I am pretty sure, but not absolutley positive) what kX uses for startup. It is just that my initial testing covered that (it was one of the first things I tried) and it did not work, but again, I will have to repeat some of my testing.

Maddogg6 · Jan 14, 2006, 07:43 AM

Ok - I installed i - and I see that - I DO have to open sonar FIRST - then send KXCTRL command - disable/re-enable KX Synth Midi driver..

Sending command BEFORE sonar starts doesnt work for me.
At sonar startup - it re-sets that param back to 0 again.

So it seems initial-initialization of the midi ports re-sets that param -
if its too much pain in ass - I may revert back to h - no problem... Im learning anyway...

a simple batch file to run after sonar starts is a small price - for now anyway, depending on how improved 'i' is over 'h' in other areas.. hehe

Good work finding this one Russ..

Russ · Jan 14, 2006, 07:58 AM

Hmm, that is not the case for me, but I cannot test Sonar as I do not have it.

I had no luck with the registry settings... Something overwrites that value during kX startup.

I did however look at some of the kx debug messages during startup, and I noticed that plugins get loaded quickly, but addons seem to be loaded last. I decided to try again with an addon this time and it worked. I rebooted, logged on, opened my midi software and the drums worked, so that may be the best solution. Addionally, if I make it a per-device addon, then it will probably work for multi-card setups as well (provided that they load the addon for both devices).

thomasabarnes · Jan 14, 2006, 08:14 AM

Let me say again that using the kxctrl.exe -shw 21 0xA command works for me, but it has to be done again after a PC restart, and I didnt have to reselect the MIDI port either. With SONAR closed, I ran the command, opened SONAR and load a MIDI file, played it and the drums work. I closed SONAR, did a restart of PC, opened SONAR opened a MIDI file, drum dont work. Closed SONAR, ran the command, opened SONAR, load MIDI file Drums work.

I dont know why it's not working for Maddogg. Is he using a different command, cause you did post 2 commands earlier (kxctrl.exe -shw 21 0x0 and kxctrl.exe -shw 21 0xA).

I use kxctrl.exe -shw 21 0xA.

Russ:

I'm glad you got the restart problem fixed. When do we get to test what you have to solve the problem?

Oh, my sound card is SB0092 10k2 [e800]. hehe

Russ · Jan 14, 2006, 08:20 AM

I only threw it together quickly for testing. I just need to make a few small modifications before it will be ready for use by others (make it a per-device addon).
It is late here (3:19 AM), but I will try and have it ready soon (I am not sleepy, so...).

I will post a message here when it is ready.

thomasabarnes · Jan 14, 2006, 08:23 AM

It's about 2:30am here.

I dont want to press you to rush. I can wait til tomorrow or whenever.

Russ · Jan 14, 2006, 08:36 AM

Hehe, no problem there. I am just trying to figure out where to save per-device settings for addons (unfortuanatley, no documentation on that, and they do not have a pgm_id like plugins do... I guess I will have to make something up.), otherwise it would be done.

Maddogg6 · Jan 14, 2006, 08:52 AM

Quote:

Originally Posted by thomasabarnes

Let me say again that using the kxctrl.exe -shw 21 0xA command works for me, but it has to be done again after a PC restart, and I didnt have to reselect the MIDI port either. With SONAR closed, I ran the command, opened SONAR and load a MIDI file, played it and the drums work. I closed SONAR, did a restart of PC, opened SONAR opened a MIDI file, drum dont work. Closed SONAR, ran the command, opened SONAR, load MIDI file Drums work.

I dont know why it's not working for Maddogg. Is he using a different command, cause you did post 2 commands earlier (kxctrl.exe -shw 21 0x0 and kxctrl.exe -shw 21 0xA).

I use kxctrl.exe -shw 21 0xA.

Russ:

I'm glad you got the restart problem fixed. When do we get to test what you have to solve the problem?

Oh, my sound card is SB0092 10k2 [e800]. hehe

Ok for me - I did this: (PS I know PROPER command is 0xA - 0x0 is the WRONG setting.

So: Ive just rebooted from updating to 3538i...

I open KXconsole and issue the command:
GHW 21 - its set to 0...

So I type in SHW 21 0xA - it accepts it.. GHW 21 reveals an 'a'

I close the console and start up sonar. - Although Ive updated drivers - Sonar doesnt seem to notice...
I load a midi file - no drums

Check the console with GHW 21 - its back to 0... I do SHW 21 0xA and BAM drums are working..

Ill try again from a fresh reboot - now that its not a fresh driver install...

Jan 14, 2006, 03:36 AM	#1
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	MIDI drums DO work in 3538i !!! I have just discovered that you can get midi drums to work with 3538i and the kX Synths. If you read my post in the 3538i bug thread, you are aware that there is a new kX Hardware Setting for setting the drum channel (that unfortunatley seems to keep resetting to 0). Well I decided to see what would happen if I edited one of the config files (must be a config file that had 'Hardware' checked when it was saved) and manually set the drum channel to 10 (0xA), and then load that config. I did this and then re-selected the kX Synth as my midi port in my midi software, and guess what, the drums worked!!! I then tried rebooting and unfortuantley it did not last through a reboot (kX re-saves the settings to the registry and unfortunatley seems to write back 0 again). I then tried another go at using kX Console to set the drum channel to 10, and realized that it was working (somewhat). If you set the drum channel to 10, and re-select the midi port in your software it works. The keys here are that you should not read back (-ghw) the value, as that seems to break it, and to re-select the midi port in your midi software. Also, this seems to only need to be done once, so long as you do not do something to break it, it seems to stick (i.e. close and re-open the midi software, it still works without having to re-select the midi port each time). So, after booting, you should be able to use kX Console (kxctrl -shw 21 0xA), or load a saved config (and then re-select the midi port in the midi software once), and have working midi drums with the kX Synth's in kX 3538i. I still have to do some more testing to try and get a setup that does some of this automatically (i.e. I have not tried using a batch file, or modifying the kx startup command line arguments as of yet to see if I can get it to work automatically, nor have I found a way that does not require re-selecting the midi port at least once), but I want to share this info as soon as possible, as I think this should make some people happy.

Jan 14, 2006, 04:10 AM	Thread Starter #4
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	BTW: The 're-selecting the MIDI port' thing may not always be necessary. I just tried doing the following from the 'RUN' line. kxctrl.exe -shw 21 0x0 I then opened the midi software and tested it and had no drums. Then I tried setting the drum channel to 10 (again from the 'RUN' line). kxctrl.exe -shw 21 0xA I again opened the midi software and tested it, and had working drums, without having to re-select the midi port. So it seems that the thing with having to re-select the midi port may depend on the midi software itself (i.e. how it initializes the midi port when it first opens), and the method that you use to set the drum channel to 10. So it seems that it may be possible using batch files to get it work with minimum hassle.

Jan 14, 2006, 05:33 AM	#10
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,375 Rep Power: 0 System Specs	Good news Russ! Us not to sharp kX users will need some kind of Getting MIDI Drums To Work Using 3538i For Dummies fix. So I'll keep following this thread to see what you end up with. Thanks for the info! __________________ May a song always touch you in a positive way. SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Jan 14, 2006, 06:25 AM	#16
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,375 Rep Power: 0 System Specs	Russ: The kxctrl.exe -shw 21 0xA command run from the Run box did it, but it has to be done again after a PC restart. Oh yeah, I didnt have to reselect the MIDI port either. I'm glad you figured this out, and I think it's good for us to know this because as you say Eugene may get busy and the release date for the new driver version may be delayed. Thanks, and it would be even better if you can figure out a way so this command can be run auotmatically at restart (after the kX Mixer loads right?). __________________ May a song always touch you in a positive way. SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Jan 14, 2006, 08:14 AM	#26
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,375 Rep Power: 0 System Specs	Let me say again that using the kxctrl.exe -shw 21 0xA command works for me, but it has to be done again after a PC restart, and I didnt have to reselect the MIDI port either. With SONAR closed, I ran the command, opened SONAR and load a MIDI file, played it and the drums work. I closed SONAR, did a restart of PC, opened SONAR opened a MIDI file, drum dont work. Closed SONAR, ran the command, opened SONAR, load MIDI file Drums work. I dont know why it's not working for Maddogg. Is he using a different command, cause you did post 2 commands earlier (kxctrl.exe -shw 21 0x0 and kxctrl.exe -shw 21 0xA). I use kxctrl.exe -shw 21 0xA. Russ: I'm glad you got the restart problem fixed. When do we get to test what you have to solve the problem? Oh, my sound card is SB0092 10k2 [e800]. hehe __________________ May a song always touch you in a positive way. SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs Last edited by thomasabarnes; Jan 14, 2006 at 08:20 AM.

Jan 14, 2006, 03:48 AM	#2
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	well, hell Russ -you figured out the hard part -- seems liek a bat file in the startup start menu - that calls a .reg file - and 'kxctrl -shw 21 0xA' - all at boot up.. No?

Jan 14, 2006, 03:51 AM	Thread Starter #3
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Yup, a simple batch file should work (no .reg file necessary), I just haven't tested it as of yet.

Jan 14, 2006, 04:56 AM	Thread Starter #5
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Ok, I tried using a simple bat file in the startup folder and it did not work. Unfortunatley, I cannot make sure that it executes only after kxmixer has finsished loading and restored settings (I could probably add a bunch of pauses, etc, but that is not a great solution). I am thinking that maybe a simple addon or plugin, that does nothing more than set the drum channel to 10 might work better (as it should only execute it's code after kxmixer has finished loading), I will have to give it a try. BTW: With mutiple card setups, you proabably would have to set the drum channel to 10 for each device.

Jan 14, 2006, 05:07 AM	#6
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	Maybe... .. This command CAN ONLY be sent after FIRST attempting to open the midi port? Is this possibly the case? - I dunno - just throwing out ideas...

Jan 14, 2006, 05:30 AM	#8
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	I will install i and see how it is - doesnt sound too painful to get drums working again..

Jan 14, 2006, 05:32 AM	#9
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	WHAT IF - you replace the kx mixer registery entry for startup with a bat file that first loads KX mixer THEN the KXCTRL command.. thats should work no?

Jan 14, 2006, 05:52 AM	#13
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	Well. maybe no sense banging head against brick wall when Eugene indicated a new release soon.. ?? But kudos on finding the problem...

Jan 14, 2006, 06:13 AM	Thread Starter #14
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Yes that is true, but you can never be sure how soon is soon (there was an indication about sometime in January, but you never know what problems he might run into that may push off the target date). I only wish I figured it out sooner, as I did test the drum channel thing before, but I guess I kept making the same mistakes in my initial testing. I either, read back the value (which seems to make it not work), or I had my MIDI software open when trying (and did not try reselecting the port or closing/re-opening the program) or some combination of both. During my initial testing this time, I did the same thing, I had my MIDI program open during the test, but I happened to have the MS Synth selected for the drums, so I had to select the kX Synth, and that made it work (otherwise I may have missed it again), and after some more quick tests to ensure that I could consistantly get it to work, I posted the message to let others know.

Jan 14, 2006, 06:22 AM	#15
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	I just tried to D/L 3538i - and DH wants me to DISABLE MY FIREWALL - um.. WTF! I dont think so. Ill need to find my archive - I know I have it on a disk somewhere.. but DAMN! get real, turn off your firewall - This seems VERY UN-NECESSARY. - Anti-leach or not..

Jan 14, 2006, 06:46 AM	#19
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	DAMN! - what about re-compiling KX MIXER - to send that command in its code... ?? I know- I'm strecthing...

Jan 14, 2006, 06:49 AM	#20
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	OR is there a cmd line param for KX Mixer to send that command also.. ??

Jan 14, 2006, 06:55 AM	#21
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	OK - ALSO - the reason I thought of the REG file - is to PUT that setting into the registery if the kxctrl ran before mixer finishes loading - I assumed those settings was being read from the registry - and turning off ch10 drums also from those settings... ?? I thought would cover both bases running kxctrl AND changing registry - depending on if kx mixer finished loading or not - no matter - the right setting would have been read from the registry - but I now assume this setting is not stored in the registry.. . Im dumb with this stuff... but I try.. lol

Jan 14, 2006, 07:00 AM	Thread Starter #22
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Well we cannot recompile kxmixer (we do not have the source code), and I do not know of any startup commands to do it. One possiblilty might be, to not have kxmixer restore the settings from the rsgistry at all, and to just load an edited config file instead. I do not know, there are lots of things to try. I was also trying to see if changing the setting in the registry would help (as that is what kxmixer uses at startup), but I did not have any luck, but I will have to redo some of my testing anyway, to be sure I did not make any mistakes in my testing (as we have allready figured out some more things since I originally posted the message, and did some of my initial testing).

Jan 14, 2006, 07:43 AM	#24
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	Ok - I installed i - and I see that - I DO have to open sonar FIRST - then send KXCTRL command - disable/re-enable KX Synth Midi driver.. Sending command BEFORE sonar starts doesnt work for me. At sonar startup - it re-sets that param back to 0 again. So it seems initial-initialization of the midi ports re-sets that param - if its too much pain in ass - I may revert back to h - no problem... Im learning anyway... a simple batch file to run after sonar starts is a small price - for now anyway, depending on how improved 'i' is over 'h' in other areas.. hehe Good work finding this one Russ..

Jan 14, 2006, 07:58 AM	Thread Starter #25
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Hmm, that is not the case for me, but I cannot test Sonar as I do not have it. I had no luck with the registry settings... Something overwrites that value during kX startup. I did however look at some of the kx debug messages during startup, and I noticed that plugins get loaded quickly, but addons seem to be loaded last. I decided to try again with an addon this time and it worked. I rebooted, logged on, opened my midi software and the drums worked, so that may be the best solution. Addionally, if I make it a per-device addon, then it will probably work for multi-card setups as well (provided that they load the addon for both devices).

Jan 14, 2006, 08:20 AM	Thread Starter #27
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	I only threw it together quickly for testing. I just need to make a few small modifications before it will be ready for use by others (make it a per-device addon). It is late here (3:19 AM), but I will try and have it ready soon (I am not sleepy, so...). I will post a message here when it is ready.

Jan 14, 2006, 08:23 AM	#28
thomasabarnes Long Time ***** Friend Join Date: Jan 2003 Location: USA Posts: 1,375 Rep Power: 0 System Specs	It's about 2:30am here. I dont want to press you to rush. I can wait til tomorrow or whenever. __________________ May a song always touch you in a positive way. SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Jan 14, 2006, 08:36 AM	Thread Starter #29
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,563 Rep Power: 62	Hehe, no problem there. I am just trying to figure out where to save per-device settings for addons (unfortuanatley, no documentation on that, and they do not have a pgm_id like plugins do... I guess I will have to make something up.), otherwise it would be done.