Features for a pure live keyboardist

Hi,

I’m using VSTL since two seasons as a pure live keyboardist in a regional semi cover band and first of all : I like VSTL very much, I wish I would have had that piece of software 30 years ago …

There are some things that would make VSTL perfect in my usecase (or maybe I did not understand how to get it) :

(1) list of shared layers usage
I’m using the shared layer feature intensly but I don’t know by heart in which songs I’m currently using e.g. “Layer Piano 1”. So in the situation when I would like to globally change the instrument of “Piano 1” to another new instrument (cause I bought a new killer VST :stuck_out_tongue_winking_eye:) I MUST know which songs will be affected.
So my only chance is to walk throught the A-Z song list and check visually if the layer is in there - annoying.
Proposal : Menu “Layer => Show related Songs”

(2) list of used setlists
A similar problem. I want to delete a song from a project. Often I get the message “The Song … is used in one or more setlist. You need to remove a Song from all setlists before you can remove it”.
Sure - you are right ! But this is only easy if you have a low number of setlist, meanwhile I have twenty.
Proposal : Menu “Song => Show related setlists”

(3) better overview in the Layer Controller Map
The Layer Controller map always displays a list of all available 127 Controllers. It does not fit on the screen so I always have to scroll up and down - annoying.
Optimum solution would be to have a user defined filter of controllers I would like to see in the list. As this list - in my usecase - directly depends on the masterkeys I’m using (and I’m not changing often) that would be a more or less permanent list of lets say 10-15 pedals/sliders/knobs that where in my list - no more scrolling !
If I could even name them (“foot pedal lower manual”) that would be cool.

(4) define controller range
incoming controller ranges are always forwarded to the mapped controller 1:1.
It would help (me …) a lot if I could define that e.g.

  • incoming volume 0 should send 80 to the instrument
  • incoming volume 127 should send 127 to the instrument
  • between them linear interpolation for sure
    So in a live situation I would have much more feeling and could avoid the accidental “pedal off”.

(5) user defined colors/icons for Layers
It would help me a lot if I could assign a color or even an icon bitmap to the layers in the Layer view.
That would give much more overview at a first sight (“damned, where is the strings layer ?”) in songs where you are using more than a couple of layers.

Thanks for your reading.
I understand that my use case is a little bit old schooled and your priorities are different. Maybe some others can join my wishes.

Thanks for you excellent work.

Gerhard

5 Likes

Some very good points!
Shared layers: somebody proposed the idea of song layers a few months ago (ie available in all parts). I wonder whether that would help.
Song delete: @Spork can there be an override in song delete ‘yes I know - just delete it’? And have it delete the song from all setlists?
Layer colours: great idea! In the meantime I call my layers after what they do: strings, organ, whatever… (I don’t usually have enough for it to be an issue).
Defined controller range: I think it’s possible to map a quick control to your VST and then define another controller to control the qc in actions, so that would give you a level of remapping. It’s never going to be MIDIox though, but if you’re on Windows you could use MIDIox to remap your controller before it gets to VL.

Hi @gerhard.kiessling and @CliveJ,

yes, I agree to all of your ideas. Let me add them to the Feature-Request list.

Thank you,
Michael.

2 Likes

I love your comments, though I am a novice in this particular case. I wish there could some detailed online tutorials for us new users.