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

 
 
Latest News
Extending the test-suite of v2.0.x posted by jkraehemann, Wed 10 Oct 2018 02:38:35 AM UTC - 0 replies
Got segfault after a while of recording posted by jkraehemann, Thu 20 Sep 2018 03:04:31 PM UTC - 0 replies
Advanced Gtk+ Sequencer v2.0.0 - new major release posted by jkraehemann, Mon 10 Sep 2018 03:20:12 AM UTC - 0 replies
currently dealing with capture of soundcard posted by jkraehemann, Tue 04 Sep 2018 12:21:58 AM UTC - 0 replies
Advanced Gtk+ Sequencer v2.0.0-beta posted by jkraehemann, Fri 31 Aug 2018 10:43:05 AM UTC - 0 replies
[Submit News]
[66 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

No messages in Inaccurate attack calculation of bpm

 

Back to the top


Powered by Savane 3.3