Hi, global automation patterns are placed in Song::globalAutomationTrack() which is a hidden/internal automation track where all automation patterns are placed at MidiTime( 0 ). This all is provided for convenience as the user does not have to deal with managing and connecting automation patterns if he just wants to control a knob/... in the song-global domain.
If the song-global automation pattern of a control (i.e. tempo) is not empty and you manually assign another automation pattern it will be the same as having two automation patterns connected, i.e. the behaviour can be undefined if they overlap (which will certainly be the case for song-global automation patterns). This is just what I remember from the implementation - correct me if I'm wrong. Toby ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
