This is a read-only archive of the Mixvibes forum. Posting, login and search are closed. For help, visit mixvibes.com or join us on Discord.

Cue point issues

   Discuss technical issues with the community. Mixvibes staff provides no support on this board.
Forum rules
Click here to join MIxvibes on DISCORD https://discord.gg/gMdQJ2cJqa

Cue point issues

Postby Djfitty1 on 21 May 2013, 17:41

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
User avatar
Djfitty1
 
Posts: 39
Joined: 08 May 2013, 17:33
Location: Houston Texas


Re: Cue point issues

Postby Hannes on 21 May 2013, 18:19

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.
June 2012 Mixvibes DJ of the month

https://soundcloud.com/han-nes-10/fridaybeatdown2ndedition
no support by pm

beta troll

Macbook Pro 13, late 2011, 6GB RAM, 480GB Crucial M500
Thudrumble TR-1S, Vestax VFX-1, ESI Maya USB+, Rane SL2
User avatar
Hannes
 
Posts: 4168
Joined: 07 Dec 2010, 02:57
Location: Vienna


Re: Cue point issues

Postby Djfitty1 on 21 May 2013, 18:40

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.
User avatar
Djfitty1
 
Posts: 39
Joined: 08 May 2013, 17:33
Location: Houston Texas


Re: Cue point issues

Postby Hannes on 21 May 2013, 18:59

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.
June 2012 Mixvibes DJ of the month

https://soundcloud.com/han-nes-10/fridaybeatdown2ndedition
no support by pm

beta troll

Macbook Pro 13, late 2011, 6GB RAM, 480GB Crucial M500
Thudrumble TR-1S, Vestax VFX-1, ESI Maya USB+, Rane SL2
User avatar
Hannes
 
Posts: 4168
Joined: 07 Dec 2010, 02:57
Location: Vienna


Re: Cue point issues

Postby Djfitty1 on 21 May 2013, 20:04

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
User avatar
Djfitty1
 
Posts: 39
Joined: 08 May 2013, 17:33
Location: Houston Texas



Return to Community Support




Board index

 
 
   
 
© 2014 Mixvibes
 
cron