roundabout

I'm seeing the same problem. It's like Logic overcompensates. Because the compensation is always wrong, it's hard to tell what Logic is doing. For example, it's hard to tell if it applies the reported latency for the interface when the offset is zero. If I put in a negative offset, that helps, but the maximum negative value you can enter is -500, and I'm seeing an error of more than that. Has anyone ever been able to get the I/O plugin to work properly?

That makes it sounds like there is a problem with Klopfgeist. Are you running native or under Rosetta? The chances that all 584 of your plugins running native is near zero, so it sounds like you might some plugins that are have apple silicon compatibility issues, even if they validated.

Yes, aux tracks seem to have different monitoring behavior, so I was able to get it to work by doing that. Compared to other DAWs though, I'm not sure I'd go so far as to not call it a workaround though :). Again, thanks for the ideas.

Hmmm, I can get it to pass audio if I turn on Software Monitoring, but of course that screws up my direct monitoring.

I game to try it. But I can't get any signal from the input mono tracks to the bus (Aux2), and from there to the stereo audio track (Audio 4) so it can be recorded. If I record some audio onto the mono InWet and InDI tracks, then play it back, the audio passes through the bus as expected, but not until then. Am I overlooking some input monitoring option?

Thank you, but for my specific situation with large projects where many such tracks are added dynamically, a single stereo track is better than multiple mono tracks, stacked or otherwise. As I mentioned above, the Loopback technique would be a better workaround for me to achieve that. The point is I don't need to employ a workaround at all in other DAWs, so I was just asking if I've overlooked something when I concluded Logic doesn't have this feature that I've come to rely upon. In other words, I am not asking for workaround ideas. I am only asking if this feature exists in Logic. David says "no". That's good enough for me.

I do, it has the DVD, and I'd be happy to see it go to a good home. PM me with your details.

It does indeed get tedious 😀. The channels are coming over usb from a multi-channel digital amp modeler device, so I can't simply move cables. I have no idea if it's a frequently used feature, but since other DAWs do have this feature, I'm guessing I'm not alone.

He offered an idea for a workaround, and that's appreciated. The stack idea is helpful too. However, a workaround is just that, a workaround. Recording an arbitrary pair of channels to a stereo track can be done in other DAWs without resorting to a workaround, and I was just asking if Logic also has this feature. It seems the answer is "no". For anyone in the future who reads this and is trying to do this in Logic, I recommend the Loopback workaround I mentioned above. It's a bit kludgy compared to other DAWs, but it works.

Off the top of my head, to do this in other DAWs, Cubase has I/O busses, Digital Performer has I/O bundles, Reaper has I/O maps, ... You get the idea 😀.

For anybody who comes across this, I found a workaround using LoopBack. I create a virtual audio device with stereo outputs that consist of arbitrary pairs of usb channels. I can use those to get any pair of channels I want into a Logic stereo track. Still hoping somebody knows a way to do this inside of Logic though.

That's surprising to learn. It's easy to do that in other DAWs. Even with grouping, it helps with efficient editing and reducing track clutter to use stereo tracks instead of two mono tracks. That's why DAWs have stereo tracks 😀.

This is probably an easy question for Logic Pro experts, but I'm stumped. How do I assign non-adjacent usb channels to the input of an audio track? In other words, instead of channels 1&2, how do I use 1&5?

Yes. Although, there are some exceptions that don't work. The trick is that it's not being loaded into the Logic process.

A thread can be assigned to a core, but that is not a fixed relationship. It can, and will, be moved to different cores when it has work to do. Basically, the system activity monitor is of little use in analyzing Logic performance. It doesn't tell you the important information about how Logic is allocating work to threads and it doesn't show you transient peaks.