newsAdvanced Gtk+ Sequencer - News: Inaccurate attack calculation of bpm

 
 
Latest News
Potential dead-lock due to libags-audio callbacks to UI posted by jkraehemann, Fri 17 Nov 2017 08:47:59 AM UTC - 0 replies
Better support for Apple MacOS X High Sierra posted by jkraehemann, Tue 14 Nov 2017 11:55:02 PM UTC - 0 replies
GSequencer 1.2.x goals posted by jkraehemann, Wed 18 Oct 2017 08:27:54 PM UTC - 0 replies
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
[Submit News]
[43 news in archive]

Inaccurate attack calculation of bpm

Item posted by Joël Krähemann <jkraehemann> on Sat 19 Aug 2017 11:56:06 PM UTC.

As having bigger buffers especially by using pulseaudio, the algorithm that calculates attacks of target buffer seems to fail.

The attack is calculated by one of these functions:

  • ags_devout_adjust_delay_and_attack()
  • ags_jack_devout_adjust_delay_and_attack()
  • ags_pulse_devout_adjust_delay_and_attack()

The goal of the algorithm would be having constant delay but alternating attacks. This formula was considering only buffer lengths of 512 or lower.

Rework the algorithm

The computation shall return an approximation attack with a certain tolerance of deviation. I would say it doesn't matter if there is a swing of 10 to 20 frames each delay.

It should figure out best fit of delay and approximated attack. The problem with bigger buffer lengths is the algorithm can't smaller delays accurately. This was done for simplicity but doesn't meet current requirements, yet.

By Joël

Comments:

No messages in Inaccurate attack calculation of bpm

 

Back to the top


Powered by Savane 3.1-cleanup1