© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Playing with my BeatMap fix:
https:/
I notice that it is already hard to correctly use the 2/3 BPM and the 3/4 BPM buttons.
It looks like that we need a bunch of those buttons to entirely solve this issue, sticking to this approach.
It is hard to predict what will happen with the beat position if you press a 7/8 button, also for calculate the resulting bpm the user will likely wish he had a calculator.
It is also already hard to spot that you need to press the 3/4 BPM buttons to go from 124 Bpm to 93.
there might be a chance to make it better. But how.
What are the use-cases?
The main use case is:
A auto detected "not ideal" beatgrid is likely on a lets say 1/8 grid of the desired beet, because it was triggered by an different sound (instrument).
Tapping a beat will more closely at the desired beat, but not exact. so it is not a good solution.
Think we have two cases:
1. Visual beatgrid editing align the beatgrid to one beat and you see that it misses the following beat.
Here we need may introduce an option to pick the next beat but stick on the 1/8 grid
2 Tapping the beats. Here we may round to a 1/8 grid
Any thought ... did I miss something?