On 03/06/2014 01:53 PM, Raine M. Ekman wrote: > Beat patterns should really be upgraded to have both a length and a > denominator. 36 48ths for a drum fill? 16 quarter notes for a long, > stiff beat where you don't need those smaller notes? No problem! (But > it might be a lot easier said than done... :) >
I don't know, you can already do that by editing the pattern in piano roll. If implement the per-pattern time sig, then beat patterns could have both a time sig (pattern length) and another value for step length, ie. how many subdivisions each beat has. > As for where I'd like the time signature situation to evolve, see picture. I have to say I'd rather have the time signature as a property of each pattern. That would still allow doing what your picture shows (by using different patterns for each segment), but it would also allow mixing different time signatures, eg. overlapping 5/8 patterns on one instrument and 3/8 on another... this wouldn't possible with fixed time signature areas. Also your suggestion has many ambiguities, like what happens when you move a 4/4 pattern to a 5/4 area... will a space be inserted in the tacts, will the notes stay where they are (making them misaligned with the signature)... with per-pattern time sigs, this wouldn't be an issue, as the patterns would be the same no matter where they are in relation to the song, as the global time sig would just be used as an adjustable grid. ------------------------------------------------------------------------------ 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
