Posts by FilipeQ

BECOME PART OF THE COMMUNITY - Sign up here

    I am trying to create a simple macro so that I can easily turn on/off the "CommandLine Enable" on sequence settings.

    None of the macros below are working:

    Code
    Set Sequence 1 Property "CommandEnable"
    Code
    Edit Sequence 1 property “CommandEnable”
    Code
    EditSetting Sequence 1 Property "“CommandEnable”"


    I am shure this is absurdly simple to solve. I've been trying to find the solution but I am missing some basic stuff for sure...


    Thanks in advance.

    Thank you all!

    Lots of great tips. Lots of ways to handle this issue…

    What applies best to my situation is to change the fixture profile or use sifferent dimmer curve.

    But it’s great to have all this feedback


    Thanks again

    Happy new year

    Hi there!


    I am using a couple of hazers on a theater play. I stored them on several separated sequences, apart from the main one.

    Instead of readjusting the haze/blower values on each theatre venue we go to, I would like to have a inhibitor fader so I could limit the haze machines.


    Since I am using haze personalities instead of two dimmer channels to control them, I am not figuring out how to do this.


    Hope this made any sense. Any suggestions?


    thanks in advance.

    Rikurama :

    That's what I do.

    This is not easy to explain:

    I would like that the command "block cue x" would interrupt the tracking of every single attribute on every fixture included on that sequence.

    For example: if I only store the position and dimmer of a spot, I would like that the block also stored the default values of this spot shutters, beam and focus so the tracking is blocked...


    Hope this makes any sense.

    (I come from the etc eos environment where block works like this. And it has an auto-block tool, which is really useful on theater sequence programming)

    The answer I got from ETC is that they are not interested on GDTF because they are building their own fixture types for eos Augment3d. Since these fixture types are built by them, ETC has 24/7 support when there are issues to be solved.

    My experience with GDTF was far from that. When I had issues and tryed to get some help, I had very precarious or no support at all, even when the fixture types were built by the manufactors.

    I am sure GDTF will be a great tool in a near future though.

    Personally, ai see it in a much simple way.

    When I use “block cue x” I don’t want to block the tracking of the saved paraneters ONLY. I want to block ALL the parameters of every single fixture used on that sequence x.

    That way I am sure that cue is totally protected. (Shouldn’t the LOCK option on sequences sheet do this??)


    I am avoiding to use the example of eos’ blocking and auto-blocking tool… ;)


    zangetsu : that macro might be useful but it seems way too dangerous to use on a fast theater programming environment like the one I work at. Thanks anyway!

    Thanks for the quick response, Clintos


    The reason its not automatic is there are a lot of times where someone WOULDN’T want to add to cues they have already written.

    Sure. Personally I find it messy to work that way (I prefer to build new presets) But I understand why it exists. We all work differently.

    Maybe RECAST could be activated/deactivated on settings


    I will try that command when I have the chance.


    Thanks in advance!

    Some thoughts about block keyword:


    > When you use “block cue x”, ALL parameters should be blocked, even default parameters that are not recorded yet (eg:when you don’t activate/store the default shutter position on the cues)


    > it would be really nice to use the syntax “block fixture x” to block in a fastest way ALL the parameters of a specific fixture.


    Please note that I work on a theater environment. Working on a massive cue by cue show, these small changes would make everything less time consuming then the “select fixture>please please please > store cue/merge” solution.

    These issues might make no sense on other uses of the software.


    I totally might be missing something. Any suggestions or solution are welcome.

    I am still quite new on gma3.


    Hope I was clear.

    Thanks in advance

    Hi there.

    Is there a way to recast ALL presets at once, to make sure all of them are “refreshed” on all sequences?

    Honestly, I don’t understand the need to recast presets after adding new parameters or fixtures on them. In my perspective it should be automatic.

    thanks in advance

    Thank you for the quick response.

    But I'm not sure I got it.

    If you want to get it into an external file, you can dump log the current state once by using the DumpLog command

    Am I able to do this after I shut down the console?

    Sorry, but I didn't understand how to use the DumpLog command... What is supposed to happen hen I use it? In the manuel it says that it is "used to deposit the output of the system monitor in form of a text file". Where is that file stored?

    you can pipe out the messages by using the standard piping from Windows.

    You mean using FileZilla, for example?

    Where will the messages be stored? In the crashlogs folder?


    In this case there was no crash. I just wanted to check the system monitor to find some midi intputs and some possible errors made while operating a theater play.


    Thank you for your time

    Hi there!

    Yesterday I had a problem during a show concerning input midi notes and I would like to check the system monitor info or some log file to understand what went wrong.

    Where is this info stored/where can I fin it?


    Thanks in advance.

    I don't know what happened, but today it works as it used. I was doing something wrong for sure.

    One last thing: is there any way to insert the makey settings in default settings?

    Can´t configure executors MAkeys the same way I used to (at least until 1.6), using the command "Set Executor x makey"

    The only way is to do it on Pages settings config

    Did the synthax changed?


    I really got used to have "hidden" or "safe" buttons that you can only use pressing MA/shift button. And it's great to have a quicker way (macro) to configure them.


    I'm using onPC with a mac; didn't try it on a console yet.