If this works well, the only thing Steinberg peopels can do, to make this more visible to the users, is to add an additional “Action track” to the track menue, which is quite a MIDI track but with an hidden output to an predefined virtual MIDI port and the possibility to add this to “Actions&Shortcuts” as Controller.
Better will be, when the action could be selected directly, without the detour over virtual MIDI.
Maybe this wish will work with action in the track at the specific position to set marker on the fly with “Set Marker” action also 
.
We call that automation track 
To come soon…
Loads of loops to come
This is the quote of my day 
That would solve my problem as I would be able to make the changes I want while playing the song and then I would click revert and it would be in the original, saved state again. Another way of solving this would be to have a ‘rehearsal mode’ (or edit mode) and a ‘concert mode’. In rehearsal mode the songs would not revert to saved state. In concert mode they would always revert. You change the song and the song you were playing before reloads in the background and is again ready for a perfect repetition.
Hi @Daniel_Drummond ,
Do you already try the tricks mentioned above?
Hello,
I can completely understand the requirements.
It’s exactly like that what I need.
1: EDIT MODE (see which songs have been edited, store all edited songs or each song separately), PLAY/CONCERT MODE (Selection of whether the song should be set to its original state when called up or the previously made changes should be retained)
2: Button to reset a song quickly
Kind regards, Heiko
We’re considering “Edit mode”, it stills tands out. With a “don’t show again” warning when you switch to “Revert Mode” - or what would best describe that “destructive” mode, which inevitably reverts the entire Song when unselecting?
It would probably also additionally provide a Song menu “Revert Song” option.
I know I’m not involved to this topic, … with a little fear in mind regarding, at future implementation of that feature, I would like to vote to keep current behaviour as “default” (all adjustments are kept at/accross song/playlist/setlist navigation(s)/rehearsal/soundcheck/concert, then all changes saved with a “SAVE” at closing app). While the drop-changes-mode as an extra toggle-able option.
No fear, of course the current behaviour (“Edit”) would be default as it is now.
An update on this…
It is more complex than one might think, because there are dependencies like setlists, channel sends, shared Instruments etc that may have changed along with the Song beeing edited.
Best we can offer is a “Revert” function in the Song menu which would extract the Song from the project file loaded, delete the Song, and replace it by the loaded one. This would be similar to Save Song / Delete Song / Load Song, which may or may not be what you want - it should be, as long as you don’t change anything which depends on objects outside the Song.
As I described some posts above. If I need a defined setting at the start of a song, I use a MIDI track to set this settings on the first beat of the song with virtual MIDI and “Actions&Control”. With the new posibilites of actions with 1.4.60 this becomes much easier now and works really satisfying. With this, I also have no issues anymore, when saving the project with “wrong” settings, or at least I don’t care anymore .
What I can think of. Maybe it could be possible to save predefined and fixed initial settings of controllers, mixer, etc. for each song which comes everytime effective when a song will be selected and transport is on the start of the song.