traktor pro - noob q's and WTF!!1

[Flaekiface]

And the grid still dosent match after this point?

[DvlsAdvct]

Um… that’s cause you have an auto-grid marker being set, whereas in T3.4 it’s not setting the grid marker. I can almost guarantee that when you delete that grid marker the lines will match the T3 lines.

I don’t let Traktor set auto-grid markers.

And, at that, I have had no issues gridding tracks in TPro that I didn’t have in T3. I know there’s a reason that the waveform isn’t being displayed, I just don’t know what that reason is. I had the same problem with Traktor Scratch when I first got it. Which is why I say just bring it to the NI forums, or get in touch with support or something and see where it can go.

[buzby]

@BentoSan

Sounds like the tracks arnt being analyzed at all by Tpro, not too sure why that is.

Go into your Traktor Pro preferefernces - File Management tag - them make sure Background Anaysis when loading into deck is enabled.

thanks for all the replies

i turned the background analysis off to stop tracks loading into the decks at different bpms

just to add to my whingeing - it wont find my midi controller either

i ve been using ableton for 3 years so know how to set a controller up

[buzby]

@MisterMoleyMole

You runnin a proper copy of traktor ?

With regards to the beatgrid it sounds liek you have some drift. So you will need to either set multiple beatgrid markers or warp it in ableton then render the track out and then beatgrid in traktor!

hi - yeah - its a legal copy - upgraded from traktor le which came with my NI audio kontrol

i tried setting multiple beatgrid markers cos i thought it would work similar to ableton -you know.. anchoring them at the point where you set them but nope..

[nemo]

I learned something new today by reading this thread, thanks a lot.

[buzby]

@nemo

I learned something new today by reading this thread, thanks a lot.

what did learn?

i think i learned that i either have a really buggy copy or i just wasted my money

[buzby]

hey deepstereo

this is the problem i have - i am not using the autobeat grid - it is switched off in the preferences etc

but that little blue triangle in no mans land is there before my load marker at the start of tracks and like i said i have to press the hotkey to get it to snap to the load marker

i tried something - i set a load marker on a new track - no other cues - mr blue triangle as there - i started to play the track … pressed the cue button hoping it would
go to the load marker but …

it snaps to the blue triangle !!!

i ve just crawled out of bed … im at home really sick - but i will open traktor later and take some screen shots later and post them up or better still post up some video shots

[deepstereo]

In that picture it has the beats wrong but the bpm is good so if you just nudge the marker to the first beat it is done. I have no problems with setting warpers in traktor, just make sure you get the first beat right and from there it is not difficult except for non electronic music and songs with tempo changes.

This is of course true, and manually adjusting the first marker woudn’t be a problem, however I noticed that many tracks do drift towards the end, and this makes the whole feature of tempo syncing useless, you have to beat match manually.
And again - there is no drift in Traktor 3.4.

If you prepare the whole set beforehand, than you could spend some time to re-grid your tracks, but what you want to throw in some track you hadn’t planned? Chances are high that it won’t be regocnised properly.

[DvlsAdvct]

This is easily fixed by nudging the BPM. It takes around 4 seconds to do it. And I have had the same drift in T3.4.

I haven’t seen, nor heard of, a single BPM locator that is perfect, in any software.

[deepstereo]

@Flaekiface

And the grid still dosent match after this point?

no, the grid is messed up throughout the whole track. Gotta try switching off autogrid and maybe background analysis on load.

[DvlsAdvct]

I’d keep background analysis on load on. That’s why the wave form doesn’t display. (I think I’ve figured this out)

Okay

So I recommended turning off background analysis on load to try and see if it was a latency issue. When the background analysis on load is off the crackling stopped, which to me says it could be a latency issue.

But when you turn off background analysis on load it doesn’t give you a wave form. So maybe try tweaking your latency a bit, and turning the analysis on load. Or, just analyze your whole collection and then don’t worry about it. I turn it off cause I analyze my entire collection first thing. There’s no need to reanalyze the tracks.

[deepstereo]

@DvlsAdvct

Um… that’s cause you have an auto-grid marker being set, whereas in T3.4 it’s not setting the grid marker. I can almost guarantee that when you delete that grid marker the lines will match the T3 lines.

I don’t let Traktor set auto-grid markers.

OMG! how simple!
it worked, as soon as I delete the marker the grid goes back to normal!

thanks a lot!

[DvlsAdvct]

Keep in mind it’s a setting to drop an autogrid marker. So, if you turn that off, it won’t do it anymore.

Also remember that if you have written tags to any track with that autogrid marker there it will stay. But it’s easy to fix with simple hotkeys.

[deepstereo]

That’s cool!
I take my criticism of TPro back and will need to do some thorough manual reading ))

Thanks again!

[buzby]

@DvlsAdvct

I’d keep background analysis on load on. That’s why the wave form doesn’t display. (I think I’ve figured this out)

Okay

So I recommended turning off background analysis on load to try and see if it was a latency issue. When the background analysis on load is off the crackling stopped, which to me says it could be a latency issue.

But when you turn off background analysis on load it doesn’t give you a wave form. So maybe try tweaking your latency a bit, and turning the analysis on load. Or, just analyze your whole collection and then don’t worry about it. I turn it off cause I analyze my entire collection first thing. There’s no need to reanalyze the tracks.

thanks again for the reply

latency thing has nt been the issue i think- i ve tried runnig 4 decks with all effects on and crackling does nt occur until a very low latency value is chosen

thing is - if i turned the back ground analysis on and then put the same track into 4 empty decks - it gives a different bpm value for each?

legal tracks bought from beatport by the way - i will try to analyise the whole collection

[DvlsAdvct]

are you gridding the tracks and locking the BPM?

[buzby]

well

im trying to grid the tracks as best as i can without much success and also locking them…but would nt a track show the same bpm even if has been badly gridded?

maybe im used to ableton but i would like to be able to zoom in on the waveform a lot more than you can ..

[DvlsAdvct]

If the track is locked I don’t think it would change the BPM. But, I guess a work around would be to analyze the whole collection and then see what happens.

Gridding is hard to get the hang of, I know, but once you do it becomes really basic.

What kind of music are you working with?

[buzby]

yeah - i gotta try to be patient with the gridding

i guess im used to working with ableton and i can warp in that pretty quickly now

working with minimal/progressive/tech - pretty straight forward beats

cheers

[buzby]

one more thing
i can just use a midi controller with a usb connection right ?

i cant get it to work although it is working in ableton fine