automap plugin

Hey Cyrax, To my knowledge there are no midi map plug ins for my dmx. you don't even need a midi map. They just work.
How is the launchpad? I am thinking about getting one. I have a Korg Nano Kontrol.
Sincerely,

hi

so far, everything works FINE. it's just the launchad supports 3 colours, each in 2 intensity's.

i would like to have the active scene in Green, the inactive ones in Yellow, and the buttons that don't have a scene to be triggerd in red (or off for that matter ...)

i think this is where i'd need the plugin ... so far we haven't been able to pull that off ...

OK well Let me check with our developers and I will post their response. Please note that it may take a few days for them to get back to us. So I could possibly have an answer for you by the end of next week.
Sincerely,

Jingles,

any news yet ?


regards

Nope. Sorry. Still Waiting.

Jingles, Any news on this one ? still waiting

You know I think red is all your gonna get. One of our other users recently bought a launchpad and did testing and red is all he will get. I do not think our developers have a automap plug in made. I have emailed them but I have not gotten a response about it.
Sincerely,

I seriously doubt that Automap or any sort of bi-directional communication will be integrated into MyDMX.

The purpose for what I use automap for is to turn on the lights for the Launchpad for use with MyDMX, which all I get that is usable is red, which while not perfect, is better than nothing. But, Automap's primary function is to let you adjust settings in the Launchpad, such as change what pad does what and that sort of thing.

Launchpad is one of 3 primary controllers built and intended to be used almost exclusively with Ableton Live, as Live has included some sort of plug in or other communication to control colors on the surfaces. The other two are the Akai APC-20 and APC-40, which also have color changing buttons. Also, the COLORS are important, because it shows status of what's going on. Also, depending on what page/mode you're in(especially with the Launchpad, which is more of a universal catch-all surface as well), some functions use different colors. As I understand it, when Ableton Live is launched AND a session file is opened, that session file pushes color information to the Launchpad based on commands received from the Launchpad(or the other devices for that matter).

Yes, I would like to use colors as well, but sadly, it is not going to happen.

Adding this sort of support into MyDMX would clearly be a NEW FEATURE request, and I don't see it happening. It would require a lot more than just plug-in support by the way. But, unlike Ableton Live, it would not need as excessive integration. It could be a global sort of thing. Such as "Set your active scene to Green, idle scenes to yellow, and unused to red" or something like that. Then, based on how you choose to program MyDMX with the Launchpad, it would have to SEND data to the Launchpad to change the color. The bigger issue right now is the poor implementation of MIDI into the MyDMX product. This issue must be addressed as it is a stated feature and therefore must be done properly.

Plug-in support would be the first feature request. Integration of the plug-in support would be a second feature request(because while tied in from our perspective, is NOT from an R&D point of view). MyDMX has been very clear that they do not wish to add new features, which makes sense to me because of the target market. So, as I've stated already, what the developers need to do is to properly handle a few things with the software(MIDI and USB, especially MIDI) and then they are done. Honestly, I think if we as users want plug-in integration, our needs are not inline with the target market for MyDMX. Such integration needs more of a fuller-featured product, such as perhaps Compu software, which may or may not include plug-in support, but we have a better chance of it supporting plug-ins. My needs are also exceeding what MyDMX can offer, but that's because the shows and events I am becoming involved with are placing high demands on my capabilities in regards to lighting, and MyDMX is not the ideal product. That doesn't mean MyDMX is leaving anytime soon. MyDMX has proven itself and is ideal for smaller events, especially where I may have to leave others in charge and I don't have time to school them on the software.

I personally can live with just red. But, my application is as follows:
I need real time control, so the korg nanoKontrol works just fine, but I want scene triggering, hence enter the Launchpad. Or I can use something else, say a Korg nanopad or still something else. But that's a whole other slew of problems tied to MyDMX, handling of USB and MIDI.

But, get this: MyDMX must be the foreground application to listen to MIDI.

I also need to start using Ableton Live for Launchpad to be used for sample playback. Censor beeps, crowd noises. Think a combination of gameshow and sitcom type sound effects. My little Roland MS-1 is not able to handle the complement of sounds I need in a dynamic and random environment, so I could use the Launchpad to trigger samples if I have to. Live can sit in the background if necessary because it will actively listen to the MIDI streams of any device I tell it to work with. If Sonar can listen to multiple MIDI devices at once regardless of where and how they are attached(mainly USB, including a MIDI interface, but also by an audio device with a MIDI interface on my firewire port), then why can't MyDMX?

indeed,

i have a VERY basic setup, and only got the launchpad to not have to instruct every guest DJ or whatever on the lighting panel. with the launchpad, all i have to say is: HIT SOME BUTTONS AND SEE WHAT HAPPENS (short version ...)

therefore; color changing would be nice. OFF for no scene programmed, RED for inactive and YELLOW for active (or whatever)

anyway, i would also be happy if i could just make it RED for programmed scenes, and OFF for the opposite ... (because i don't have 64 scenes programmed, i don't need all the buttons at once).


also indeed, MyDMX being on the foreground for receiving MIDI is a setback, since my PC isn't dedicated to myDMX, but hey, i can live with that ...

i'm looking into Chamsys for replacing myDMX, but that isn't for any near future ...

greetz

hey guy's I just put in another request to our developers for midi. We will see how it goes.
Sincerely,

For the reasons Cyrax stated is EXACTLY why MyDMX won't be leaving my rig. By using short descriptive scene names and button-pressing convenience(find it, click it), MyDMX brings the illusion of powerful lighting control quickly and easily into the hands of an ignorant newbie or someone otherwise not versed on a system.

My main reason is this rave I do, where I sometimes leave and want the DJ's to be able to control the lights, or at least have the option to. They love it. And we're not talking idiots either, but definately not lighting guys.

At the same time, MyDMX does put some rather powerful lighting into a super affordable package.

Your idea of putting it onto the Launchpad takes it a step further. Now, while you're doing your lighting via computer, you've made it more user-friendly with a big bunch of pads. Organization is they key. "Washes on the first 2 lines with different colors, patterns on the next 2 lines, chases on the next line.... strobes on the last line". Organization is key for that. The Launchpad is all at once friendly by the looking so clean, but at the same time hides a very powerful set of featues sure to scare a lot of people off if they knew what it was capable of. And for the retail price, it's CHEAP! Even at the list price, it's a bargain when you consider what you can do with it if you reall put yor mind to it.

If I were to use the Launchpad for those DJ's, yeah, it would basically be "hit some buttons and see what happens", which I know they'd like as well.

Right now I'm trying to evaluate Compu Show because I'm staying loyal to the ADJ, Antari and Elation brands. All I can say is that I feel that for what I'm doing, this is an ideal product, but it requires a higher learning curve than I was expecting. I can also see my current batch of "toys" getting integrated into this, to the point were it almost seems silly with all the accessories I would be using.

I won't argue the desire for the color changing you want via MyDMX. It would be very handy to have, not just for the reason you stated(which is the best one), but also for my own purposes at live events so I don't re-trigger the same scene.

Now, the implementation of MIDI, SHOULD the developers add a "select devices", would mean that a device would not be available for something else at the same time. I think this would be acceptable. So, I wouldn't be able to use my Launchpad with both myDMX and Ableton or Reason at the same time, fine, that's acceptable. I would simply use my Korg nanoPAD to trigger scenes instead, as I don't have a massive need for scene triggering, and 48 scenes is a lot(12 pads, 4 banks of 12 pads each). I don't see this as a feature request, I see this as the developer properly integrating MIDI into the product.

It will be interesting to see what I can do with MIDI and Compu Show. I have to complete osme other projects before I can get back to evaluating and learning Compu Show, but I also am allocating funding for this product.

I heard back from my head developer for my dmx. They will not add support for automap. Sorry.
Sincerely,