Delay/Lag Issues With Beam 2.0

Trying out Beam 2.0 for the first time with my set, having issues with a very noticeable ~10 second lag when sending signals to my lights. Happens even with the test fixture command so I’ve narrowed it to be an issue with Beam 2.0. Same issues don’t appear with Beam 1, lights run fine and I was able to do a full set the other night no issues.

Beam is synced with Ableton just fine, and it responds to commands in Ableton, albeit with a 10 second lag. Tried futzing around with settings such as refresh rate, etc. No change.

Here’s my hardware:
ENTTEC DMXIS
MacOS M1 Ventura 13
Ableton 12.1.5
Beam 2.0

I’m having this exact same issue that emme describes above, also with the ENTTEC DMXIS. In my case it’s about a 30 second delay for any DMX changes. Beam’s DMX monitor shows the changes immediately. No such issues with Beam 1.5 or 1.6 – those send DMX data to DMXIS with near zero latency.

Here’s a video of the issue: https://photos.app.goo.gl/sgfpRPRG2YCkab9H7

MacOS 15.3.1
Beam 2.0.2
Live 12.1.10

Hi @emme and @tdk,

Thank you both for reporting this issue!

We had one such report before, but as we have not been able to reproduce it with our DMXIS unit, and as the user had only tried Beam for Live 2.0, it was not clear that this is a Beam-specific issue, considering that similar behavior has also been observed with other software:

It seems that in some of those cases the issue was resolved by reinstalling firmware/reseting unit settings to factory default using the Enttec PRO Manager software, but as the latter doesn’t exist anymore and its successor EMU doesn’t seem to offer an option to do that with DMXIS, we were not able to verify whether that might solve the issue for the user who first reported this.

Your observation that things are running fine using the same DMXIS unit with Beam for Live 1.x suggests that this is likely indeed a Beam for Live 2.0-specific issue, so we’ll get back to investigating this. We’ll get in touch if we need more information - please stay tuned.

Thanks Luka for the follow-up. To be fair, the DMXIS is quite old and not officially supported anymore.

Rather than roll back to an older version of Beam, I used this as an excuse to try out an artnet node and that worked perfectly. So while I’d still like Beam 2.0 to work with my DMXIS box, it’s not currently blocking me.

David

Thanks to everyone who has reported this issue! As DMXIS and its accompanying configuration software has long been discontinued by Enttec, we are unfortunately unable to continue to provide official support for this device.
While several users have now observed this problem, we haven’t been able to reproduce it with our DMXIS unit on several computers, which prevents us from investigating this any further.

We recommend getting an Enttec DMX USB Pro or an Art-Net node instead.

Still, there are a number of DMXIS devices in circulation and it would be nice and planet-friendly to have a fix for this. If you are experiencing this issue, you are welcome to send us your unit and we will have another look. You can get in touch about this via support@showsync.com.

Hi,

NO SIGNAL is transmitted to the lights with my (old blue :wink: DMXIS Box, on both computers Apple silicon (Mac mini M1, and Macbook M1 Max, both Sonoma, Ableton 12.2) unlike my Hackintosh (Sonoma, Ableton 12.2 as well), witch everything worked fine.

Beam is correctly connect with Ableton and receive messages but the lights won’t do anything, even with the little “light ON” in Beam.

My DMXIS Box is seen and connected to Beam, unlike here (that’s why I start a new topic / Solution for him : change hardware) :

Before that, I tried on my Hackintosh, Beam worked fine with the DMXIS box AND transmitted everything to the lights. And my old lights’ plugin (DMXIS VST, on Hackintosh and Apple Silicon M1) works with the lights also, so it’s definitely not the hardware !

Maybe a little problem of incompatibility between DMXIS box and Beam with Apple Silicon ?

Thanks for enlightening the problem

Hey @Bez, thanks for reporting this. I moved your post here, as it seems to be about the same issue.

This is something that seems to affect certain DMXIS units, but not others. As you can see above, we have been aware of this for a while, but hadn’t been able to reproduce it (doesn’t happen with our DMXIS) until recently, when one of our users kindly brought in his unit that finally allowed us to properly debug this.

As I replied to you in the other thread (that is originally indeed about a slightly different issue):

You are welcome to send an e-mail to get a test build or wait until we release the fix in an update soon.

Hi @Luka ,

send you an email to get a test build.

Hi @Luka

Did you received my e-mails about the test build (I’ve got a show in a month, would like to resolve this problem) ?

Thanks for your response