Has anyone else had problems with new Tpro?
Using VCI100SE, audio kontrol, dell 9400, 1.6TSI and now when I select effects I get crashes - audio freezes and Traktor won’t shut down until I disconnect the VCI.
It’s all been fine till this update.
![]()
Has anyone else had problems with new Tpro?
Using VCI100SE, audio kontrol, dell 9400, 1.6TSI and now when I select effects I get crashes - audio freezes and Traktor won’t shut down until I disconnect the VCI.
It’s all been fine till this update.
![]()
Sounds like a bug inside traktor and nothing to do with the SE.
Have you looked at the NI forums? TPro has more bugs than the bottom of an Orkin man’s shoe.
Damn Traktor bugs, that sucks that you having problems with T-Pro, I havent had any but I wouldnt take my chances playing live..
Yeah, the bugs are pretty bad at the moment. Had a live crash early-mid night last week, was not fun at all. Luckily my partner was pretty quick on the draw, but that sort of thing can unnerve you for the rest of the night.
I’ve been having some trouble using the Korg nanoPAD.
Touching the xy pad sometimes seems to make the controller stop working until I restart Traktor Pro. ![]()
very annoying!
I was djing at a gig the other night and my tk pro like froze up so then i had to use traktor 3 le for the rest of the gig
I have been experiencing audio lockups as well, since upgrading to Traktor Pro 1.1.1.
I posted about it in the other thread. Ticket filed with support.
Wow it has more problems than todays economy and that says a lot
I thought Obama said today during his unoffical state of the union address, that he was going to bail out NI and have a fix for traktor asap.
Yeah, I bought Pro in Oct 2008 but won’t gig out with it, sticking with Traktor non-pro until they sort out the problems.
woops, it seems NI has some major QA issues on the TP team… the fact that it took so long to simply add 14bits midi support, and even more the fact that all kinds of stupid bugs came up that weren’t there in the first place shows me they don’t have a decent continuous build and automated unit testing setup in place, which is a huge issue for professional software development, as we all can see now …
That’s not the half of it, either. Frustrated users continuously crank out new forum threads on what’s wrong, some other users are (rightfully) complaining that the forum threads are evolving into bash/flame NI parties (when the frustrated users need to (rightfully) vent). Even the moderators are taking some of those frustrations as personal digs against themselves which has resulted in at least one accusation of censoring when a thread becomes locked.
We need an intervention. :eek:
I am really surprised how buggy and imperfect 1.1.1 is.
I mean all this time and beta tests and final testing stages and makes me wonder how many people are on their beta testing team..? Maybe 5?
I’m thinking of just going back to Traktor 3.4
From what I’ve gathered, it seems that the beta testers have caught alot of the issues we are experiencing.
The problem seems to be the developers don’t immediately fix the issues when caught, they instead mark them to be fixed on the next upcoming release.
Just a flag. I started yesterday with TPro 1.02.. Doesnt seems so buggy for the moment… I’ll give a deeper try tonight in order to be sure It won’t crash on saturday night
With everything i have heard from the NI forum and comments on our forum i have been holding off going on to TPRO for sometime, but to be honest i think im going to stick with 3.4 till everything is sorted so 2020??![]()
I was gigging with 1.0.2 since it came out and had no issues at all. This intermittent crashing with the midi devices is a new feature in 1.1.1
Don’t update!
Or if you have the option of a second computer, I would use that to test out 1.1.1 before installing it on your performance machine.
Maybe it’s just me and Slooney but I’ve never had any problems with Traktor Pro.