On Sun, Mar 02, 2008 at 03:54:50PM +1300, Robin Sheat wrote: > On Sunday 02 March 2008 13:40:42 Albert Santoni wrote: > > Let's hear your fun ideas! :) > * Improving the way the BPM detection works so that not only detecting the > BPM > (which it seems to be doing a fairly good job of now), it is also able to > align the markers with the actual beats. If this works well, then the sync > button can not only match the tempo, but also align the beats.
There is still a lot of improvement that could be done around the BPM stuff. I'd like to see tap tempo buttons on the main screen, that feed into the BPM detector so that (a) it knows what a beat looks like, so should do better at finding the next one, and (b) the beat marks move to the right place. That would enable Sync to work better as Robin says (though it's not a function I'm ever likely to use no matter how well it works!) > * (probably too small for a project, but...) automatically setting a cue > marker at the first beat/remembering were the user last put a cue marker on a > track and putting it there by default when the track is next loaded. This could be combined with other cue-related shenanigans: * Multiple recallable cuepoints (or hot cues) per track. * Memorising audio shortly after each cuepoint to avoid latency * Loops (which are just a specialised instance of cues with the addition of an endpoint) Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
