Comment 3 for bug 898213
Revision history for this message
| Phillip Whelan (pwhelan) wrote Re: turn quantization on by default | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
There is a conundrum here. At the moment our beatgrids are not accurate enough so cues will not work properly, but beatloops are mostly useless without it.
At least in my case I have some songs where I have fixed the beatgrids and others where I have not. Those without are close but are off by at least a margin of .3%, more than enough to render the beatgrid useless at 150+ BPMs. 90% of my problems would go away with bpm rounding, but that patch has been rejected.
As I see it, to get the best user (and least confusing) experience we have to either merge in the forthcoming vamp branch or turn off quantize by default and make beat loops always quantized. I think this is actually why I had programmed it the way ai did in the first place. I know the way it is now is the 'correct' way to do it, but the 'correct' way is usually more suited to technical programs, internals etc... and not UIs for end-user programs where convenience should be more important.