Any early adopters of Traktor 2.6.8?
Just wondering if anybody is using it yet or if there’s and new bugs that come from using it. I’m loath to upgrade until I see people are using it in real world application.
Upgrading doesn’t remove the old version so you could try it yourself too.
True but I’ve taken the stance of waiting a while after each release to see whether it’s even worthwhile to clutter my computer with it. I just recently deleted 5 versions of old Traktor updates and with the resent rash of 2.6.blah fixed this but broke that, I’m just a bit gun shy when my current version is working just fine.
Do you need any of the new (few) features in 2.6.8, or are you having problems with 2.6.7? If not, there’s your answer. Just wait. Or, add one more version of Traktor to your hard drive so you can test drive it with your specific setup (best way to test it).
2.6.8 has a few bug fixes that some people that use m4a files may have encountered. If you are on 2.6.7 I would update to 2.6.8.
I have been gigging with it for the past few weeks with no issues.
Whats new in 2.6.8
Does it have a ‘few’, or does it have one, as per the release notes?
I must say, coming from the Serato world, I don’t appreciate the vagueness which always seems to accompany NI’s releases. IMO it doesn’t encourage bug reporting by users, because how would you ever know if your bug actually got fixed?
I mean, just compare 2.6.8 with the release notes for SDJ 1.5.2 (also released a month after it’s predecessor).
Either NI are not getting much done, or they’re choosing to not tell their users what they are doing. I’d prefer it was the former, TBH.
Listen - you should NEVER upgrade if you have a working version that you are happy with.
You’re asking for trouble. Although, Traktor has a GREAT parallel install process…
I agree that NI can be ‘less that transparent’ with release notes but that’s just the way they are, always have been. They only really release notes on ‘show stoppers’ like the playlist bug in 2.6.6.
I agree, I think they should address ‘reproducible’ bugs and whether they have been fixed and provide more information.
When they release hotfixes like the recent ones in quick succession it’s reasonable to assume that they bring little or nothing new and they fix what is broken (supposedly).
What I find odd about that Serato release note is that none of the fixes are software only fixes. They are fixes for 3rd Party Controller Hardware..? It kinda suggests that SDJ’s controller implementation is their Achilles heel. There are no software only bug fixes listed (and there will be some) or any for Rane users (which most Serato DJ’s are).
I mean, are there ‘any’ bug fixes on that list relevant to you? If not that release note is of little use if you have previously reported bugs.
It’s all well and good certifying all these new controllers but there a lot with issues and I’m not sure “Dicer showing unpredictable behavior” is a particularly descriptive release note.
I am by no means excusing NI and the way they report bug fixes, I agree with the premise that they could do it better.
I’m just not sure the grass is that much greener in New Zealand 
You’re asking for trouble if you don’t upgrade from 2.6.6 or 2.6.7 that’s for sure.
The new Controller Editor is important for Kontrol MK2 users (S4/S2/X1) and Z1 users who wish to use midi mode.
This update is a bug fix and stability update. The last few updates have addressed issues and brought issues. I think NI is suffering a kinda backlash because their updates used to bring new features and at a steady rate much more so that Serato or any other software. This plateaued last year but people still expect the same output and are critical when it doesn’t materialise.
There’s usually a good reason when NI go quiet or start shoring up the river banks.
I certainly agree that the grass isn’t always greener, Karlos.
That’s why, despite having fallen for Traktor in a big way, I still keep a foot on both platforms.
Both companies have their quirks, for sure.
As for updating, I always do it immediately; I trust that the beta testers will have found any show-stoppers.
Of course, I do a full clone of my system using SuperDuper before that, though… 
Is the metadata sync back with 2.6.8?
I upgraded last night. First thing traktor did on me after playing 3 songs was crash, and I don’t mean a stutter. I mean completely close down the application. I had nothing else running. Its actually the first time Traktor has ever done that to me. I was counting my blessing this was at home and not out.
I’ve lerbd never to update traaktor ubti the udte has been out for a month. Its nice to know exactly what to expect. If their cu of continue to increase with each update like it has I will be seeking a new DJ platform soon. 2.6.7 brought with it a 15mb ram and 20% CPU increase average on a 4 machibes we have in the house. Multi core processor support also causes it to crash one both our laptops running win7 .
I rolled back to 2.6.4. I’m not updating until they get the metadata sync back. TDJ and Traktor have been a disaster lately.
I just updated to 2.6.8 and am already seeing 10-15% more CPU load.
I had planned to use SDJ for my gig yesterday, but after reading these reports I fired up 2.6.8 for the first couple of hours.
I’m pleased to report no issues.
Then rebooted, hooked up my SX for the rest of the night, and had a crash with SDJ 1.6 for the first time ever! You win some, you lose some…
Just don’t upgrade to 2.6.8. Don’t say I didn’t warn you.
With 2.6.8 I had major problems. I also had the CPU jump described above (I never had any in the past, considering I have a quad-core MBP). I had problems with loops that would miss beats and go out of beatmatch (I generally don’t use sync, quantize, or snap). I had strange static once in a while. All kinds of mess with this version.
I did notice the looping issue would fix itself if I turned on Sync. Though that is rubbish and not a solution.
I have to give it to Native Instruments though. They backup everything, including the app for you automatically. It was super simple to roll back to 2.6.7. 2.6.7 is not perfect, but 2.6.8 is so bad I couldn’t even mix for fun let alone a gig with it.
Good luck
P.S. I even renamed my .TSI file to see if I started over with a new .TSI if it would get better. Nope. Same issue with loops skipping out of beat. At this point I went right to my backup of 2.6.7. Loaded it up and bam, problems were gone immediately.
Here’s my recommendation as an IT guy that’s been working in the industry for twenty years developing software:
give any release at least a month for people to find bugs and see if you can live with those bugs, because software by its very nature is going to have bugs. You’ll see all kinds of reports of the bugs in the first month or two, and you can then decide if you can live with those or not. The only reason IMO for anyone to update to a new software version when it first comes out is if a bug is fixed that leaves you completely dead in the water. And even in those situations, tread very carefully.
If you are back on 2.6.7 then I hope you are not using m4a files. For anyone using m4a files the above statement should be ignored. Don’t say I didn’t warn you.
As I asked the previous poster, where are you seeing the “CPU jump”, in Task/Activity Mon or in the Traktor header.
Having a Quad core isn’t gonna help. Traktor won’t make use of it.
Mac or Windows ? Have you optimised your laptop if it’s Win.
I don’t understand this point.
How can a loop “miss beats” a loop length is determined by the bpm that Traktor has detected. If the bpm is correct and the track has a steady bpm the loop will be perfect, it does not matter if sync or snap are enabled but if you want loops to loop on the beat then snap is essential.
If you turn sync on and a track loops perfectly then the bpm detection is correct thus your loops should be perfect without sync. Your point about engaging sync does not make any sense to me.
Are you using timecode or controller. How are you beatmatching? Manually without sync or snap on? If so and, if your bpms are correct and you are not using sync then it’s just down to your skill as a DJ to make 2 tracks loop in properly.
I’d like to see a clip of a loop “missing a beat”. I am lost as to how a loop can miss a beat..?
Did you check to see if all your settings were the same in 2.6.8?
Do you grid your tracks manually or use AutoGrids or no grids at all. I would imagine if you are not using sync that you do not grid your tracks.
This needs some clarification please.
First off, renaming a tsi will not change it. It’s still the same tsi just with another name. I trust you mean your user tsi which is just controller mappings? If you changed the name of the TraktorSettings.tsi Traktor will just create a new, empty one with the basic settings.
I don’t know how a tsi can make your loops “miss beats” unless you have borked your midi assignments. The TraktorSettings.tsi is comprised of the preferences and settings that you make within Traktors preferences dialog. If your tsi is corrupt you need to rebuild it which is why it is wise to save all your user created mappings separately as well as the whole tsi. This way you can add the ones that are not corrupt and rebuild the settings.tsi.
Did you make any changes apart from renaming your tsi in 2.6.8 ? because there were no changes made to Traktor from 2.6.6 to 2.6.8 that could affect loop functionality.