Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand the tempo range for the metronome #32

Open
Don-Stevenson opened this issue Jun 22, 2020 · 6 comments
Open

Expand the tempo range for the metronome #32

Don-Stevenson opened this issue Jun 22, 2020 · 6 comments
Labels
enhancement New feature or request ui/ux Frontend issues
Milestone

Comments

@Don-Stevenson
Copy link

Don-Stevenson commented Jun 22, 2020

Background

...

Acceptance Criteria

  • ...

Approach

  • ...
@KCarlile
Copy link
Owner

@Don-Stevenson, do you mean the literal tempo range of the slider? That is, do you want it slower than 60bpm and faster than 220bpm?

Or is this intended to be a reference to the option to have accent beats on 2 and 4 like we discussed?

@KCarlile KCarlile added the enhancement New feature or request label Jun 23, 2020
@Don-Stevenson
Copy link
Author

@KCarlile Yes, I mean to expand the tempo range in the slide. I think about 20 to 250 BPM is probably good.

I will create an issue for the specific 2 and 4 and the approaches possible to solve that issue.

@KCarlile
Copy link
Owner

KCarlile commented Jun 23, 2020

I already added the 2/4 accents to issue #31. I’m okay with going up to 250, but I think 20 is way too slow. Maybe 50, but I think Adam Neely has a video on how 33bpm is the slowest possible music. :)

@KCarlile
Copy link
Owner

I guess you haven’t seen the new feature yet were you can do multiple measures per chord. That might solve the issue of wanting to go even slower. Check out http://dev.flashchord.com

@Don-Stevenson
Copy link
Author

Don-Stevenson commented Jun 23, 2020

@KCarlile I saw that video of Neely's! I really like his channel BTW.

My rationale was thinking about using 20 as two and 4 gives 40bpm. That said, come to think of it, when I practice slow tempos on a metronome I do think of it as being on each beat. So maybe 33bpm, or 30 for an even number, is the low range following Neely's suggestion.

I checked out the latest dev version. The multiple measures thing is great!

The issue with the metronome is maybe more about the direction of the project. My thought is to use this site in a way that I currently use a metronome with the added functionality of flashcards to help me practice different scales, arpeggios, key areas, etc.

When I practice with a metronome, my goal is to make it as musically real an experience as I can muster. To do that, practising with the click on 2 and 4, on beat 3 for up-tempos, on beat 1 (or beat two) for waltzes, on 1 and 4 for 6/8, etc allows me to best approximate a musical situation while laying bare my rhythmic execution/abilities so that I can correct and improve them.

Edit: this is the reason I would like an unaccented metronome click, so that I can think of each click in different ways.

Just in case the above isn't clear. Jens Larsen gives some great examples of what I am talking about. https://www.youtube.com/watch?v=XUnu-oYWvtM

Does this clarify it all? If so, does that sound like a good direction to go in?

Sorry for the short novel BTW! :)

@KCarlile KCarlile added the ui/ux Frontend issues label Jun 24, 2020
@KCarlile KCarlile added this to the Release 2.0 milestone Jun 1, 2022
@KCarlile KCarlile moved this to Ready in FlashChord 2.0 Jun 1, 2022
@KCarlile
Copy link
Owner

Adding a note from #104, as a dupe:

Could you please extend the BPM lower range to 40 BPM (or lower) on the BPM slider?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ui/ux Frontend issues
Projects
Status: Ready
Development

No branches or pull requests

2 participants