›

Interaction Group Scope whole project

FredLaFAFredLaFA
in MAIN

Hello,

When I duplicate a board, I would like to keep all the Interactions linked to layers duplicated if I put those Interactions in an enabled whole project group.

It's a way to build several options very quickly except if I have to recreate each interaction as it is actually.

For example :

I link a Midi fader to the scale of a layer

I put the interaction in a Group "whole project" scoped and enable the Group.

I duplicate the board

In the Copy board, The Midi fader doesn't work. If I have 20 interactions in the board, I loose time and may recreate with mistakes.

I would like to have also the same behaviour even if I copy only the layer and paste in another Board.

Does it seem right for you ? If yes, I'll put in the uservoice...

Thanks

Fred

Comments

  • MilluminMillumin

    Hello @FredLaFA,

    Thank you for your feedback.

    Yes, this seems quite fine, please create an idea on Uservoice.

    Best. Philippe

  • FredLaFAFredLaFA

    I already used all my votes so it's written I can't publish a new idea...

    But I wrote it.


  • FredLaFAFredLaFA

    Hello I refresh this last year discussion about Interactions group scopes.

    I didn't find the way to use well this scope whole project or single board.

    If I link for example the opacity of layer x to o a midi or osc it will not work on layer x of a duplicated board even if I selected "whole project" option.

    And there is no written information when we create an interaction of the target board so it's confusing later of which "layer 2" of several boards for example.

    I have no votes anymore on the uservoice so I'll write here another missing :

    If I create an interaction on a shader parameter on layer z, it will work only on the column where I created it and not on others columns if I duplicate the column later.

    It would be great to have in that case a "copy interactions" option.

    Thank You.

    Fred

  • MilluminMillumin

    Hello @FredLaFA,

    If an interaction is assigned to a specific object (specific layer, specific media, ...), it will not affect another object, even this object have the same name. And groups for interactions are for a different purpose : regrouping interactions or enabling/disabling interactions (scope is a limitation, not an extension).

    Rather than duplicating your interactions, this would more efficient and easier to manage to use Millumin OSC API. Click the label of the property you want to control, then Copy OSC Address to use it with your controller.

    This way, you will be able to control what you want whatever is the board or timeline.

    Best. Philippe

    PS : on Uservoice, you can unvote, so you could have a new vote

  • FredLaFAFredLaFA

    Thank you, I'll check these directions.

    Fred

Sign In or Register to comment.