Video Router Inputs

[AcdNrg]

Is there a way to have "crossfader output" as an input for the video router source?


What I´m trying to build is something like this:

Group A = Layer a1, a2, a3 -> everything assigned to crossfader A
Group B = Layer b1, b3, b3 -> everything assigned to crossfader B

A "Master FX" layer that affects whatever I crossfaded to and send that to the output.


Currently I can only pick group A or B (or the different single layers) as video router input for any effect on the Master FX layer.

One very crooked way to build this might be:

Master FX group
mfx layer fx = holds fx clips
mfx layer b = just a single video router object that takes group B as input
mfx layer a = just a single video router object that takes group A as input

and then simulating a crossfader by binding the opacity of both input layers to the same MIDI CC, inverting one of them. We do have crossfader results as a source for the monitoring, why not in a video router?

But that´s a workaround I´d rather avoid by finding a more elegant way

[Zoltán]

Doesn't placing the video router above the last crossfaded layer work to pick up the result with layers below?

[AcdNrg]

Unfortunately it doesnt.

Here is my setup:

(EDITED, layers renamed)

Adding a router to MFX/src a for example works when I set source to "A" (group) but shows blank when I select "layers below". I´ll double check tonight whether some misconfig happened, but maybe there is something obviously wrong in my setup - I´m still learning the ropes.

[Zoltán]

Looks like You have the crossfaded layers in separate groups.

Groups have their own crossfader passes, in this case, the A and B layers in different groups are actually not crossfaded together. If you move them out of the group, then the layer router (also not in a group) should catch the crossfader output.

[AcdNrg]

Understood, that is the root cause then. The groups A and B are to stay though, as they are needed to recall a combination of their subtracks via the group columns.

But that´s ok, the workaround via the two "grabbing routers" works for me and I can flatten then if I run out of GUI real estate.

Thanks for reviewing the setup, it may not be the most common use. Basically it´s based in my history with DAWs, as I like to think in tracks, groups and masters as well as inline and send fx. It´s probably a bit forced to apply this logic to resolume (as in: a visual DAW = DVW) but the fact that I can actually run things that way speak for resolume´s flexibility.


Cheers!