MBP - Traktor 1.2.6 UI freezes

MBP - Traktor 1.2.6 UI freezes

I took my setup round to a friends party at the weekend and all was well for a while, but then Traktor started to freeze and stutter. Audio was fine but MIDI and visuals didn’t work. I’d installed My friend’s 2 Kontrol X1s from the supplied CD before we started. The freeze happened on two occasions.

My set up was as follows:
13 inch MBP

Front USB: Audio 8 with 2x Faderfox DX2s via MIDI cable.
Rear USB: Powered USB hub with 2x X1s, USB snake light and small mouse.

There were no drives or anything else plugged in. The only software running other than Traktor was Twitt3r_DJ (the first time it froze, not the second).

Anyone got any ideas?

What was your latency set at? Where you on wifi? That might have had something to do with it it although I run on wifi all the time and have never had a problem. I hear of others who have had problems though.

Latency was set to 4ms. I tried setting to 11ms but the same thing happened. Also, wifi was disabled the second time it happened.

Anyone?

I sure i read over at NI that the USB port nearest to the power cable draws the most power and is more suitable for the Audio 8 and that the other port shares power with something else.

Im sure i read that..? Could be wrong but worth a punt. Worth googling that to see if im not imaging it.

Sounds more like a software problem than a hardware… Was your laptop over heating?

What I thought it might be was the X1 driver. I’ve upgraded that and will test.

I’ve had similar issues and only run VCI-100 SE & Audio 2… I have an external HDD. I connect them to my pc tower (not the laptop) for practice and it freezes when I use fx [jogwheel & volume fader] Usually happens when I use them simultaneously. Its really random but when it does happen once it is bound to occur 2 or 3 more times right after. VCI-100 & fx freeze but Traktor does not: audio keeps going fine and can adjust with computer cursor/mousepad.
Hardware or VCI firmware issue perhaps?
Once VCI is restarted, everything is back to normal …

Not really looking for a fix… just informing you of a similar issue. It’s random and maybe that new firmware can be a fix [might get the upgrade kit to try]