RGB values to DMX control

    Feb 28 2014 | 3:51 am
    I am completely new to this program, but I am trying to take plain RGB values from another MSP patch (created by someone else) and then use these values to send through an Enttec DMX Pro interface. We played around with DMX 512 external plug-in for Maxand that worked OK, but we just need to figure out how to take R,G,B values and incorporate them into the mix.
    Thank you in advance for the help

    • Feb 28 2014 | 4:51 am
      What you're asking is kinda general. If you have a patch that shows where you're stuck, folks can more easily help out. Highlight what you want to share, copy compressed (edit menu) and paste in the message window.
      You more or less want to make a list of RGB (0-255) values and convert that into a packet to send to the entec box. I assume the external will convert the list to a packet. You should have info about how to format the list so the packet works properly. I don't think it's same for all devices.
      If you don't know how to build a list in Max, that's easy enough. You can get that rolling with just a few objects, but in order to help you, it would be good to know where the values are coming from and what objects you're currently using.
    • Feb 28 2014 | 5:08 am
      David Butler's excellent objects are always my starting point for working with DMX. http://www.theimpersonalstereo.com/software/imp-dmx/
      I assume you're working with Olaf Matthes' external for the DMX Pro, which also has a fairly usable help file with it - you just need to play with the channels to figure out which one relates to the R, G and B on your particular light.
    • Mar 19 2014 | 1:15 am
      Attached is the file I am using. We need to take the RGB values it is creating and use them to output with the Enttec DMX Pro Box.
      Can anyone help with this?
      As asked for, here is the patch:
    • Mar 19 2014 | 6:40 am
      As Kodamapixel wrote...
    • Mar 19 2014 | 2:04 pm
      Chris (or anyone else),
      how can I implement that part to talk to the RGB values that this patch is already creating? I just need those RGB values "linked" to the Enttec DMX output
      Thank you
    • Mar 19 2014 | 2:27 pm
      Again echoing Kodamapixel...
    • Mar 19 2014 | 5:08 pm
      Christopher, May I send you an email off of this forum to extra help in setting this up?
      I am just on the last step and need some guidance. Thank you again
    • Mar 19 2014 | 7:46 pm
      I've pretty much just bestowed the sum total of my wisdom on the topic :), but feel free to send me an email if you want. No guarantee of how fast I'll be able to respond, though, since I'll be traveling the next few days.
    • Mar 20 2014 | 2:17 am
    • Mar 20 2014 | 3:11 am
      The way that my RGB lights work (and there's every chance that yours might be slightly different) is that each unit takes 4 channels, each with a value of 0-127.
      The first channel is strobe; second is red; third is blue; and fourth is green. Remember that this will be the case for each light. So the first light takes channels 1-4, the next takes channels 5-8, the next 9-12 and so on.
      I'm going to assume that you're using the [dmxusbpro] external and this example should at least let you test which channel does what...
    • Mar 20 2014 | 3:02 pm
      This is the patch we have now.
      We are able to control lights within the patch. We just need the Colors that are being generated in the large square to become the colors that are output by the DMX. How can we link these?
      Thank you
    • Mar 21 2014 | 7:43 am
      Take another look at the patch that I posted above. You're already there with the messages coming from the [IDCILightingMstrPrgrm] object. Just [unpack] these, before they go to the [prepend] object and follow the steps from my patch to see what the result is.
      I'm not sure where the breakdown is between being "able to control lights within the patch" and getting the "colors that are being generated in the large square to become the colors that are output by the DMX". If you're clearer on what's actually happening with your lights, we might be able to troubleshoot further.