Reverse in traktor - works!!!

Reverse in traktor - works!!!

Hey guys

Since I’m mapping my MF3D, I’m figuring out a few things I’ve never done before :rage: and I’ve been spending more than 2 weeks already trying to figure out some things. :expressionless: :scream:

I thought I’d share this with you as I realized a lot of people are trying to get this done. Anyway, here’s a mapping to REVERSE in Traktor. It works fine so far with me. :tada::smiley::thumbsup:

ONE BUTTON ONLY!
Make sure Deck is playing than hit the button and it will reverse. Hit it again and it will play back normal.

Add in: Tempo Bend (stepless)
Type of controller: Button
Interaction mode: Direct
Assignment: Deck A
Button options: Set to value: -1.000

Add in: Play/Pause (Deck Common)
Type of controller: Button
Interaction mode: Toggle
Assignment: Deck A

Add in: Jog Turn
Type of controller: Button
Interaction mode: Inc
Assignment: Deck A
Button options: Auto Repeat • Resolution: Switch

Let me know if you have any issues, if there is a way to perhaps modify it or anything happening so I’d know. :smiley:

Love to hear some feedback.

-MOE

Sometimes you can get an accidental reverse function by being too aggressive with the jog wheels in scratch mode, it kinda bugs out :stuck_out_tongue:

Anyway, could you explain this mapping, just out of interest?

Well the mapping was no accident. I’ve got a mixer & midi controller but wanted to map it to my MF3D since its very portable and I’ll be using this now in the future…

I’ve basically mapped it to my MF3D. You have to map everything I wrote above onto one button using Traktor Controller Manager.

Set play/pause to direct=0 and listen that scratching :laughing:

haha:expressionless: not sure if ur serious or tryin to joke with me :tada::smiley:

but I did that anyway, it starts reverse playing… but can’t stop it. :thumbsdown:
The toggle mode uses the same button to reverse and then play it back normal… :stuck_out_tongue:

lol. at the direct=0.

Now we just gotta figure out a way to get it to work in timecode mode. :disappointed:

What about including Flux Mode in this…?

Nope. Flux mode only affect jog touch, loops and beatjumps. However I can imagine making a emulation of flux mode using one extra deck and duplicating a track.

dont think flux will work. +1 on that. emulation of flux means losing a deck… depends if someone uses all 4 at once.
i’ve mapped the MF3D to work with all decks. Plus FX AND Remixdecks using the firmware… :smiley:
now I just need to figure some minor things out then it’s perfect.

never used timecodes in all these years… how is it? why doesnt it work in timecode mode? can’t u combine timecode and a mapping for instance on the computer keyboard?

to utilize internal pitch, you have to be switched to internal aside from sync functionality

Been gone a while… what do u mean? I’m guessing u mean I have to use internal mode?

yessuh. it can be done with midi map set to hold if you wanted to switch between the two easily.

Have to try this some time!

??? dude, u writing to me? cuz I dont get what ur tried sayin in the 1st place :laughing:

hi friends, i was mapping other trick, and i arrived to this thread looking for information on “tempo bend” & “tempo bend(stepless)”, so first of all thanks for your posts, really helpful …

Decided to push your model further:

Backwards Playback + Flux.
this is Serato is called “Censor”:

- Press Pad: it play backwards while press, returning to normal on pad release, is using the flux, so is “censoring” the part of the track that was suppose to play while the Pad was press…

  • after using the Pad, “FLUX” will end up always on.
    (i tried to make the “Flux Mode On” in Hold, to end up the operation with “FLUX” Off and it would not work,
    tried also to add another line of “Flux Mode On” value to 0, invert “On”, to turn it off on pad release, and it would not work.)
  • If used inside an active Loop, if the Pad is not released before crossing the “Loop out” marker, the Loop will be exit (Because of the “FLUX” kicking in).
  • Since is mapped using the Jog Touch On, is not possible to fiscally operate the Jog W. while playing backwards, the “FLUX” will kick in when ever the Jog W. is touched.

this is how i mapped it:

Tempo Bend (stepless)
Button*Direct
Value
-1.00
Cond 1__Deck Play, Deck A=on
Jog Touch On
Button
Direct
Value_____1
Cond 1__Deck Play, Deck A=on
Flux Mode On
Button
Direct
Value_____1
Cond 1__Deck Play, Deck A=on
Tempo Bend (stepless)
Button
_Direct
Value0
Invert “On”
Jog Touch On
Button____Direct
Value
*0

Invert “On”
The Led…
at your own taste…
my one:
“On” when the Deck is playing.
“Off” when the Deck is not playing, or
while press (if Deck is playing).

Bonus:
This is what i was trying to map when i arrived to this thread looking 4 information:

Vinyl slow Stop & Jump Back:
On Pad press, creates & stores “Hot Cue 8”, and It slowly pitch down the track to -100% tempo until it stops the track, it takes around 3 seconds to stops the track (if the Pad is not released before).
On Pad release it jumps back to previously created “Hot Cue 8” to start playing and it deletes it.

  • If “Hot cue 8” already exists, it will jump to it on Pad press, then it will pitch down and it will start playing on Pad release from “Hot Cue 8”, to then delete it.
  • If made inside a Loop it deactivates Loop on Pad release.
  • Do not store a any Cue in “Hot Cue 8” if u want this feature to work correctly.
  • Scratch is not possible in the middle of this operation.
  • Warning!, for the complexity of the “macro”, If tapped to fast, could happen that it will not have time to create Hot Cue 8, so it will jump to what ever previous Hot Cue is stored, if a Hot cue is not stored it will jump to the Grid Marker, (usually at the beginning of the track), it will not go further than what ever previous Hot Cue is stored, just do not tap it to fast.

this is how i mapped it:

Loop Active On
Button*Direct
Value
0
Invert “On”
Cond 1__Deck Play, Deck A=on
Cond 2__Is in Active Loop, Deck A=1
Select/Set+Store Hotcue
ButtonHold
Value
HotCue 8

Cond 1__Deck Play, Deck A=on
Tempo Bend
Button
Hold
Value
Down
Cond 1__Deck Play, Deck A=on
Jump to Next/Prev Cue/Loop
Button
Direct
Value
Previous
Invert “On”
Cond 1__Deck Play, Deck A=on
Delete Hotcue
Button
Direct
Value
_____*HotCue 8

Invert “On”
Cond 1__Deck Play, Deck A=on
the first line visible in the picture is a modifier state added to the Pad to discriminate the “Play Pad” from the operation, where the Play will have as a condition MX=0, where X= the number of the Modifier used for this purpose.
I did not added as a line to create in the explanation because is not really necessary, just do not press play in the middle of this operation, or the Deck will start playing Backwards for good :laughing:, where to make it play correctly again will require a combination of pad press that i can not remember at this moment.
Best regards.