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

 
 
Latest News
GSequencer version 3.10.5 released posted by jkraehemann, Sun 29 Aug 2021 07:41:14 AM UTC - 0 replies
implement VST3 C API Wrapper posted by jkraehemann, Tue 10 Aug 2021 12:53:03 PM UTC - 0 replies
refactored utility functions posted by jkraehemann, Tue 03 Aug 2021 06:26:38 AM UTC - 0 replies
GSequencer version 3.9.1 released posted by jkraehemann, Wed 30 Jun 2021 06:07:07 AM UTC - 0 replies
preparation for migration to Gtk4 posted by jkraehemann, Thu 18 Feb 2021 10:38:40 AM UTC - 0 replies
[Submit News]
[103 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.7