Click “New from current” I guess (as I do) 
Thanks - Blindingly obvious you’d think, but apparently not to me 
1 Like
Thx to @fkalmus
I did it like that 
2 Likes
please note, the button will create a new setlist from the PLAYLIST (in the main window), not from the current selected SETLIST (in setlist-editor)!
1 Like
Oh yes.
Then I have at least 2 points for improvements.
- “from current” should be named as “from main project” (cause this active window focuses on setlists)
- a “from setlist” button would be more logical, or should be added for conveniance and efficiency.
Guys, please 
it was IMHO so logical from the very first moment that feature became available 
I wouldn’t touch setlist editor, I’m glad how it is working.
But I understand the particular need to “all songs” listing
3 Likes
Hello @musicullum , @fkalmus
Isn’t the middle window the list for all songs in the current, opened project?
but anyways, a deeper look into the setlist window inspired me to that:
The buttons “from current” and “SYNC” are for me some “small steps”, to synchronize a setlist to the projects playlist, but this for me comes short.
To implement a more modern way of connecting “project’s playlist” to “a setlist” would be imo:
- Spend a setlist entry a connection as current to the project’s playlist and “sync” this one automatically + playhead position.
- Spend a “last current setlist” entry with a “playhead position”.
- Spend an easy activation for setlist to make them the playlist and go to the last playhead position (important if is was “last current”). (“Activate” button is ok)
And everything would work like a charm and the buttons “from current” and “SYNC” would be useless.
No. It is the list of all Songs of all setlists.
The right column shows the current setlist if SYNC is activated.
There is a) the SYNC button which syncs the current playlist to the setlist (right side), so any change you make at one place is reflected in the other, and b) “From current” at the left column which creates a new setlist from the currently active playlist. We call it “Playlist” so to differentiate from setlists.
I don’t understand that, also what does “playhead” have to do with setlists? You mean which Song should be selected when you activate a setlist?
Select and activate is available…what is missing?
I’m lost, taht is what you ask for but you want to remove it…maybe make a scribble.
If I add “for the opened project” to your sentence, I can’t find any difference in the meaning?
So the answer should be “Yes”?
Because it’s “no matter of setlists”, it’s a matter of an opened project how the “complete or ALL song list” in the middle of the setlist window looks like.
So to me, it seems to be the list of ALL songs in a project (no matter of setlists).
I can add a song to a specific setlist, but it adds to the project too, right?
(or is it a connection the “song list” internally? - anyway it is part of the project)
with different words: A “Playlist” is an activated “Setlist” in the current opened project and this I already find a good definition.
And this gave me the idea to connect those two in a good way together (and more automatic), not dividing those in any way or only connect them via “manual” syncing.
If I analyze what “Playlist” means in VST Live 2, I can find obvious global attributes:
- a song list
- an active song (with all fancy parts, layers and much more for single songs/parts…)
- a current song position (I called it: “playhead position”)
and maybe in the future added (some I can think of): - already played songs
- deactivated (skipped) songs
- included songs from playlist x
These attributes could also be valid for “Setlists”, because they are closely related to each other.
If that would be the case, a smarter handling between “Setlists” and “the Playlist” would be much more easily to implement, so that you don’t need the buttons “from current” or “sync” any more.
You could use an “Setlist” entry as a kind of storage for temporary “Playlist” switching and much more…
eg. “last used playlist”, “current playlist” plus fast and consistent switching between them e.g.
I hope this will make my ideas about “Setlists” integration a bit clearer.
It is not just about buttons - it is more about a good internal structure and automatic connection between related objects.
I’m afraid, I doublechecked the Songs setlist window and it behaves like that in v 2.2.49.
And this is different as you told above.
Following steps lead to a song in the Songs list which is either in a playlist, than in one of the listed setlists:
(use only names like in the setlist windows)
I created a “New Song” → it pops up in “Songs” (alphabetic order)
I put it in “Setlist 2” and “Setlist 3” - > it is still listed in “Songs” - OK.
I deleted it in Playlist, and “Setlist2 &3”
(So “New Song” is no longer in any list but: → it is still listed in “Songs” - Not OK!
Thx God it’s there. That is your “Song Pool (any song ever created within the project)”, if you want to delete your song from the song-pool, delete it (setlist editor middle column).
1 Like
I know, but why not calling it “Song Pool” in the Software, is that a problem?
Even you guys are giving different answers. 
So a good definition would be:
All ever builded songs of a project are listed in the “Songs” list, right?
As expected it is project bound and this is good.
I gave answer what might help you to understand. I’m a performing artist and were using VL in the last years since V1 that I purchased for money and gave it a try for my own.
So if you want to catch me, do it…
Don’t take that personal, please …
I always like clarifying things and structures, because there is a lack of information on manuals here. So you don’t have to fight ;-). and Thx for your advice.
1 Like
Sorry, you are correct, there can be Songs in the middle column which are in no setlist at all. Which can be challenging for us developers, so maybe that is why
Still don‘t get what you suggest though, that is different from what is available already?
Personal aspect: I like how it’s currently working 
“If it ain’t broke, don’t fix it”
1 Like
Thx for trying to help me with my understanding for VST Live definitions.
The user interface don’t need much change.
And Maybe it is very different or not at all, I don’t know the current internal structure. You do.
So my answer is YES and NO, cause of my information booth.
What I mentioned is mostly about internal class structures and how near are the setlist class and the playlist class are related to each other, to streamline the programming between them.
My information about programming may be a bit outdated now, but for me it feels like the connection right now is not close enough for some of the feature requests and some wishes of the customers for an even more efficient implementation. I may be wrong?
I think this is more internal stuff and here is not the right place for making that plan if it fits to the already used internal data structure.
But Short, one feature visible for customers would be:
There are new list entries - using the left list “Setlists” also for some stored “kinda Playlists”:
called “current set/playlist” and “last used set/playlist” and building an ancestor class for both and connecting them together for the mentioned functionality.
If you make them active they do know the last position in “the playlist”
Eg.: “Current set/playlist” already has this sync feature automatically available.
I feel this could close the gap between the main project “Playlist” and the “setlist” list.
I don’t know if you are programming this part of VST Live, but the guy(s) working on these classes, will kinda know what I mean. Is it Spork, btw.?
What’s it’s there is fine for me.
Except that the sync for the current setlist gets lost by marking a different setlist in the list field.
What I do miss, is what is not there!
SO: I’m talking about an addition.
Let me give you an other point of view:
- open SETLIST editor
- activate desired setlist
- clikc SYNC
- close SETLIST editor (and forget it for a while)
- work, reorder songs, add new song
- CLICK SAVE and grab a coffee
YES, and I like this very much!!! I feel this is a must if it wouldn’t be there 
But why not integrating this to an even better systematic approach?
e.g.
- current setlist is linked and synced already with the connected setlist entry
- I only have to open the setlist list for a change of the current setlist, which is the playlist
- I don’t care about syncing, because VST Live do it for me, but I can unSYNC if I like
- or sync to another setlist entry
and all the benefits of your workflow is included.
How is that sounding?