Very Serious Bug in Traktor v2.5

As not all music is the same

I'm all for a bit of editing - if I know the results are going to be consistent.

Cubase has Hit Points - which detects the beats incredibly well
And then has Time Warp - so you can define a tempo (beat) map - to sync everything together

With Tractor - I don't mind putting the work in to setting the beat grid - for those more difficult songs
And a similar editor to the one above - or Re-cycle would work great, or Wavelab, Soundforge

It only has to make a reference track to a bunch of Markers

 

WHAT? is a very seriuos problem men...You don't use this ok...but The people pay for ALL functions of traktor OK?
for me is a SERIOUS problem...
waiting for solution in next patch....:angry:

 

Agree with you man, i have many bootlegs in my collection, that have more then one Beatpoint, and YES i need them all. I can do phase sync manually but, sometimes, during the gig , i mixing 2 tracks and also using samples, i dont wanna that something going out of SYNC in the peak of the mix, so its true this function is VERY VERY inportant for me, and im gonna wait for update(((

 

Totally agree. Maybe we are a "minority" (a really bad chosen word, more if is coming from a moderator), but we paid for the software like everybody else. Some people (I won't say nothing like "the majority" or "most of us", I just don't want to play the same game...) prefer to have Traktor running 100% fine before having remix decks, other new gadgets, etc, etc.

I think it's totally logical.

 

Guys, it is clear that company related persons will do anything just to minimize the size of the problem. Up to outright lies in the face. When i sent a bug report about the second beat grid marker issue, the guy from NI answered me, that following the second beat grid marker is technically impossible! With this kind of attitude to customers, my confidence in the company reduced with each passing day.

 

Agreed - bugs in 2.5

Wow... no wonder it is a free update. You get what you pay for...

I am also experiencing phasing and beat grid/sync issues. Does anyone have an idea on when the next update is going to be released?

 

you're right - this point has still room for improvement (and it's actually taken care of already).

 

it didnt in older versions neither, that was always an issue. i tend to not set the autogrid - however the tempo detection itself works much better. it's easier and faster setting the gridmarker manually than correcting the tempo. my preparation time definitely has become shorter.

 

we moderators are here to read the forums. we bundle feedback and bring that to the forums admin.
since i'm based in berlin and working so many years for NI now, i often enough bring up certain issues directly to the respective ppl.

usually, the perception of the moderators in the forum correspond to the absolute figures of the tech supporters.

 

cant comment on those, since i dont use them.

you dont have to believe me - you can believe absolute figures.
NI tested several playlist from various ppl (including a hiphop playlist from me) and given you're using the right range before analyzation, the results are much better in 2.5.
i still can confirm this from my daily preparation time.

traktor never had flexible beatgrids to enable gridding of tracks with variable tempi.
this also didnt happen in 2.5 - beat detection, gridding... that's all for quantized tracks.

 

a serious problem is where the music stops.
where traktor crashes.
something like this.

an unwanted phase-shift (and nothing else is happening) is annoying, yes (and that's why it's taken care of for the next update), but it's not "serious".

 

please note that i'm not a native english speaker. what word would you have chosen?
i wanted to put the bug (which it is, that's not the point) in perspective: by no means all users are affected by this, since a second beatmarker is useful only in a split-amount of tracks in general.

 

please let me know the ticket number.

 

4 DJ Freshfluke:

I don't want to make the ticket number public, so here is the copy/paste:

 

i need the ticket number to investigate and make the supporters aware of the respective (internal) bug number to this issue. this issue is confirmed. it's no problem in giving me the ticket number here or via pm, whatever you like.

 

If NI implanted the feature for second beat markers and so forth, it's because that feature is needed. Not having that feature work correctly in 2.5 is a big reason for me not using 2.5. I have(along with others i am sure) put in a lot of work to insert second and third beat markers and it is unfair to not be able to benefit from it in 2.5.

 

Yeah, exactly. Tracks of ours with multiple beat markers may be a subset of our overall collections, but when those tracks are needed, they're needed. It's as simple as that. Trying to reduce the issue by saying it only affects a small percentage of tracks/users isn't helpful. NI built the multiple grid marker feature. People obviously use it. Not everyone plays modern edm ALL the time.

I haven't bothered with 2.5 because of this bug specifically. Unfortunately all the other issues just cemented the deal. I'll wait, no big deal. 2.1.3 is pretty sweet already IMO.

 

Thanks for clarifying on the downbeat detection issue and saying it's being taken care of. It's not one of the major issues, but one of those that when ironed out, nobody will miss.

On the sentence about NI hiring someone to read the forums i was being slightly sarcastic. I know they have to know what's going on and what we need, but for some reason many things are dismissed. And besides that there are you moderators who of course have a relationship with the company, so big issues and nice suggestions may be reported to them.

In no way i intended that semi-joke as an offense to you all, i imagine it may be hard to be as close as you are to the company and seeing sometimes that things can't move forward at the pace that would be optimum, or in the way one would like. So i apologize if the point was taken in this direction, it wasn't what i meant.

Although not for as long as you have, i have been using traktor for years and i still use it on a weekly basis. I think that i know it fairly well, at least the areas i use, and while there are awesome things in it that no other thing can provide -the actual reasons because i still use it- there are some 'minor' annoyances, long time requested improvements that would make the software much more usable and enjoyable, that could be easily implemented, that are simply ignored. And that is frustrating when you have to deal with them constantly.

I try to be constructive and make proposals based on the day by day experience with the software, but sometimes i simply can't hide my anger seeing the apparently poor care NI puts in my (maybe our) needs. If there was a little bit more transparency on their side, i'd probably be more patient if i could find sense to what's going on.

 

since traktor doesnt support multiple tempi, the second beatmarker does not much... it's more like a side effect, since it's a cue point and you can set endless cue points in a track.

a second beatmarker only resets the phase, which really only helps in a few occasions. depending on the sync type you chose (tempo or phase sync) or if you use timecode, you'll never see the difference either.

i'm not saying it should not be changed to the former behavior, i'm just putting it into perspective.

 

for sure. since i'm in berlin, i'm visiting the office every now and then.
so i have even shorter communication ways with the devs and project managers when it comes down to forum issues.

taken! and yes. often enough it's like "sitting between all chairs" as we say in german

if you only knew how often i'm the sporn in NIs flesh - they must sometimes hate me as much as some forums users must do