Enttec PRO INPUT question / issues
Posted: Sat Jan 11, 2020 5:20 pm
I am interested in external input control surfaces and was curious if incoming DMX information can be used to operate sliders on the Virtual Console?
In so researching, I purchased a NEW Enttec DMX Pro to augment my existing and rather old Enttec Open DMX, a very early run black not blue box, no serial number even shows up when plugged in (perhaps normal ?).
The theory was plugging an old (~2006) Scene Setter 48 DMX output into the DMX Pro, but hardware issues arise.
Having some moving heads plugged into the DMX Pro output and operational under QLC+ 4.12.2 under Ubuntu, plugging the Scene Setter 48 into the DMX Pro input causes (best guess) a timing issue and loss of DMX signals to the moving heads (they glitch* out repeatedly every 10-15 seconds). Glitch= looses DMX signal (DMX indicator turns off) and wild random movements.
Moving the Heads to the Open DMX and only using the DMX Pro for input, the moving heads don't glitch, but QLC+ doesn't see anything from the scene setter.
By best guess is a timing/synchronization issue in the buffering inside the Pro. Not sure if it is some option in the DMX Pro hardware setup or an OS issue (suspect not) or a QLC+ driver/handler issue.
I am sure that others in other setups (Windows, Enttec "driver", commercial software) probably can accept incoming DMX signals and programmatically do things with that information. But not entirely sure.
--Doug (dx9s)
In so researching, I purchased a NEW Enttec DMX Pro to augment my existing and rather old Enttec Open DMX, a very early run black not blue box, no serial number even shows up when plugged in (perhaps normal ?).
The theory was plugging an old (~2006) Scene Setter 48 DMX output into the DMX Pro, but hardware issues arise.
Having some moving heads plugged into the DMX Pro output and operational under QLC+ 4.12.2 under Ubuntu, plugging the Scene Setter 48 into the DMX Pro input causes (best guess) a timing issue and loss of DMX signals to the moving heads (they glitch* out repeatedly every 10-15 seconds). Glitch= looses DMX signal (DMX indicator turns off) and wild random movements.
Moving the Heads to the Open DMX and only using the DMX Pro for input, the moving heads don't glitch, but QLC+ doesn't see anything from the scene setter.
By best guess is a timing/synchronization issue in the buffering inside the Pro. Not sure if it is some option in the DMX Pro hardware setup or an OS issue (suspect not) or a QLC+ driver/handler issue.
I am sure that others in other setups (Windows, Enttec "driver", commercial software) probably can accept incoming DMX signals and programmatically do things with that information. But not entirely sure.
--Doug (dx9s)