> re: above, the cue-pause behavior persists (I still haven't > profiled; tomorrow) but it seems to more more often succesfully > if I hit CUE-while-playing within a few (1 - 10?) seconds of > the cue point, than if I'm a minute or two in from it. But > it's sort of splitting hairs to tell and short of 100 tries > documented it's fairly vague correlation.
This isn't that unbelievable, when you load the song initially there's bpm detection and summary generation going on so the system is just under more load. Especially when the summary generation is making the decoder read some location while the playback is making it read some other place and then you press cue and ask it to decode some third place that probably confuses the hell out of any caching algorithm you might expect to be trying to help you. Adam ------------------------------------------------------------------------- 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
