1st ctrl point on Song-global automation

[stephencarboni]

Hi Everyone,

I'm using LMMS 0.4.6

Whenever I edit the song-global automation for any control, I find myself unable to delete the first control point, even if I Ctrl-A and deleted them all. This causes the value to always snap back to the automation's one every-time I start the song over. In other words, I'm stuck at it's mercy the moment I edit it.

This continues at every new file as well as it seems the song-global automation carries over until I quit LMMS.

-Stephen.

[musikbear]

yes, this is because the envelope will emulate the current value of the diel /knob that you drag into the automation-envelope-
Eg if you want the value '0' as start value in your envelope, you must set the diel to 0, before you drag it to the envelope.
(I can btw remove 'leftover/rest' of the yellow box with the mouse, regardless of the value of the dropped diel -Have you tried that?)

This default behavior can actually be used to your advantage!
It is a nifty way to find the 'destortion'-limit of a filter and set this value as max-line. I btw. plan a tutorial for this in near future
BR.

[stephencarboni]

I am not talking at all about dragging a control into an envelope in one of my own automation tracks. I'm talking purely about the song-global automation envelope.

This is envelope you are presented with when you right-click on a control and select "Edit song-global automation".
It is this envelope that I'm having trouble with.

-Stephen.

[musikbear]

oohh.. interesting! i learned something new here, especially what the mysterious 'automation editor' (f8) is meant for (btw, clicking the button has made my lmms freeze several times) -but i cant see that the behavior is different from using an automation track, and I can also manually remove the yellow box with the mouse in this 'song-global automation' envelope too. The largest (only?) difference seems to be that the envelope isent visually represented in the song-editor.
Furthermore, i find that this 'song-global automation' has less fexibillity than an automation-track -eg you cant 'reuse' (copy/paste) the envelope nor can you bind several diels to the same envelope.
I cant see any strong points in using this 'song-global automation' in contrast to the automation-track at all, nor can i see any difference in editing behavior (win32 ima).
-But If you can explain any benefits in a 'song-global automation' bind, it would be great.
BR.

[stephencarboni]

I don't find it a better option either.

I find that when I import a MIDI file, the Song-global automation envelope for the tempo/BPM control has been edited.

In other words, if I try to change the tempo of the song I imported, it just resets back to it's own right in the beginning.

LMMS does make other automation tracks when it imports but it doesn't leave this one alone. And now that it's there, I'm stuck with using it as I can't "delete" it, since it's a special track.

I can of course attempt to cope-paste the notes from the piano-roll from one instance of LMMS to another but some MIDI files have a lot tracks....

-Stephen.

[musikbear]

That one i can solve for you :)
I think the behavior is not from lmms, but from midi.
When you import a midi, the bmp of that midi is kind of 'baked in' The info lies in the very first part of the track. Try setting the looppoints just a few note inside the track and then set a new bmp. Now the bmp you chose is the valid one.
But thats not really a usefull 'solution' at all.
Instead, what you do is import a new empty midi only with the bmp that you want for your project. This last imported midi will 'overrule' the bmp and you have the bmp that you intended in the first place.

BR