Main menu
You are here
Session Length in BBT Anomaly
Greetings,
I've noticed an anomaly regarding the session length indication, and am not sure if it's a bug or simply something I don't understand.
My song is 79 complete measures long, and is in 4/4 time. The first 20 measures have a tempo of 100 bpm, and the remaining 59 have a tempo of 120 bpm. So, the tempo change occurs at the start of measure 21.
In what follows, assume the playhead is at the very end of the song.
If the playhead position display, up in the toolbar, is set to frames, then I see an indication of 7320600 both in the playhead indicator and in the session length indicator in the status bar (near the bottom right of the screen). These match.
Now setting the playhead position to show in time, and I see 2:46.000 both in the playhead position display and in the session length indicator in the status bar. These, too, match.
But setting things to show in BBT, at the top I see 80.1.00 and in the status bar I see 69.0.640.
So the session length in BBT, shown in the status bar at the bottom, appears to be at odds with the true value. The numbers suspiciously suggest it was the tempo change which caused this.
Or am I stupidly missing some vital factor? Thanks for any explanation which can be offered.
Thomas
Aha!
Thinking about this a bit more, I see now that 69.0.640 BBT is equivalent to 2:46 in minutes and seconds, if the tempo is assumed to be 100 bpm throughout.
So it appears Qtractor doesn't take into account the tempo change when computing the session length in BBT. Hence, the value appearing in the status bar is inaccurate in this case. Time and frames seem to be okay, though, as mentioned.
Thomas
re. Session Length in BBT Anomaly...
hi, the more you harness the beast, more the likelihood to shallow its bugs... :)
now hopefully fixed in 1.4.0.27git.567f3a
nb. a length or duration is displayed in delta-BBT format, as a number or count of bars and beats. eg. a zero time length, displayed as "00:00:00.000" is "0.0.000" in delta-BBT format, which differs from the usual way, normal-BBT="1.1.000".
thanks
That fixed it. Thanks for
That fixed it. Thanks for your diligent work!
Thomas
A tip
Hi everyone; here's something related (in appearance) that perplexed me at first. Even after the fix Rui provided, one of my compositions was showing a discrepancy. The length of the composition didn't match where the clips in the tracks ended. In fact it was seven quarter notes later!
After several days of head scratching and trying this and that to locate the fault, I noticed a very fine and faint vertical line (one pixel wide, presumably) in one of the tracks. I managed to rubberband (select) it and voilà, a name for it popped up. Turns out it was actually a clip itself of presumably no length. Don't ask me how it slipped in, but it was clearly operator error. This was a drum track and probably I was copy/pasting some repetitive measures and failed to notice it when moving things around. I don't remember. If it isn't clear, I'm just an aging novice.
So my point is: it's possible to have a clip of zero or very short length beyond the end of the legitimate composition. If your eyesight is lousy or the video monitor rather poor (both of which apply to me), then it's easy to miss. This will give a faulty length report, and furthermore the play head will continue to that point.
Thomas Henry
re. A tip
yes, you may have clips of near zero length but not zero;
you may zoom in to the maximum and still not seeing much of it (unlikely but possible, depending on your eyes and screen ;))
I saw one of these a few
I saw one of these a few weeks ago and brushed it off. That said, I suppose I'll look to the filesystem next time I become suspicious.
Add new comment