On Mon, 2008-02-18 at 14:54 +1300, Robin Sheat wrote: > On Monday 18 February 2008 14:45:47 Tom Jennings wrote: > > Umm, a suggestion? Make the CUE function while playing to be, > > jump to cue point then pause. Then a PLAY from that spot might > > be better behaved? Gross, I know... > I'd like that just because I think it'd be more functional, unless I was > doing > some kind of manual looping or something. Which I don't. Get the beat timings > the same, press cue, wait for start of a measure, press play. At the moment, > I either have the other track going in the monitor, which makes it harder to > follow the master output, or I press cue, press pause, seek back a little > bit, and then press play. >
We had this big discussion about this last year, and the current CUE behaviour is a compromise that was reached. We had a decent write-up of this on the old wiki: http://mixxx.sourceforge.net/wiki/index.php/Feature_Discussion#Cue_Handling_Specification Note that if you right-click on the cue button, it'll currently go to the cue point and stop. I'll agree with Robin here that it is awkward when I want to "goto-and-stop". I like being to push cue and do faux-looping when I'm trying to adjust the pitch of a track though, helps me get the beats in sync faster. Thoughts? (If someone can think of a better compromise than what we already have, and it works well with controllers where you only have a single cue button, I'm listening...) :) Albert ------------------------------------------------------------------------- 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
