Resolume Forum

Any news about the ability to use ArtNet in two applications on the same computer ? cf this thread.

Even if you implemented the Lumiverses,
some people still need to use MadMapper AND Arena on the same computer,
and would love to stop going thru an Enttec USBDMX !

pmdjh wrote:I am starting to wonder if there is an order of operations issue.

When it was not working on Arena5, did you launched "Artnet monitor" before launching Arena5 ?
If some app is listening to the ArtNet port, Arena wont listen to it.

Loading a deck takes few seconds (depending on how may clips you have inside),
so you should do that not in the same cue as triggering the clip.

Unless you have a ton of media (more than 250 per layer for the whole show)
You can use only one deck and using columns 1-10 for the first song, 11-20 for ...

Any news on that point ?

UDP ports can be opened with non-exclusive mode, so others can connect and listen the same port, and most of the Art-Net apps on OSX works this way (not sure about Windows).
It's also possible on Windows, I successfully used multiple art-net applications on the same ...

Same here.
Smooth Y-X moving is currently really hard to get with dmx,
even going thru a link to be able to ajust from where to where you wanna go, 256 steps is still too few for a slow translation.

I don't see a reason why you would still broadcast to every IP on the network, once you have seen the info and have confirmed that you are connected to the right node.
If you want to implement a "auto-unicast" (that's what you seem to mean),
it's useful to keep a way to manually force the ...

Every user I know who tried to use Arena (with ArtNet control) and MadMapper on the same Mac
ended using a "Enttec DMXUSB Pro" for Resolume controls, to avoid the binding of all the interfaces...

I'm actually first converting ArtNET to DMX with a "Luminex Node8" then sending the DMX to Resolume ...

Hello,

I have an other issue with controlling Arena 5.0 using DMX (thru a Enttec USB-DMX Pro),
this time on AV Faders and A-B Faders not sticking to it.

When the "AV Fader" DMX value of any layer goes "cut" (not fading) to any other value than 0% or 100%,
the AV fader moves but the A and B faders ...