u/kemcds

▲ 3 r/grandMA2+1 crossposts

I'm writing a simple macro to skip the timecode timeline cursor to a specific point in time:

  1. SetVar $timecode1111 = "Timecode 1 Time 1h0m0s0f"
  2. Load $timecode111(Load Timecode Event Number?)

First line sets a variable with the target time of the timecode timeline

Within a macro, second line was expected to prompt the popup to enter the value to fill the "$timecode111" with an "1", but MA is interpreting "$timecode111(Load Timecode Event Number?)" as a whole variable name, instead of prompting the popup.

Am I missing something?

reddit.com
u/kemcds — 12 days ago

I set a 2sec offtime for a executor, but it also offtime the MixColors attributes. Is it possible to offtime only the Dim attribute?

reddit.com
u/kemcds — 12 days ago

https://reddit.com/link/1syky3q/video/opuaz3m8b1yg1/player

I have an LED bar with a master dimmer (coarse and fine) on the main module and virtual dimmers (no channel) on the pixel instances (RGB).

For the dimmer on the instances to light up, the dimmer on the main module must already be on.

To achieve this, I have an effect that allows the main module dimmer to be set always to 100% with the flat-high effect form on effect line 1 (to keep the main module dimmer always at the high value of 100%) and the pixel instance dimmer with the random effect form (low value at 0% and high value at 100%) in effect line 2.

However, with program time enabled or fade time between cues, an expected but undesired behavior occurs: when changing the effect form of the pixel instance dimmer from random to chase, for example, the following situation occurs:

  1. Main module dimmer always at 100%

  2. Effect form of pixel instances in random (i.e., some pixel instances with dimmer at 100% (high value) and other instances at 0% (low value) throughout the effect phase, all normal so far)

  3. Therefore, when changing the effect form of the pixel instance dimmer from random to chase with program time enabled (1sec), the dimmer of ALL pixel instances goes to 100% and drops to 0% within the 1-second program time interval, keeping activated only the pixel instances that are being affected by the effect form at the moment of the random-to-chase fade.

As I said, I believe this is expected and standard behavior, but it's not desired behavior because it breaks the design during the crossfade from random to chase.

Is there any way to make this crossfade smooth without this undesirable behavior?

reddit.com
u/kemcds — 16 days ago