Hi All,
Im having an issue with a fixture profile I created. There were a lot of questions online on how to get the TMS QX-K stage limps to function properly with DMX. So I decided to order a case of them to test out. After testing them and troubleshoot the issues I read about everyone having do to the direction that came with them were not accurate at all. Ive created a profile and tested on 10 of the QX-K light and everything works fine except channel 1 has multiple functions. So I created two modes. One mode allows channel 1's values to range from 0-255 (Brightness/Flash/On). The second mode is set to only allow channel 1's values to work between 0-127 (Brightness only). But when I add a fixture using the second mode to a project it doesn't limit channel 1 to 0-127 like I have in profile.
If I goto VC it allows me to manually set perimeters and works fine. But since the fixture profile it self isn't importing these perimeters automatically to bypass the lights built in "flash mode" I'm worried this could cause an issue when creating widgets on the fly.
Would anyone mind looking at the profile I made and possibly suggest a way for me to fix this profile please.
Thanks!
Fixture Definition Editer issue?
- mumbles
- Posts: 113
- Joined: Thu Jul 16, 2015 4:39 am
- Location: Central USA
- Real Name: Justin
- Attachments
-
- TMS-QX-K.qxf
- (4.73 KiB) Downloaded 30 times
OSX 10.10.5 QLC+ 4.9.1
Surface Pro4 Windows 10
Raspberry Pi B OLA 0.95
Raspberry Pi 2B QLC+
Swisson XMt-350
Chauvet RDM2Go
Enttec Pro Mk2
ultraDMX Micro
FTDI USB-RS485-WE-1800-BT XLR
Korg nanoKONTROL2
Korg nanoPAD2
Surface Pro4 Windows 10
Raspberry Pi B OLA 0.95
Raspberry Pi 2B QLC+
Swisson XMt-350
Chauvet RDM2Go
Enttec Pro Mk2
ultraDMX Micro
FTDI USB-RS485-WE-1800-BT XLR
Korg nanoKONTROL2
Korg nanoPAD2
- nedmech
- Posts: 83
- Joined: Sat Jun 20, 2015 12:39 am
- Real Name: Nathan Durnan
I have these same lights (or at least another generic clone that behaves the same). I was never able to get a profile to limit the DMX output for that pesky multi-purpose Channel 1 either. What I ended up doing was just using the "Generic RBG" profile in "Dimmer RGB" mode for those fixtures. To limit the output to Channel 1 and keep it between 0-127, I used the "Channels Fade Configuration" tool (purple icon with the diagonal white line thru it in the toolbar). In the Modifier field, I created a new channel modifier based on the "Linear" profile that takes a 0-255 value and transforms it into a 0-127 value. Not as straightforward as changing modes in a fixture profile, but it works well and is transparent to other functions like RBGMatrix scripts.
- mumbles
- Posts: 113
- Joined: Thu Jul 16, 2015 4:39 am
- Location: Central USA
- Real Name: Justin
Thanks nedmech!!!
That helped me out tremendously! I had started manually configuring each scene light to 127. I knew there had to be a better way.
I still hope theres a way to get a profile to work some how. But this work around helps out a lot right now!
That helped me out tremendously! I had started manually configuring each scene light to 127. I knew there had to be a better way.
I still hope theres a way to get a profile to work some how. But this work around helps out a lot right now!
OSX 10.10.5 QLC+ 4.9.1
Surface Pro4 Windows 10
Raspberry Pi B OLA 0.95
Raspberry Pi 2B QLC+
Swisson XMt-350
Chauvet RDM2Go
Enttec Pro Mk2
ultraDMX Micro
FTDI USB-RS485-WE-1800-BT XLR
Korg nanoKONTROL2
Korg nanoPAD2
Surface Pro4 Windows 10
Raspberry Pi B OLA 0.95
Raspberry Pi 2B QLC+
Swisson XMt-350
Chauvet RDM2Go
Enttec Pro Mk2
ultraDMX Micro
FTDI USB-RS485-WE-1800-BT XLR
Korg nanoKONTROL2
Korg nanoPAD2