The Official TSP2 Bug and other stuff that should work the way i want it to thread.

Yeah on the Vestax site I have the latest one they offer and the ASIO site itself hasn’t had an update since last June. I’m just confused as to why the Dicers being plugged in makes traktor unable to read that the Typhoon is connected as a soundcard.

Btw, I can get all 3 controllers to work at once if I use the laptops built-in soundcard, but obviously this is a problem to use.

BUG FOUND!!!

On the Filter 92 in advanced, the resonance control makes no difference, the filter is weak. just did a side by side comparison with TSP1.2.7 to check it wasnt my ears, and im right!

Bah… that sucks! :disappointed:

I know a few of you having vanishing waveform’s after the playhead, my waveform in the main view is fine in every way. but the smaller complete track view waveform below doesn’t show up at all. I’ve done a few re installs, all is well at first and then after a few songs the little waveform disappears again. This also means none of my sample slots waveform’s are visible too.

The weird thing about this bug is when I copy something I’ve sampled from the loop recorder to any sample slot then it DOES have a waveform display.

I think this is a bug, I’ve tried many things but I keep going full circle.

I can see why NI aint put key lock on the sample decks yet, it would cripple most laptops. T2 is already a power hungry bitch. I used run TSP at 3 latency without a glitch while kicking the crap out of every feature. With the latency on T2 set around 8, I’ve found high CPU use to be random, I’ve had pop’s and crackles just while beat juggling but I restart Traktor do the same thing and the CPU is fine?

Key lock is one of the most CPU hungry features, T2 needs a lot of fine tuning under the hood before we’ll see this feature come to the sample decks.

Until the next much needed update, anyone who gigs with T2 live is either very brave or plain mad.

It would be much easier if they implemented support for multiple CPU cores, or even made it 64 bit.

Amen to that!

Considering that ASIO remains the driver of choice, why are they so stagnant? The site alone looks like its from the Jurassic era.

Is it me or do the sample decks do a poor job of syncing loop recorder samples? I tried this quite a few times and had not fantastic results. Although it seems that the loops provided with the software are ok…

Any ideas… am I doing something wrong or is it just the swing of the beats that make them clatter?

are your grids tight? otherwise they will drift

They are now, Im having to re-grid all my tracks thanks to the new hi def wave forms. Im not sure whether its the swing in the loops Im recording that makes them sound off tempo, they just dont seem to line up very well as opposed to the official loops.

Load the backup collection before you analized the whole deal. Lock the bpms of the whole collection and reanalize, it should respect your previous grids.

I have been keeping the tracks locked and then dragging them to the deck… what happens then is that the original grids are not kept in line… they seem to shift as if the definition increase nudges them out of sync with the downbeat. Is there a better way that Im missing?

whatever you do, please do not analize your traktor collection. It won’t be happy.

Can you post a screen grab of a deck ad the shifted grid..?

Worth mentioning that the new Tru Wave does not show the envelope of the track like in previous versions. Its a bit fuzzy to look at now.

Heres a good example of a perfectly gridded track but the grid lines look a bit off. Its just the transient before the grid line.

Hi guys,

First off I am brand new to Traktor (got the S4 10 days ago) and DJ Techtools. I’ve been a Serato user since 05/06 on 1200’s and have been through various controllers primarily just to control looping and cue points, so this whole concept of “syncing” and “beat gridding” is new to me, at least from a practical perspective. I’m well versed in modern digital audio hardware and software - I own Logic, ableton, recycle and literally every other product NI has to offer. I had been thinking about Traktor for sometime and the release of the S4 finally interested me enough to begin the painful transition of moving from my library from one platform (Serato) to (Traktor) another.

As I’m sure is the case for many dj converts, the concept of “syncing” was quite foreign from a practical DJing perspective. It seems a great feature provided you can get your grids set up accurately.

I have read all I can find on the matter, trying to find the most effective and efficient way to quickly grid tracks as I have found that the T2 built in algorithm is effectively useless (which I found quite surprising as this is one of the fundamental differences between the two platforms). So that said, beat gridding from what I can make of it so far is going to be a manual process, track by track.

Now I play a cross of styles - Hip/hop/Electro/Dub/D&B/Breaks/Pop/etc - I have ammassed a massive collection of tunez over the last 15 years (traktor is saying some 100,000+ in my collection) - obviously I’m not going to care about immediately gridding all of them - so at the moment I’m just focusing on what I’m currently playing. Over time, I would like to get a good %age of my collection accureately gridded. As already mentioned I have been completely immersed in this over the last 10 days and have played 2 gigs with TP2 and S4 and have gridded at least 100-200 tracks, my experience was that traktor could sync the bpm pretty well but i would have to nudge the track slightly out of phase for it to sound right. Some regridding was required for tracks I gridded initially and then realized were incorrect after learning new techniques. Generally the BPM are fine, but fine tuning the phasing takes a bit more attention.

I tried using the metronome approach - but for whatever reason, be it a bug or the more likely user error - the tick will randomly dissappear for some beats and then show up again. The click is not getting “lost in the mix” as i have reduced the gain of the track as low as possible and it is also sporadic in track breakdowns. However on the few tracks that it did continue to be audible, I managed to get the grid locked down to the internal clock perfectly and in effect I know had these few tracks to use as a reference.

Therefore:

My current approach to beat gridding is this (assuming Traktor has roughly got the BPM right) -

  1. Load Track
  2. Delete any and all beat grid markers from the auto beat grid process
  3. Find the cleanest snare (i find snares more often lie properly on the beat) closest to the beginning of the song, set a cue point, then covert this cue point to a grid marker.
  4. From here Traktor lays out the grid, I go back then and set cue point 1 to grid at the beginning of the track
  5. I then use the mouse (in snap mode) and go to the end of the track to see how the grid is lining up on snares/claps towards the end and make any fine adjustments to the tempo to stretch/compress the grid)
  6. Once I have done steps 1-5 is when I actually play the track against another reference track and fine tune the grid. Here I run the two together and will adjust the track I am gridding with the jog wheels so it is locked with the track that i know is gridded already.
  7. As i adjust the jog wheels the phase meter shifts slightly to the left or right.
  8. I will then use the grid shift tool to shift the grid left or right until the phase meter is back in the middle.
  9. Once it sounds right against another track I lock the grid and move onto the next - always leaving the reference track in 1 of the 4 decks i move on and repeat.

It is quite a process, but so far as I can see is the only way to truly “sync” your beats so that they sound properly mixed?

This is one of those things that I want to get right from the beginning so as to avoid what would amount to a massive amount of re-work in the future.

Therefore, my question to more experienced traktor users out there who have obvioulsy had to go through this - Is this the right way to beat grid? Should it be this much of a process? I can easily spend 2-3 minutes per track getting it bang on, longer for the more problematic tracks.

Apologies if this is the wrong place for this, but I’ve seen alot of beat gridding chatter in this thread, and I’ve also been hearing that the beat gridding in TP2 behaves differently than it did in prior versions (which I have never used).

Cheers,
-Brad.

Karlos,

The picture you posted resemples what I have after its been re-tweaked. What happens is that once I load the track and zoom in the precision is raised and for some reason the downbeat is off. Im not sure whether its beacuse my gridding was slightly off before and hence is amplified due to the increase in definition, or whether it is a Traktor Pro 2 issue. All I know is that my mixes were in time before.

Having said that the higher definition is amazing… so tight, better than CDJ’s :smiley:!

I personally go for the start of the grid at the start of the downbeat, then assuming the bpm is correct (which seems to be pretty good in TP2) I go to the end of the track find a decent waveform and then adjust it to suit, then I check the middle and if all is ok lock off the track. It seems to work pretty well for me (I mix house)

Yeah don’t put your gridmarkers on the snares. I promise you’ll regret it later. The first gridmarker is 1.1.1 so your beatcount will be off if you put it on a snare unless the snare comes in on the 1. More often it doesn’t. You can adjust your grid visually with the snare if you prefer that but put the first marker on the 1. Otherwise traktor will think your beatcounting is different than it is and that can screw up your phrasing, especially if you start using the beatcounter as another visual cue.

NO MIDI-COMMAND for sampler source selection :rage:

This, and this question probably would have been better in of the many how do I beat grid posts. It’s your first post though so we’ll let you slide. :wink: