DMaX - DMX Lighting System for M4L

[j250x]

Here's some of my work on a modular DMX system for M4L, which I've called DMaX. I have fairly ambitious plans for this system eventually, but I thought I would release my initial experiments so far. These modules require the dmxusbpro object and an Enttec DMXUSBPRO device. Currently there is only a central hub module and an LED Par controller, however:

My Plans:
- Make considerably more modules, including basic dimmer pack and moving lights.
- Create a template device so people can make their own modules easily.
- Expand the system to work with other manufacturers brands of USB DMX.
- Expand the system to be able to output MIDI data which can then be converted to DMX using hardware.

If you have any comments, suggestions or bugs to report, please contact me.

Instructions and downloads available from the project website: http://prodavid.wordpress.com/dmax/

[LOFA]

Very cool. Thank you for sharing this!

In the meantime, I have not been able to access these devices, even after logging in.

EDIT: I see it was edited! Cool.

[j250x]

I had to resubmit the devices to change some information so the links changed. All the ones on the project website should be OK now.

[LOFA]

I see you are thinking of supporting the martin atomic 3000 series in the future. I would be very happy to see this

[j250x]

Yeah. It's the only strobe I've ever seen used professionally so I imagine it's the one in most demand. I've currently made the Stairville strobe module because it's the one I own.

I can make the module pretty quickly from looking at the DMX spec in the manual. However, as I don't own an Atomic I can't test it. If you have access to a Martin Atomic and the necessary Enttec hardware and could test the module for me it would be a big help!

[LOFA]

Please check your inbox.

[j250x]

Some minor bugs have been fixed, and there are some additional modules available now. If anyone has any requests for particular fixture models they want then please say so below.

http://prodavid.wordpress.com/dmax

[Khazul]

Great job - just started playing with this and busy making controllers for my cans, moving head, lasers, smoke machine etc via a usbdmxpro

[j250x]

If you make any new device modules please send them to me so I can put include them in the package. I want to support as many dmx fixtures as possible.

[Khazul]

Ive switched over to my own direct control of the olaf's entec dmx external. It seems using of dmax was crashing Live alot for me as well as taking a very long time to load and even do simple things like moving/copying control clips.

Anyway - my own seems very lightweight and far far less CPU intensive by comparison - not sure why. I may post fixtures in the future anyway as when done for one, then its pretty easy to convert to the other - just takes a minute for each.

Anyway - good luck - happy to share stuff.

[j250x]

That's interesting. Can I ask what your machine spec is?

[Khazul]

I dont think its a machine spec thing (3.6Ghz Pentium D, WinXP SP3). I think it may have something to do with the default driver start up. The odd bit is that it even takes ages to copy/move clips around 5-10 second to copy a clip in session view on midi tracks that have DMaX plugins in them. I have absolutely no idea what Live could be doing.

[j250x]

OK, does this happen only with DMaX plugins or with other types of Max For Live devices? Do other devices that use Jitter have similar problems?

[Khazul]

OK, does this happen only with DMaX plugins or with other types of Max For Live devices? Do other devices that use Jitter have similar problems?

M4L+Jittter devices are fine so long as the refresh bangs are carefully controlled - after all mine uses M4L and JS and Jitter.

I have found it useful however to severly throttle update events to jitter (mine has a similar data monitor to yours, as did my original windows app) to stop event storms (Severe CPU spikes) on the update bangs to the controlling matrix. I also have a button to switch the monitor matrix/pwindow off completely - Ive found it useful to minimise CPU use when it isnt needed as well as putting active control of it as well.

I basically use a combination of a qlim and a counter to control a gate on the bangs to ensure there is only ever one outstanding bang in the qlim.

If it makes a difference - I only have M4L, not full max/msp/jitter - I'm not sure what the jitter cripppling that M4L gets may involve - I hope not performance!