Logic Pro - routing one input to multiple tracks?

[thewildest]

I’ve been a Logic (Mainstage) user for 10 years and never thought this would be a limitation... insane. In Mainstage (Logic’s live version) you could setup n channel strips using the same input in parallel with no issues, I can’t understand why this would be a limitation with Logic...

 

[ToneMonkey]

Perhaps I didn't understand the instructions, but this didn't work for me:

input 3 (of eight) to track 3, no record, monitor enabled, destination bus 1
input 4 to track 4, no record, monitor enable, destination bus 2
bus 1 (aux 1) to track 5, record enable, destination output 1+2 (my normal output)
bus 2 (aux 2) to track 5, record enable, destination output 1+2

only silence is recorded.

If I enable recording on tracks 3 and 4 (the real inputs) then I get a mono recording on tracks 3 + 4, and dual-mono versions of those tracks on 5 + 6.

It's an interesting approach, but I don't see a practical application for me. Usually my takes need some fixin', so duplicating my playing into multiple tracks is probably not going to be helpful.

Nevertheless, thanks to Hummergeist for the tip!

addendum - I just noticed that I got some audible latency between the "direct" tracks and the "bussed" tracks. I guess this is to be expected. However, it prevents me from using this solution rather than my outboard hardware solution.

Still, it was fun!

Try tracking in low latency mode. Google it. There’s lots of good instructional videos.

 

[Dirk Diggler]

That seems odd, in Reaper I can select as many duplicate inputs as I want.
For input select which input on your device, make a new track and repeat.

I'm surprised Logic has this limitation, seems curious.

 

[Tosh]

Try tracking in low latency mode. Google it. There’s lots of good instructional videos.

my interface round trip latency is 2.7ms. I know it's a tiny amount, but I can hear it.

"Google it"?

 

[silky smoove]

my interface round trip latency is 2.7ms. I know it's a tiny amount, but I can hear it.

Humans can’t hear latency that low as has been shown on many tests. The human threshold is around 8ms. If you’re hearing audible latency there’s something else introducing more latency, such as monitoring through the software which can quickly add far more latency than one pass through the converters.

 

[ToneMonkey]

my interface round trip latency is 2.7ms. I know it's a tiny amount, but I can hear it.

"Google it"?

You can make it go to zero. Just saying. Sorry if I somehow pissed you off. Wait, no I'm not.

 

[silky smoove]

You can make it go to zero.

Only if you put an analog mixer in front of the converters. There’s no low latency mode on the planet that can get around physics. You can get it down to inaudible levels on most modern interfaces but truly latency free monitoring when converters are involved is a marketing claim that can’t actually be delivered.

 

[Tosh]

.... Sorry if I somehow pissed you off. Wait, no I'm not.

Sorry, you didn't piss me off.

I was making a lame joke about how a made-up word that was introduced to the public in a movie from the 1980's has become a verb used all over the world.

You have to be of a certain age to get it.

 

[ToneMonkey]

Only if you put an analog mixer in front of the converters. There’s no low latency mode on the planet that can get around physics. You can get it down to inaudible levels on most modern interfaces but truly latency free monitoring when converters are involved is a marketing claim that can’t actually be delivered.

Yes but <1ms latency may as well be zero. It’s effectively zero. There’s a setting for that in Logic. I use it all the time.

 

[silky smoove]

Yes but <1ms latency may as well be zero. It’s effectively zero. There’s a setting for that in Logic. I use it all the time.

Indeed it is. Keep in mind that all Logic’s low latency mode does is bypass any plugins that exceed the defined allowable input latency. Depending on the software monitoring needs, if any, the input latency settings, i/o buffer size, the interface being used and the comp itself, it’s still possible to have unacceptably high levels of latency when using low latency mode. It’s definitely not a panacea. I’ve seen many folks struggle with this when trying to monitor through amp sims on insufficiently powerful machines. Still, it’s a good option if you absolutely need to monitor through software which is something I avoid whenever possible so that the only possible latency introduced is the roundtrip latency through the converters.

 

[DirtDog]

Sorry, I should have done that. Here you go! View attachment 4209366

So, I tried this method last night but got some VERY unstable results. I mean, it worked, but the net results were not that great. Not sure what's going on so will try a fresh attempt tonight. And move step-wise though the process to make sure each part of the process works as expected.

Might be symptomatic of what @silky smoove describes above...

I may try this with external hardware instead (SCR-DI and a Strymon Iridium - using the Thru capability of the SCR-DI).

 

[DirtDog]

I tried splitting the signal before going into two separate channels in Logic.

I'm still having issues recording two channels at the same time. Now I'm wondering if I've inadvertently changed a project setting or system preference that overrides what should be a intuitive out-of-the-box function. Or pilot error.

Yes, I did start a new, fresh project.

Perhaps I'll try to record a short video and post it here - maybe someone can figure out where I'm making the pilot error. Biggest symptom is when I select and arm one track for recording, the other track becomes disarmed.

Puzzling. This is not something I've encountered before.

 

[silky smoove]

I tried splitting the signal before going into two separate channels in Logic.

I'm still having issues recording two channels at the same time. Now I'm wondering if I've inadvertently changed a project setting or system preference that overrides what should be a intuitive out-of-the-box function. Or pilot error.

Yes, I did start a new, fresh project.

Perhaps I'll try to record a short video and post it here - maybe someone can figure out where I'm making the pilot error. Biggest symptom is when I select and arm one track for recording, the other track becomes disarmed.

Puzzling. This is not something I've encountered before.

What interface are you using?

 

[DirtDog]

What interface are you using?

Presonus 1824c

 

[silky smoove]

Presonus 1824c

Using two separate inputs on that interface into Logic where you've assigned two separate tracks to the corresponding interface inputs (i.e. Logic track 1 assigned to input 1, Logic track 2 assigned to interface input 2, or similar) and you're still not able to arm two tracks simultaneously?

 

[DirtDog]

Using two separate inputs on that interface into Logic where you've assigned two separate tracks to the corresponding interface inputs (i.e. Logic track 1 assigned to input 1, Logic track 2 assigned to interface input 2, or similar) and you're still not able to arm two tracks simultaneously?

Correct.

And it's not a thing that I've had trouble with before.

Edit: typical use case for me for multi tracking at home: guitar on one track, voice on another track. Record both inputs simultaneously. No issues.

It's like I've inadvertently changed a setting somewhere and now I can't figure out how to reverse that change.

Pilot error could still apply!

 

[silky smoove]

Correct.

And it's not a thing that I've had trouble with before.

Edit: typical use case for me for multi tracking at home: guitar on one track, voice on another track. Record both inputs simultaneously. No issues.

It's like I've inadvertently changed a setting somewhere and now I can't figure out how to reverse that change.

Pilot error could still apply!

That’s very bizarre. Any system changes to your OS? You didn’t upgrade to Big Sur did you? If so, is Presonus compatible yet? Maybe reinstalling the Presonus software would resolve the issue.

 

[DirtDog]

Correct.

And it's not a thing that I've had trouble with before.

Edit: typical use case for me for multi tracking at home: guitar on one track, voice on another track. Record both inputs simultaneously. No issues.

It's like I've inadvertently changed a setting somewhere and now I can't figure out how to reverse that change.

Pilot error could still apply!

Edit again: and now it's working. G-D buttonology. But I don't know what I was doing wrong before.

 

[silky smoove]

Edit again: and now it's working. G-D buttonology. But I don't know what I was doing wrong before.

Glad you got it working. Now as long as you don’t touch anything, look at your computer the wrong way, breathe on it slightly, etc. nothing should change