Understanding Dependencies

danm

I'd like to better understand the semantics of certain dependency relationships in Loopy Pro and how these relationships are set up.

As an example,
On one page, I have a a number of rows of clips set up as a play groups and a button to the right of each row/play group that triggers the clips in the play group to play.

On another page, I have a Clip Slicer that is bound to one of the clips, say clip 1, in Play Group 3.

When pressing the button next to Play Group 2, this button "lights up" and the clips in the play group next to this button play.

While the clips in this play group are playing, if I go to the other page and tap around on the clip slicer, then the button next to Play Group 3 "lights up" and clip 1 also "lights up".

Can you explain what specific aspects in the config create this dependency and where in the UI/Setup one can make the choice around how these dependencies are set up.

Thanks,
Dan

espiegel123

@danm : when using a clip slicer, you are playing the target. So any buttons that would be highlighted as a result of target 1 would be highlighted.

You may find this page about State Feedback worth reading: https://wiki.loopypro.com/State_Feedback

danm

Thanks.
The button next to play group 3 in my example has Target "Play Group 3" and action "Play".
The clip slicer is not ever acting to play "Play Group 3" (which is the target of the button), rather the clip slicer is acting to play clip 1 (in Play Group 3) yet just playing this one clip in the group is turning the button on, which is what I'm wondering about and also not sure this case is explicitly covered by the description in the State_Feedback page you cited (let me know if I missed it).

So, can you explain if there's a config that creates the dependency between a play group and the clips it contains and if I can modify this in a way that might make this more intuitive (ie: The button is "on" when something triggers the play group to be on and the button is "off" when something triggers the play group to be off, but the button state/visual doesn't change when something triggers a single clip within that play group).

Because I want the button to light up when the play group is playing or not playing as a whole, but not when the clip slicer plays audio from one clip that's part of the play group.

I can certainly figure out some workarounds, like using a duplicate of the clip 1 audio (that's not part of the play group) to bind to the slicer to break the dependency, but I also think it'll be helpful to others, not just me to better understand how this works, so thanks for any clarifying comments or pointers you can provide.

Dan

espiegel123

@danm: if any clip in a group is a playing Loopy will treat the play group as active. That isn’t configurable.

Since a clip slicer works by playing a clip, if state feedback is on, the group the clip is in will show as playing

danm

Understood.
Would seem more intuitive to me to treat a play group as active when either the play group has been activated or when all clips in the play group are active and to treat the play group as not active when either the play group has been de-activated or when all the clips in the play group are not active

Thanks