This is not possible, yet. Only native MIDI input via a Command Wing or an I/O node is possible for onPCs.
Posts by dherderich
BECOME PART OF THE COMMUNITY - Sign up here
-
-
Is MIB active in this sequence?
-
Yes, but at moment you have to switch it into Mode2:
-
When the parameters that will be unlocked by the compact console are enough for you to visualize, then you don't need the viz-key. In this case, you can use Art-Net or sACN to feed capture with the DMX data.
If you want to patch more parameters as the compact console will grant and you want to visualize them all together, then you have 2 options:
1) Take enough processing units into the session with the compact console.
2) When you don't want to use the processing units in this case, then you need the viz-key.
-
Which version are you running?
Was the path before "Shared>Resource>lib_mvr" refecting the first three digits of this version number?
In the import dialog, is the button at the top right set to internal or to a USB drive?
Did you import the image to the image pool before you tried to use it in an appearance?
-
As far as I know, this is a bug.
-
One side note:
Your system does not meet the minimum required specs:https://help2.malighting.com/P…ystem_requirements/en/1.4
You need Windows 10. Windows 8.1 is not officially supported. The side effects of using Windows 8.1 can be manifold.
-
Have a look at the fixture type in the patch menu.
Each beam geometry has a color temperature property. This color temperature is used by the 3D window.
-
Quote
7. What is the utility of the keyword « Action » ? I did not understand the explanation in Help documentation.
QuoteIt's not especially relevant for most day-to-day programming. I don't have a better explanation for it though. Perhaps dherderich might have one?
As the action keyword topic already explains, the Action keyword is used for special operations that do not have a designated keyword for this special operation:
https://help2.malighting.com/P…MA3/keyword_action/en/1.4
At the moment, this is the case when working with the position calibration within the 3D window.
When using the position calibration, there would be the need of several keywords like StoreCalibrationPoint1, StoreCalibrationPoint2, ..., CallCalibrationPoint1, CalCalibrationPoint2, ..., SolveCalibration. This would have resulted in 9 different keywords.
Therefore, the more versatile keyword Action was introduced. Together with the Action keyword, the desired action has also to be defined when executing it in the command line.
In the future, it can be the case, that the Action keyword might get some more options to do special operations.
In general, Action can trigger operations that are not used so often by users.
To learn more about the 3D position calibration, read here:
-
Maybe the signal is too loud or silent for the hardware input.
-
There are 2 separate ethernet interfaces.
-
And you are following these steps?
-
Assign Group a At Preset x.y.z
Assign Preset b.c at Preset x.y.z
Assign MAtricksPool d at Preset x.y.z
x.y.z:
x = Preset Pool ID (4 for color, 21 for the first All pool, etc.)
y = Preset ID
z = Recipe ID
-
No, at moment only the label (as you can see above the fader) of an executor displays the appearance.
-
Das ist doch soweit im Manual beschrieben:
http://help2.malighting.com/Pa…hor_3#toc_header_anchor_3
QuoteThe dot2 Node4 (1K) allows you to control 1024 DMX channels if you connect a dot2 onPC and a dot2 Node4 (1K). A dot2 onPC can only control 1024 channels if it's not connected to a dot2 console.
-
Your input is disabled. The input button at the top is off.
-
I tested it here with macOS and it worked.
Do you have a session running? The macOS station would be then in the state of IdleMaster or GlobalMaster.
-
Yes, this is the intended behaviour.
When you want to use global data as source, use a Global fixture as source: Clone Global x At ...
If you want to clone and get global data at the destination, use a Global fixture as destination: Clone ... At Global y ...
To clone global data to global data: Clone Global x at Global y If Preset a.b.
-
This should do the job:
CodeSet Macro x.y „Enabled“ „Yes“x = ID of the macro
y = Line within the macro.
-
When your update mode in the update menu is set to "Original Content Only" you can only update the values of attributes in cues, where they are stored.
You can change this setting to "Add new content". Then data can be added to every cue via the update function.