Hi everyone,

Part of our 1.8 library rewrite will bring multiple-cues and hotcue 
support to Mixxx. Previously this was only possible through script. As 
I'm coding this up, I figured I'd reach out to the community to get some 
feedback on my current plans for exposing cue functionality to scripts, 
standard MIDI mappings, and the skins/GUI. The basic idea is that every 
track can have multiple cue points. Each cue point can have a position, 
a hotcue number, and a label.

The following are the controls that will be available for modifying 
hotcues. Please note that this is not for modifying cues. For 1.8.0, I 
don't believe that scripts will be able to operate on a tracks cues if 
the cue does not have a hotcue assigned to it. The number of hotcues we 
provide is totally arbitrary. I was thinking something like 64 or 128 
would be more than enough. In all of the following controls, XXX is the 
hotcue number.


hotcue_XXX_position : value
  The sample position of the hotcue. -1 if hotcue_XXX is not set.

hotcue_XXX_enabled : toggle
  Whether the sample position of the hotcue is valid (i.e. not
  -1). This is for convenience (so you could make a light respond
  to to this value in a regular binding)

hotcue_XXX_set : pushbutton
  A pushbutton command to set hotcue XXX to the current
  playposition of the player. If hotcue XXX is set, then the cue
  currently in hotcue position XXX will lose its position as
  hotcue XXX, and hotcue XXX will be set to a new cue positioned
  at the current playposition. This is the same as calling
  hotcue_XXX_clear before calling hotcue_XXX_set.

hotcue_XXX_goto : pushbutton
  A pushbutton command to cause a player seek to the position of
  hotcue XXX. Does nothing if hotcue XXX is not defined.

hotcue_XXX_gotoandstop : pushbutton
  Same as hotcue_XXX_goto except stops the player after seeking.

hotcue_XXX_activate : pushbutton
  A pushbutton command to activate hotcue XXX. Activation works
  as follows: If hotcue XXX is not set, then the same as
  hotcue_XXX_set. If hotcue XXX is set then the same as
  hotcue_XXX_goto.

hotcue_XXX_clear : pushbutton
  A pushbutton command to make the cue marked as hotcue XXX no
  longer hotcue XXX. The cue's hotcue number is cleared in the
  database, but the cue is NOT deleted. hotcue_XXX becomes
  disabled (i.e. its position is set to -1).

Please keep in mind that these are only for hotcues! The old cue 
commands will still be present. Their role is less clear now, but we're 
still figuring that out.

Thanks,
RJ

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to