This is a long standing bug.

Why is it there?  No idea.  I believe it's usually caused by a rougue Automation track, but I've had this happen on songs without the automation track at all.

If you have any memory as to what happened leading up to the bug, please try to reproduce.

In terms of any automation events being fixed in recent versions, I'll let the programmers chime in.


- Tres.Finocchiaro@gmail.com

On Thu, Feb 27, 2014 at 7:35 PM, David Gerard <dgerard@gmail.com> wrote:
I have a project which I worked on for ages, in various iterations, at 115bpm.

Tonight I've been doing a new version, which I want to be at 110bpm. I
set the tempo to 110, I press play ... and it immediately starts it
running at 115bpm. I save it as 110bpm, restart LMMS (freshly compiled
from current Git), press play ... it sets itself to 115bpm.

Looking at the .mmp, I see the following:

line 5:
    <bpm value="110" id="6760747"/>

But! Line 1420:
        <time value="115" pos="0"/>

So. (a) why is this happening (b) how did that get there (c) how do I
get rid of it, short of editing the .mmp by hand?

Project file: http://reddragdiva.co.uk/lj/doom%20kingdom%202.mmp

- d.

Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
Lmms-users mailing list