Posts by Ringen

BECOME PART OF THE COMMUNITY - Sign up here

    I ran into exactly this today.
    Phone was showing only a few buttons.
    iPad was better but reported resolution was 1104 x 716 and I believe the display is 2160x1620
    Tried resolution setting 'unlimited' and 1080P.

    Any tips?

    Luckily there's always a workaround :)

    I already got it working in my code.
    And you solved the read-problem too of course.


    Thanks a lot Andreas

    This example shows how you can display faders on a dialog.

    This was INDEED helpful.
    I managed to integrate it in my code but I have a question about the fader-values.

    How can I read out the current value of the faders and use it as a number in my main code?

    I've catched it from the caller.value near the end of the script, but I just need the value after the fader is adjusted so I thought it might be a simpler way..


    And - is it possible to set the initial value of the faders?

    When using syntax "FaderTemp Sequence 67 At 10" I got some unexpected result.


    FaderTemp moves X, XA, XB and TEMP

    FaderX moves X, XA, XB and TEMP



    Edit: I see now that they are linked when adjusting the actual fader also, but still...

    Can see how XA+XB = X but don't understand connection to Temp.

    I'm not surprised.
    This is probably the reason for strange behavior on my last show.

    Did not have the time to investigate - just had to repair and move on.


    I noticed the urge to change already defined cuenames automatically to something useless has also gone one step further.

    Sometimes TWO cues get new name during update now.

    I really hoped you were doing something wrong here but can only confirm that this extremely ugly bug exists.

    When this can slip through who knows what else.

    MY old desk had this since 2016 (LSC LX 600) so I'm also hoping for MA to make this happen because I miss that function.
    Having the waveform alongside the events is very helpful - and the obvious way to do it in my opinion.

    I was very surprised when I found out that MA lighting takes NO responsibility when it comes to supply of Fixture Types.
    Every other light control developer in the world, regardless of price range, seems to do that - and have one ready for you in days.


    I've exported from MA2, it could work but probably not very good (I get problems with multiple channel sets) and they're known to not work with cloning.

    I'm using some of these but they usually needs some tweaking in the Editor.


    I learned to make GDTF in the online builder, imported to MA3 and it was changed in the process and did not work. (Not bothered to try in last version)

    Only thing that seems to work good is to make one yourself from scratch in Fixture Type Edit inside the MA3 software.

    Yes, this is the change.

    But I don't understand why..
    The defined Part in a Preset affects the Programmer? - Always? What Preset?

    I would think that in the Programmer the SELECTED Part would be a good Part to use when "activating values in the programmer via the encoders."

    #8 (1.5.2.3)


    I can no longer use Programmer Parts..

    As soon as I change an Attribute it switches back to Part Zero.


    Could it have something to do with this 'Improvement' mentioned in the Release Notes?


    ....This defined part will also be used when activating values in the programmer via the encoders.

    How can it come up, that a GM won't have any effect on my Output?

    I've noticed that if a fixture have sub-fixtures with individual Dim you need to have the sub-fixtures in the Group used for group master.
    E.g. select Fixtures / Press Down / Store Group


    When you assign a Group Master it uses the selected Exec Config for some reason (bug?)
    You might have to define the fader as a master.

    Check settings for the group (Edit Settings) and see if MODE is set.

    If you have another group master for the same fixtures somewhere it could cause problems.


    It could also be that the Fixture Type is missing a setting.
    (Grand and Group seems to do the same thing to me..)

    And is it true, that if I have e.g. 4096 possible Parameters (for onPC usage) and I start to adress from 1.1 on forward, that the first about 8 Universes (4096 / 512 =about 8 Universes) will be used to get DMX-Data from them so I should use Universe 10 (or 11 or above - depending on the amount of 16 or 24 Bit Channels I use...) and above (because of a Parameter is NOT similar to a DMX Channel) for Lamps that are patched but not for use (e.g. to not forget the adress I used former)?

    Yes

    License will by default allow universe 1 and up as long as the available parameters take you.
    BUT you can override this pr. universe in the universe pool so you could get output from universe 50 if you need to.

    #7


    It's hard to get a full hour of work done without running into a new bug.


    Now XBlock has lost count... "XBlock 2" gives me 1, 2 or 3 fixtures selected while next'ing through.

    Seems to have something to do with shuffled selection order, but must be something more to it...

    This is expected. Tapping on a fixture in the fixture sheet adds that fixture to the end of your selection (more accurately, it adds it at the location of the cursor as shown in the selection grid). If you already had the fixture selected, then it moves to the end of the selection. By the way, this is also how it worked in MA2.

    Are you sure?
    I found it confusing.
    Have not really used MA2 much, but since my desk for some reason can start in MA2 mode too I thought I'd give it a try.

    In MA2 it does add the fixture I tap to the end of the selection, but it doesn't disappear under my fingertip!


    Only if I disable and re-enable 'Fixture Sort' will I see the new selection order in MA2.

    This makes more sense to me.

    That's also how it works in MA3 with Prog Only OFF by the way...