From: Florian J. <flo...@gm...> - 2013-02-03 13:10:29
|
Hi Tim, i think if we tell the user "just don't touch the tempomap", it doesn't matter which tempo MusE silenty uses, whether it uses 120bpm, 60bpm or a constantly degressing tempo. As long this setting never changes. Because all GUI controls can easily (and must!) convert these XTicks into a frame- or second-number anyway, and never show the user the underlying XTicks value. So i'd just leave it to whatever it was set before. greetings flo Am 03.02.2013 10:05, schrieb Tim E. Real: > I wanted to point out but got buried in the noise, that we are > already very close to having linear time - without frames required, > using your XTicks. > > I said if a user desires linear time, we tell the user "don't touch > the tempo, leave it flat". > > Let me elaborate: > Simply by turning off the Master button in the Transport, > this disables the entire tempo map. Et voila! Almost... > > However we would need one further step: > > There is as you may know a manual 'static' tempo value, > settable only via the Transport tempo box when Master is off. > > By default it is 120bpm. > > If the user desires a true flat linear time, must we not ensure > that this manual static value is overridden with 60 bpm, > so that there is a sensible 1 beat per second and then 1 second > divided into sub-ticks ? > > Or... not necessary? 120 bpm is default but so what? > > What I'm getting at is this: > > At a flat 60 bpm, if your sub-ticks can truly represent a one-to-one > sequential correspondence with what should be the exact frame-times, > with no skipped frames, then for linear time we are "home-free" as we say. > I think, then we could... we might... completely *remove* frames. > When the user desires flat linear time, turn off the Master tempo map, > set the static value to 60 bpm, and presto! Linear time without frames, > using only XTicks. > What do you think? > A 120 bpm default is 2 beats per second, further divided into sub-ticks. > That seems kind of odd to me, so that we should set it to 60 bpm? > But then, 60 bpm clashes with a default 120 bpm project so we > should be consistent and leave it at 120 bpm always? > > Cheers. Tim. > |