On 23-Oct-08, at 1:50 PM, Ben Wheeler wrote: > On Thu, Oct 23, 2008 at 01:06:26PM -0700, Albert Santoni wrote: >> Having a custom number of cue points would be very hard, > > Really? > Couldn't you just have an XML structure something like this: > <cuepoints> > <cuepoint pos="12345" /> > <cuepoint pos="67890" hot="1" /> > ... > </cuepoints> > Read into a linked list. Cuepoints marked as 'hot' go into > the appropriate numbered Hot Cue for fast recall (see below).
To my knowledge, the XML code we use isn't very flexible. This would be a good way to do it though, and I'll make sure to point whoever wants to code multiple cue points in the future to this email. > > >> - Think about how MIDI controllers should deal with this. Most only >> have a single CUE button. How do CDJ's deal with multiple cue points? > > Ok there are 3 different sorts of cuepoint. > 1. *The* Cue point, that is the currently-set point which you return > to when you hit Cue during playback. > 2. Multiple cue points. On the CDJ1000 there is basically no limit > to how many you can have. There are left and right arrow keys which > move the Cue to the next cuepoint after/before the current track > position (NOT the current cue point). To record one of these cues, > there's a button marked [CUE/LOOP] MEMORY. As the name implies, > this records the current cue point, or loop if you are looping, > as a multiple cue point, marked on the waveform display as a little > red marker underneath the wave. > 3. Hot Cues. There are 3 of these with individual buttons A/B/C plus > Rec which toggles between recording and recalling a hot cue. In record > mode, pressing A/B/C records the current position (not the current cue > point), unless you're in a loop, when it records the loop. > When a track is loaded, loading the Hot Cues associated with it is > optional, because it takes a while. This is because it reads the > first few seconds of audio for each hot cue, so that when it's > recalled > it jumps instantly to that point and starts playing. Obviously this > is because it would take a while to seek to the point on a CD. > > Personally, I very rarely use Hot Cues, but I make extensive use > of multiple cue points, not only for cueing but also as all-purpose > markers. It's really useful not to have any limit on how many > you can set (though in practice I don't think I've ever used > more than 8 on a track, but if I were heavily into scratching, > I might use more, and probably would make more use of Hot Cues) > > Ben Good to know, thanks for sharing this detailed description Ben! Thanks again, Albert ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
