Impressions, bugs and feature suggestion (1.2.1)

You can select which info you see in the Deck Header in Preferences in Deck Details.

Karlos

 

you should not sync to the master clock then.

imagine the following:

track is detected with 105 bpm and that's ok for the initial loop/first bars.
in the middle there is a break with 120 bpm you wanna mix via fx.
in INT mode, dial in 120 in the master clock and use the effect.

the effect is now synced to the actual tempo of the track, not the detected tempo.

regarding the starting point, i'd set a beatgrid point at the beginning of that loop just for restarting the phase.

i know it's not the king's solution, but at least a bit of a workaround so far.

 

Your workaround is basically what I do now for older tracks that I use a loop to get out of. For example, take Billie Jean; the beat drifts a bit, but I just set a second beatgrid right before my out loop and it's fine. However, that isn't such a good solution for effects because we're basically tied to only triggering an effect at a certain point in a song. Not very spontaneous is it?

Like I said, I think it's just another issue where the increased functionality is (at least partially) nice for perfect tempo tracks, but the downside outweighs the benefits for older tracks. Short of flexible grids, the only solution I see is to have something similar to the Quantize or Snap button for effects--when it's on it works off of the beat grids, when it's off, it works like it did under T3.

 

yep, the workaround is similar. although billie jean only drifts a lil bit, where funk and soul tracks often have really widely different tempi per track and a 2nd beatmarker makes only few sense (in that case: only for restarting the phase for the fx, a proper loop you wont get then).

we both agree, that a more flexible beatgrid concept would not only be the solution to your gripes, but also be a big improvement talking about all genres of music that are not 100% fourtothefloor with a constant tempo throughout the track.

 

Billie Jean is a corker aint it. Ive got one grid that works just fine. It drifts like a tramp for most of the track but it loops perfectly at the beginning and comes back into line near the end for another loop.
No need for the 2 grid workround fortunately .

 

Sorry can find that can you guide me on how to get there......

 

Ive just read your posts to see what software your using and i see its DUO not PRO.

Neither Deck Details nor Layout Manager is available in DUO im afraid.

Karlos

 

Wow that's horrible are you guys going to fix that on the next update I need to see the time into a track to mix .....
---
Karlos I when back to the older version of Duo and now I cant load my tracks using the CTRL and ARROWS keys opn my laptop why?

 

open the prefs, then click import and import the respective *.tsi file (mappings file).
i dont know if older mappings files have been overwritten, so you probably have to take it from your backup.

 

OK, another weekend, another report.

1) Prior to my gig I setup and tested timecode control on one deck (just for a little scratching). Everything worked fine so we left to return just before the start of the gig. Got back, fired up Traktor, tested out a couple of tracks (without vinyl control) and they worked fine. Tested vinyl control and nothing. No input at all. As far as I know, nothing had changed at all on my Mackie d.4 mixer and the outputs worked fine (which should indicate that no settings were wrong). I also double checked the input, but I was getting no signal in at all. I never did get this issue resolved (it wasn't critical that I be able to scratch). Not sure if anyone else has experienced this, but I would consider it another black mark on the list of reservations about TPro.

2) Audio glitches. A little different scenario than last weekend--I did not experience any glitches in my 3 hour set, but my brother (running on an almost identical configuration) indicated that he had 3 or 4 over the course of 7 hours. It goes without saying that the number should be zero. Always. Like in 3.4.

3) Beatgrids/cue points. I feel like I'm having deja vu here because I KNOW I've posted this problem in versions past (several of them, IIRC). After setting several cue points on some tracks, when I reload, they're not there. It's not ALL of the tracks, just certain ones. Same thing goes for locked beat grids--they stick MOST of the time, but occasionally they don't. It's very annoying, ESPECIALLY since we've been down this road SO MANY TIMES BEFORE. I mean, once someone at NI figures out what the problem with this is and how it can be addressed, CAN'T THEY WRITE IT DOWN AND PUT IT SOMEWHERE THAT EVERYONE CAN FIND IT? I understand bugs related to new functions, but should we really have the same bugs popping up version after version after version? Again, here's a problem that HAD BEEN FULLY FIXED IN 3.4. See a pattern yet?

I do want to say that by and large, I'm getting used to TPro. Given everything, I would say that TPro--even at version 1.2.1--is not a step forward from 3.4. At best, it's a step sideways. And that's pretty poor considering the amount of time that's elapsed since TPro was released...

 

Has anyone noticed this one:

Set a few Hotcues (different kinds: grid, cue, loop...) and then mess around with them,
pressing and switching them rapidly in 16ths (1/16th of a note or 4 times in a beat).
What happens?
They (Hotcues) change their state/mode, if you had the Hotcue 3 set as a loop cuepoint, now becomes, say, just a regular cue. Every change is possible. :S
I'm using Maschine as my MIDI controller.

 

I personally think that the update has make things even worse as they've been before. I don't care much about all extra features traktor is offering to me...the most important thing is to mix properly in a way i used to when i was still burning tons of cds for a gig. That's why i've decided to buy Scratch DUO.

Using the CDJ 1000s on most of my gigs, setting a cue point has just moved on to be a very annoying thing! In CD Mode you'll never hit the right spot when you think you've reached the first beat. Actually hearing that first beat hitting the CUE is almost impossible. So far so bad...i can handle that by scratching the beat in.
But playing acapellas is now only possible if you want the start to sound like big ****. This has been bad under 1.1.2 already and now it’s ridiculous.

This is not the only problem i have with the new update. There are several other things working bad on 1.2.1 such as:

- Looping on the CDJs is now, depending on the spot, almost impossible since it got some kind of delay in it...even if you hit it right on the exact spot.

- Using the hotcues on the CDJ is still not really possible. Think it’s because of that delay when you set it. If you place it just on a beat and record it you will later when you play it hear nothing.

- Another bad thing is that after waking up my macbook from standby i always have to reboot it because when i play on traktor all i hear is bad sound and crackling. It doesn’t matter if i had traktor open before standby or if I start it after standby.

These are my impressions of the new update. Don’t know if anyone has the same problems as I. I couldn’t read all threads and search function didn’t work properly.

I’m seriously thinking about switching back to cds since I’m very disappointed. First step was a downgrade to 1.1.2...I’ll check what will happen next. Maybe another update will get rid of all problems I have.

Therefore I hope that someone from NI is reading this.