This is the NI Forum thread for the ones wondering: http://www.native-instruments.com/forum/showpost.php?p=1026933&postcount=4
IMO it’s sad to see the people at NI heading this way, even with their own controllers (X1, Maschine). Looks like they are walking away from the idea that made them big. Hope this gets adressed with an (unlikely) update.
The whole thing is a sobering read to be honest. The remix deck mapping thing is the only real surprise, but you can’t blame us for hoping against hope that we’d hear something different than this:
The 2.5 update will have no relevant improvements in the domain of TRAKTORs MIDI mapping with the exception of a reworking of the names and organization of controls within the Controller Manager
A reorganization of controls and names might be helpful (though it’s mildly annoying to those of us who have learned what all the current names mean) but a consistent message has been expressed from users that we want better midi mapping controls and they’re pretty clearly not interested in providing that.
And of course there was this on variable beat grids: “There is currently no news on the implementation of this feature.” Sigh. Again, not surprising, but it doesn’t make anyone jump for joy, especially when all competing products have them and handle them well.
If I wasn’t so lazy I’d be taking a much closer look at Mixxx these days.
per device (well port really…) you can address 16 channels and within each channel 128 notes, 128 cc’s and 1 pitch bend (ignoring all the other messages that dont really apply to traktor). then the value/velocity of each message has 128 different options except for pitchbend that has 16256. so i’m pretty sure this is just NI being an ass.
i’ve started looking at it - and what i may want adding/changing (it is open source ofc…).
some cool stuff coming in this years “google summer of code” Mixxx Development Blog: Google Summer of Code 2012 Projects! the “key sync” could be interesting
i didn’t want to use it before as it has no effects builtin really but i’m now routing all my traktor audio into ableton - so that’s not such a biggie.
mixxx is getting some new spunky multi coloured waveforms in the next release too.
THIS is ASSSSSS!
Was really hoping to configure my APC80 to handle the Remix Decks.
BAH!!!
Instant FX it is then I guess.
SUX!!!
But then…I might just get the damn F1.
Well, bye bye x1 (and money 
) welcome f1.
I’m on this page. Those flashy RGBs looks great, and so will an F1 beside my X1. Traktor is still great software, best I’ve used, so I’m not too beat down about the inability to map those samples.
NI fails again.
Fortunately for them, the F1 was obviously the best controller for the Remix Decks anyway…so they won’t lose too many customers.
Fortunately for DJs, it might push more people towards Ableton, which is just plain better anyway.
I wonder how long it’s going to be before Traktor is as closed as Itch?
This is crap. NI development - 2 setps forward, 1 step back.
i like the look of the F1 but to have full control (easily) over all four slots you’d need two anyway - and can’t see me finding/forking out that sort of cash just for remix deck control any time soon. ableton live8 upgrade for me it is then 
now surely they’d be insane to not also allow that “Select Cell in Slot” control to be midi mapped? that’s all we need to have the same control (minus pretty colours) as the F1 since u can only play one sample per slot at a time anyway.
For you maybe… I think Traktor is far superior for DJ purposes having used both extensively.
It’s also a shame that Maschine users won’t be able to use the 16 pads to control the remix decks either, seems like a big opportunity missed in my opinion.
for straight dj’ing i don’t think there’s any argument that traktor is better for dynamically browsing a big track collection and chucking them in - but the remix decks weren’t going to be as good as what ableton can do anyway - i was just hoping they’d be “good enough” so that i wouldn’t want to use clips in ableton. i’ll stick with what i’ve been trying the last few days then - external mixing mode in traktor feeding into ableton so i can use vst effects there and also launch clips.
@zestoi - yes, I was referring to straight up A>B DJ’ing.
If you’re doing remix deck/ableton clip type of remixing/playing live then there’s probably much less to choose between the two.
I’m initially just going to get one F1 I think. That still gives me 16 slots, which is double what I have now. Then I’ll use the third deck as a track deck.
sure - that’s basically what i meant. personally i wouldn’t like to use ableton as a dj app - but i do want to be able to add clips of my own produced stuff, or full live remixes from my own stems and/or other stems over the top. the remix deck stuff should have been enough for me as opposed to synching ableton with traktor. i may still get an F1 sometime but would have preferred to be able to map something like one of my launchpads to control the remix decks.
guess we still don’t know for sure tho whether this “Select Sample X in Slot Y” control wont be available to be midi mapped tho.
I looked, it’s really not viable yet and has years to go.
Me too, I’ve been thinking of adding another x1 as well.
3 decks would have their own X1s and there’d be no need for hitting the Cue shift button
1 deck would be the F1 and the new Sample decks
i know very OT for here… but what areas in mixxx do think really have to be improved on. i’m thinking about seeing what i could fix/change in there - not looked at the official roadmap yet. for me it seems to use too much cpu and there’s too many reports of it crashing. beatgrids are quite simple but seem to work. quantized stuff in 1.11 seems ok. total lack of effects or vst support ofc isn’t good.
Really the speed thing, it seemed laggy and the whole thing had latency including the waveforms on a pretty decent laptop. No nudge button or anything to adjust beatgrids. Library takes forever the analyze. Lack of available skins to fit pretty standard monitor resolutions. It’s hard to explain but I just found using it awkward and everything had a delay.
cool sure. i couldn’t quite put my finger on what i didn’t like about it. you can adjust beatgrids in 1.11 - not sure about previous. it wasn’t obvious which button to press tho to do it - and moving the grids about seemed quite laggy and not very accurate. the mew multi coloured waveforms use more cpu than the old ones but do look nice. i hope more basic usability stuff is a prority but they seem to be more interested in new features than that. i may just have a go at messing with the code in my spare time and see what i come up with.