newsAdvanced Gtk+ Sequencer - News: Fixed time forever

 
 
Latest News
GSequencer gets triple-sync and additional dialogs posted by jkraehemann, Fri 13 Oct 2017 04:28:05 PM UTC - 0 replies
GSequencer first major release 1.0.0 posted by jkraehemann, Sun 01 Oct 2017 05:41:43 AM UTC - 0 replies
Reduced latency of JACK posted by jkraehemann, Fri 22 Sep 2017 12:37:27 PM UTC - 0 replies
Advanced Gtk+ Sequencer v1.0.0-beta posted by jkraehemann, Thu 31 Aug 2017 06:14:22 PM UTC - 0 replies
Inaccurate attack calculation of bpm posted by jkraehemann, Sat 19 Aug 2017 11:56:06 PM UTC - 0 replies
[Submit News]
[40 news in archive]

Fixed time forever

Item posted by Joël Krähemann <jkraehemann> on Sat 12 Nov 2016 10:03:56 AM UTC.

Take a look at time and consider start counting from 0. This is your very first offset. Now you want to play 120 beats. Whilst the ordinary user might want to start count from 1 the programmer doesn't. For sure you want to play the very last quarter note entire.

This gives you a discrepancy of 2 beats. Whereas 1 beat consists of 16 clicks at least in GSequencer. Contrary MIDI has 32 clicks but forget this.

What I'm doing now is making you feel like producing silence. But in fact it's up to you. Having a 4/4 beat producing 2 times 64 clicks of silence is over-helming. So I solved it by counting you and programmer as 2 and divide the silence by it.

So we could say you have a need to play the very last quarter note. Just enter within export 120 - 12 = 108. That's makes the programmer happy. And you can play your very last quarter note as well. Whereas 120 are the beats and 12 is calculated as following:

  • 4 ticks multiplied by 16 clicks equals 64
  • minus last quarter note 16 clicks equals 48
  • now divide by 4 ticks equals 12

That's it. I hope this helps you.

Cheers,
Joël

Comments:

No messages in Fixed time forever

 

Back to the top


Powered by Savane 3.1-cleanup1