Posts by Martinus



    I'm trying to generate and store colors from a lua script using a dummy fixture 1001 (generic RGB fixture). After reading a bit I'm stuck at getting the attribute values from ColorRGB_R/G/B. Is there a relatively easy way to achieve this, or does it need to be pulled in a more specific way?

    Thanks! I'm not comfortable running devmode for users, so I'll hold on it. It is good to know it exists, I'll let my local distributor know it's a request to pop it over to the stable branch though :)

    Hi there hello.

    Following…ndMA3/macro_create/en/1.9 and the step-by-step to create macros from the CLI, it's all fine and dandy until i try to add something into a line.

    The command

    set 1 command "select exec 301"

    produces an error: Illegal property: Set 1 "select exec 301" CommandDelay ""

    Using List lists the created lines, but they are empty. I've also tried variations over the described commands, those produces an illegal object error. What might I be doing wrong?

    Hi there!

    Have started to learn the basics of Lua programming, and would like to make a plugin to easily create and append an OSC setup based on user inputs and such. I've been able to find and print the necessary parts using:

    local function main()
        local oscChildren = ShowData().OSCBase:Children()
        for i = 1, #oscChildren do
            childContent = oscChildren[i]
    return main

    My question now is how I can add a new child to ShowData().OSCBase with the listed properties?

    If MA was a song, that would surely be the refrain. I will speak with them in a couple weeks, and can then post the reply here.

    It does, however, feel a bit backwards to do so for a one-sentence reply of something with some public interest.

    Thank you! Yup, am using IP address now, but for ease of configuration for others the discovery function would be nice.

    Would it be possible to get confirmation from MA if bundles will/will not be implemented?

    When programming an OSC sender, it seems like #bundle is not supported. Can this be confirmed? Although I can't find it mentioned more than once in the 1.1 vision (not spec) (https://opensoundcontrol.stanf…les/2009-NIME-OSC-1.1.pdf), it is part of the 1.0 spec that should be supported by 1.1.

    From the vendor of the sending software (


    When Send OSC Messages has only 1 drawer item, it sends a regular OSC message. When it has 2 or more drawer items, it sends the messages as an OSC bundle.

    Our hypothesis is that the MA3 lighting consoles don't handle OSC bundles.

    I also don't get auto-discovery going, so it would be neat to have some more documentation/information about the implementation generally speaking.


    In order for Vuo to auto-detect an OSC device (in List OSC Devices or a Device input editor), the OSC device has to advertise itself over Bonjour (a.k.a. DNS-SD, Zeroconf). Is your MA device doing that? If not, you'll have to use Specify OSC Output or Specify OSC IP Output.



    Getting into the recipe part of MA3, I can see a few possibilities for improving the functionality of it. Particularly spread values and variable positions in a preset seems a bit awkwardly handled from a just-getting-into-it perspective at least. Ideally I would like to update my group, update my presets and be done. This without the whole cooking bit.

    An immediate idea that springs to mind (not guaranteed to be good though) could be using "from - to" presets (single fixture, universal), and a phase value as the "spread" setting. Then you could use your base presets (lead/band/out etc.) to quickly fit the show to the venue. This should also go along with the mental framework recipes as far as I've come to understand it. By using phase in this manner, color gradients would also be easy to adjust for instance.

    Ideally, there would also be a phase distribution setting; going from exponential-in, through linear, to exponential out. I'm not sure how this could be previewed in a sane manner though unfortunately.

    Hope this is considered constructive, cheers! :)