On Sun, 17 Feb 2008, Albert Santoni wrote:

> 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 can see the logic behind the decision with it. Using the
keyboard (eg Shift-O) to cue-and-stop is fine, but on the Herc
controller (my current myopia :-) there's no shift key... :-)

> 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.

If there wasn't the "waveform bug" then this would be mere
aesthetics (though wars have been fought over mere aesthetics...)

I was beginning to get the hang of beat matching purely by ear,
without waveform, but waveform does give contextual visual
timing info, its just so damn useful!




> 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...) :)

Ugh, even I hate this... a "cue mode" button from the plethora
of extras on the Herc and presumably others... CUE STOPS vs
CUE PLAYS. I hate modal interface crap like that.


-------------------------------------------------------------------------
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

Reply via email to