Traktor 2.5

[Michielygil]

I can't even install it since the installer says it can't detect the installation folder. When I open the service center to locate the installation folder however, it says it can't detect the stand alone application (and it really is there...)

Must be a sign of the gods then, I'll have a wait for the next version and do a complete install i guess.

[oliosky]

Another beta development release from NI that isn't ready, released to the public under the guise of a software update. Good to see things don't change. I envisage another 20+ pages of people griping about how buggy and unstable 2.5 is and the wailing "how can they do this to us!!????", then another few threads about how 2.5 ruined peoples gigs. Its all deja vu in here.

[rotebass]

I have no pity for anyone that installs a major update before a gig, software 101...

[oliosky]

I have no pity for anyone that installs a major update before a gig, software 101...

you really do suck up to NI alot don't you... Surely you can agree that NI's record with stable Traktor releases is atrocious?

[rdej47]

For the most part I've had great experiences with software updates. I think it can seem worse then it is just because there's such a concentration of people using the new software and discussing it.

[oliosky]

I guess I'm used to decent, generally major bug free updates from the days when I used Serato. Serato updates are light years better than Traktor. You could actually be confident downloading the serato beta versions and play out with them, which is a far cry from the PUBLIC release of TP2.5

[rotebass]

you really do suck up to NI alot don't you... Surely you can agree that NI's record with stable Traktor releases is atrocious?

Can you explain to me how exactly that was sucking up to NI? Name me one software company that releases a major update and then doesn't follow it with at least one bug fix, I bet you can't do it.

Look at Apple, Microsoft, Google, Adobe, every video game company in existence, every software company in existence. Look how long it took Apple to patch the battery meter when they released iOS 5.0. Look at every version of Windows that has ever been released.

They release a major update, bug reports come in, they patch it. Talk to anybody in software development, if they held off releases because they were worried about bugs then nothing would get done. Everybody knows this, you NEVER download a major release when it first becomes available and expect it to not have problems. Anybody that downloaded 2.5 and took it out to a gig did so knowing that they were playing the odds, if they ended up on the losing end, they get no pity from me.

So, if applying simple logic constitutes "sucking up to NI", then sure, guilty as charged

[oliosky]

I'm not talking about minimal issues or "one bug fix" with NI releases. Its usually an unstable clusterfuck with a release and the bugs aren't fixed all that quickly IMO.

I thought everyone just knew that NI are the kings of using a public release to beta test, so I guess i agree with having no pity for early adopters.

[rotebass]

I'm not talking about minimal issues or "one bug fix" with NI releases. Its usually an unstable clusterfuck that isn't fixed all that quickly.

Everybody with an iPhone 4S that had three hours of battery life thought that was an unstable clusterfuck too, shit happens.

Regardless you are only proving my point more, if it is usually an unstable clusterfuck that isn't fixed all that quickly, then what kind of idiot updates their software knowing this?

P.S. It's working quite fine for me

[oliosky]

:shrug: I just really don't get the whole "its a public 1st release so don't use it" defence of TP2.5. I don't really care that much TBH, I'll wait til the next release and hopefully the F1 sales have peaked and the the remix deck mapping is opened up.