nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to duplicate an active loop from Deck A to Deck B (MIDI / QML) without saving Cues?

technocrat

Hi everyone!

I’m looking for a way to duplicate an active loop from one deck to another when both decks have the exact same track loaded.

Ideally, I'd like a solution where pressing a button copies the currently active loop from Deck A over to Deck B—matching the exact active loop length and position.

I’m aware that loading a duplicate track (or using Deck Duplicate) copies an already active loop automatically. However, in my workflow, I first duplicate the track to Deck B, and only after that do I set and activate the loop on Deck A. Because of this sequence, the loop doesn't get copied over automatically, which is why I need a way to duplicate the active loop on demand afterwards.

I know this can be done by saving Hotcues/Loops and triggering them on the target deck, but I’d really prefer to avoid creating and storing these loops permanently.

I’m open to achieving this either via custom MIDI mapping or QML tweaks. Just to give some context, I’m quite experienced with advanced controller mapping—my current setup runs a fairly complex mapping integration involving Traktor, Bome MIDI Translator, and Ableton Live—so feel free to share technical or advanced approaches!

Has anyone managed to achieve this seamless loop transfer without writing Cue points? Any insights, QML variables to target, or MIDI workarounds would be greatly appreciated.

Thanks in advance!

Find more posts tagged with

Traktor Pro 3

Comments

Stevan

Hello, another technokrat here.

Since you are duplicating first and setting the loop later, why don't you map one button that sets the loop at the same time on multiple decks.

1 - Map Loop Set + Size on deck A.

2 - Duplicate the command.

3 - Assign to the same Note CC an dchange assignment to Deck B.

technocrat

Hi Stevan!

Thank you so much for the input and for taking the time to share this idea. That was actually my initial thought, but unfortunately it doesn't fully work for my case due to an issue with track positioning.

The problem is that, in my workflow, I duplicate the track first and then manipulate that duplicated track on Deck B (doing beatjump forwards or backwards to find another point). Therefore, if I assign the loop after moving the track with the beatjump, the loop position on Deck A and Deck B won't match anymore, since the playback point on B will have shifted.

Still, I really appreciate the help and the intention! If you happen to think of another alternative or a way around this detail, I'm all ears.

Cheers!

Stevan

Maybe duplicate the track with the Loop already activated and then use the Move function to jump around the Deck B track without moving the loop.

Move Mode = Beatjump

Move Size = Loop Size or any specific Size

Move = Inc or Dec

Sûlherokhh

If it's a duplicate, you can save the loop as a hotloop. It will appear in the other deck immediately with the same saved number, although it will not be active right away.

Quick links

Unanswered questions