Page 1 of 1
The fixture monitor is always at 0, is this normal?
Posted: Sun May 25, 2014 5:52 am
by Prettydirty
My ARTNET/DMX fixture monitor output is black and has a zero value regardless of what color is highlighted on the screen. I am trying to get a supernight rgb led strip to turn red using a redsqure image from modul8. when tested in enttec nmu the sliders for the 3 channels (rgb) all light just fine but I get no response from the led or any output data in the output monitor on madmapper. Please help.
P.S. lighting n00b
Re: The fixture monitor is always at 0, is this normal?
Posted: Wed Jun 04, 2014 12:47 am
by ghostofelvis100
I'm getting a similar response.
It was fine earlier today, but now only seems to work when I select the fixture, then sticks on that value!
but wait, I'm on 1.60 will update and check back....
Re: The fixture monitor is always at 0, is this normal?
Posted: Wed Jun 04, 2014 11:12 am
by franz
With the fixture monitor you can monitor ANY universe.
Are you sure you're monitoring the correct universe/subnet ?
Re: The fixture monitor is always at 0, is this normal?
Posted: Wed Jun 04, 2014 3:13 pm
by ghostofelvis100
Hey Franz, Thanks for the speedy response!
I don't think that can be the problem as it works intermittently.
I'm testing the new 'limited edition Madmapper Show Jockey USB' from the Mapping Fest. Initially I had a bit of trouble getting MM to sense the Show Jockey. I'm running this with M8, and the problem started when I switched syphon sources!
Presumably there's only 1 universe on the USB version (i.e. universe 0?)
Q. Does MM compete with M8 for access to the Show Jockey? Ideally I'd like the option to send DMX from both softwares simultaneously...
And like I mentioned before, when I select fixture it correctly calculates the DMX and sends it, but then remains stuck on that value. And no further DMX is sent either.
I'm using the 'Generic Pixel L'.
MM 1.61 was no better
Any ideas?
Andy T.