When using the colour parameters "Blue_3" and "Green_3", the unit didn't seem dim these colour values when the intensity was set to a level Less than full, however "Red_3" did dim. When I edited the fixture profile to use all 3 colour types as parameters "Red", "Green" and "Blue", the problem went away. Another thing I noticed though was the Green and Blue parameters where on the other side of Hue and Saturation, almost as if they were not included in the group of colours? (on ML Controls).
Also, when I used a pixel map on these fixtures, it would only apply the colour data to the first RGB parameters. It would make sense to me to extend the fixture across 3 cells making cell 1 control RGB 1, cell 2 controls RGB 2, and cell 3 controls RGB 3. I managed to work around this by changing the pixel map patch too each RGB as a different fixture, but I'm sure I read somewhere that eventually pixel mapping will reference the channels in the patch. If that's the case, then I feel this would become an issue.
The units we are using are American DJ Mega Bars (which I had to build my own personality for).
Liam Jones, York Theatre Royal
What version of software are you running on your console? Also what is the exact fixture type that you are using? We have several Mega Bars in a library update coming soon and want to see if it will help the issue you found.
Steven PetersonETC Test Technician
I first had the problem on 1.9.6, but the problem still occurs on 1.9.9 build 39 & 40.
The units are these - Link! We are running them in 11 channel mode.
This is what I'm unsure about though (sorry about the picture being small, the forum seemed to restrict the size of the image).
In the picture, all the colour parameters are set to full but the intensity is set to 30. All the colour parameters (including red_3) are dimmed to 79 except for green_3 and blue_3 which is still at 255. I can only presume that this may have something to do with the fact that green and blue 3 are on the outside of the hue and saturation.
If anyone would like a copy of my show file to test this on, please let me know!
There are a few different issues here related to the RGB2, 3,...etc parameters. Green 3 and Blue 3 have the incorrect default parameter values when creating a fixture. This is causing the inability to control them properly in Live and with Pixel Mapping. Also pixel mapping isn't controlling RGB2, 3...etc parameters which is a separate issue.
You did find the correct work around of repatching all addresses as RGB parameters for Live control and pixel mapping.
Have you tried using the Mega Bar LED P3 profile that was included in the 1.9.9 release? This should also fix the problems.
If you have any more problems and questions, please let us know.
I did not try the personality released in 1.9.9, but I have just checked it out and it is identical to the profile I made.
Sorry to bring this back, but I just thought of a question:
Why does this problem occur in the first place? The units have there own intensity master built in, so why should the desks intensity dim the colour values too? While I completely see the point for a virtual intensity for units that don't have a dimmer built in, I think it makes sense for the units that can dim themselves, to do so.
If I'm not mistaken, with the current set up, does this mean that since the intensity is being dimmed on the DMX intensity channel and also all the colour values being dimmed, that a 1% intensity change is actually a 2% change (there or there about).
I guess that I am not sure what you are asking.
How the color values are controlled depends on how the profile is set up. If you create a profile with a virtual intensity, then the Intens parameter controls the actual value for the color parameters. This would be for fixture without the built in intensity control. If the profile has a real intensity value, then Intens only controls that value. You can create an potentially incorrect profile that has an intensity parameter that also controls the color parameters by creating the RGB params first and then giving the virtual intensity parameter a DMX value. This might be what you are seeing.
Looking at the screenshot above, it looks like you are using a virtual intensity and not the fixtures actual intensity, although it's only a guess because I can't see the actual intensity parameter.
If you want me to look at your showfile, please send it to eos (at) etcconnect (dot) com and put attention Steven Peterson.
It looks like I made a incorrect profile as I think I made the colour attributes first, as you described. Is this a bug that will be looked at? Also, is there a known way to fix this (without having to start again).
Would sending you my show file help now it seems that is my problem?
It sounds like a bug, but there might be a specific reason why it behaves this way. I will look into it a little more.
Anyway, it looks like if you insert a new parameter to the fixture (pan will most likely be created) and then make that an 'Intens' parameter that now intensity works as you want. That was the only way I got the intensity parameter to control only its value.
I probably don't need your showfile unless you can't get fixture to work as you are expecting.