this section of the manual seems to be a little ahead of time.
in the releasenotes of v1.0.0.3, Cue Only is listed as yet to come...
As a workaround you can try the Block and Unblock command
e.g. blocking the whole sequence while you do a store that you don't want to track:
Block
Store cue 2 /merge
Unblock
as Dominik described, the function works slightly different in gma3 vs gma2
In gma2 the default clone scope is 'everywhere'
In gma3 v1.0.0.3 the default clone scope is the Programmer
try :
Clone Fixture 601 At Fixture 101 If Sequence Thru
I would believe this is intentional.
I don't want my houselights to be directly selected by ifOutput.
If one want fixtures with a Custom ID to be selected by IfOutput when Fixture is selected ID-type, one can choose to not remove their FixtureID when adding the CustomID
- seems like the calculator is currently limited to +- 100%
both encoderturn and commandline can be used to over/undershoot.
tip:
if you select the "Move Handles" tool in phaser editor, you can see the bezier control vectors, - also in 1D-layout
tip2:
the visualization of bezier vectors has some glitches in 1D layout, when next step also is previous step.
- so add a third step, to properly visualize in 1D layout the vectors for step 1
Please notice that the popup calculators have separate keys for subtraction and negation.
the subtraction key ( - ) , enters the minus sign with a space
the negation key ( +/- ) , enters the minus sign without space
Just to be clear, the +/- button in the calculator is the negation key, so following the keypresses in the tutorial means that you entered the value -100%.
---------
This is not easy to explain with just text but let's try....
- to my understanding:
An Acceleration of 0% represents a linear transition to the next step, the exit vector, has the same angle as the direction to the next stepvalue.
An Acceleration of -100% represents a ease-out towards the next stepvalue, the exit vector is horizontal.
A Deceleration of 0% represents a linear transition from previous stepvalue, the entry vector has same angle as direction from the previous stepvalue.
A Deceleration of -100% represents an ease-in from previous stepvalue, the entry vector, is is horizontal.
When entry and exit vector both are horizontal the transition is smooth, as a sinewave
Acc/Dec with even lower value than -100% represents direction vectors further away than horizontal, in other words in the wrong direction of the target.
Acc/Dec with positive values represents the equivalent vectors on the other side of the vector of the linear transition, representing a more aggressive entry/exit
for testing try the following with some fixtures selected:
At 75
Next Step
At 25
Step 1 + 2
Accel -100
Decel -100
Accel -400
Decel 200
Accel 100
Decel -300
When the sum of Accel and Decel = -200, the entry and exit vectors are parallel
When entry and exit vector are parallel, the transition is stepless/smooth
The math behind is bezier curves, the valueranges are normalized for easier interaction.
This bug seems not be related to storing out of order, but to storing cues below Cue 1, which by default will have Release mode enabled.
Please turn off tracksheet display and disable the Cue property "Release" for these lowered numbered cues.
To my knowledge there is no good workflow for cue-part management yet.
However, a macro that goes something like this seems do the job:
(assumes your sequence is selected, your multipart cue is active, and your programmer is empty)
Store Part 99
Block Part 99 If Part Thru
Move Part 99 At 0
Delete Part 1 Thru
to reset all properties of the matricks object, try
Reset Matricks
tip:
check the commandline feedback when operating the MAtricks window.
tip2:
you can set multiple properties in one go:
Set Matricks "xwings" 2 "xblock" 3 "xgroup" 4
tip3:
if you are creating macros, write the full syntax, in case shortcuts are cultivated in upcoming software versions.
Hi Axel,
the MAtricks functionality maybe could be an easier approach?
e.g.
mat "xwings" 2 ; ph 0 t 180
mat "xblock" 2 ; ph 0 t 60
The main purpose for screenconfigurations is to allow a second station (typically a 3D computer) to use the same userprofile as the primary station (console/onPC) to enable sharing of cameraselection, programmercontent, etc.
- But to display different/other Windows on the second station (e.g. permanently a full screen 3D window)
Without the screenconfigs option, the second station would merely be mirroring the screens of the primary station, when using the same userprofile.
Screenconfigurations are a subset of the userprofile, so any alternative screenconfigs you create, are export/imported with the userprofile.
Screenconfigurations rely on objects in other sibling subsets of the userprofile (e.g. viewpool/views), so the usecases for exporting only the screenconfig subset is quite limited, (if there is any at all), thus import/export-support of this sub-object is "yet to come"
What is your actual purpose, what are you trying to achieve?
the screenshot I am seeing is a generic editor, that would open for any object you call by Edit, which hasn't a dedicated editor or other defined edit-behavior.
This generic editor may have generic buttons & function that relies on information of the object, which may not yet exist ( e.g. a proper import/export path) thus will not always have full functionality.
Where in the manual did you find the topic regarding support for exporting screenconfigs?
seem that your computer does not meet the minimum requirements:
Seems you need to refine your syntax
try checking the keyword reference of the manual,
(keywords: Import, Export, Drive, Library)
To my understanding, export from the grandMA2 library to the open format GDTF is not possible/allowed.
The grandMA2 library is based on data from a third-party database, licenced for use in MA consoles only.
The Stage tab lets you define objects that divides the whole Schedule into different physical Location, and are userdefinable top-level objects in the object-tree, each with its own bounding box and own origin/zero-point. Use multiple stages if your system covers multiple venues, rooms or stages.
A 3D Window (Formerly known as Stage Window) will visualize one Stage (or Room, Venue etc)
With the Stages concept you can visualize different venues/stages/rooms in different 3D Windows, within the same showfile
Try to get familiar with the Filter button. (shaped as a funnel in the top right) When your object tree grows, using Filters to only see what you want is a big help for navigation.
If you want to filter on your own terms, not only by Fixturetype, or DMX address etc, head over to the Layer and Class tabs, and create your person grouping preferences.
e.g. Layers: Floor, Roof etc
e.g. Class: Wash, Spot
assign the appropriate Layers and classes to your fixtures, and use Filters to easily find your Wash fixtures that are on the Floor.
Unfortunately the background properties didn't make it to the "List Appearance x " response in the commandline feedback window in this very first release version.
It seems however even if not being exposed by commandline feedback you can still manipulate these properties by syntax.
Please try the property names BackR, BackG, BackB and BackAlpha, with decimal 8bit values (0-255)
Be aware that this syntax likely will change in future version, for consistency in property naming and value format
Are you able to save and load showfiles with this stick on the console? is it formatted as FAT32?
Rex & Sille,
The gma3 Fixture Schedule is a representation of the real world.
The real world includes not only lighting fixtures, but also any other physical items.
When you hang a fixture on a truss, or put a floorcan on a drum-riser, they all need to be able to be connected in the same object tree, - you should recognize this from gma2 3D
for virtual, nonphysical relations, e.g. "Wash Lights" you have two dimensions, Layer and Class, which can be used to group items you feel belong together, across any physical relations, which you later can filter by.
Please also remember that this is version 1.0.0.3
I am sure that we in the future will see improvements in workflow on the subject of importing scenery and other custom objects.
