8 Comments
User's avatar
minor9's avatar

A solution to the wireless headphone problem would be to get something like the Mipro MI-58RT wireless transmitter/receiver and connect the beltpack to your favorite headphones or IEM's. I've looked at so many options for wireless monitoring for our band, and the Mipro seems to check every box. It's priced around 500$, the audio transfer is digital (meaning audio quality is practically unchanged, unlike much more expensive but analog options from Sennheiser / Shure etc) and the latency is sub 2ms.

I'm excited to get another laptop and finding a new workflow, following your guide!

Christoffer's avatar

Super interesting! Thank you for sharing! Really makes me want to try this out, especially with drum recordings. Because right now I have to run between my desk and my drum kit :C

Gregory's avatar

I don’t know why, but after reading this article I feel so inspired, great thanks to the person who wrote this, your energy and enthusiasm make me feel much better. I’ll try to organise my future studio with this vibe and surely will apply the great suggestions. Thanks for sharing!

Cooper's avatar

Love this. Immediately, I had a couple reasons I wanted to try this. I started tracking drums for the first time recently. My setup is two mics (a kick and an overhead) through a preamp and compressor into my mixer and back out through a chroma console that I have on a aux send.

First problem: I can’t see my screen from behind my drum kit, even if I try and use a wireless mouse and keyboard.

Second problem: I can’t control the chroma console from behind the kit.

Using the new Control CC plugin that comes with Live 12, I mapped all the controls of the chroma console to the plugin.

So now, I can actually see the screen while I’m tracking and monitor the drums while I mess with the chroma console, all while sitting at the kit!

I have a console piano in another room and I’m thinking I may try to run some mics from it all the way to my mixer and then I can track that now too without having to run back and forth. Definitely a game changer! Thanks!

Jacob Reske's avatar

Terrific use case! That's one of the primary reasons I set this up: tracking and editing drums at the same time, without running back and forth.

Sam's avatar

This is mind-blowing! Really enjoyed reading about your investigative process and hurdles you encountered. A couple questions: (1) Is there any reason not to use an iPad, aside from the form factor of a laptop? (2) Can you close the laptops (without turning them off) and maintain connection? Or do the computers need to stay open be connected? Stoked to try it out, thanks for the in-depth breakdown!

Jacob Reske's avatar

Good questions!

1) no other reason, as Jump Desktop works for iPad as well. The laptop form factor drew me to the idea initially. I had heard of people using iPads in this way, but it always seemed inconvenient to use something like a DAW without a keyboard and mouse. Once I set it up as laptop-to-laptop, using the remote machine felt so familiar to me—easy to get used to. And it's something I can pass off to others.

2) If you mean in clamshell mode, yes— my studio computer is a laptop that's closed all of the time and uses an external monitor, which is what's being shared. If you mean the other computer: if it's closed and put to sleep, it will try to reconnect as soon as it's awake. So you could have the remote laptop closed, and just open it when you want to use it.

Henry's avatar

Such an awesome concept and an incredible breakdown. Feel like this is what i’ve been after - the ability to really jam ideas out, not get stuck in the “loop trap” at the computer.

Keen to give it a run all the way in down Melbourne, Aus!