Los remix decks y la censura proteccionista de NI

Mus Musculus [Mµ] escribió:

te vendo un seat ibiza full equipe, pero el aire no tiene carga, el airbag sin explosivos, y el sensor de parquing sin avisador acustico o pantalla... oye que te lo vendo al mismo precio que si no tuviera nada!...

Alguien escribió:

"last week I fired off a deliberately provocative email to NI, designed to illicit a response about this obviously contentious matter. Here’s what I sent:

“Does this mean that to use the remix decks to their fullest capability, you’re forcing people to buy at least one Kontrol F1? You won’t be able to map other NI products, let alone 3rd party controllers to Remix Deck functions?
For argument’s sake, let’s say I own a MIDI Fighter Pro, APC40 or A&H K2 and want to map them to the Remix Deck functionality – you’re saying that you simply won’t allow this to happen? Or is it a limitation of the current controller manager? Or can current open protocols simply not handle the complexity of messaging so you need to do some fancy proprietary messaging?”

Oh I got a response alright. Sorry if I annoyed you NI, but this needed an answer. And essentially, the original forum post is correct, but doesn’t give the complete picture, something that we now have, thanks to a couple of detailed skype calls with the NI mothership.

Firstly the good news, there will be limited mapping ability for Remix Decks in Traktor v2.5 NI have also told me that more (rather than the expected less) functionality will be added in future versions of Traktor.

But right now in the upcoming v2.5, the interaction between Traktor and the F1 is currently hardcoded in a deliberately closed loop. This will allow NI to hone and perfect the workflow without impacting on anything else. Things are getting so complex now that a small change in one place can have a house of cards effect and break much more than it fixed. Thus the full Remix Deck functionality remains closed off to everything else except the F1.
For now that is.

Once NI are happy that the workflow functions as they want it to in the closed loop, they’ll open it up to mapping in the controller manager. This is no easy task, as it’ll require quite a bit of deconstruction of Traktor and the controller manager to reengineer relevant parts to work in an open manner."

Irwin J. Cespedes escribió:

Interesante, hace unos años para poner música y hacer enloquecer a la gente solo se necesitaban dos tornamesas y un mixer junto a sus audífonos y varios vinilos.

Milanozero escribió:

por otro lado decir que maschine es un soft/hard..totalmente independiente a traktor..

Milanozero escribió:

y con tyraktor a jugar con tracks..