You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A solution to this would be to spawn three instances of Beat Detektor, low BPM, medium BPM and high BPM, then have an instance selectable through the BPM configuration.
The BeatDetektor instance does nothing when it isn't called, so CPU won't be affected, only a small amount of memory.
The text was updated successfully, but these errors were encountered:
BeatDetektor works best when limited to a BPM range.
Currently we have it set to detect between 85 and 169 BPM, which doesn't allow detection of faster music.
https://github.com/vcync/modV/blob/next/src/application/setup-beat-detektor.js#LL4C41-L4C48
A solution to this would be to spawn three instances of Beat Detektor, low BPM, medium BPM and high BPM, then have an instance selectable through the BPM configuration.
The BeatDetektor instance does nothing when it isn't called, so CPU won't be affected, only a small amount of memory.
The text was updated successfully, but these errors were encountered: