Carl Cox Crash & Burn on traktor S8

Painful... Anyone know if he is still using an S8 after this crash?

 

wooooops... i guess we're all humans when challenged by traktor technology...

 

#futureofdjing

 

somebody should tell him to open a support ticket

 

He did and had obviously upgraded to the most recent version as recommended :-D

 

At least he is using the s8, there were a whole lot of naysayers replying over at djtt site, saying he only made a promo, Traktor is a major software and for me the most promising, many would say fanboy or whatever but my progression has only been software.
Traktor seems to be the best way to create and put my own twist into things. So finally he crashed, I think in general I haven't seen a crash for a while.
Strange thing is, this makes me think of the Superbowl, that was a well done mix and show for halftime, but premade and rehearsed, it had to be. The point is many of us like to see someone show talent, read a crowd, and create right in front of us, that is what made me like a live dj and shows. To me that is the most impressive, but with that comes a crash every now and then.

So Carl if you can hear me, I still say "much respect".

 

weeell yes you're right, and provide valid points. i havent seen a crash live in my system for years, until recently, unortunately, and it's been solved, fortunately, by just reinstalling both traktor and osx.

i should say i would also use the S8 if i was carl. i'm about to speculate here but i'd bet he's receiving money (and probably quite a bite) from both the gig itself and NI for using their hw.

most probably his crash was due to a poorly maintained computer, and/or because of not following the optimisation tips, disabling the wifi and bluetooth... or using corrupted files... or using a cheap usb cable... ah, who cares. maybe the intern who watches over his music collection got sloppy.

i was having a good moment seeing these things can happen to everyone. at least he is playing faithfully (i.e. not pre-recorded) and for his sake he's going to have all the force of NI worried and looking into his issues.

bottom line: respect, carl, for an outstanding career, of course. that said, welcome to the real world. sorry to see your computer crashed mid-set, but let's be fair. most probably the problem was not traktor.

 

Based on what exactly?

A lot of users are reporting issues with the S8 revisions of Traktor and a lot (like myself) are avoiding it altogether because of file compatibility issues. It's a disaster of a release.

The bottom line is regardless of what caused the crash it looks bad for NI because if I was in the market for DJ software and controller and saw such a high profile crash so early in the lifespan of the controller I'd avoid buying it until I had a much better idea it was reliable.

 

i was being both sarcastic and truthful, based on my experience, however bipolar this may sound.

i have actually had around 6 years of trouble free operation (in terms of crashes i mean) with traktor, all updates applied on day 1, and all OS updates applied on day 1 as well. yes, call me rebel.

but when **** hits the fan and you get in touch with support, you'll agree with me, the reply is always in the sense of, traktor's not the problem, it's something else unintentionally interacting with it, something got corrupted, etc.

which, to be fair again, can happen to any software application. so, in ideal circumstances, traktor is rock solid. however, but there are a lot of variables left out which can make this statement become appear to be false.

i, for one, still put my hands over my head whenever i hear in 2015 that somebody suggests, in case of trouble, to turn off the wifi. or when i read that someone has to follow "optimisation tips". i find it amazing that app developers still haven't found a way around these kind of issues to prevent their apps from crashing.

again in speculation mode but, best of all this, is that whatever made carl's computer crash, will surely be looked at with utmost care and addressed as soon as possible. worst of it all, is that there's a difference in NI's treatment to carl compared to the rest of people using traktor, having whatever problem and finding their issues are at the bottom of the bug tracker.

 

Sorry mate but I believe that someone who was making for his living by djing in past few decades knows how to prepare his computer for djing, how to maintain his library, how to find corrupted files, which cable to use and how to switch off the wifi ;-)
I believe that most people would not care about that it did crashed if there wasn't the whole situation around - you know - that s8, that poorly maintained traktor and the person wasn't Cox who was chosen as the face of S8, who is supposed to sell this crap to the masses... Thats why its so ridiculous... ;-)
But the one thing on the video is sooo true - noone can now say that he did not knew what he is buying and Cox absolutely honestly presented the Traktor as it currently is.. :-D

 

Gotta love Carl...he just laughs it off. When you got skills and a fan base like him its easy too do.

For the average Traktor DJ, a crash like that in front of a live audience can be very costly.

Here the full video of his entire set.

http://www.be-at.tv/brands/blue-parrot/bpm-2015-intec-digital/carl-cox

Great set and pretty cool video despite the crash toward the end. Love how happy he is when he is DJing.

 

So last Sunday I did my yearly gig with Carl Cox and Eric Powell where I supply production for their "Mobile Disco" winery gig. I spoke to Carl about the S8 and the issues that have come up and he said that they have been solved with the latest software update, and that he used it at his club gig last Friday without issues.

 

Awesome gig you got there Frankle. When you say latest...do you mean 2.7.3?.. i would imagine a guy like Carl would get special treatment so perhaps its 2.7.4 ? I really hope 2.7.4 is going to be out and fixes all of the major issues.

 

His laptop (15" MBP Retina) is running Yosemite and 2.7.3 at the moment so I'm guessing that he's reported faults with earlier 2.7.x versions and they've fixed them ...

And yes, an awesome gig!

https://www.facebook.com/video.php?v=10152640836032644

 

Frankle hate to see carl or anyone crash and burn... i have tested 2.7.3 on the the same laptop Carl is using and it crashed while trying to access explorer Node folders as well as the archive playlist other have reported the same problem on the board. If you have a direct connection to Carl I would warn him about this.

I opened a TT and support says that can duplicate and that they think my music files are corrupt. I do not think this is the case as this crash do not happen on 2.6.8 with the same files\folders.

I believe the S8 does not work on 2.6.8 but from my experience its the most stable. 2.7.3 maybe ok but should be used with caution and tested on the explorer and archive crash issue.

 

I'll have a chance to catch up with him in a few weeks so I'll ask him about it then.

I myself have moved back to 2.6.8 because after trying the S8 it doesn't suit my workflow, although last night and the night before I had a pause/stutter happen about 3 hours in.

Taken from the Console Log:

21/02/2015 1:53:23.000 am kernel[0]: IOAudioStream[0xffffff80163bf000]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (9abf,378)->(9ac0,7ac).

21/02/2015 1:53:23.000 am kernel[0]: IOAudioStream[0xffffff80163bf000]::clipIfNecessary() - adjusting clipped position to (9ac0,378)

Thoughts? I probably should open up a separate thread

 

well, **** happens. sovereign reaction!

i've had a turntable die midway during my set once. and in +10yrs with traktor i've had 2 crashes. one was back in the T3 era, with a beta version. super reproducable and fixed for the release version. the other is only a few weeks/months ago and yes, disabling wifi (i have a hardware switch for that on my laptop) was what i forgot and what made it happen. my computer is fairly old and edgy regarding the specs and not disabling wifi makes a massive difference here.

 

traktor works best if you un-map everything todo with the browser and use the mouse or touch pads instead

 

you really think so?
i always panic that i accidentally click on something unwanted... ^^ i love to have everything browser related on hotkeys (be it the keyboard or a controller).

 

the browser is always refreshing and going to random folders if you have it mapped, so its probably some midi buffer overflow for the browser that makes it crash more then any other bug