Save and Recall Individual Fader Layers from the Library

dLive dLive Feature Suggestions
1

I would like to suggest the ability to save and recall individual fader layers as Library items, rather than only complete Fader Layouts.

Currently, the Fader Layout Library stores the entire layout (all layers). On the C1500, where screen and fader space are more limited, it would be extremely useful to build a library of individual layers that can be recalled independently.

For example, I could create and save layers such as:

  • Drums
  • Band
  • Vocals
  • Monitors
  • Playback
  • Festival Inputs

Later, I could recall just one of these layers into Layer A, B, C, etc., without affecting the other existing layers.

This would provide several benefits:

  • Reuse common layers across multiple shows.
  • Build a personal library of frequently used layer layouts.
  • Update only one layer without overwriting the rest of the surface.
  • Speed up setup, especially on compact surfaces like the C1500.

An even better implementation would be a Save Layer and Recall Layer option directly from the layer setup page, allowing the user to choose the destination layer when recalling.

I believe this would complement the existing Fader Layout Library while providing a much more flexible workflow for users who regularly move between different productions.

1 Like
2

I completely agree with this suggestion.

That being said, I also feel it is important to ensure that people know they can use DCA groups combined with the DCA Spill functionality to achieve most of this desired effect.

When you “spill” a DCA group onto the Surface, it will temporarily replace the current fader layers with the members of the DCA group. The system will spill members across all six fader layers (A-F) if needed. With a C1500 this means you could spill a DCA group with up to 72 members and be able to access all 72 faders easily. (Larger Surfaces can obviously support even larger DCA groups and be able to display all of their faders).

The “ah-ha” moment in all of this is when you realize you can “spill” DCA groups by assigning this functionality to a user assignable button. You don’t even have to have the DCA groups showing on the Surface faders which obviously takes up precious space - especially on a C1500 with just 12 faders and 6 layers. If you want a button to immediately show your Drum channels, or Band channels, or Vocal channels, etc, etc, etc. You can easily do this by creating a DCA group and assigning the spill functionality of each DCA to a unique user assignable button. You are only limited by the number of spare DCA groups and user definable buttons that you have available.

When set up, you will have a user definable button for your “Drums” and another button for your “Band”, another for “Vocals”, etc, etc, etc. All you have to do is press the button and all of those channels/busses/fx paths, etc (defined as members of the DCA group) will appear on the Surface, even flowing down to other layers as needed (if you have more DCA members than faders). Simply pressing the user defined key again will make the DCA group disappear and the original faders (what ever was showing right before the DCA group was spilled) will reappear on the Surface.

It is a super easy, quick and convenient way to access tons of other faders that might not be part of your normal 6 layer design. If you haven’t implemented this into your workflow, I would highly suggest that you look into it.

3

I know about the spill functionality. I use it all the time. It’s great. But still I miss the layers in library.

But when I load a showfile made for S5000 into a C1500, i need to edit some of the layers, but not all of them.

1 Like