Hello Philippe
Je teste la Beta V2+, la gestion des lights est une excellente idée, simple à intégrer et configurer - chapeau !
J'ai testé cela avec des lyres et mappé les fonctionnalités des lights via touch osc pour en faciliter l'ergonomie.
Voici cependant les limites rencontrées :
- Dans le dashboard le controle fonctionne parfaitement via osc
- Dans une timeline, quand des points clefs sont integrés on ne peut plus modifier les valeurs des fonctionnalités via osc : la timeline force la valeur et en empeche toute modification.
> Il serait super de pouvoir garder la main afin de générer de nouveaux points facilement !

It would be amazing to allow a timeline to have an offset Start TimeCode.

The scenario is as such

A master timeline synced to timecode would playback a whole show, the master timeline contains other timelines for each song/moment in the show. This way, when editing a specific song, it can still be playing back in sync and have it's timecode offset relative to the whole show, and yet when we play back the whole show in the master timeline, that timeline can be synced to the master of the show clock.

For example
Master Timeline --> TimeCode starts at 00:00:00:00 [all media placed in this master timeline would follow master timeline timecode and ignore their internal TimeCode]

Timeline (Song 3) that is supposed to start at TimeCode 04:00:00:00 in the show should be allowed to offset it's starting to TimeCode 04:00:00:00 when editing it.

A "3D" timeline. For instance allowing to put a recurring event, which remains active once activated, even if I go back in the timeline.

In the short term, maybe a very simple thing to allow simplified access from an environment to another, would be making available to our diverse controllers:
- the direct activation of layers (as for columns, without passing through opacity)
- and, above all, the dashboard selection options ?

________________

Une timeline pensée en “3D” -par exemple pouvoir poser un événement récurrent dans le temps, qui reste actif une fois déclenché même si je reviens en arrière dans la timeline-.

À court terme, peut-être une chose très simple à faire pour permettre l’accès simplifié d’un environnement à un autre serait de rendre accessible aux divers contrôleurs :
- l’activation directe des layers (comme pour les colonnes, sans passer par l’opacité)
- et surtout les options de sélection de dashboard ?

Specify transition time when recalling column using OSC message:

The idea is to be able to transition to a column in a specific amount of time when using a external cue manager.

This can be expressed by this articulation:

Transition to [ COLUMN_NAME ] in [ TIME_MS ] milliseconds.

This way, a stage manager could manage a OSC Cue in his qlab for instance that does ' transition to "column_1_blackout" in 10000 ' and 'transition to "column_2" in 5000' and still be able to change this time value without having to interfere in the Millumin composition.

The simplest way to integrate it on message side could be to add a float at the end of the recall message as following.

/millumin/action/launchColumn "column_1" 5000

The time value does not have to change the transition time in the Millumin set, it should only trigger a temporary transition time used once. If no time value is sent in the message, Millumin should fall back to the set specify transition value.

The particular use case where this needed emerged is on a theatre show where Millumin is used to compose the different video scene and a Qlab is used to recall these columns alongside other parameters and timing ajustements.

This way, a Millumin set could have only a empty column (blackout) in the first column and populated column in 2, 3, [...], n .
The qlab could recall non-sequencialy the different column with different timing value and this way skip the redundancy that is needed for some use case (particularly; blackout);

for example :
/millumin/action/launchColumn "column_1_blackout" 0 /*start on column 1, in 0 ms (skipping the transition time) */
/millumin/action/launchColumn "column_2_scene_intro" 5000 /* transition to column 2 in 5000 ms */
/millumin/action/launchColumn "column_3_scene_outro" /* transition time default to what is in the Millumin set because time is not specified in the OSC message */
/millumin/action/launchColumn "column_1_blackout" 10000 /* fade back to 1, in 10000 ms */