Posts by Clintos

The attributes that aren’t in your current selection do hide once you cycle to something that is but would be nice if this happened straight away of course.

As would filtering in the Smart window obviously

Its very simple to achieve this.

The first way is with width of the steps (exactly the same as grandma2 btw).

The second would be just make 4 steps with one fixture on it each steps. This takes less time than recording 4 cues in MA2. And then instead of needing a separate sequence set to chaser you can just store it in a single cue. Again arguably quicker and easier than MA2.

Unless you use Recipes you will have to rejig your cues just like we did in MA2.

Just changing things in your groups (ie arranging the selection grid) will have ZERO effect on your existing programming if you don’t use Recipes.

In a traditional cue a group is purely a mechanism to select fixtures, it’s not stored in the cue in any way.

To have your fades, delays, phase, etc carry over you will need to ensure you clone specific fixtures to the new fixtures (ie clone fixture 1 thru 12 at 101 thru 112).

Copy and Paste in the patch will also achieve this, make sure you copy the correct fixture for each though.

As for using Recipes for cues being time consuming, this plugin may help with that https://www.gaphux.com/product/store-as-recipe-plugin/

Just select the appropriate drive as part of your script.

Is this because you want to start a new show each time?

The config should be remembered on each restart and also when starting a new show (or loading one) you can choose not to overwrite the output config…

I don't think there is any change to this behaviour currently yes?
The on screen overlay always shows the same executors regardless of the wing setting (ie it does not follow the physical executors...)

I like using the trackpad window in Pan and Tilt mode.

You may have got a bit confused with the actual consoles (non onPC hardware).

The Command Wing XT has powered ports and will let you use a DP-HDMI adaptor just fine in nearly all cases.

Compacts, Light and Full-size require an Active externally powered adaptor.

I actually don’t think you should.

As a programmer my eye is trained to look for the focus frame I know anywhere on the console.

Introducing a change for one dialogue breaks this eye ‘muscle memory’

In my opinion anyway.

This is not the function of ‘stomp’ in MA3.

In MA2 Stomp was a value, kind of like *static* if you will.

In MA3 Stomp is an automated function https://help2.malighting.com/P…eyword_stomp/en/1.9/Stomp

So your workflow in your case would be to re-assert the original static preset.

You could store it as a subsequent cue, tap it twice in the pool, or ON the original sequence. Kind of depends how you want to stop this dynamic effect happening.

I often use it to shift fixtures no longer in use on the show presently so that the actual patch stage is clean and current (think touring).

I also do a lot of themed entertainment programming and we might separate out different parts of the attraction or precinct on different stages.

This forms one of the entry options for the MessageBox component.

Quick forum search for that should give you some good info.

Doesn’t necessarily have to be in patch.

EDIT FIXTURE X PLEASE will open the fixture editor where it can be set on screen without having to actually enter the patch.

There just doesn’t appear to be a syntax to get to this via CMD.

Same thing as a fixture mode really. Technically is part of patch but can still be done via cmd line

There was an error in previous versions that allowed recipes to be added to cues when they should only be able to be added to cue PARTS.

That has been corrected so perhaps this is why your syntax is no longer working.

I’m not in front of a console but does

Set seq cue part 0.1 property "preset" "default.presetpools.21.100

work?

Anyone have a valid command to assign a DMX Curve to a Fixtures Attribute?

What version are you running?

The max is based on the min of the subsequence channel set.

If there is nothing ‘above it’ then the mac will be 255 as there cannot be any unallocated gaps.

Sometimes its easier to build the channels backwards starting at 255 and working down.

Are we considering that correct expected behavior?

Because it does kind of make sense.

This is a confirmed bug.

Please report it to your local distributor anyway.