Citerar Vesa <[email protected]>: > I think we should rather move to a model, where instead of one global > time signature we could just allow setting a time signature for each > pattern individually - you could mix in 5/8 patterns at the same time > with 3/9 patterns, at the same time. This would be implemented for both > melodic and beat patterns. This would also pave the way for adding other > neat timing-based effects such as shuffle.
Sounds like a crazy idea. But probably not too hard to implement, time signature should logically be mostly a UI thing anyway. Hopefully it's all ticks on deeper levels... > This would allow cleaner implementations in many cases, I seem to notice > that the current time sig system causes many issues in many parts of the > software... even now there are multiple open issues all related to time > sig in one way or another. Bad math and bad assumptions will remain even if the time signature is local instead of global. -- [email protected] softrabbit on #lmms ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
