Automation does not save

[Yorrick]

Hello people,

I'm using LMMS now for a while and have been working on several songs. I experience again and again that the automation is not saved as I arranged it. Even while I'm working on the song and saving it in between, it messes up the automation. So either if the program is completely closed and reopened or while using it, I have to re-adjust the parameters in the automation window. Which ones it messes up LMMS choses randomly. It is so annoying.
Does someone know how to stop this please?

[musikbear]

Hello people

Hi, Welcome to the forum Yorrick! Here are all our important links:
http://lmms.io/forum/viewtopic.php?f=1&t=4740
-And a few rules for Avatars, signatures, posting and using the right sub-forum :)

I experience again and again that the automation is not saved as I arranged it.

That does not sound right
please post your:
* OS (+service-pack-ver)
* lmms vers

[Yorrick]

Hi,

Thanks for welcoming me.

My system: Windows 10 Home, 64 bit
processor: Intel core i5-5200U CPU, 2.20 GHZ + 2.20 GHZ, 64 based processor
RAM: 8 GB

LMMS version: 1.1.3 Win 32/x86_64, Qt 4.8.7, GCC 4.9.3, 20150305 (prerelease)

I think the bigger and more complicated my songs become, the more likely it messes up the automation. I guess at some point the program cannot handle all the information inside the song anymore.

But maybe there is another version that does not cause these problems? A version in which I still could use the songs I'm editing currently?

Thanks in advance!

[musikbear]

I think the bigger and more complicated my songs become, the more likely it messes up the automation. I guess at some point the program cannot handle all the information inside the song anymore.

Now i cant say anything in respect to how complicated your projects are, but i really doubt that its the reason. Lmms can handle files of large size, but have you made copies of automation patterns?
if you upload the project, AS MMP! -and send me the link as IM, i will take a look at it

[Yorrick]

My project has 90 KB, approximately 50 tracks for instruments, then about 8 tracks for vocals and maybe 10-15 tracks for automation. Maybe I'm using the automation in a wrong way? I have sometimes several effects on one instrument and often I don't want to stretch the automation window about the whole time the instrument is running (I find it very inconvenient), so I use for example one window to raise the volume, then in the middle in another window I vary it maybe a bit, and in the end I have an extra automation window for bringing it back to the volume at the very beginning of the song (otherwise LMMS wouldn't automatically switch back to the volume in the beginning). So I have several windows for the same effect, and I'm opening a new track for each new effect. Currently the maximum number of effects on one instrument is 3.

Thanks for your offer, but I don't understand how I could could save the file in the way you suggested it and where I could upload it. It is still somehow in the beginning and development, so apart from my lack of knowledge I would also feel a bit embarrassed. It is very kind of you anyway!

I could send a screenshot, I know how to do that

So what do you think? Am I not using the automation correctly or is it maybe a bug?

[Yorrick]

And I didn't copy the automation windows at any time (I tried with ctrl+, but it didn't work or maybe I did it wrongly).

[musikbear]

My project has 90 KB, approximately 50 tracks for instruments, then about 8 tracks for vocals and maybe 10-15 tracks for automation. Maybe I'm using the automation in a wrong way?

No, your description does not point to that, its fine what you do. You should however never bind 2 or more different dials to the same automation!
UNLESS the dials are identical -Eg ets fine to bind 3 VOL-dials to one automation, because all the VOL dials have the same span
BUT!!
If one of the dials has been set to exponential-setting, then i think it could budge the automation

Thanks for your offer, but I don't understand how I could could save the file in the way you suggested it.

Easy:
* Open project
* File | save-as
* chose a name... 'autoproblem.mmp'
press save
You can upload on any file-host like tiny- or google drive
I will ofcause respect your rights

So what do you think? Am I not using the automation correctly or is it maybe a bug?

There nothing wrong with your usage, afaik. I doubt an lmms bug, but clearly something is wrong

[Yorrick]

Hey,

So when you are talking of different dials on one automation, you mean different dials on the same automation track, right?

I'm always using the same effect, let's say volume or one specific dial of one specific effect, on the same automation track. So for each single effect I'm opening a new automation track.

I want to clean my track a bit first, then I can send it to you. Yes, of course, now I know about mmp, hahaha! I wasn't aware of it.

How can I give you the link (not publicly)?

Will take some days though, just for you to know.

[musikbear]

when you are talking of different dials on one automation, you mean different dials on the same automation track, right?

Well actually on the same block
The current architecture allows you to use only one automation-track, and then have all automation in this single track, but in different blocks
I do not recommend this, because, even though you can name individual blocks in that one track, it get really messy fast.
But it goes in the bin, if more than one not-identical controller are bound to one block
Like
if both a VOL and a PAN is dragged into the same block, that will not work
if a VOL is dragged into own block and a PAN is dragged into own block but in the same block, that will work, but will be confusing.

How can I give you the link (not publicly)?

You use the internal IM on this board. I better add a paragraph on this in the 'welcome-post', others may be interested in that too :)

[Yorrick]

Hello Musikbear,

What do you mean by internal IM?

The stuff about the blocks sounds really confusing, I mean I wouldn't recommend to have different effects in one block either.