VL3 3.0.62 Routing Issues

App	Global Layer/Stacks should not be able to route to Tune Channels

Can someone describe what the App Area is?
And what is a Tune Channel?

Application area

Sorry, “Tune” is our internal name for “Song”.

Thanks … why I‘m asking: I try to figure out if my Project still works if I update, because I have to select the Output of a Global Channel pointing to a local whatever (the things we discussed). And I have a feeling that the solution was, that i can‘t do that anymore.

Inconsistency:

A Global Stack can Send to a Song Group in the mixer.

Add another Song and the Send still points to that Song Group even though it does not exist in the new Song,

Also. Surely the Mixer Send dropdown for Pre-Insert/Pre-Fader/Post-Fader should highlight the currently selected config when opened?

Yes, it is somehow unfinished.

But while they didn’t fix it, let’s call it a feature that no other DAW has. I mean you are free in doing whatever you want and if things connect, you get sound :wink:

Also. I agree a little about showing current config in drop-down menu, but maybe this could help you and some others - imagine the icon as a knob (called Fader), then

  • if dot replaces right half of knob, it’s Post-Fader,
  • if dot replaces left half of knob, it’s Pre-Fader,
  • if dot is above rectangle, it’s Pre-Inserts (rectangle for block of Inserts).

But for some users a checkmark in drop-down menu definitely could help.

Well, that’s easy:

  • rename your existing VL app
  • download the latest build
  • install it
  • both versions will live peacefully side by side
  • check if the new version works as anticipated
  • if not: let us know(!) :grin:

Hi,

let’s say you have two songs and one “Global Stack”

“Song 1” is selected and there are two targets for the output routing. Let’s select “Global Stack” to “Song 1”.

Now, “Song 2” is selected. What should happen to the “Global Stack” routing? “Song 1” is not available anymore. One could argue that, in this case, the “Global Stack” should now be routed to “Song 2”. Okay, fine. Let’s imagine “Song 3” and do the same routing. But in one scenario, when “Song 10” is selected, it should not have a destination; it should be <nc>. So a “Global Stack” would need multi output routings.
Let’s save and reload the project. How would you know what is routed where?

Besides that, all those scenarios would have to be implemented, and the current implementation for that workflow has already bugs and loose ends …

… so: to remove this kind of complexity, we have decided that local channels like a “Song Channel” or a “Song Group” …

… are not valid destinations for Global Layers or Stacks.

To summerize.
In older versions, a Global Stack/Layer could be routed to these destinations.

In newer versions (since 3.0.62) we have removed these destinations

What happens with older projects? Those routings will be removed and will end up at <nc>. And what should you do? Create a “Group Channel” or “OUT Channel” instead and route the Global Layer/Stack to it

I hope this helps and doesn’t affect your workflow,
Michael.

Yes, I see the point. But it needs UI, it needs code and so on.
But why is that “Global Stack” not a “Local Stack” which belongs to the Song?

… Can you give me some more hints? I don’t get this one, sorry :frowning:

/Michael.

I was looking at @PHAgeBang ‘s problem when I came across it.

As for the drop down - see the difference?
Cubase:


VSTL:

.. ah, sure! Thank you,
Michael.

And to be clear about the song group…


… ah, I see. That scenario should not be possible, too. We’ll fix it.

Sorry for it,
Michael.

For me it‘s because there are global settings made for „the venue“ or changes I make that should affect all Songs.

… yes, if Globals Layers/Stacks should run the complete show, then route them to your main channel

See you,
Michael.

What if I want to compress them with a Backing Track?

… please give me an example. I guess you have a Global Stacks and you have an Audio Track in Song_1. And then?

Michael.

If I may chime in here:

@PHAgeBang What you want to do is:

send a Global Layer/Stack and song tracks of your choice to the same compressor plugin. Am I right?

Yes … „glue them together“

Why not create a Group Channel, insert a compressor, and then route the Global Stack and the backing tracks to that group? Group goes to Stereo Out. Maybe I’m missing something here; please let me know.

Can the Group Channel have individual Settings for each Song?

And can I go to two different Outs from there?