On 03/05/2014 05:45 PM, Raine M. Ekman wrote: > 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...
Yes, that's exactly what I'm talking about - making time signature a UI thing. Global time sig would act like a grid which you can adjust without moving/changing the patterns. Local time sig would act as a hint for piano roll on how to display instrument tracks. Automation tracks would also have time sigs and it would be used to display the background grid, just so it's easier to align them with various instrument tracks. Bb-tracks would also a time sig, and for them it would arguably make the most difference: bb-patterns take the length of the loop sequence from time sig, so this would allow creation of beats with any loop length. This would work so that the bb track itself has a time sig which determines the length of the bb-track and I do believe deeper levels use mostly ticks for timing, the tacts thing is mostly UI. And yeah, I don't think this would be very hard to implement - I've taken a look at the code and I think it's entirely doable. > Bad math and bad assumptions will remain even if the time signature is > local instead of global. Granted, but I think it would still help, since with this implementation, we can possibly do some things in cleaner ways. ------------------------------------------------------------------------------ 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
