Mapping the Remix Decks in Traktor 2.5?

Remix Deck ScreenshotWelcome to the longest article that I ever wrote for my website. Yes, the Traktor Bible is several hundred pages but an article with 10 pages is quite long for a blog.

The simple reason for the length is that I want to provide a fact-based and well-balanced personal view to the remix deck mappability question. Make some time, pull up a comfy chair and take a read.

Here we go.

 

Content

Never has there seemed to be as much negative publicity regarding the launch of a new version of Traktor as there has been for Traktor 2.5 and the new Kontrol F1 controller.

Damage Control

Quite a few users in various forums have remarked that the price for Kontrol F1 is too high. Others have expressed concern that despite already owning a Traktor license they will recieve another if they buy the F1. And they cannot resell the new license as this would violate the Native Instruments License Agreement. In other words: these users would want to buy the controller as hardware-only, and then for a lower price.

Announcement Kontrol F1

Since the product announcement of Traktor 2.5 and Kontrol F1 on March 14, 2012 it was clear, although possible quite cryptic, that Kontrol F1 is the "only hardware for controlling ... Remix Decks". Then, at the beginning of May 2012, an article covering the non-mapability of the remix decks published by the colleagues from DJ Techtools caused quite a stir. Shortly after the initial release this posting was updated, corrected and revised - apparently after some intense communication between Native Instruments and DJTT.

Fact is: The Traktor 2.5.0 release does not allow users to map the new remix decks features to a controller of your choice. But, Native Instruments have promised, that once they have implemented improvements in the Controller Manager, they will make the features mappable for other controllers as well.

 

Why are the remix decks not mappable?

The whole discussion about the mappability of the new remix decks features gets interesting when we try to find an answer to the question, WHY the features aren't mappable at all. Native Instruments says in some official statements that the high level of integration between Traktor 2.5 and Kontrol F1 is their main reason. Here are some quotes:

Jim Mazur, F1 Project Lead at Native Instruments:
"This was a very conscious decision to focus on integrating the F1 perfectly." 1
Everybody who takes a closer look at the feature set of the remix decks and its integration with Kontrol F1 will see, that this integration is seamless.

Jim Mazur, F1 Project Lead at Native Instruments:
"We basically decided it would not be possible to do this in an open fashion, and really nail the nuances that we really wanted to go into with the F1… ." 1

Changing the playback parameters of individual samples requires a sequence of several steps when using the F1: First the parameter that you wish to change (for example Gain) needs to be activated. Then you must select the sample you wish to change. Then you change the actual parameter and finally deactivate the parameter setting mode. Everybody who ever made their own Traktor mappings can see, how complex the process. Using the current mapping architecture to provide a similar access to the remix deck features can can only be done - if at all - if you try really hard.

Jim Mazur, F1 Project Lead at Native Instruments:
"The last thing we want is any stability issues because we tried to do too much." 1

No hardware or software manufacturer wants any stability issues. But, what does "because we tried to do too much" mean. Does it mean that it would have been to risky to implement a new and better controller manager in time for the scheduled release date of Traktor 2.5? Or does it mean that it would have been too much to provide only some, but essential playback commands for the remix decks?

Friedemann Becker, Senior Product Designer at Native Instruments replied to the question, whether there will be an update for controller manager with new templates for Maschine/Maschine Mikro:
"You probably want to assign the 16 pads of the Maschine hardware to the 16 cells of the Remix Decks. Unfortunately, this will not be possible. The reason is that the depth of integration between the F1 hardware and Remix Deck exceeds what is possible through regular MIDI mapping in the Controller Manager." 2

This answer suggests, that the deep integration between the F1 hardware and the remix decks makes it impossible to provide any mappable controls at all. In this generality I cannot believe this. This article shall show, why I think that the basic commands allowing a Prepare & Play workflow could have been available now, in Traktor 2.5.

 

The 3 Layer Architecture of the Remix Decks

On first sight the remix decks look similar to what we know from the sample decks in previous Traktor versions. However, the architecture of the remix decks is quite different. The remix decks use a 3 layer model.

  • Features on the Deck layer
  • Features on the Sample Slot layer
  • Features on the Grid Cell layer

The Deck layer: What can be done?

Other than the sample decks from previous Traktor versions, the new remix decks offer some of the features that were formerly only available in the track decks. The features on the deck layer affect all samples that are currently playing in the slots.

Remix-Decks, Deck Layer

A remix deck can act as tempo master, something that a sample deck could not be. If the remix deck is the tempo slave, then the complete deck, i.e. all currently playing slots, can be synced to the current tempo master by using the SYNC button.The remix deck behaves here like you know it from the track decks.

The remix deck has a phase meter showing the phase of the deck in relation to the tempo master. And, as with the track decks, you can use the tempo bend buttons to nudge the remix deck slots.

Below the sample grid you see the standard transport controls (Play, CUE, CUP) and the loop control: all four slots can be looped at the same time. Furthermore, the complete remix deck can be controlled via timecode.

Mappingbefehle Deck Common

The fact, that a remix deck has common properties with a track deck, is reflected in the menu tree of the mapping commands:

  • All commands that can be used for track decks and for remix decks can be found in the node Deck Common. (There is one little bug in the Deck Common menu: Analyze Loaded Track should not be in Deck Common but in Track Deck, as you cannot use it for the remix decks.)
  • All track deck only commands can be found in the node Track Deck.
  • The remix deck commands can be found in the Remix Deck node. (More information about the remix deck commands can be found below.)

Then we have the Remix Sets. A remix set is a container that stores all 64 samples, that are currently loaded in a remix deck. The playback parameters of the samples are stored in the remix set as wel. You can save a self-made remix set and then load the complete set with one button (same as if you would load a track into a track deck). The remix sets are a huge step forward.

And, the remix set are also useful for Traktor users who plan not to buy the F1, or who are waiting for the controller manager update that allows users to map the remix decks to their controller of choice: They can use the remix set feature to load and control the samples in the first row of the sample grid already now. Traktor 2.5 provides one mapping command to save a remix set, and another one to save it.

Strictly speaking there would have been no need for a distinctive command to load a remix set, as the command Deck Common | Load Selected loads a track into a track deck and a remix set into a remix deck.

 

The Deck Layer: What is missing?

Next to the features that are common with the track decks, there are some special properties provided for the remix decks.

  • The quantize setting (on/off)
  • The quantize value (14 beat to 32 beats)
  • The base BPM of the deck
  • The source for capture actions

Fehlende Mappingbefehle auf Deck-Ebene

It seems that the first three features could easily have been made available within the current architecture of the controller manager: Traktor has plenty of On/Off commands; a mapping command for setting the quantize value is no more difficult to implement than one that sets the loop length; BPM values can already be set for the Master Clock and the track: why not for the base BPM of a remix deck?

More effort would need to be done for a mapping command that sets the capturing source. Such a command would only make sense when the functionality of the currently separate copy command (Slot Capture from Deck, Slot Capture from Loop Recorder) would be combined. Then a more general capture command would use the prior selected source.

All in all my conclusion is, that neither the good integration of remix decks and F1, nor stability issues could be a serious reason not to provide the basic commands on the deck layer in the next version of Traktor.

 


The Sample Slot layer: What can be done?

The sample slot layer offers the most mappable features. This come as no surprise, as the sample slots were already available in the sample decks from previous Traktor versions. Here is what you can map:

Remix-Decks, Slots/Player

The following table shows all sample deck mapping commands from Traktor 2.1.3 and their equivalent in Traktor 2.5 (if the mapping command is still availalbe in Traktor 2.5.0).

Traktor 2.1.3Traktor 2.5.0
Deck PlayDeck Play [1]
Load from ListSlot Load from List
Load from DeckSlot Capture from Deck
Slot Play Mode [2]Legacy | Play Mode All Slots
UnloadLegacy | Slot Unload
Save SampleREMOVED [3]
GainREMOVED [4]
VolumeSlot Volume Adjust
Filter On/OffSlot Filter on
Filter AmountSlot Filter Adjust
Seek PositionREMOVED [5]
Play PrimarySlot Capture/Trigger/Mute
Group PlayLegacy | Play All Slots
Group TriggerLegacy | Trigger All Slots
Mute/UnmuteSlot Mute On
Play SecondarySlot Stop/Delete/Load from List
RetriggerSlot Retrigger
Retrigger PlaySlot Retrigger Play
Copy from Loop RecorderLegacy | Slot Capture from Loop Recorder
Copy From SlotLegacy | Slot Copy from Slot
Slot Play Mode [2]Slot Play Mode
Slot Size x2Legacy | Slot Size x2
Slot Size /2Legacy | Slot Size /2
Slot Size ResetLegacy | Slot Size Reset
Slot SizeREMOVED | Slot Size Adjust
Phase SyncREMOVED [6]
FX EnableSlot FX On
Monitor CueSlot Monitor ON
Key LockSlot Keylock On
Tempo BendREMOVED [7]
Slot Punch On [8], NEW

Notes:

[1] Deck Play is only available in mappings imported or converted from Traktor 2.1.x. You cannot add Deck Play in Traktor 2.5. Use Slot Retrigger Play instead.

[2] Due to a little bug the command Slot Play Mode exists twice in Traktor 2.1.x, but with different functionalities. One command switched the play mode for one slot between Loop/One-shot, the other one switched all slots. This bug was repaired in Traktor 2.5.0 and the commands now have unique names.

[3] You can no longer save individual samples. However, a captured sample is saved automatically when you play it three times. And, you can save the remix set now; this saves all captured samples as well.

[4] In Traktor 2.5 the Gain value is no longer a property of a sample slot, but a cell property. It is no longer possible to map it; however, you can use the Gain knob in the advanced panel to change the Gain of the selected cell.

[5] Seek Position can no longer be mapped for individual slots, but only for the complete remix deck. I regret this change, as I have used the Out command Seek Position to outpout the current playback position of all slots in a Lemur mapping for the iPad. Perhaps this is only a rare use case.

[6] In Traktor 2.1.x you could use Phase Sync to synchronize the phase of a sample to the phase of the tempomaster. Synchronisation of the new remix decks works slightly differently. The remix deck slots do not use the global tempomaster as reference, but the timeline of the remix decks. And the remix decks timeline then uses the global tempomaster as reference.

[7] Tempo Bend is no longer available for individual slots. Alternatively you can use Deck Common/Tempo Bend to pitchbend all playing slots. Additionally, you can use the Nudge feature of the sample cells (but this is available only with the F1 and has no UI element).

[8]  This is the only new command for the sample slots. It is used to enable/disable the Punch mode for the slot.

 

 

The GRID/CELL LAYER – HERE (ALMOST) NOTHING CAN BE MAPPED!

The sample grid of the remix decks has four pages, each page has 16 cells, so in total you can use 64 samples in one remix deck. You can play one sample per column at a time; the playing sample is loaded in the slot player.

This section gives a quick overview of the feature set of the remix deck cells and tries to find an answer to the question what basic features one would need to fire all samples in a remix deck.

Remix-Deck, Zellmatrix

 

Starting Samples

Even the basic action of firing one of the 64 samples cannot be mapped. And this would only need two mapping commands:

  • Grid Page Selector  This simple command would be used to switch between the four pages of the cell grid. The command should support interaction modes Direct, Inc, and Dec. The functionality of such a command already exists internally in Traktor, as you can trigger this action by either clicking the page indicators at the left side of the grid, or by using the encoder on the F1.
    I cannot see why it would be difficult to provide such a command.
  • Cell Play/Trigger  This would be the one and only command needed to launch one of the samples. The command should consider the currently selected page. Then in the Assignment list one would need to select the remix deck and one of the 16 pads. There are some other places in controller manager with extremly long lists (like the one to select the MIDI note), but they are cumbersome. A menu with 16 subentries should be easy to handle.
    Starting a cell can be done by clicking with the mouse. Why not with a simple mapping command?

You can assign one of 16 pre-defined colors to each sample. In order to be able to use the color information with controllers having colored pads, one would need an Out command like Cell Color with a controller range from 0 to 16 (0 for off = no sample loaded, and 1 to 16 for the 16 different colors). Combined with a command/modifier condition like Cell State (paused, triggered, playing) one could set the intensity of the LED and/or let it blink (if the controller supports it).

 

Playback Parameters

Each cell (=sample) in the grid had several properties and playback parameters. All can be set with the F1, some of them can be set in the GUI or with a mapping command. The following list briefly describes the parameters and properties. The text in parentheses tells, if the property can be set in the Traktor user interface (GUI), on the F1 or via a mapping command (MAP). If a mapping command is available it affects the sample currently loaded in the slot player only.

  • Sample Type (GUI/F1/MAP) Corresponds to the "old" Slot Play Mode command; is used to mark the sample as loop or as one-shot sample.
  • Trigger Type (GUI/F1/MAP) Sets the Trigger Type for a sample to Latch or Gate. (In Latch mode pressing the pad triggers the sample; when the pad is released the sample keeps playing until the end (one-shot) or until its stopped. In Gate mode the sample plays for as long as the pad is pressed).
  • Pitch (GUI/F1) Allows changing the key 12 semitones up or down. The key change is audible only if the keylock is engaged on the sample slot.
  • Gain (GUI/F1) Allows you to change the Gain value of a sample.
  • BPM (GUI/F1) Allows you to change the BPM of a sample.
  • Start Offset (GUI/F1) Allows you to adjust the start offset of a sample in steps of 1/16th note.
  • Sample Nudge (F1) Allows you to fine-adjust the start offset.
  • Sample Color (GUI/F1) You can assign one of 16 pre-defined colors to each sample.
  • Playback Direction (GUI/F1) You can change the playback direction (forward, backwards) for each sample temporarily or permanently. If you change the playback direction permanently, the setting is stored in the remix set.
  • Sync (GUI/F1) Configures whether the sample playback shall be in sync to the tempo of the remix deck or not.
  • Playback Speed (F1) The playback speed can be halfed/doubled without changing the BPM setting of the sample. Can be simulated by using the buttons BMP/2 and BPMx2 in the Edit panel of the remix decks.
  • Sample Size (F1/MAP) The size of a sample can be stepwise halved or doubled. This sample slot functionality is the same as in the sample decks of the previous versions (Slot Size x2, Slot Size /2, and Slot Size Reset.

Making each of these properties mappable shouldn't be too difficult. However, doing it in a way that all settings can be easily mapped to any other controller with the same limited number of controls that the F1 has, would be quite complicated if it would be possible at all. Add the commands to capture, copy, delete, and move samples on top of that.

But: Maybe it would not be necessary to have all these features available on your own controller while DJing. The remix decks are so feature-rich that not all features can be accessed very quickly. And with very quickly I mean by one button or one encoder. This is also true when using the F1.

This leads to the question if a simple "Prepare&Play" workflow could be the perfect method to use the remix decks for all users who just want to fire samples.

 

"Prepare-and-Play"-Workflow

The simplest way to use the remix decks can be described as "Prepare-and-Play". In this workflow you would prepare some remix sets with all the samples you want to use at home. And then, during a gig, use the remix decks as a very convient way to launch your samples.

As described above, most of the cell parameters can be set in the UI of the remix decks. For the properties marked with GUI you wouldn't even need a Kontrol F1, but could easily just use the mouse instead. Maybe using the F1 would be more comfortable. However, if the only thing you want to do is fire samples, the F1 is total overkill. Any other controller could be used for this purpose.

 

Having always full control

On the other hand, if you wish to have always control over any properties and features of the remix decks all the time, the F1 is a good choice (and the only choice you have).

Even though this was the longest article I ever written for traktorbible.com, I could only give a brief impression of the remix decks and Kontrol F1. I would recommend that you read the F1 manual which is installed with Traktor 2.5. You will get an even better idea of what the remix decks offer.

And then decide, whether you want to invest into the F1 or if you want to wait until Native Instruments opens the remix decks for use with other controllers.

 

My conclusion

The most important and basic features of the remix decks should be easy to implement with the current architecture of the controller manager.

Maybe we don't get all features with the next update, but hopefully we get at least some of them. Native Instruments has promised, but didn't mention a time frame. Getting some in Traktor 2.5.1 would be great!


Sources

X1 Traktor's 2.5 Remix Decks will have Limited Controller Function.. For Now (Updated)
on DJ Techtools

X2 Traktor on the Record, April 24, 2012, Native Instruments Forum

 

Author: Rainer G Haselier
Last Update: May 25, 2012

Share

23 Comments

Mr.Aybar
wrote on May 26, 2012 at 04:48
They need to fix this fast!!!!!! An update is mandatory there are too many bugs in this version i may rollback until some of these features are fixed!!!!!
 
bbt
wrote on May 26, 2012 at 13:39

another week of work instead of an early release might have allowed for some mapping implementation?


 


i can sympathize though with the complexity of what they are releasing. i hope they open it up and give us a chance to muddle through making our own attempts to map some remix deck functions to the various controllers in use.


 


NI software/hardware is complex and expensive and that means they have standards to maintain. thank you for this article highlighting the interests and concerns of a large number of Traktor users with regard to the new 2.5.

 
Ingo van Lakum
wrote on May 26, 2012 at 23:39
Super Artikel. Ein F1 kommt für mich vorerst nicht in Frage... Danke Rainer..
 
Herbapa
wrote on May 27, 2012 at 19:09
Danke für diesen Artikel..ich kann noch anfügen, dass ich sicher bin dass Native Instruments absichtlich die Mapping-Befehle unterschlägt..Habe gestern stundenlang allerlei Mapping-Kombinationen ausprobiert, aber es ist unmöglich, ein Mapping hinzukriegen, womit man die Remix-Decks einigermassen vernünftig steuern kann. Nimmt man z.B. Retrigger Play, so kann man die Slots meist nicht mehr stoppen.
Es ist schade, ich kenne dieses gebahren aus dem Aufzugs-Sektor, da wird die Elektronische Steuerung schon seit Jahren möglichst kompliziert gestaltet, um der Konkurenz das Leben schwer zu machen..
Ich meine aber, wer ein gutes Produkt hat, braucht keine Konkurenz zu fürchten..Für NI wird sich das vermutlich eher negativ auswirken.
 
Silkworm
wrote on May 28, 2012 at 20:34
Super Artikel...sorgt für einen klaren Überblick!
Bin der selben Meinung wie HERBPAPA und DJ Til Dawn. Hab es auch nicht hinbekommen die RemixDecks ähnlich einfach zu steuern,wie vorher die SampleDecks.
Als Beispiel :Slot Start/Stop (SlotNR.) scheint nur noch über allgemein DeckPlay zu funktionieren,entweder alle Slots oder keiner.Notlösung mit Unmute/Mute!
WENIGSTENS die SampleDeckBasisBefehle hätte NI doch wohl beibehalten können.
Back 2 TSP212 .... auch wenn ich dann nicht mehr in den Genuß der Bugfixes komme....muß mich dann aber auch nicht über neue Ärgern. ;o/
 
Gyasi Sutton
wrote on May 30, 2012 at 23:40
It's really hard to believe that that with all of the knobs and buttons on the Maschine controller that the same functionality of the F1 cannot be mapped....Even if was hard wired to the software... This is practices that are similar to apple except that the are not even letting there own controllers talk to each other on this one....I believe they will release something to alleviate some of our pains...but it wont be ready until after the holidays...Remember forcing someone to by your hardware to use your specific product is a familiar strategy in the business world as one company has hit the ball out the park on that one...
 
djvc1993
wrote on May 31, 2012 at 12:16
I have made a solution.
You can use EVERY midi controller that you want
check this out: https://www.youtube.com/watch?v=cn5torYF3Xw
 
dj_lem
wrote on May 31, 2012 at 17:34
anyone test djvc's solution yet? so this should work okay with an AKAI MPD24?
testing now, if anyone got it working, do tell
 
guinnes
wrote on June 1, 2012 at 12:59
Vielen Dank für diesen wieder sehr ausführlichen Artikel.

Beim gestrigen Workshop, der extra von NI für Traktor 2.5 im JustMusic Hamburg gehalten wurde, hat der Mitarbeiter eindeutig gesagt, dass es nicht vorgesehen ist, dass ein vollständiges Midi-Mapping mit anderen Controllern außer der F1 möglich ist. Es wurde ganz offen gesagt das man somit mehr eigene Produkte verkaufen kann.
Leider hat es gestern niemanden groß gestört.
Hoffe es führt nicht dazu, dass in Zukunft bei neuen Updates nur noch NI interne Produkte bevorzugt werden......
 Rainer G. Haselier (admin) says:
Hat das der NI-Mitarbeiter wörtlich so gesagt?
 
malzfreund
wrote on June 1, 2012 at 17:18
Great analysis!

My 2c: NI is not limiting users' options due to technological constraints. Instead, I believe it's a business strategy. They must think that there's more money to be made from selling hardware and bundles as opposed to just software.

However, I am skeptical this will work out for them. One of the main strengths of Traktor has been its flexibility and relative openness. If they continue to close things down--as they now do with the remix decks--they partially take away what makes Traktor unique.

Imo, NI cannot pull an Apple here. They do not have as loyal and enthusiastic a following as Apple does. NI's hardware isn't nearly as unique, either.
 Rainer G. Haselier (admin) says:
I agree with you.
 
alex
wrote on June 5, 2012 at 01:31
please guys .  I'm in agreement with everyone who said NI should not be doing this.

What can we do to speed up the process on their end.  They SHOULD make remix decks OPEN and mapping friendly like EVERYTHING ELSE in traktor AS SOON as possible.


 Rainer G. Haselier (admin) says:
Write an email to Native Instruments and tell them how you think about it.

At the end, Kontrol F1 is just some plastic and metal (like any other controller). The power of the remix decks is in the software, not in the controller (even though NI marketing tries to make it look different).
 
Florian P.
wrote on June 11, 2012 at 13:13
Vielen Dank für den ausführlichen Artikel! Habe die Funktion Slot Mute On auf meinem Denon DN-MC 6000 auf die vier Cue-Tasten des entsprechenden Remix-Decks gemappt. Dadurch lassen sich die Samples, wenn sie im Loop-Modus laufen, zumindest komfortabel ein- und ausschalten.

 Rainer G. Haselier (admin) says:
Gerne doch und gut zu hören, dass der lange Text neben informativem auch einen praktischen Nutzen hat.

Grüße

Rainer
 
louis
wrote on June 15, 2012 at 00:46
I FOUND A WAY TO MIDI MAP ON TRAKTOR 2.5 WANT TO KNOW E-MAIL ME 

 
JensH
wrote on June 16, 2012 at 10:26
Eine Ergänzung zum Kommentar von Herbapa: Der entscheidende Vorteil von "Deck Play" ist eben genau, dass man den Slot nicht nur starten, sondern auch stoppen kann. Das kann "Slot Retrigger" eben nicht, und damit kann es der F1 auch nicht - in einem Live-Gig ist das ein sehr irritierender Mangel: Man muss sich dann mit dem Lautstärkenregler behelfen. Oder man "startet" eine absichtlich leere Cell, das hätte den gleichen Effekt, ist aber höchst unpraktisch.
Ich hab mir den Xone:K2 unter anderem deshalb zugelegt, damit ich ihn zur Steuerung des Remix Decks D einsetzen kann (den F1 lasse ich auf Remix C - und somit wollte ich mir das Umschalten ersparen, weil ich wirklich gerne synchron acht Slots ansteuern wollte). Er wäre dafür hervorragend geeignet, bräuchte aber dann die beiden von Rainer erwähnten Befehle. Und nun diese Frustration !
Immerhin kriegt man die "Deck Play"-Befehle auf den K2 gemappt: Haltet deshalb unbedingt noch eine 2.1.x-Version am Leben !
 
DJ Girish
wrote on July 3, 2012 at 16:38
Kontrol S4 and Maschine controlling Remix Decks - mapping very necessary.
 
Anders
wrote on July 8, 2012 at 21:18
Hi.

To me this is quite obvious. 
NI of course want to earn some money on their hardware as well. Developing a new hardware interface that user don't want to buy because they already own similar functionalities in maschine or similar product is not in their interest. 

When they have sold enough of this product they will probably open up traktor for full mapping. Midi mapping has existed for 10 years now. What kind of complex programming has NI used that won't work with ordinary controllers. 

I am thinking of buying Maschine since I can use it for more things. I won't buy both, thats for sure.

/Anders

 
Dan
wrote on July 17, 2012 at 07:11
Hi Louls: OK, I'm emailing you on how to map 2.5.
Don't know  what your email is but hopefully you'll
read the posts hear

Thanks! Dan
danhum@me.com

louis

wrote on June 15, 2012 at 12:46 AM
I FOUND A WAY TO MIDI MAP ON TRAKTOR 2.5 WANT TO KNOW E-MAIL ME 

 
Insider
wrote on July 29, 2012 at 01:13
Hey,

believe me or not but the main reason for not mapping the remix decks was NOT the selling of our own products (still that came up later by some people). The main reason were technical restrictions in the code and a lack of time for the release - F1 was Prio 1. 2.5.0 was quite a tough one and a lot to do to get it stable.

Even if it looks to you all as a small task this consumes considerable effort in specification, development and TESTING !!! As we move on with current development this effort "comes not for free". If we invest this other things fall of the table.

I understand that users are sad but please stop your conspiration therories about NI becoming a greedy company which doesn't give a damn. I assure you that there are people that care about the users but it's hard to satify everybody and in the end - greedy or not - a company needs to make money.

Again, don't get me wrong. You can be mad at NI that they won't listen to you. But you shouldn't think NI is becoming an "evil" company.
 
midos
wrote on July 29, 2012 at 21:38
Hi,
I have a big problem mapping the BASIC function of the Remix Deck, and i wish i can find the answer here.

My question is : How can we get to a BASIC SAMPLE DECK mapping with this new Version ? 

So let me explain my problem :
what im used to do with version < 2.5 (2.1 specially):

Button A :  Slot Play/Stop --- Toggle Mode : when i press A the sample start playing, if this sample is a loop, it will keep playing until i press A again. If it's a One Shot sample, it will play when i press A (without holding it), and when it reaches the end it stops by itself.
To this, button A i mapped the LED too.  Whatever the Type of the sample is, the LED keep ON until the sample Stops, then it turns off. That's wonderful for me, and that's what i'm searching to do.

Now applying the same procedure with the 2.5 version is a nightmare.

button A : Slot Retrigger Play or Slot Retrigger i tried them both several times. Set toggle Mode, when i press A : The sample play until the end, and repeat if it's a loop, or stops if it's a one shot. I also set the sample trigger mode to gated so it don't keep retriggering everytime i press A.
Everything was allright until i noticed this two problems :
When the sample slot is empty, the slot retrigger/retigger play function will capture a loop from deck A/B/loop recorder !!! I thin
 
DJ Abide
wrote on September 11, 2012 at 05:47
I have high hopes that ALL Maschine controllers will be supported just after the release of the MKII Maschine units. If they only add Remix Deck control to the MKII units WE as a community need to band together and protest as this whole limitation was clearly a marketing tactic to sell hardware. I have two different pieces of NI kit that I opened up and repaired myself both of which had shoddy soldering from the factory. The Maschine was actually duplicating the LCD screens as the solder from the factory was bridged between two pins. My Kontrol S2 had poor soldering on the Mic Engage switch. The quality of any NI kit is very poor from my experience and I'm running out of USB ports to add another controller. My Maschine and Mikro are more than capable of controlling all four decks as Remix Decks. I have 2 pages of pads on each reserved and waiting for NI to do the right thing and open up these features to users. I own over $1300 worth of NI kit and feel cheated that they have taken this approach. I will not purchase anything further and will consider switching to Rane/Pioneer/Serato if they continue on this path of greed and customer strong-arming.
 
shootdaj
wrote on December 28, 2012 at 15:50
You said that the remix decks launch command cannot be mapped. How, then, can we use the prepare and play workflow like you described? How do you launch the samples?
 
DJ ForcedHand
wrote on January 6, 2013 at 20:48
I think this is one of those things that Native Instruments would just go away. It was a very dirty game the company played with users and that doesn't win loyalty, fans or anything positive. I don't buy for one second that Native Instruments was unable to make the Remix Decks compatible with a Maschine and in fact they *SHOULD HAVE* sold the new version of Traktor Pro as "Now integrating with Maschine!" to be followed up with "...or the Kontrol F1 for DJs who don't need the full Maschine solution."

This would have worked so much better for them but because something at Native Instruments got snagged up, we now have this unsavory scenario where someone decided to make a piece of hardware (similar to Maschine pads), ram-rodded through the company (presumably) because they didn't want to deal with the Maschine Product Manager and somehow the higher-ups didn't catch wind of this until it was too late, the F1 controllers were already being shipped and the Traktor Product Manager was going to force the Maschine Product Manager to do things their way. Which is petty and stupid for a company of this size. I pieced this together from events which are known public and the open job requirement for Traktor Product Managerat Native Instruments following the release of Traktor 2.5.

Locking people out of controlling things in Traktor is not what people have come to know this state-of-the-art the product for. I imagine there's more anger over the hardware lock out than there
 
moreno
wrote on May 7, 2013 at 13:46
realmente no tiene el código midi en abierto de la sección de sample decís.yo he tenido que volver a la versión 2,totalmente  mapeable
 

 

Leave a comment

  Name

  E-Mail (will not be published)

  Website

Cancel