Another crazy example would be if a track's mute state was set with 'Init song with this position'.

This could work but imagine having to keep setting initial value like this. One of the solution could be to set track 6's levels to -5db, and re-initialise this value as initial position on track 6's volume, before playing again to hear this new level for another part of the song. I play back the song again wanting to hear another part of the song with the new level at track 6, and lo-and-behold, my track 6 level jumps back to -10db because the track is initialised to that value. I'm happy with it, and I stop the playback. Later on I tweak the levels of track 6 while the song is playing, from -10db to -5db. I do a rough mix of the levels, and I set the 'init song with this position' for each fader on each track.

Say at the beginning of my mixing stage I have 16 tracks. Having knobs initialised with a certain value, without knowing how to remove that initialisation, can be annoying. It behaves like an automation snapshot that remembers that value without writing automation data on that control. This is where the 'Init song with this position' comes in very handy. However, if that control has no automation set, that value would be lost and I would not be able to know what it was originally set at. If that control has recorded automation, there would be no problem with this since during playback automation will automatically get the control back to the correct values. I may actually mess up the value if I accidentally bump on my physical sliders positions (or someone changed the slider positions while I am away from my computer for a while). The most helpful situation for me, would be when I am going to use a physical controller's slider (Korg NanoKontrol2 for me) to affect the values of a FL Studio knob for example. I can think of many uses for this feature.

Fl studio song position stuck