Any idea why event triggers set to use the timer and second point value might not be working for BPMIntervalTrigger? I can get transition triggers working just fine, such as changing the intensity of a light source for example, but if I try to change the intensity with an event trigger and use a timer or second point value, nothing happens.
Iâm not completely sure what exact problem you ran into, but Iâll try my best to explain. Each phase in BPMIntervalTrigger offers two types of triggers.
The first type is the event trigger. It fires once at the end of each phase cycle. For example, if your music BPM is 120 and Phase B is set to 2 beats, then it will fire once per second. If you want to use event-type triggers, this is where you should set them up.
The second type is the transitional trigger, which youâve already tried.
If you set up an event trigger but donât see any effect, based on the example you described, the most likely issue is this: you probably assigned an event trigger to change the light intensity, but at the same time you also have a transitional trigger controlling that same intensity. In that situation, the event trigger wonât produce any visible result, because its change is basically overwritten in the same frame by the transitional triggerâs value.
A simple way to check whether an event trigger is actually firing and what itâs doing is to test it with something very obvious. For example, create a new cube shape and set a âToggleOnâ trigger for it in a certain phase, then watch whether it repeatedly appears and disappears on the beat.
Or hereâs another way to test it: (A setup method that follows the rhythmic logic while still creating a slight sense of randomness or drifting offset.)
Letâs say you have two phases,
A and
B.
Phase A has an interval of
2 beats, and Phase B has an interval of
3 beats.
You assign the
light intensity to Aâs
transition trigger, and in Aâs
event trigger, you set the light color to
red.
Then, in Phase B, you add another
event trigger that changes the color to
blue.
What youâll see is this:
The lightâs
brightness keeps pulsing smoothly in sync with Phase Aâs rhythm, while the
color keeps switching between red and blue â but not in perfect timing, since A and B run on different intervals.
Every time their cycles overlap (every 6 beats), the two triggers line up for a moment, and the color pattern briefly resets before drifting out of sync again.
With this setup, on the sixth beat, and assuming thereâs no trigger delay or frame-order variation, B will usually fire after A. VAMâs trigger system generally runs in list order or execution sequence, so the final result will end up being blue.
Visually, the light keeps flashing between red and blue, but because the two cycles arenât aligned (2 beats vs. 3 beats), the color changes slowly fall out of sync. This creates a shifting loop rhythm, repeating roughly every six beats.
*** You should be aware that when using this kind of setup, you need to avoid situations where two phases have intervals that are exact multiples of each other, such as 2 and 4 or 3 and 6. In those cases, the event triggers line up perfectly every few cycles, and one phase, usually the one with the longer interval, will always overwrite the other phaseâs color change right after it happens.
Even though both events are technically firing, the color gets replaced immediately, so visually you wonât see any change at all. The light will appear to stay locked on a single color.
Release Note â C&G-STUDIO Audio Visualizer Suite
