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.
:(
Printable View
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..
http://www.virginmedia.com/images/starship-troopers.jpg
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.Quote:
Originally Posted by olafmol
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??;)Quote:
Originally Posted by claudek
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.1Quote:
Originally Posted by slyooney
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.Quote:
Originally Posted by Jack Bastard
Maybe it's just me and Slooney but I've never had any problems with Traktor Pro.
What's your setup Andrew?
Macbook 2.4 c2d. 2 gb ram. firebox. vci-100. touch osc. i only mix with two decks. would that make it more stable?
Quote:
Originally Posted by JesC
hahahah , starship troopers!!! nice one
Yes, but he had some stipulations for how the money could be spent, and Richie Hawtin showed up in a gold limo to personally refuse the offer.Quote:
Originally Posted by JesC
Ah, I'm on XP here. Looks like it's only an issue for Tpro on Windows.Quote:
Originally Posted by Andrew Loay
Damn Richie Rich, there he goes f-en things up for the little guys. What can you do? Damn Old' Boys ClubsQuote:
Originally Posted by steveboyett
I tested TPRO 1.02 with the vci 100 SE during more than 5 hours (rig below) today! it works flawlessly.
Everything works fine (except Fader fx but I'm still on 1.4 tsi - I'll give a try to 1.6 beta tomorow evening)
No bug at all, no freeze, the cpu usage meter stand always below 10 %
my system run @ 7ms latency and I'm pretty sure I can go lower (core audio buffers - ie asio driver on PC)
The mapping is absolutely amazing and very intuitive. (almost) everything is on the place we expect it to be.
Well done and thank you Ean & DJTT team ! It's gonna rock on saturday night (first gig with it)
Just to clarify the freeze bug starts to hapeen when you install the latest update Traktor Pro 1.1.1.
Traktor Pro 1.02 does not have this bug.
I found 1.0.2 to be exactly as Slyooney says above.
:)
I want to help folks out with their TPro issues on DJTT and the NI forums, but honestly I feel like the odd man out sometimes in that I have no freezes or crashes ever. Seriously. I experience the documented TPro bugs like everyone else (keylock, soft takeover, etc) but otherwise the software is rock solid for me, and I really enjoy using it. No second thoughts on using it live at all. (Except in places where there is no good grounding or three prong outlets. Electrical spikes have definitely frozen my computer before - the last time it was a space heater, lol!)
When it comes to problems and freezes, (and I hope this doesn't sound like a jerk - this may be a completely different thread), I'm not always confident that people are making a distinction between the behavior they expect, what is actually programmed into the tsi, understanding the various settings within Traktor, and lastly, any bugs that actually exist in the program.
It's one thing if your system locks completely (ie, can't quit the program). If some functions stop working in the program while others keep working, it is most likely a tsi issue
I experience exact the same situation but with version 1.0.2Quote:
Originally Posted by Jack Bastard
Dont know what to do. Sometimes it freezes especially when i switch from chained mode to advanced mode and vice versa. anything I can do to solve this problem?
Maybe change the latency from 5.5ms to 7-12ms?
Just sitting and having a mix and it did it again, this time when cycling through the fx on advanced mode using the 1.6tsi.
I'm meant to be gigging next weekend and I'm thinking cds are the way to go for the time being.
Mr. SuperNoOb here:
Understanding fully that they are not the same thing, I've been looking back-and-forth between Ableton Live and TP. I'm on the mac platform and after looking at this thread again from the beginning its looking like mostly windoze-related problems.
Is that so?
G.
Windoze:DQuote:
Originally Posted by loslosbaby
After reading through this thread, nobody really says wether its Windows or Mac's that are having the issues
Ahem.Quote:
Originally Posted by Jack Bastard
:)
It happens when I'm cycling through effects on Ean's 1.6 tsi (ie holding down the far left effect button and moving the knob above it).
Massive pain in the arse.
I only ever get crashes when I tick the midi out box. with it un-ticked it has never crashed. On a Dell Inspiron with XP.
Safe Joe, I'll give it a go now.
So far so good Joe. I'm going to report that on the NI board now.
Is it correct if I assume that we dont need the midi out box when working with the VCI 100?Quote:
Originally Posted by Jo3
It sends info about LED settings, but that's it. Everything should still work in the same way, just without the visual feedback of light changes.