Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

BPM Trigger additionally to the speed trigger

Open
  • Is something wrong?
#38 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
desktop

Research direction

No files, entry points, or tests are named. Start by locating the existing speed-trigger implementation and determine how BPM detection could fit the Processing/Java application; clarify whether BPM triggers use H/S/K/P or fire once per beat, then define and verify the resulting effect behavior.

Written by the indexing model from the issue text.

Description

enhancement

Next Feature Idea: a BPM Button which blocks the speed value
I'm pretty sure either minim or another library out there is able to check the current BPM of a song and then triggers the current effect per beat

This could be additionally to the speed trigger

  1. Speed is more a blocker: a effect trigger only triggers within a time value calculated by speed + H/S/K/P
  2. BPM triggers a effect by beat

I'm not sure how easy this is to implement, though
If the BPM Trigger also needs H/S/K/P or just triggers every beat etc.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36488126-bpm-trigger-additionally-to-the-speed-trigger?utm_campaign=plugin&utm_content=tracker%2F444396&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F444396&utm_medium=issues&utm_source=github).
Dominant language
Processing
Stars
294
Forks
53
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codingjoe/MusicBeam

All issues in codingjoe/MusicBeam

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.