Posts by Christof
-
-
Set root "DeviceConfigurations"."DMXProtocols"."sACN"."sACNDataCollect".1 Property "Enabled" "Yes" / “No”
-
This fix somehow seems to be broken in current version.
-
What is the best way to make a colour transition follow a specific path through the color space?
To avoid some ugly colours between start and destination cue.
Do I need several cues or cue parts (allow duplicates) to accomplish that?
-
Activate the Setup Mode in your Layout.
Select all your objects in question.
Edit them: Change [Action] to "SelFix"
-
For me it does work with absolute phasers as well.
-
Yes, this works! But more often a lasso selection unfortunately does not work in one piece.
Too bad the object "selection" doesn't work in so many cases (as it did in MA2).
But thanks anyway for your helpful tip.
Christof
-
I think, not really a bug. More a bad translation from a MA2 Fixture Type to MA3.
And unfortunately ETC also stubbornly refuses to supply proper GDTF fixture types for their devices. Maybe they don't want to support a competitor....?
-
Edit the fixture type. Change the Attribute for Hue to "HSB_Hue" and for Saturation to "HSB_Saturation".
That works for me.
-
I would like to patch a fixture selection in a non numerical order.
I do a lasso selection in the layout that leads for example to this selection order: 1, 101, 201, 2, 102, 202, 3, 103, 203, etc
Now I would like to patch all these Fixtures in one line starting from 1.1
Patch Selection 1.1 does not work (as it does in MA2 with Assign)
Set selection "patch" 1.1 does not work
Is there a workaround?
-
It’s not a workaround though. It’s the intended function of the software.
I know how and when to use filters. My initial concern was only to mention that I find the different behavior of masks and filters inconsistent in this case.
Or maybe I just don't understand the idea behind the coexistence of filters and masks in the fixture sheet ....
-
Yes, I know and use this workaround already.
-
This is pretty much exactly what filters and worlds are for.
Yes, you are right, but the Mask filters by IDType in the fixture Sheet don't work, if you use FIDs for your "Channels".
-
Display More
Hi
You ask the desk to show Fixtures (something which has a fixture ID), so you see all elements with a fixture ID, including them with a special channel ID.
That is very logical.
You can rename ID types in the patch menu.
Channel ID types are here to help you to organise your show and your patch.
Fixtures are fixtures, every thing else is not.
You don't really need to control your basketball platform or your trusses, do you ?
If so, use markers.
In my case, the reason to use separate IDTypes Fixture and Channel is the possibility to filter them in and out in the Fixture Sheet or Channel Sheet.
At a classic theater, there are still many conventional fixtures with only one dimmer channel. I would like to hide these (IDType Channel) in the Fixture Sheet so that it is less crowded. In the Channel Sheet, however, I want to see the dimmer Attribute of ALL fixtures.
In order not to have to select the keyword "Channel" each time when selecting the conventional fixtures, I like to give the IDType "Channel" an identical FID.
I hope this makes sense.
-
Is there a reason you want / need the trusses to have IDs at all in the first place?
A possible reason could be that you can always use the default keyword "Fixture" from the command line for the selection.
-
The masks are working on the basis of logical OR statements. When one of the 2 arguments here (Fixture or Houselights) is true (An FID or CID is given), then the fixture will be displayed.
My understanding is that these masks should filter based on the given IDType and not based on a given or not given FID or CID.
-
For some reason, hiding per mask only works if you set the FID to none for these (houselight) fixtures and only use a CID.
Christof
