@em_tx Have you tried to install emu ?

@eva said:

Stairville BTL-30

 If this is the correct light. https://www.thomann.de/dk/stai...
These are 7-channel DMX fixtures.. so each light will require 7 channels to be independently controlled.
So if you set Light 1 to reference a DMX channel of 1, Light 2 needs to be set to 8, and light 3 needs to be set to 15, etc...
I suspect your issue is related to addressing your lights. Juriaans patch requires that you can set the Start Channel for each light fixture.

@dusx said:

I spent a few minutes and cleaned up the user actor

 Don't forget to put it on the Add-Ons Page if you haven't already ;)

@juriaan said:

sudo kextunload -b com.apple.driver.AppleUSBFTDI

 Hi Jurian,

thanks for the tip. But this is what I get from the terminal after having put your command

armando-new:~ armando$ sudo kextunload -b com.apple.driver.AppleUSBFTDI

Password:

(kernel) Kext com.apple.driver.AppleUSBFTDI not found for unload request.

Failed to unload com.apple.driver.AppleUSBFTDI - (libkern/kext) not found.

armando-new:~ armando$

Does this menas that the Apple drivers are not installed ?

Thanks

Armando

i ve saw you have an answer but because , one question has often many answer , I would know if it could possible to use user actor ? 

Build your user actor as you builded your first scene , then past that user actor in each scene that you need it . Then each time you need ( new show ?)  Change the value in the user actor in the first scene and when close the user actor , select update all . 

It will work , no ?

Just want to add to this ticket so that the solution is included.

After investigating the ticket, I found that an actor within the Enttec User Actor was experiencing a bug related to initial value parsing.
This bug is confirmed fixed for the upcoming 3.0.3 release, and the Enttec DMX User Actors I have posted to the Plugins Page are not affected by this issue in the current release.
see: https://troikatronix.com/plugin/dx-dmx-universe-enttec-compatible/

@kir said:

Still it took me a day and a half to figure this out with the help of @Juriaan, and the fix is only so-so. I wish Isadora would have a more integrated way to use Artnet or DMX.

Mark here. I just wanted to say I'm sorry you faced this frustration. The implementation of ArtNet is relatively basic, and we haven't put loads of energy into it because we don't have a sense that ArtNet is important for the bulk of Isadora users. Given that we have limited resources, we have to focus our energy towards the items that are most valuable to the most people.

That said, @DusX on the team uses ArtNet frequently so he is a fan, and this means you have someone who will push for a better implementation on the team. From my side, I want to see every feature in Isadora be as easy and robust as possible, beause every capability Isadora offers is increases its overall value. Please continue to offer your feedback. I and the team are listening, and we can revisit what your requests Isadora Werkstatt and see what can be done.

Best Wishes,
Mark

@fubbi great !! No more driver nightmare for DMX !!! Thank you a thousand times. Also because with Sonoma arriving I was worried that would cause DMX nightmare. 

@keftaparty

I've got a eDMX2pro from DMXKing and i'm very happy. The device has two ports and each one can be configured as input or output.

Best.

Javi

I fixed the problem -  I tried Qlab a it "hold me" that there were two files in my library that i should delete to make the DMX USB PRO interface work agin i did and it worked ... 

It was this two...

 - D2xxHelper.kext

- FTDIKext.kext 

Thanks for the replys.  

@juriaan

Either that or inspecting the actual User Actor/Macro itself in the global folder I'd think

Thank you Juriaan, Ryan & Michel! Sorry that I went into full production mode and didn't get a chance to check the thread until now. The method of going into the ENTTEC Send Actor and changing the 'min period' has resolved the overloading issue. I just changed my number to "2ms" and the FPS went back up to 30 already. I will keep testing in real situations and let you guys know if anything else I found, otherwise this topic is resolved for now! Thanks so much!