garageCube

Hi,
Is it possible to use the autopilot (sequencer) mode to assign the duration of each cue in bits?
It seems to me that such a function (especially for cues consisting of sources) would be a very good alternative to the time code.

Best regards,
Andrey.

what do you mean by bits ?
can you post an example ?

Hi franz,
We use an external BPM Waveclock generator. Accordingly, MadMapper receives tempo bits from it, which I’m talking about . You can have a duration multiple of 4 bits (4, 8, 16, 32, 64) used for similar tasks in other programs (for example, Resolume Arena). MM uses bit cue duration binding, but if I understand correctly, you cannot use this setting for each cue separately.
Andrey.

Hi,

I think the answer is yes. Let's clarify: in madMapper you can make scenes & cues, in the same grid. Scenes is the first row. Scenes are restoring the complete state of the document (surfaces, fixtures, medias, and some modules, ie Audio Player - Cue Scheduler and Cue Calendar are excluded from scenes by default). Cues are storing a user chosen set of parameters (ie you can store only surfaces colors on a cue grid row, while storing different sets of media assignment on another row)

We added an "auto-play" in the cue bank to make a common request as simple as possible, this auto play triggers full columns, so if there's a scene it will start it, if there's no scene in this column, it will trigger all cues (order bottom to top).
Then we added the possibility to defined "local" auto play settings per column where duration can be defined in seconds, "beats" (number of beats computers by BPM Global - so can be taken from audio analysis, MIDI Clock, user BPM or Ableton Link)
I think this last feature is what you requested.

Cheers!

ok I get it, you meant BEATS, not BITS.

Hi franz.

Yes, I meant BEATS...
Thanks for the detailed answer. If I understand you correctly, then the second option is really what we need. We will test tomorrow.

Best regards,
Andrey.