A useful tidbit of info...

I am not experiencing anything even remotely like that.

I guess the first question is "where are you going to do your search?" Of course, if this is all stuff loaded on the internal drive, or even a firewire or USB attached drive, it really shouldn't matter either. Sounds to me that if you're searching, you've got a minor organization problem. When I finally get around to ripping (to 16-bit .wav) my entire CD collection, I'll be dumping into an artist directory, further organized into album directories.

Just with some minor screwing around, using the latest MyDMX available via the web site, I did the following:
No myDMX Dongle, screen not maximized, but not minimized either.
Loaded MS Word from Office 2000.
MyDMX IS in(I still have it there) in USER mode, where the keyboard triggers are active.
Typing a document, mainly random WHOLE words, I was using letters I was using in MyDMX for triggers(R for red, w for white, g for green, be for blue, y for yellow). Never once did MyDMX trigger.

Going to Explorer, same thing. My typing to have Explorer quick find items did not cause MyDMX to trigger.

I am even using a relatively simple application I use for quick calling songs that operations off of keyboard triggers as well(press A, that song triggers.... all assignable)

What OS are you using? I am wholy unable to replicate your scenario. I am using XP Home, latest updates.

The only way I can get MyDMX to trigger via computer keyboard commands is to be in USER mode, and MyDMX being the active application. Maximized or windowed is a non-factor, just needs to be the front application.

Just to be safe, I would recommend carrying that DMX Operator so you have a fallback solution.

Hi Chris,
I admit I didn't try all options, but using a new HP laptop running Vista Home Premium, Virtual DJ and myDMX, those were my findings. How myDMX works in conjunction with a word processor really doesn't matter. At any given DJ gig, the listed applications would be the ones in use at the same time, in my setup. I wanted to find out how well they played together so I could use one laptop to do two things without conflict.

In my findings, typing any characters in the search field of Virtual DJ that corresponded to myDMX trigger keys while myDMX was open on the screen (and in User mode) triggered changes in the lighting scenes. It was only when myDMX was minimized to the Windows "tray" at the bottom of the screen that it would ignore keystrokes. Granted, another workaround might be to leave myDMX open on the screen, but place it in Editor mode, where it also doesn't respond to keystrokes. The only danger there is that you might do something that changes your lighting scenes accidentally. I found my method to work well for my setup. Other DJ's setups may react differently...

Well, even if just putting MyDMX in an open window, LEFT in user mode/tab, then moving to the Desktop as the active application, I am still unable to get MyDMX to trigger via keyboard presses. Again, major difference is Vista because I'm using XP Home.

Don't get me started on DJ. I'm not a DJ. I'm a sound production company.

I think you're smart to test this ahead of time, something too many people don't do. It's one thing to do a "trial by fire" in a test environment to see how it works out in the real world, but NEVER do this before or AT a show unless it can not be avoided. More people need to learn from what you're doing. I'm not here to say "right or wrong" or that your applications suck. What's important is the methodical testing ahead of time to troubleshoot problems.

I can't say authoritively because I don't use Virtual DJ, but my guess would be it may be something to do with that application. It could be some sort of setting. Without knowing much about VirtualDJ(and I'm not going to research it), I would honestly find it odd that it would "pass through" keystroke commands, ESPECIALLY while you're doing a song search

Going "low tech", doing a similar thing with Windows Media Player, I hit keys that correspond with MyDMX while audio content was playing. MyDMX failed to trigger. I did set the two windows so I could see access to each so I could monitor if my keystrokes in WMP triggered MyDMX. It did not trigger. Interesting but handy, I could click a scene button in MyDMX while not the foreground app, and it would not move to the foreground, and the scene would change as it should.

I don't see why this sort of thing should be a 2 computer application. Audio playback is far more demanding on resources than a simply asyncronous data stream(DMX-512).

Since I work mainly with live bands, I don't have these issues. And since my rig contains multiple playback decks, I use the right tool for the right job. But our applications are vastly different.

I'd do further testing in your environment, seeing if MyDMX triggers when not in the foreground, period(but not minimized). Need to narrow down where the issue MAY be.

Hi again Chris,
Good advice. One thing from your last post I really found interesting was how you described being able to switch myDMX scenes while the app wasn't in the foreground via a single click...that's different. It shows myDMX is still active to some degree. Usually, it takes one click to bring the app to the foreground and another to perform an operation in that app using the mouse. Things that make you go "Hmmm"...

On another slightly related note, check this out: I bought an inexpensive external USB numeric keypad for use with my laptop and myDMX. The plan was to set the keypad on a small stand...maybe attached to my mike stand while I play guitar in my band and try to run lighting scenes. I programmed myDMX triggers in Editor mode using the keypad...it worked fine. When I put myDMX in User mode, it no longer recognized the external keypad. The scenes would trigger just fine from the laptop's number and math keys as programmed, but not via the external keypad I just used minutes before to write the edits. I thought that was odd...

Well, I think you may have done your MIDI triggering in EDIT mode, which is where you should use continuous data controllers. That's better for assigning to a fader and then using a continuous data controller for up/down adjustments on a specific fader. In my case, it would be great for tweaking the mode on my 64B LED Pro's so I could throw them into strobe real fast and then out again.

Re-program using your numeric keypad in USER mode and that should fix it. Use that for triggers such as your progam change data and note on data. That will resolve your problem. This time your description was highly informative and showed where your problem was.

As far as "MyDMX" being "somewhat active", it has to do with multi-threading. All apps and services are active and can operate in the background. It's ability to accept input is based on how it is designed. Nothing unusual.

Our local DJ/club is a single universe 27 fixture DMX array using an Elation 192 channel DMX controller (I know, rather lame). I setup the hardware controller so the DJ can override the LED wash and floor lights while allowing the rest of the fixtures (scanners, acrobat, X-MOVE, X-SCAN, Reflex, VUE VI, etc. etc) to run the chases. This was a little hard on the DJ since we has scratching while trying to create some visual effects using manual sliders. After running the show and watching/helping him work the lights, I thought the MYDMX with a small MIDI keypad to select programmed scenes would work out better.

I purchased and installed the MYDMX software on my HP ZV6000 laptop (XP SP3 home) and a KORG NANO-Key USB midi keyboard so the DJ can run a show using this small keyboard next to his Traktor based system. I was hoping for a portable, small, and $ effective solution since the DJ booth was cramped. I was able to program MYDMX to create the effects and matched the Elation controller DMX channel assignment quickly and exactly. Installing the laptop under the table, and the small KORG next to the DJ, we were ready to rock. The hardest part was that I had to build the X-MOVE, X-SCAN and Reflex ADJ lights and the Chavet VUE VI definitions in MYDMX (they were incorrect).

First off, it worked right away - sort of. MYDMX was able to see the keyboard in CC mode and in normal note/octive mode. Assignment of the keys was simple. I was able to reprogram scenes during the night going between edit mode and user mode without to much distraction on the dance floor until we had a decent show (such as aiming the X-SCAN and X-MOVE and setting colors/strobes). Second, even thou it worked, it failed for the following issues;

1. if the MYDMX software did not have the scene button visible while in the 'user' mode, pressing a midi command for that hidden scene button instantly caused the MYDMX software to error and crash and halt the show. As long as I had all the scene buttons showing (max the user scene button window), it worked perfectly. Same for programming. Not sure if this is a laptop driver issue on the HP, but it has up to date ATI M200 video drivers. Also, it is a good idea to save your work constantly as I found out the hard way (again)!

2. The MYDMX software does not recognize more than one octave in the KORG Nano keyboard. Unfortunately, this provides only 25 scene selections rather than the possible 225. The CC mode of the Korg keyboard works fine in addition to the note mode, so in the end i had 50 possible MIDI commands/scenes from the NANO. I used them all. This is probably not a fault of MYDMX, since it may only suppose to see MIDI commands, not notes, anyway. But it would sure of been nice!

3. The DJ really liked the ability to bang away on the midi keypad sitting next to his system, setting colors and scenes to the music he would play, jumping between his software, scratching, and a small midi keyboard. He could memorize what scene/key best matched the song, and I always had one note/command as a blackout. It was a great idea, small and very cool. Plus the laptop didn't get the abuse.

So, if you are considering the KORG NANO series of MIDI keyboard, I would not recommend them for MYDMX. The club now wants a better hardware controller, even if hard to fit, rather than the MYDMX so I will be selling it.

1: Right. You have tobe in the right mode for it to work. But being visible to work? I haven't tested that far, I'm only using 4-8 triggers in my testing, and they are in a tight bunch, but I have way more scenes now and could easily spread it out. If MyDMX is crashing when "hidden" scens are triggered via MIDI, that is something support would need to look into. That just wouldn't be right.

Saving a lot is always the right thing to do.

2: If MyDMX is not recognizing more than 1 octave, then the keyboard is not transmitting information or that you've not trained MyDMX to learn additional notes. I like Korg, but I'm not familar with that unit. Are you sure you werne't in LOCAL mode?(as in don't send new MIDI information via the out, but merely do internal stuff only)? And, since at any given time, you've only got access to 23 NOTE keys, you only have direct access to 23 scenes. I don't care how many scenes you've got, but via one controller, best you're gonna get via 1 channel is 128 scenes that could be directly accessed. I think you've got there right concept though but also perhaps as you are saying, the wrong controller. I'd be checking to ensure that the Korg Naho is outputting notes on all 23 keys(black and whites). Considering an octave is 12 half steps for a normal chromatic scale, I think perhaps something might not be right?

Now, if the Korg Nano can be transposed, then the note hits should follow transposition, NOT "hard values". Say, the low C is default 36, but you want to bring it UP an octave via transposing, then that low note should now trigger 49, NOT 36. Correct me if I'm wrong, but my 1986 era DS-8 can do that.

3: Seems like you had a good thing going. I don't think they'll get exactly what they want out of a better hardware controller, but that's some ignorance of mine talking. I am familiar with the DMX Operator and it's limited MIDI implementation. Yeah, you could get the same thing done, but only to 128 scenes, where as with MyDMX, by changing MIDI channels, you can get 128 triggers times 16 MIDI channels to get a total of 2048 scene triggers. Do you really need that many scenes and triggers? I doubt it, but isn't it nice to know you can? That gets to a whole other position of "how many scenes can MyDMX actively hold in a set?".

I need an inexpensive keyboard for triggering my inexpensive sampler a bit more aggressively. I might consider the Kork Nano, but I'd rather have another octave. I have 40 notes available, but I can have direct access to 32 of them via a controller, while leaving me 1 bank of pads on the sampler available for direct play.

I'm not willing to spend any money on my own to confirm this issue with the Nano keyboard at the moment.

Hi Chris,

The NANO is great for a cheap keypad to control mini commands and to peck notes. Although I did see some good youtube demos of people actually playing music on it. It is sure fun for $49 bucks and it fits on my desk easy.

On the GarageBand software on my iMac, the up/down octaves all worked. But some of the keys activated the same scenes in MYDMX no matter what octave the NANO was set at on my PC. Again, not a feature supported by MYDMX exactly, and two different systems. But if you can be happy with 50 or so scenes and an extremely cheap hardware interface, this is pretty darn neat. And if the DJ gets crazy (they do), or you want a tiny controller for your show, cheap to replace rather than a laptop keypad. Plus, the mapping issue to the keyboard is mute from previous discussions.

Anyway, I don't want to get off topic. MYDMX is a great tool, I needed to better understand it's limitations prior to this application. Can't wait to get my hands on laser DMX lighting equipment (ADJ?) and a better hardware controller. I'm all ears for advice.

Not bad for $50. I might go to Guitar Center and blow a coupon I have to save a few more bucks on one.

Without reading a lot about the NANO, I can't fully comment intelligently. I saw a bank of 2 octaves worth of keys, plus a side pad that looked like it had another 6 or 8 buttons? Forgive me, I'm going off memory off a bad picture on the Korg site. I could see those "performance keys" being transposed and working, but the other keys being fixed function.

Going back to what you said about cheap: Yeah, sure is. Literally cheap enough to put a few together into a simple MIDI interface or merging device and have a bunch of readily available scenes on demand. That's actually a pretty good idea.

And if the DJ gets crazy, I have the master mute button on my console and a radio to call SECURITY!

Yes, MyDMX is a great tool. However there is so much stuff out there, good and bad. And even so, just because something is GOOD or even GREAT doesn't mean it's right for all things. In some cases, as you've discovered, maybe what you thought was the right thing just didn't really work out. That sucks, mainly because you wasted money, but the time is often well spent as knowledged gained can be applied as needed.

ADJ and Elation both make DMX laser equipment and better hardware controllers. Not to bash them in any way, but perhaps you might want to spend some consulting bucks with a local sound and lighting(or just lighting) production company and see how they may steer you. These places typically have spent big bucks and many have come through the ranks of cheap gear(not necessarily junk) to where they are today. A lot of them are great banks of information.

I've been looking at the Korg Nano units a bit more. While on one hand I'm excited, overall, I feel a bit flat.

Issue 1 is that these devices are strictly USB controllers that integrate to MIDI via a driver. While this all sounds good and spiffy, my issue is that "it's less costly to add MIDI interfaces than a USB interface plus the R&D and support behind drivers for multiple platforms". While I think having the USB(and USB power) is a nice option and feature, I think due to the USB bridging driver for the unit is where the weaknesses are exposed.

Neither device on its own really stands out. They have a pad controller, which is great for 4 layers of banging via what, 8 pads? Not bad, quick and dirty, lots of applications for it. The keyboard one, as stated, can get you fast access to up to 50 scenes, which again is pretty nifty. The controller one has knob and fader controllers, which is really cool if you want to assign those to specific DMX channels in MyDMX to get fast access to real-time control over whatever fixtures you want to do that with.

For me, I'm looking for more of a general purpose device that has more functions, namely a set of MIDI ports. Why? Well, I want to use this device to not only help me get scenes called up fast in MyDMX, but also to trigger my sampler. NOw, I could compromise by getting a pad controller for the sampler, but the Korg option doesn't allow me to do that because the Korg controller lacks a true on the unit MIDI interface.

The reason I need this stuff all sepparate is that the sounds would need to be recalled as-needed(think variety show/comedy show). Same goes true for lights. Neither lights or audio need to be coordinated or sychronized. And when I do the scene that needs audio, I simply run audio off a CD player while I call up that ONE scene in MyDMX(the sampelr is flat out of space). DOing lighting, video, audio and sampler triggering all at once, it's a big hectic. As it is, on one show, I keep forgetting to do a fade to blackout when we start up the movies again(Sac Horror Film Festival).

My thoughts about your statement about in MyDMX that the keyboard would only trigger certain things despite the octave settings on the keyboard tell me that this is a driver issue and that perhaps the controller must be bridged onto an active MIDI-based(or utilizing) software package(as in not MyDMX) in order to fully access the functionality of the Korg nano unit. The fact that it works properly in GarageBand(a Mac music creation package that integrates MIDI) only supports that theory.

For me, for now, I could get by with 25 scenes. But I see outgrowing that in time as the needs of the on-stage talents get more demanding or i just simply want more capability.