Can you see a message in the system monitor window, when you send the MIDI message to the grandMA3 onPC?
If yes, what does it report?
Posts by dherderich
BECOME PART OF THE COMMUNITY - Sign up here
-
-
x:y means, that this attribute has at least 2 or more channel functions. Channel functions are displayed in the column to the left of each encoder.
3:0 means, that at moment the value 0 from the third channel function is active. Unfortunately, we cannot see the Red attribute encoder in your screenshot.
-
At the moment you can use NDI as the source for a video pool object.
Video pool objects can only be used in appearances so far (v1.5). But I'm sure there will be more to come in the future.
Is your NDI stream listed in the "Select Source" list when you edit a video pool object?
If yes, and you don't see the video, please check if you enabled the "Third-Party Software" button in the EULA-tab of the software Update Menu.
-
Do you use dot2 onPC, a dot2 core, or a dot2 XL-F/B console?
When it is dot2 onPC, check if no other services in the OS are occupying port 80, e.g. the Microsoft IIS.
-
Unfortunately, it has no function until v1.4. But it looks good, that it will work with the next version.
-
Maybe Blind is enabled? What does the DMX sheet display for these DMX channels? Or maybe the iris visualization closes the iris, because of wrong physical values inside the fixture type?
-
Usually you can jump directly. I don‘t know any reasons why it should not work.
-
Instead of setting the value readout for the user profile to PercentFine, you can also enter the values in percent fine notation without the need to change the readout at all.
In your case have a look at the PercentFine keyword:
https://help2.malighting.com/P…eyword_percentfine/en/1.4
(There is a dedicated keyword available for every readout)
And you are assuming, that the user that executes this plugin uses user profile 1, which may also fail. I would recommend using the keyword CurrentUserProfile, when you want to stick to changing the readout of the user profile.
To make it more user-friendly, you could also first grab the current value readout, save it in a variable, set the percent fine readout for running the plugin, and at the end set the former readout instead of switching to the percent readout.
All your variables are defined as global values so that they can be used by other plugins. As long as I don't need the same variable with its content in a different plugin, I would define them always as local. This can save troubleshooting, if I run into a situation, that 2 plugins use the same variable name...
In case, that you have only 1 fixture selected, your plugin will apply the randomized values not to the selected fixture, but to the next fixture, as you execute first the next command and then apply the values. I know, that you have to do next first, but maybe a small if-case can save this case.
And instead of calculating the random value with the range and the minimum value, you can directly get a random value in a defined range:
CodeRandom_Pan = math.random(minvalue, maxvalue);Just my 2 - 5 cents.
-
Sorry, but l cannot see any picture.
But from what I could understand, I think this is a known issue, and I think it will be fixed in one of the next versions.
-
Nice. Is there any link for registration? Is it free? Or paid webinar?
Here is an overview across all scheduled events from Lightpower.
The next event is the LUA webinar.
-
I tested it here with my grandMA3 and I get these results:
local universe 01; amount 01; net 0; sub-net 0; universe 00 = artnet 0x0000
local universe 11; amount 01; net 0; sub-net 0; universe 00 = artnet 0x0000
local universe 01; amount 01; net 0; sub-net 0; universe 10 = artnet 0x0a00
I would have not expected other results at moment.
-
Which version do you use`?
In v1.4 a new selection syntax was introduced.
In your first case, try fixture 1.2 thru 10 please
In case of fixture 1.2 thru I don't get what you want to select. With fixture 1 thru.2 you will select every second subfixture of all fixtures.
fixture 1.3 thru fixture 2.5 please selects all subfixtures of fixture 1 starting at the third one. And with fixture 2.5 within the sytanx your starting again at the top level, and then selects fixture 2.5.
To sum up:
With the dot you're going a level down in the hierachy of the whole fixture patch. Until you start not again with the fixture keyword, you will stay at the current level.
Fixture 1.2 + 5 will select subfixtures 2 and 5 of fixture.
Fixture 1.2 Fixture 1.5 will select the same subfixtures.
Fixture 1.2 thru 5 selects subfixtures 2, 3, 4, and 5 of fixture 5.
To learn the new selection syntax, have also a look at the release notes:
-
Check also theCast Shadow option of the elements:
-
Or maybe you have enabled the Single Step option in the encoder bar?
This option would not let the phaser run, and only output the currently selected step. This allows fine adjustment of a single step.
-
The buttons were removed for the moment, as they were not functional yet. Hope to see them coming back soon, and then with functionality.
-
What are your store options?
Maybe it is best if you contact the tech support or your local distributor with this issue. Please provide them also your show file.
-
You could try to shuffle the y axis by changing the YShuffle property.
„Enabling the x axis“ in the MAtricks window is not enable. It is only show/hide of the different axes sections!
-
Sounds like the Off when Overwritten options for the sequences is enabled:
https://help2.malighting.com/P…n/1.4#toc_header_anchor_4 -
As far as I know, pause for speed masters is not programmed, yet.
-
The forms in the phaser editor are only shortcuts to combinations of acceleration, deceleration, and transition.
You can adjust these layers via the command line. For example:
