1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE
NOTICE:

Our Traktor Pro Public Beta is available again in our new online community. Join us if you want to try new features.

MORE INFO

Timecode CDs running @ 160bpms on CDJ 1000's & Z2? why

Discussion in 'TRAKTOR PRO / TRAKTOR SCRATCH PRO' started by Clemo, May 30, 2015.

  1. Clemo

    Clemo Forum Member

    Messages:
    35
    Many thanks for taking the time to read this .

    Having just bought a Z2 and some CDJ 1000 MK3s i am having a bit of trouble .
    if i put music cd's in the 1000's they run at there correct bpms (as you would guess they should)

    When i put the traktor scratch timecode cd's in they whack up to 160 ... and with adjustment on pitch control up to 170+ ( on the pioneer cdj)
    which is making it very difficult for me to get the temp from deck to deck to match .
    On the computer in traktor scratch its running at the correct bpm . say 130 for Oakenfords southern sun .

    Surly timecode cds don't run at 160 +

    can anyone point me in the right direction .
    i have trawled through preferences and have adjusted current tempo range in transport to 8%
    but this has not fixed the problem .

    I have asked native over a week ago now and had not even a cheese counter ticket number .

    hopefully one f you guys know what I'm going on about .
    Many thanx
    clemo
     
  2. djenzyme

    djenzyme NI Product Owner

    Messages:
    547
    The timecodes do not have a specific BPM. Your CDJ's are making that analysis. It should make no difference whatsoever, your tracks in Traktor are playing at the correct BPM, just ignore what the CDJ display is telling you ;)
     
  3. Clemo

    Clemo Forum Member

    Messages:
    35
    Cheers Djenzyme.
    i hear what you are saying ...
    BUT getting deck A to pitch at the same speed as deck B at 120 bpms is easier than 160+
    if i so much as touch the tempo adjusts at 160 + it goes way off .

    If time codes do not have specific BPMs why are mine spinning so high?
    I cant find that answer ..
     
  4. djenzyme

    djenzyme NI Product Owner

    Messages:
    547
    The timecode signal does not have a BPM, the only thing that affects it is the position you have the pitch fader set to.

    Just because your track is 120bpm does not mean the timecode will be as well. The CDJ is interpreting the timecode signal and giving a false reading, this is perfectly normal, my CDJ's often show the bpm to be 160-170bpm when using timecode.

    Check your pitch range settings in Traktor preferences, also check that the CDJ pitch range is not set to 'wide'.
     
  5. Clemo

    Clemo Forum Member

    Messages:
    35
    Thanks for you reply ...
    what have you got your pitch range at in preferences ?
    what do you set your CDJ to ?

    cheers
     
  6. djenzyme

    djenzyme NI Product Owner

    Messages:
    547
    Personally, i have the Traktor pitch range set at + - 10%. And then the CDJ pitch range also at 10% but i also use the CDJ with 6% for smoother mixes, no need to change the Traktor settings, just set it on the CDJ.

    Actually i think maybe the Traktor pitch range settings are irrelevant when using timecode as the CDJ dictates what speed you are playing at. Not sure about that though so i set it at 10% just in case.

    Have fun figuring it out ;)
     
  7. Clemo

    Clemo Forum Member

    Messages:
    35
    i was having fun figuring it out ,
    then i started to mess with settings .
    then i started to have an emotional breakdown
    now i am broken ... !!!
     
  8. DJ Freshfluke

    DJ Freshfluke Traktor Mod

    Messages:
    26,792
    lucky me, i read the other thread you opened, otherwise i wouldnt know what your problem is. please dont double post!

    anyways - your main issue is that the calibration is failing. as long as it is, you'll never get a correct tempo out of the CDJs. so this is the first thing you have to check - why your calibration isnt doing what it should.