The largest community for DJ and producer techniques, tutorials, and tips. Traktor secrets, controller reviews, a massive MIDI mapping library, and more.

Rapidly Slice A Track To A Traktor Remix Deck

We keep spotting awesome new concepts on the DJTT forum community, and this concept video adds to the list with a Midi Pipe script being used to take a song and rapidly create a sliced-up Remix Deck out of 16 counts of a track. Big ups to rdej47 for working on this (all night!) and building an awesome feature that should get incorporated into Traktor!

Watch his overview in the video below, and read/download the instructions beneath that to try it out for yourself (you’ll need a Novation Dicer to use it right away):

I was up till 5am working on this concept. After reading the old DJTT “String Theory” I got inspired to pursue an idea I have had for a while. The idea is to be able to chop a track like an MPC into 16 individual hits that can be drummed out and rearranged on the fly. I know you can do this with a Twitch or a properly placed cue points but I wanted to the freedom do it anytime and then save the kit if I liked it. Another concept I wished to implement was the ability to chop a bunch of cells but alter the pitch so you could play different melodies. Unfortunately this functionality is still locked for the Remix Decks.

If you’d like to test this out here is what you need.

  • Traktor 2.6.2 + Midi Pipe (free download for Mac) + Novation Dicer
  • Dicer midi pipe file and Dicer Remix Deck.tsi
  • Open Dicer midi pipe file and go to midi in on the right menu, make sure dicer is selected as the input
  • Import the Dicer Remix Deck.tsi and in the controller manager for your input select midi port
  • Make sure Deck B is Track Deck and Deck D is a Remix Deck
  • Go to the Move menu in the advanced tab of Deck B and ensure that Move is set to BeatJump (not Loop, Loop in or Loop out)
  • Now you should be able to load track into Deck B, hold button 2 (2 dots) on the Dicer, press button 1 (1 dot) and it should slice your track to the remix deck.

Let me know if you have any questions. This is still a working concept but i’ll try help as much as possible and i’m going to work on getting compatibility for other controllers as well.

Read the full forum thread here and offer your feedback!

  • jj

    is there midipipe for windows?

  • Roni

    ok i got a huge question and this will definitely help me a lot. how
    can you use maschine to act up as an f1 to function and basically
    control remix deck cell? I was reading the forum and they said with
    2.6.2 you can now use any midi controller for remix decks. PLEASE HELP!

    • Roni

      also it would be useful if you provide any links or video or any step by step process since I’m a beginner. Thanks again

  • Kinskop

    I’m working on something similar for a while. To get Traktor Slicers on a Launchpad I’m using Pure Data for all the Midi stuff in the Background. For me the classic Sample Decks from Version 2.1.2 still work best because they had a midi “seek” function with LED feedback…

    you can check out an example her:

    http://www.kinskop.com/following-the-broiler-boom/

  • Andy Russ

    Hey there Ryan – I am getting a message on the Remix deck that tells me I cannot copy from an empty loop recorder. This occurs whenever I hit the Slice pad on the F1. Any ideas on how to fix this?
    Thanks, Andy.

    • Hey Andy, what you need to do is select the correct capture source. In this case your Remix decks are set to capture from the loop recorder. If you have an F1 the way to change this is: 1) Put your Kontrol F1 default mode (full remix deck control) 2) Hold the capture button down and the LED should start flashing (it will either display “cA” “cB” “cL”. 3) Rotate the encoder until it is displaying the track deck you want to capture from. Hope that helps.

  • Mike Lawrence

    nicee work man. Pretty cool

  • jimmazur

    Nice trick! Would be curious if there was even a 1ms delay between sequence events if the double captures would go away. Could be that the buffer isn’t keeping up with the capturing. Would be easy to prove using midi-translator.

    • Hey jimmazur. According to the original String Theory on DJTT, a 3 ms was actually the minimum needed for Midi Pipe to not skip over commands. Fellow member Rafiq has played with the delay settings and reported some success. I think he may have increased the delay slightly?

      Here’s the forum post where he’s discussed his experimentsL http://forum.djtechtools.com/showthread.php?t=73575&page=4

      • jimmazur

        Thanks Ryan, that was going to actually be my next question. If the commands are truly being serialized on the output side of midipipe. I know that in MT the event processing happens in order of their placement in the translator preset. I don’t know much about the engine of midipipe though and that’s why delays might need to be incorporated in order to ensure proper sequencing (or let alone not skipping / swallowing of messages) once those event are pushed into Traktor.

        There is kinda a grey area in this whole domain due to virtual midiports, where you can actually break the rules of MIDI (1 standard (note/cc) message per millisecond, if memory serves me correct). In that case, if you wanted to stay true to midi standards, for every chain/string you would delay each corresponding output from an input by 1ms. i.e:

        Input arrives (gets swallowed by engine)
        Standard midi output event 1 – w/ 0 ms delay
        Standard midi output event 2 – w/ 1 ms delay
        Standard midi output event 3 – w/ 2 ms delay
        … and so on.

        It could be for other reasons that midipipe needs a bit more time (+2ms) due to its processing and architecture. Hope that makes sense. 🙂

  • Ray Eng

    Hey rdej47, great work and thanks for sharing. I’m kinda lost…sorry. But can’t you just place a hot cue point at each of the 16 points on the track. Hence it would be 8 points on the X1 only. Do you have a video of this in actio so I can visually see what this translates too in finger drumming? Have you seen BassKleph do his sets on the Maschine? Is it like that concept? Thanks for your help and btw great article.

    • Hey Ray, i’m going to upload a better demo using the Kontrol F1 (along with a simple template for that as well).

      The benefit this has over placing 16 cues on a track is that you can do this at any point in a song and slice it very quickly. In my opinion this is much faster then going to 16 different points in a song and dropping cues. This also reserves your cue points for key points in the track. Where as this is more for quick inspiration and jamming.

      • Ray Eng

        Got it. I just dawned on me by watching this video and the older post about “String Theory” that this way is much faster doing it on a live set. Looking forward to seeing the F1 demo. Thanks for sharing!

  • Nukemi

    Awesome.

    Would love to see if this works on F1!

    • Nukemi, i’m just uploading a video now that will walkthrough Kontrol F1 setup and a quick demo of it. I’ll post a link once it’s uploaded.

      • Here’s the F1 setup and demo. http://www.youtube.com/watch?v=knuMdZoQuMY

        • Nukemi

          OH man. You are awesome! Will try this today or on friday when i get the chance!

        • Nukemi

          One thing, do you mind if i share this on reddit? as i’ve seen people ask for this in there after this link was shared.

          OR, even better, if you’d share it yourself, so you get the credit you deserve 😉

  • Hey everybody, rdej47 here. I’m super stoked that DJTT thought this was worthy enough for the blog. I’ve worked on some updates to the concept that I will upload shortly. Also fellow DJTT users Rafiq and Stewe have been adding their own ideas that have been incorporated as well.

    These new features are in the works, 1) More consistent slice behaviour 2) Deck A + B Slice functionality 3) Support for any midi controller (you just need a couple free buttons). Once again thank you DJTT for sharing this, i’m excited to see what the community can come up with.

    • Shaun Bruyninckx

      Do you have any idea yet on how to map everything to a launchpad? Considering the fact that it has 64 buttons, you could make a mean “sampler” with this…

      • No doubt on the sampler. You can map all 64 cells it’s just really time consuming as that requires mapping each individual cell to the launchpad buttons.

  • Anonymous

    That is awesome, great work.

  • Robert Printa

    I would love to see these to x1.

    tried but not quite got the to work.

    • Hey Robert, this will definitely work with an X1 however it would only work through the X1’s midi mode.