Very Serious Bug in Traktor v2.5

if your using time codes and you are playing a song with a second beat grid and you must mix the next song to that second beat grid then the feature is needed so it's not a side effect. I see no reason why 2.5 does not use this feature correctly(hence why it's a bug). The difference a second beat grid marker can do makes a huge difference in time codes.

 

Onöly when you use Sync with timecode.

Otherwise you mix with your ears end not with your eyes.

 

nope, i just tested that yesterday... had 2 tracks, one of them having a second gridmarker resetting the phase. both synced to the master clock.

it happens... nothing when reaching the second gridmarker. i see no difference to any version before.

what sync-mode (preferences) are you using? and what deck sync-mode (clock, auto, manual, ...)?

 

ok just to be clear here, i use timecodes with tempo sync and i use the current deck that is playing as a master, so there fore the next tune must sync to the second beat marker of the active tune(if a second marker is set) which is set to master on that decks. This makes a big difference with syncing. You cannot sync to a second beat marker in 2.5 but you can in previous versions there is no question about it.
---

if i wanted to mix by ears only and not use my eyes what so ever, i would still be mixing with real cd's been there, done that and no longer interested.

 

absolutely not! and i expect it to be fixed in the next update.

i only want to put the "serious" into perspective. a phase shifting that has to be done now manually now until the next update might be annoying to the few that are only seeing this due to their workflow, but is by no means hindering your performance for real.

 

you are right it is very annoying when an upgrade comes along with new features but some old features get broken in the process. You are right it won't hinder my performance for real because I simple won't use 2.5 til NI fixes and then if they break other things in other updates, then I won't use the other updates.

To me an upgrade means making things better and not just saying "we'll fix it in the next update".

 

This is a bad bug for anyone using sync with bootlegs ect and tracks that change BPM ... the 2 grid points no longer work as the other deck syncs to the original beat grid .... Sort this NI
---
Ive rolled back to 2.1.3, that sync issue isnt good and i think the program itself felt abit strange.

Also didnt like the way the drag and drop feature didnt take u back to the playlist you was working from (minor change)

 

yeah and this upgrade made a lot things better and more fun. like always, a few things have to be worked out and some affect you more, some less. it's the same with every update.

 

I've now got Tractor working with Tempo changes

an un-orthodox approach - but it works

the beat grid might not line up - but it stays in sync nicely with the next track - and the Remix decks

 

That is absolutely shocking behaviour but not surprising. NI spent well over a year telling people there was nothing that could be done about VCI100 midi outs causing crashes, and that it was Windows issue, a Windows issue that mysteriously disappeared with the release of NI's TPro 2.

Bottom line, as soon as there's something that lets me work like Traktor I'm jumping ship and that's all down to NI's awful customer services/relationship with their users/unbelievably awful 'beta testers'.

2.5 is riddled with problems - I've experienced clicks and pops when using keylock and switching fx, the software is definitely slower to analyse it seems to freeze for a second or so after analysis is complete, and the beatgrid problem too, that's on two seperate setups, one 6 core AMD desktop and one Core i5. Never was a problem before.

 

care to share ?

 

On Hard to sync tracks (i.e. played with live instruments)

I'm using cue-loops for the cross-overs. (fade-in | fade-out)

I'm pretty much ignoring the beat grid
(preferences: sync to Tempo – although I find it still works with sync to beat as well?)

I'm setting the tempo by looking at the end of cue-loop I'm intending to sync with
(where the green section ends)

So if the loops lasts 2 bars (8 beats)
I set the cue point at beat 1 of the loop
and manually adjust the tempo until the end of the green loop matches up with the start of beat 9

Then do the same again for the fade-out loop

Tractor allows you to change the tempo on the fly whilst the track is playing

So after you've played the fade in loop (at the original tempo)
manually type in the new tempo before the fade-out loop starts
as long as the loop function is active – you now have a reliable loop to sync the start of the next track with – or the Remix decks.

It's crude
it's manual
it requires some preparation and having a written record of the tempo of the loops you wish to sync with
(I set the initial tempo to match the first fade-in loop)
it's also much easier having an external midi controller

but it works – and sounds far more fluid than an unmatched loop

However – it would work much better if Tractor allowed – or included a feature to allow Tempo overrides with the hot cues.

i.e. when Tractor gets to Cue 6 (set as a 2 bar loop) Tractor updates the tempo to match this cue-loop
- then it could be automated in a play-list.

 

all the beta-testers have used their 2.5 in live situations. actually they were begging for it way before the devs wanted that since they all felt good going live with it.

 

a windows issue NI found a workaround for is still a windows issue.

 

It worked fine in T3, got broken in TPro1, got fixed in TPro2. How can it be MS's fault if NI's coders can't program on their platform? Other dj software never had the problem. Furthermore they never even admitted that they fixed it, not one of the people who raised a ticket with NI ever got a reply to say 'I think we've fixed your problem', it was never made a mention of on the changelogs. They never even tried to resolve it with anyone, we just got the usual tips for tweaking windows sent several times. This was clearly caused by them, absolutely all evidence points to it.

It's not like Windows and it's APIs aren't well documented, the onus is on the application coders to follow them.

Honestly Freshfluke, your willingness to defend poor practise at NI no matter what does this forum a great injustice.

 

Im with you as well and thats not the only problem with the new updated version which i think was kind of downgrade. I use F1 as well and have lots of litle enoying things that happends without any reason. So I do hope Native will update this asap. Like you guys said, lots of stuff depends on beatgriding, Im kind of safe with the beat mixing since im from the vinyl school but i lose all those other good things like syncing a loop with F1 and its sometimes impossible too keep it in beat and it totaly falls out of hand due to that grid glitch.

 

Threats

DJ Fleshfluke threatened me in a private email saying i should not speak my mind or else be BANNED PERMANENTLY from these forums.

y'know where freedom is encouraged

 

That's a pain in the ass! I was thinking to upgrade to 2.5 but I think is better I wait a lil bit.

 

if i'm not the programmer. but if NI says that there's some windows thing going on, i have no reason to doubt that.

you have no idea how many things get fixed in every update without further mentioning. only the most important/global things are mentioned. there are always little tweaks and stuff that isnt mentioned. also, you do not honestly expect that given to the number of users writing to the support for this and that are written back if anything changes anywhere?

i do not need to defend anyone. i'm kinda tired of the emotional bashing where facts would do a better job.