Posts by DanielK

    So, got some results here already :-)

    Ringen : We can reproduce the issue with the channel functions on the 5th encoder and will address this to our developers. Thanks for this!

    What we can not reproduce is the issue with the value jumps when you press the encoder. Could you maybe do a short video where we can see this and send it to us (

    That would be really helpful. Thanks a lot!

    Hey guys,
    thanks a lot for your feedback. This is always very helpful for us.

    • Regarding the Fixture At Fixture issue: This is something we are already working on for the next software version. So we know that there are some issues but this will be definitely improved.
    • The "Do not save" bug is also known and currently we are working on this to fix it!
    • About the issues with the dual encoders - some of them are known, but some seem to be new as well (at least for me ;-)). Let me check this and address it to our developers.

    Thank you very much again. This feedback is highly appreciated!

    Hey hannie,

    the difference here is that in the MAtricks window 0 thru 360 is really 0 thru 360 - so the first and the last fixture will do exactly the same.

    Setting the phase in the encoder bar takes your number of fixtures and recalculates the phase, so that all fixtures do something different.

    But as mentioned this behaviour most presumably will change again.

    Hope that makes sense....

    Hi hannie,

    Bentoylight is correct. When you change the phase to 0 thru 180 that should work.

    The issue here is that currently the phase is not recalculated when you set it in the MAtricks or Recipe dialogs - that means 0 and 360 are exactly the same point. It is different when you assign the phase via the encoder bar - then it will be recalculated for the number of fixtures (columns in your selection grid).

    We expect this behaviour to change again, to have a recalculation in all dialogs.

    You can try to work with the ProgramSpeed Master.
    So you set the fade time using the ProgramSpeed Master and it will be used for everything which happens in the programmer - so calling presets as well.

    Then you can also use your "normal" presets without an individual timing.

    Hi guenter,

    there is a bug currently that switches to default values before using the individual timings. This will be solved most presumably in the next software version.

    So everything you did is correct, but not the software in this case :-)

    Hi Jerome,
    ASCII import is currently not implemented in grandMA3. Another thing which is work in progress is to store the DMX input - this is going to be implemented in one of the next versions.

    But maybe you can get in contact with your local distributor. They can help you to transfer at least patch and fixture type information depending on your show.

    Hi Dan,

    thanks a lot for this feedback! Let me try to comment on some things here:

    Subfixture selection with the 3D window

    You are definitely right, this is something to improve. It is also about how the main fixtures will display things in the selection grid - but we are working on this.

    Create a layout view from the camera

    This is something which will be implemented in the next version 1.5. We can already see it in the alpha versions. What will also be possible is to create a layout from the selection grid - so you can keep the grid look in a layout view.

    Selecting subfixtures in the grid

    As you know the Up/Down keys place the subfixtures in a grid - this is a big advantage to use some easy grid arrangements for LED walls etc. But since v1.4 we improved the selection syntax to deal with the subfixtures in a more proper way. What you can do:

    - Fixture 101 thru 110.thru Please --> this will select all subfixtures of the main fixtures 101 thru 110 and place them in a row in x-direction

    - Grid 0/0 thru 0/100 Please --> Creates an area in y-direction in the selection grid. Then you type again Fixture 101 thru 110.thru Please and your subfixtures will be arranged in y-direction.

    In general we are also working on some more tools of course to edit the selection grid, move the fixtures, turn the whole grid around etc. But this is some more work to do. Maybe you also find this thread as helpful:

    Working with the Selection Grid

    Here you can find a LUA plugin which provides some very clever tools to deal with the selection grid.

    Hope this answers some questions :-)

    Hey mlogdstrom,

    you are right, this behaviour will change. At the moment the individual timings are grabbed and you have to switch them off automatically. But we are working on it.

    Hi jlevesque,

    in general it can be possible to build a grandMA3 network session via VPN.

    But I would recommend to get in contact with your local MA distributor. They can help you a bit more in detail in discuss some aspects of network and session handling with you directly. You can also get more detailed MA-Net3 information.

    Hi hui123,

    there could be some reasons for this behaviour....

    - Network problems in between

    - Some things in the showfile

    - Hardware issues

    I would recommend to contact your local distributor with a detailed description of your network. Maybe the processing unit has to be repaired as well....

    Hey Felipe,

    in general we have different possibilities here:

    - You can use Stomp to go back to your step 1 and combine it with a direct absolute value.

    - You can use Stomp to go back to your step 1 and combine it with a Release value - so when your position should come from a different executor.

    What is the issue at the moment is the combination of absolute and relative within one sequence. So currently we always recommend to work with absolute values and relative changes in different sequences. But we will see a lot of improvements of this behaviour in the next version.

    Sorry for having not the best solution right now, but we are working on it.

    Hi Henk,

    your description is a known bug currently.

    The problem is that fixtures snap to their default values in the programmer before they use the individual timing.

    That´s the reason why preset 1 with 100% looks good in the programmer and preset 2 not. The fixtures snap to 0 (which is the default) and then use the individual timing - but then you can not see anything.

    This bug will be solved in one of the next versions.

    Hi both,
    so in general as you said this is quite expected behaviour. Stomp deletes all steps >1 and goes back to the absolute value of step 1.

    What you need in this case is a third executor which has the blue again and is at the same (or higher) priority as your sequence with the phaser running. Then it would automatically stomp the running color phaser and would playback the blue.

    But you could do the same with your basic look sequence of course. Have it at the same priority and the LTP behaviour takes care that you run the color phaser and when you press the basic look executor it will be automatically stomped and sets the fixtures to blue....

    Hope that helps....