Traktor pro 2.6.7 Critical update !

"What's new:

Fixed an issue in version 2.6.6 that corrupts playlists containing Remix Sets or tracks when these are relocated
Fixed a bug in the search function that returns additional results not matching the query
Fix required the full deactivation of Metadata Sync with TRAKTOR DJ for this version



Please note:

We strongly recommend 2.6.6 users to update to this version to avoid potential data loss.
Version 2.6.6 has been withdrawn from Service Center and the Update Manager."

Jeeez NI .... really ?????? I know that there are challenges in any software development but lately ?
I'm so disappointed with the latest set of events since last year with the TRAKTOR DJ APP and Ipad Air, so much that I had to sell my traktor S2 MK2 because it simply does not work with my Ipad Air.

First I had to wait like 3 months just to get the update for the metadata sync, now disabled again , are you guys for real?

What happened to you? You used to be awesome. How did you lost it?

Sad ....

 

don't worry, give em two more weeks and you'll have 2.6.8 with the metadata sync back again.

traktor pro may be close to having the same amount of patches that windows xp had... time to start thinking about building a brand new platform from scratch, innit?

continuing with the analogy, if there's a new platform, better a windows 7 than a vista... but even better an osx rather than a windows...

i'm greatly surprised how it's still holding up and being quite "the reference in performance stability", after the nasty amount of patches, re-patches and stitches it may have in its guts.

 

Yeah, aren't there years and years of "legacy code" by now in the current version? When was the last true re-write of the software?

 

Why doesn't the Service Center show any updates? I mean not just 2.6.7 but for a long time now I have been updating TSP2 manually.

 

have you been in contact with support?

yes. we encountered a major issue that slipped through all nets. in 10 years i'm married to the firm we only had one other time we had such a big thing slipping. **** happens, but as you can see: even before you noticed the bug, there was already this update. so, this is not the time to hate. regarding your ipad issues, please contact the support (i dont have any mac devices so i'm not much of help now).

 

exactly.

 

nah osx and win 7 don't compare

 

My Fair friends I have been using traktor for a while now,and what I wanna know is why a well develop company as NI up to now cannot deliver a stable free of all major bugs version of traktor. Why all these updates all of a sudden come on guys you need to put your act together. So many other software are being updated out there. So please can I have One very good version of traktor to work with I know you can do it. It's just my thought.

 

I waited to upgrade to 2.6.6 and now I'll wait to upgrade to 2.6.7. I'm not doing beta testing for anybody unless they pay me or give me free software.

 

if you mean you're still using 2.6.5 it's ok. but if you're already using 2.6.6, i'd update if i were you, there's a nasty bug pretty well detailed.

i'm one of those that updates as soon as an update comes out, a guinea pig if you want, in fairness i'll say that so far the issue with 2.6.6 is a pretty rare thing. all other updates have gone well, at least for me. no major issues since a long, long time ago. although no major or breakthrough improvements either, anyway.

 

so should i not update?

 

Yeah, I'm still at 2.6.5 Didn't upgrade the last 2 rounds. I always wait to see what "new" bugs they roll out.

 

Have you ever heard of a company called Microsoft? The release things all the time as first versions that are quite buggy.

The problem with software development (I've been one for 20+ yars) is accommodating all the potential OS's, software that could be running on the computer, and with Traktor - you have a number of hardware drivers to support as well. It's not as easy as one would think and things will get lost between the cracks, even for the most experienced of software development houses.

IMO, NI did a good job of releasing something that fixed the issue quickly. Please be patient and give us software guys a break.

 

there will never be such a thing as a completely bug free software. no software in the world is bug free! however, major bugs that made it into a release i have seen exactly 2 times. IN TEN YEARS. that's an ok share i think.

why "all these updates"? well, back in the years there were 1 or 2 releases per year of traktor. you know what ppl were saying: why not update more often. now you get an update per quarter and now a very fast quickfix when it was needed. i think we're pretty ok here.

perfect? well, nobody is.

 

Not fixed, for example if I search in BPM the not existing 126 then the search results are 125, 123, 127, 124, 128 instead of not found/empty search result. Again If I search for the existing BPM 125 then the search results are 125, 123, 124.

 

historically traktor search has always returned exact and similar bpm results. i think this wasn't considered a bug.

the mentioned bug related to search, that has been resolved, is this one:

http://www.native-instruments.com/f...Search-returns-unexpected-results-since-2-6-6

 

I have a big problem now with 2.6.7. i just get a new Macbook PRO (last week) and cannot work with Traktor 2.6.7 because it craches every time i open it in the first few seconds...

I have to work with my old version of Traktor Scratch 1.2.7. which is working well.....

Anybody have the same issue ?

 

Process: Traktor [466]
Path: /Applications/Native Instruments/*/Traktor.app/Contents/MacOS/Traktor
Identifier: com.native-instruments.Traktor
Version: 2.6.7 [R337] (2.6.7 [R337], Copyright * 2014 Native Instruments)
Code Type: X86 (Native)
Parent Process: launchd [150]
Responsible: Traktor [466]
User ID: 501

Date/Time: 2014-01-20 13:42:41.778 -0500
OS Version: Mac OS X 10.9.1 (13B3116)
Report Version: 11
Anonymous UUID: 5B6A5216-9A65-9AA0-1420-B0FC7622C998


Crashed Thread: 25 BackgroundThread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called

 

I don’t think only searching in key-text is more important for users than searching in bpm in both cases users expect a serious results.

 

I'm highly apprehensive of any updates since the one before this wiped all of my playlists…and despite following all sorts of advice couldn't retrieve them….If it ain't broke don't update imo.