(You can also accidentally produce this phenomenon if you are in automation enabled record mode, and you solo/mute/un-mute tracks during your playback. Well known for its unique pattern-based workflow, Image-Lines FL Studio is also. So having them init-ed and keep jumping to a certain position at the start of the song is unthinkable. Learn Document-level-undo skills by watching tutorial videos about The. I don't know about you, but in my workflow I need to keep changing the states of mute/un-mute/solo. Every time you play the song, that track jumps to be muted, or un-muted as dictated by your init value. 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.
How to undo in fl studio how to#
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 would like it to undo only that one action, but leave all the following actions the same.I can think of many uses for this feature. If I go to find that that action (undo delete measure) in the undo history and undo it, it will also undo all the following actions (simple note entry, expression entry, repeat sign entry, etc). and then, I realize that I would like to undelete that measure from several steps before. For example, let's say I deleted a measure, then I did many other actions after that, such as simple note entries, expression marking entry, repeat signs, etc. and instead, it just undo that single action. Lastly, If I would like to undo an action from several steps before, I would like Finale to NOT undo all actions following that one. From recording song ideas to full-fledged mobile productions, Audio Evolution Mobile sets the standard for music creation, mixing and editing on Android. For example, instead of saying "simply entry edit," it could say "1/8 note rest entry" or something like that. I also would like the undo history to be more descriptive in what the action was. I would like there to be a way that after saving or closing a session, Finale would NOT delete the undo history.