Mixtour Pro: Direct 4 deck volume control no layer switching

DJ Hardware
1

SDDE 2+2

Simple Direct Deck Engagement

2 faders + 2 rotaries = 4 dedicated deck volumes

Out of the box, four deck mixing on the Mixtour Pro means switching layers just to get at decks 3 and 4 volume. The fader positions don’t match after a layer switch. So the volume can jump or bump when you touch the fader. I wanted to remove that problem and have direct physical volume control for all 4 decks at once.

Since I use auto gain, I don’t need the gain knobs for their default job. So I mapped them to decks 3 and 4 line volume. Faders handle decks 1 and 2, gain knobs handle decks 3 and 4. Four dedicated volume controls, no layer switching.

To do it, leave the channel faders as is. Deck 1 fader to deck 1 line volume, deck 2 fader to deck 2 line volume.

Then in DJ Pro’s MIDI settings for the Mixtour Pro, map the deck 1, left gain knob, target mixer, action deck 3 line volume. Map the deck 2, right gain knob, target mixer, action deck 4 line volume. Save.

Now you’ve got deck 1 volume on the left fader, deck 2 on the right fader, deck 3 on the left gain knob, deck 4 on the right gain knob. Four decks, four dedicated volume controls, no layer switching.

2

Hi @RickVincent, welcome to the Community! Cool idea. Thanks for sharing.

4

You could also set the ‘pick-up’ option in the midi mapping of the controllers. The jump is avoided but you have to move / turn the controller to the position that represents the internal value before it has any effect. Oddly the pick-up option is only enabled for the filter controls but you can set them for the others in the midi tool.

5

Thanks for sharing this @Brainbox

6

@Brainbox Thanks for the feedback. I can definitely see the value of using Pick-up Mode and it’s a good way of preventing the sudden volume jump when changing layers.

The reason I’ve gone down the 2+2 route is slightly different: rather than managing the mismatch between the physical fader position and the software fader position, I’m trying to remove that mismatch altogether.

With Pick-up enabled, after switching layers the physical fader has to be moved until it reaches the current software value before it takes control. That prevents the bump but it also means the fader can temporarily do nothing while you’re searching for the pickup point. My concern is that during a live mix I want a volume control to respond immediately when I reach for it.

With the 2+2 mapping, Decks 1 and 2 retain their normal dedicated volume faders, while the two gain knobs are mapped as dedicated volume controls for Decks 3 and 4. As djay’s Auto Gain already handles most of my gain management, those two physical gain knobs become very useful controls for the additional decks.

So instead of switch layer → find the existing volume position → pick it up → adjust, it becomes simply reach for the deck’s dedicated volume control → adjust.

Pick-up is a good solution if you want to retain the normal layer-switching workflow. What I’m experimenting with is whether the need to switch layers for volume control can be removed altogether. That’s really the idea behind what I’m calling the 2+2 / Simple Direct Deck Engagement (SDDE) mapping — four decks, four directly accessible volume controls, with no volume-layer switching required.

Thanks again for pointing out the Pick-up option. It actually helped me clarify the distinction between the two approaches.

7

One thing I’ve realised after using this mapping is that it’s more than just repurposing two gain knobs.

For volume control, it effectively removes layer switching from the Mixtour Pro altogether.

Normally, changing Deck 3 or 4 volume means switching layers with Mode + Deck, moving the fader until pickup engages, confirming you actually have control, making the adjustment, then switching back to Decks 1/2 — while the music is still moving.

With this mapping, Deck 3 and Deck 4 each have a permanently assigned rotary volume control. Hear that Deck 3 needs adjusting? Turn the left rotary. Deck 4? Turn the right rotary. One direct action.

So for volume, the Mixtour Pro effectively stops behaving like a 2-channel controller accessing four decks and starts behaving much more like a 4-channel controller: two proper faders for Decks 1/2 and two rotary faders for Decks 3/4.

The biggest gain for me is not just speed. It’s removing the layer switching, pickup uncertainty and extra mental load during a live mix - Priceless

8

Yeah this seems like a good setup if you regularly need to adjust the levels for Deck 3 & 4 on this hardware. Especially if you’re using Autogain anyway.

9

I’m incredibly proud to say that Mixtour Pro-V is now a working concept.

Pro-V started with a simple philosophy:

A four-deck workflow shouldn’t make the DJ think in layers. It should respond to the deck the DJ intends to use.

I wanted to strip away unnecessary decisions between musical intention and physical action.

Deck-driven, not layer-driven.

Touch the volume control for the deck you want, and that deck becomes the focus. The shared controls follow. Instead of stopping to think about which layer I’m on, I interact directly with the deck I want to hear.

This also addresses one of the biggest things I wanted to change: the opportunity for human error created by manual layer switching and uncertainty about which layer is currently active.

If I don’t have to consciously select a layer, I can’t accidentally select the wrong one.

Touch the deck. Engage the deck. Control the deck.

The controller starts to become what I always wanted it to be:

“The controller becomes an extension of my impulse.”

Getting there has taken a remarkable amount of trial and error. There were dead ends, failed mappings and several points where the technical barriers appeared insurmountable.

The eventual solution required going beyond the standard controller mapping and building a MIDI workflow using StreamByter and MIDI Mittr.

And now it works.

Move Deck 1’s volume control and the workflow follows Deck 1.

Move Deck 3’s volume control and the same shared transport control follows Deck 3.

The interaction determines the deck.

That sounds simple.

It was anything but simple to achieve.

But simplicity at the point of use was always the objective. I don’t want the complexity of the engineering in front of me while I’m DJing. I want that complexity working quietly in the background, taking care of the layers while I concentrate on the music.

Which is why Pro-V has acquired a nickname.

Simon.

Simple Simon — my layer roadie.

Simon handles the layers. I handle the performance.

There was another principle I felt strongly about from the beginning: if I could get this working, I wanted it to be free and accessible to everyone.

This isn’t something I want locked away.

I now have a working concept and I absolutely love how streamlined the workflow feels. There is still testing, refinement and documentation to do before I release anything, but once I’m satisfied that it is ready, I intend to make Pro-V available for others to try and evaluate for themselves.

No grand claims.

Use it. Test it. Push it. Tell me what works and what doesn’t.

For now, though, I’m allowing myself to enjoy this moment.

After everything it took to get here:

Pro-V works.

Deck-driven. Not layer-driven.

Less switching. Less uncertainty. Fewer opportunities for error.

The controller becomes an extension of my impulse.

And Simon finally has a job.

10

For me though, in my opinion. If I was using 4 decks regularly, I’d simply prefer an additional controller for control over decks 3+4. I’ve owned 2 channel controllers that are advertised as being able to control 4 decks, but I just don’t find it intuitive at all.

I love my Mixtour Pro, so if I wanted to regularly control 4 decks, I’d consider an additional Mixtour Pro (in midi only mode) or a A&H M3 for the additional decks control.

11

Hi Bill,

That’s a completely fair approach and I actually think you’ve identified the exact problem I’ve been trying to address with Pro-V.

If you’re regularly using four decks, adding dedicated hardware for Decks 3+4 is probably the most obvious way of avoiding the layer problem altogether.

My challenge to myself was: can I get a two-layer Mixtour Pro to behave more intuitively without adding another controller?

That’s where Pro-V and Simon came from. Rather than me thinking, “select Deck 3, then use the controls” I wanted the deck itself to effectively announce my intention. I move Deck 3’s dedicated volume control, Simon makes Deck 3 the focus and the shared transport controls follow it. Move Deck 1’s volume and they follow Deck 1 again.

So we’re really solving the same problem in two different ways — yours by adding dedicated physical controls, mine by trying to remove the need to consciously manage the layers.

And your comment that conventional 4-deck control on a 2-channel controller doesn’t feel intuitive is exactly why I’ve been pursuing this.

12

Very interesting!

Just to share thoughts and discuss.

I’m coming from a controller that has the real estate to cover all 4 decks simultaneously and that is the way to go if you want to remix with unrestricted use of decks. As extreme example B2B mixing.

But in my most use cases I can perfectly mix with 2 decks where I use the other two to remix or mash-up. Most of the time simple vocal or drum replacements or additions. Even the simplest cases of that are complex enough to require preparation. That works fine with the Mixtour concept with a few changes imo.

A point that is maybe overlooked is the UI mode of DJay. In these simple remix cases I just keep using 2 deck view mode to get some overview. I just don’t like the 4 deck view, but maybe that is like building view memory like muscle memory for control … I only use the 4 deck view to set effects etc or in exceptional complex mash-ups. I’m not sure I would like to be in 4 deck view very often …

That said, I use 1 or 2 midi fighter twisters for the stuff the Mixtour concept is limited; controlling the looper and to route stems to the effects. Both require a lot of real estate if you want to do it in an ergonomic way.

I’m curious how you did it. As far as I understand the Mixtour already sends controls through additional channels to DJay, where DJay uses the required routing based in the state it is in? So part of this ‘architecture’ seems to be already there … but need to dive into that better …

Cheers, Bart.

13

Hi Bart,

It took a fair bit of trial and error but now that I’ve worked it out, the actual setup is fairly straightforward. I just need to document it clearly.

It wasn’t achievable with a simple MIDI remap. The Mixtour’s Mode + Load deck-layer switching is hardware/firmware controlled, so I couldn’t simply retarget it in software.

I ended up working around that rather than trying to force it. The solution uses MidiMittr for MIDI routing, StreamByter with a set of rules I had to create and specific MIDI mappings inside djay. MidiMittr and StreamByter are both iOS apps. All three pieces work together.

I deliberately stuck to free additional apps because I want the finished solution to be accessible to anyone who wants to try it.

The basic philosophy is from layer-driven to deck-driven. Rather than selecting a layer first and then controlling the deck, I engage the deck I want and the controller follows.

So the complicated part was figuring out how to get around the hardware limitations. Once that was solved, the actual workflow became very simple and direct.

I’ll make the setup and instructions available once I’ve finished documenting and testing everything properly.

Cheers,
Rick

14

The Teenage Engineering EP-136 KO Sidekick is another small form factor device to consider for additional 4-Deck control. I’ve used one alongside the Mixtour Pro for Deck 3/4. Actually, you can easily daisy chain multiple EP-136’s together.

15

The Sidekick is definitely an interesting suggestion and I can see the appeal of having proper faders for Decks 3 and 4. For me though, it starts to move away from what I’m trying to achieve with Pro-V. I’d suddenly have two separate control surfaces, extra cabling, another device drawing power, more space needed on the table and another layout that I’d have to become completely familiar with. A big part of this for me is keeping the whole setup genuinely portable and instinctive. I want to be able to throw the Mixtour Pro, iPad, headphones and the essentials into a light backpack and go. In a dark or pressured environment, I want my hands to know exactly where to reach without thinking about which device a control is on.

I think of Pro-V a bit like central locking in a four-door family car. Before central locking, if you had passengers getting in, unlocking the driver’s door didn’t unlock theirs. You either had to reach across or go around the car and unlock the other doors individually. Nothing was wrong with the doors or the locks — they all worked. The problem was the process. Central locking changed that beautifully: one action communicated the intention to the whole car, and the system took care of the rest. That’s what I’m trying to achieve with SDDE. I already have four decks available; I don’t need more hardware to give me four decks. I want the system to understand my intention from the control I touch and take care of the background switching for me. Move the volume for the deck I want, and the controller follows. Same capability, fewer steps — impulse-driven rather than layer or component-driven.

16

Fair enough and I totally understand that perspective. Regarding power, the EP-136 has another trick up its sleeve - can be powered by 2 standard AAA batteries in addition to USB-C.

17

I remapped transport buttons to turn red if on deck 3 or 4. Instant deck engagement with binary red, blue, left or right.

17912233838855308146675060215419
179122338388553081466750602154191920×887 497 KB

18

Nice @RickVincent. Looks good.

19

Mixtour Pro-V - Would Anyone Actually Want This?

I’ve now reached the point with my Mixtour Pro-V project where I’m considering putting together a proper installation pack for other Mixtour Pro/djay users. Before I spend the time documenting everything, I’d genuinely like to gauge whether there’s enough interest to make it worthwhile.

The idea behind Pro-V is pretty simple: “I wanted to stop thinking in layers when mixing four decks.”

Decks 1 and 2 retain the two physical volume faders. The two gain rotaries become direct line-volume controls for Decks 3 and 4. But the part that’s made the biggest difference for me is what happens next.

Touch the volume control for the deck you want, and the controller follows you.

The two Play buttons then work as shared transport controls, with a very simple binary visual system:

BLUE = Decks 1/2
RED = Decks 3/4

Position tells you the side. Colour tells you the deck bank.

So:

Left + Blue = Deck 1
Right + Blue = Deck 2
Left + Red = Deck 3
Right + Red = Deck 4

If I touch the Deck 1 fader, the left Play button goes blue and Play controls Deck 1. Touch the Deck 3 rotary, the same Play button goes red and now controls Deck 3.

Same principle on the right for Decks 2 and 4.

There’s no mental sequence of:

“Which layer am I on? → Do I need to change it? → Check → Play.”

In normal use it becomes:

Touch deck → colour confirms → Play.

The interesting thing for me is that after using it this way, I’ve stopped thinking in layers . The Mixtour hardware is still fundamentally a two-layer controller, but that layer management has effectively disappeared from my normal four-deck workflow.

And that’s probably the biggest compliment I can give it: I’m having more fun mixing. I’m looking at the controller less and thinking about the music more.

Getting Pro-V to this point wasn’t just a normal djay MIDI remap. I ended up using StreamByter and midimittr to create the additional logic and LED behaviour behind it.

I’m now considering turning the working setup into a proper Pro-V installation pack : mapping, StreamByter rules, routing setup, step-by-step installation, testing procedure and troubleshooting, so somebody else doesn’t have to go through all the trial and error I did.

But I don’t want to spend a lot of time producing something nobody particularly needs.

So this is really an interest check:

If you use a Mixtour Pro with four decks, would eliminating conscious layer management like this be useful enough that you’d actually install Pro-V?

I’m equally interested in hearing “No — layers don’t bother me” as I am in hearing yes. That would help me decide whether a proper installation package is worthwhile or whether this is simply a workflow that happens to suit me.

For me, though, the difference has become very simple:

Before Pro-V, I operated the layer to reach the deck.

With Pro-V, I touch the deck — and the controller follows me.

20

I downloaded your other mapping you put up and I love it is it possible if we can have this also

21

file_000000001a3c820bbb65f2b3e0522ff0
file_000000001a3c820bbb65f2b3e0522ff01122×1402 111 KB

I will just leave this here, IYKYK