LED STRIP DIGITAL control with Madmapper

definetly possible with ArtNet tools, or even with an arduino (although the path to success is more likely to be much longer and painfull). Simply generate a structure of RGB data and feed it to the KnM ArtDMX sender patch.

FYI MadMApper will feature a LED/Light mapper built in function for the next coming release (that is, after the 1.2), which will allow you to do just that ...

This can be done right now with QC and an Arduino, and using the Peggy Kit from Evil Mad Scientist. Are you looking for something prebuilt?

Thanks Franz ! Serait-il possible de te demander deux trois précision en français via mail ou autre ? je retraduirai par la suite pour la communauté kineme avec l'avancement du projet.

Yes i took a look on the Peggy Kit. However i only found matrix screen product but my goal is to do this with LED Stripes.

If you want to send artnet, right now your limit is going to be two universes - tested 10.6, most recent artnet tools.

i'm noob about dmx/artnet, universes are the equivalents of channel in Midi ? Can you explain me why i'm limit to two universes ?

pas de soucis

universes are the equivalent of midi channels. artnet supports up to 16 universes par sub-net, and 16 subnets. So you have a total of 256 universes, each having 512 channels.

Funnily, I'm DMXing at the moment at the office, and I'm successfully sending 5 artnet universes from QC to PC running wysiwyg.

@gt: i dunno what limitations you're talking about, on my config it runs fine with even 10 universes.

Woah that's excellent to hear then. There must have been some quirk in my setup or something else about the software or hardware that was making it not work correctly. In my test case, between my MacBook pro and older white MacBook, every time I would try to send more than two, it would stop working. I'll have to set it up again.

@gtoledo3: not sure what you mean. Kineme Art-Net Tools's ArtDmx sending and receiving works just fine with all 16 universes simultaneously.

Attached is a composition pair demonstrating it (these demo compositions also require Kineme DataTools). Open the sender on one workstation, and the receiver on another. All 16 universes will transmit and receive data simultaneously (even over the saturated wifi network here).

I haven't looked at this yet, but when it came up I emailed you, and detaile the settings I think. You asked for a sample, I (thought I) sent it, but I don't know if I heard back (certainly didn't get you to do a test like this apparently lol).

Anyway, glad to hear it's working for sending so well! I'm unsure what could have caused it... Maybe I was using two different versions of the plugin or something, but I really thought I checked that. I was even going so far as to restart qc after edits to see if that would jog it I to action. I could always delete the third and get it working. I wish I had my second laptop so I could check it right now and figure out what the settings issue is. It'll have to wait until I have access to it.

I'm pretty thrilled because I'd gotten together a patch that converts a raster directly to artnet style structure that is really fast, but I needed more universes for most scenarios (not anymore apparently).

Question- if loop back was added back in like it was originally, would it break anything with performance? That was handy, even if not to spec.

I'm looking back at my notes, and my problems were happening when I'd switch it to non-normalized values (what I usually use) with more than two. I'd see "noise" spurious values on channels that shouldn't have been there.

Looking forward to checking that out again.

Apropos your email, there is a bug in 1.4 in that the Normalized input on the ArtDmx Receiver has no effect (the values are always normalized to 0..1, regardless). But this doesn't have anything to do with multiple universes. In the bunch of tests I've run, I haven't been able to reproduce the "noise" you described.

I mean, it may have even been a cruddy cable, who knows. Now that I'm thinking about it, it had the plastic tang that keeps the cord stuck in more tightly snapped off on one end. I thought it was in there snuggly, but maybe not. I'm certain that I was running into that thing of sending non-normalized and not receiving them as expected.

I'm definitely going to set this up again and test, but since you and franz are both getting it to work fine, it obviously looks like there was an error gap somewhere in my setup, which makes me happy. I'm really glad this has come up and I'm not sitting here thinking it only does two out reliably anymore. Shoot, I'm kind of excited about it.

Oh, any thought on the loopback thing? By that I mean, the fact that it was originally possible to listen to something on the same machine, but it wasn't technically spec so it was taken out? I can see that if it causes any problems it wouldn't be worth chancing, but it was handy.

The UDP outbound port has to be explicitly set (rather than chosen by the OS as is more typical) in order for the Art-Net packets to be recognized by many Art-Net devices, such as the Net-Lynx O/P (made by the company that invented the Art-Net spec, no less). Unfortunately, forcing the UDP outbound port also breaks loopback. Undoing that would break compatibility with these devices, so it's not an option.

Ahhh, thanks for the education. My main concern about it would have been breaking compatibility, so yeah, not an option. As I write that I start to think "but as a test mode?", but I see how it's not worth the time really, and might be confusing.

Anyway, it's a really great plugin, and well worth the money. I've had great performance from it, and even one bug fix in the middle of the night a long time back :-)

Ah yes. That was a fun excursion.

does anyone ever try to connect digital led strip with artnet ? If yes, what model of digital led strip do you use ?