Main menu
You are here
beat/4 and beat/16
Hello Rui,
we discovered something that we do not understand and strikes us as a possible bug. I took some screenshots so i can explain better.
I attached screenshot beat4.png that shows that with the magnetic grid set to beat/4, the playhead can be set - in minutes and seconds - to 1:56.000.
When we set the beat to beat/16, we are unable to set the playhead in the magnetic grid to 1:56.000, but have to choose between 1:56.010 or 1:55.995. Screenshot beat16_1.png and beat16_2.png are attached as well.
Is this correct behaviour? Why is it not able to be set to 1:56:000 as well?
The offset is minor but not when we copypaste several clips; every time the small offset is added and is really becoming a problem as you can see in screenshot shift.png.
(As a sidenote, we are aware that our tempo and measure are somewhat unusual. This has to do with the fact that the counter of the playhead corresponds with the minutes and seconds minus 1 JackTranport Clock on the second computer. It is the other computer that is the Master while this computer is Slave)
| Attachment | Size |
|---|---|
 beat4.png | 105.38 KB |
| beat16_1.png | 105.47 KB |
| beat16_2.png | 106.12 KB |
| shift.png | 134.88 KB |
re. beat/4 and beat/16
that's an interesting finding.
most probably due to rounding and to extreme low tempo (30bpm) and incredible low time-signature divisor (/32).
you probably know that you'll get virtually the same "metronomic" result, but with better display accuracy for that matter, if you, say, set tempo=240 bpm and beat divisor to the regular standard quarter-node (/4), don't you?
all that to say it's more kind of a "nit-picking" decimal representation and numerical precision problem than a real bug one ;)
hth.
cheers
>you probably know that you
>you probably know that you'll get virtually the same "metronomic" result, but with better display accuracy for that matter, if you, say, set tempo=240 bpm and >beat divisor to the regular standard quarter-node (/4), don't you?
No, we didn't as a matter of fact :(
I guess we are not that "musical" but we are looking to use QTractor to organize sound and soundclusters by sending MIDI data to VSTs etc.. We do this together with a second computer, the Master computer, that runs Blue/Csound. Blue sends via JackTransport code the seconds and frames. The playhead of QTractor will be guided by this JackTransport system and will jump between soundclusters we have prepared in QTractor.
I tried it and certainly can use the 240 4/4 division, and 120 4/8 and 60 4/16 work fine as well. Beat/16 works fine in these resolutions - there does not seem to be trouble because of the rounding error. So all is well!
.
Thanks for mentioning this.
Add new comment