Page 1 of 1
Cue point issues

Posted:
21 May 2013, 17:41
by Djfitty1
Using Cross 2.4 with Mac 2 ghz intel core 2 duo. Os 10.6.8
I use Cross with turntables. My issue is if I load a track in deck a and set cue then load the track in deck b(it's cloned as expected). After that setting cue points don't transfer back n forth like expected. So setting a cue point in deck b will not show up in deck a and vise versa. My expected result is setting cue points in either deck after cloning should transfer instantly
Re: Cue point issues

Posted:
21 May 2013, 18:19
by Hannes
If you reload the track it will show up.
Cue Points are written to the database, a already loaded track does not access the database again, but only on load.
Re: Cue point issues

Posted:
21 May 2013, 18:40
by Djfitty1
Hannes wrote:If you reload the track it will show up.
Cue Points are written to the database, a already loaded track does not access the database again, but only on load.
Is that a bug? Because it just slows your work flow down to have to reload a track evertime you make a cue point change. Hope this is something that will change soon.
Re: Cue point issues

Posted:
21 May 2013, 18:59
by Hannes
No bug, actually it's quite smart as you can have 16 Cue-Pints on one track if you want to this way.
E.G. 8 Cue Points on Deck A, 8 different Cue points on Deck B for the same track.
-> the Cue Points that are written to the database are those of the Deck that's playing longer. -> if you load another track to deck A, the Cues from Deck B wil be written to the database and be available next load.
Re: Cue point issues

Posted:
21 May 2013, 20:04
by Djfitty1
Hannes wrote:No bug, actually it's quite smart as you can have 16 Cue-Pints on one track if you want to this way.
E.G. 8 Cue Points on Deck A, 8 different Cue points on Deck B for the same track.
-> the Cue Points that are written to the database are those of the Deck that's playing longer. -> if you load another track to deck A, the Cues from Deck B wil be written to the database and be available next load.
Not exactly the work flow I like. When I set a cue point on the fly its important to be able to go back to that exact same point on both decks to scratch what I thought was important. Not to fumble around wondering whats what and whats where. Hope this is something they consider changing