Bierman

I stand corrected, glad to hear that.

Thanks David. I just submitted a feature request to Apple. I'm sure that's a naive thing to admit to doing, hah!

Every time I try using MIDI to control parameters of 3rd party plugins as inserts on audio channels, I regret it. I must be doing something stupid but, do I REALLY need to create an instrument channel, put the insert effect on that, and route the audio from the original channel, thereby cluttering up the arrangement with an extra track I really don't want or need? I assume that an audio channel does not handle MIDI data nor does an instrument/MIDI channel handle audio files?

I'm assuming this feature has not been implemented yet. Does Apple listen to customer feedback about Logic? This seems like it should be relatively easy to implement but what do I know about software programming?

Thanks David, wow a convo from 14 years ago. I found locking SMPTE and trying to resize from the lower left handle didn't actually change the content of the region at all... however like you suggested, using shuffle L and resizing start and end handles is actually a totally workable approach, if a bit long... Ableton handles this particular thing so gracefully though.

In Ableton Live, there's a very useful way to scan through a recording you've made which maintains the audio or MIDI region's place in the timeline while "slipping" the content to play different parts of the recording. Is there a way to do this in Logic? Lock position in track when moving anchor achieves a kind of inverted effect of what I would want. I can't see any way to do this using the Track Editor but maybe I missed it.

Thanks Volovicg, this solved my problem... (copy/pasted from my thread on the Apple forums): https://discussions.apple.com/thread/250787312?page=1 I now properly understand how Auto Demix by channel works and I can see its power and usefulness. Essentially Logic's Sequencer Input is treated as a single MIDI input port, and there are 16 channels through which you can potentially send MIDI data into Logic, I now see/understand this. This means that my hardware (the ones I wish to discretely send/receive MIDI to/from) must be set to send and receive on discrete MIDI channels, even though they are addressed by different MIDI output ports on my MIDI interface. This is problematic because I have quite a few hardware synths and drum machines, some of them send data on multiple channels (in particular the Elektron devices, drum machines and multitimbral synths), so there are a couple of situations where multiple devices are sending on the same MIDI channel. I should be able to jostle things around though to mitigate this. One thing I have discovered is that this does not seem to work at all if using the old-style MIDI Instrument objects you create in the Environment, which is what I have been using all this time, hence why my earlier tests didn't work. I also noticed the record-enabled status of these tracks would be lost if you clicked on another track... I replaced the old MIDI Instrument channels with the External Instrument plugin and things seem to be functioning correctly now. also, multiple instrument channels must be record-enabled for this to work correctly - if there are no record-enabled instrument tracks then the behaviour will revert to omni in terms of which incoming MIDI will send data to the selected track, which can be dangerous for the reasons I outline above, ie sending unintended MIDI messages to the "wrong" track. It would be good to know of a way to prevent record enable from being disabled when selecting other tracks (I notice this happens when selecting a track stack/folder track, but not when selecting an audio track) Anyway, many thanks for the help, god bless the internet community!

Hey fuzzfilth, thanks a lot for taking the time to reply at such length... I don't think this is going to work for me as ultimately there's no consistency between the different hardware synths I own in terms of which MIDI CCs are useful/important, and they don't match up in any meaningful way between one and another. eg the Voyager's filter env attach sends CC#55, which on my Nord Lead controls the rate of LFO2, which might control some other parameter on my Matrix Brute and so on... Setting up a conditional split controller device in the environment and then needing to remember to bypass it under certain circumstances kind of defeats the purpose of what I'm trying to achieve, which is to create a system where I don't need to worry about remembering to change something in my Logic system in order for things to work as expected. I already need to remember to have the correct track in the arrangement selected before I touch a physical control on one of my synths, and/or I need to remember to bypass/unbypass their inputs being routed to Seq Input in the environment . While I agree with you that in some scenarios, having the ability to control any track from any incoming MIDI port can be advantageous, it's still inconvenient for it to be fixed that way. Certainly, when it comes to a USB MIDI keyboard whose purpose is only MIDI control and which has no sound generating capabilities, you definitely want to be able to control any track with that. But ultimately I have "broken" a synth patch far too many times because I forgot to select the correct MIDI track in the arrangement and I turned a knob on a different synth. Ableton is easily able to route the MIDI data in exactly the way I need because its MIDI tracks have the ability to specify both incoming and outgoing ports, or not. That way I can have one MIDI track whose sole purpose is to send MIDI information OUT to a hardware synth, and I can have several other MIDI channels whose sole purpose is to funnel specific incoming MIDI data (set by specifying input port and channel) to specific MIDI tracks... all that being said I much prefer working with Logic and would certainly NEVER mix using Ableton, and in just about every other way Logic's MIDI editing and control is superior, just not in this scenario... anyway again, thanks for your time in trying to help me.

Yes I also have an External Instrument plugin set up to control my external synths (useful because I can use MIDI FX plugins on those) but the same issue still applies... I cannot see any way to specify and restrict which incoming MIDI ports and channels will send MIDI to these instruments, I can only specify the MIDI OUTPUT port and channel... also it's worth mentioning that I don't want a situation where an track can ONLY be controlled by one particular port and channel... I have USB MIDI controller keyboards that I would want to use to control any synth I have selected in the arrangement, as well as the actual hardware of the synth in question. It's just that if I am modifying the parameters of a particular hardware synth and I have the wrong track selected in the arrangement, it will send CCs to the synth connected to that channel and therefore change the sound, often in very dramatic and undesirable ways.

Unless I am missing some kind of fundamental feature of Logic's MIDI instrument objects (and I have been using Logic since '97) I do not see any way to specify the INCOMING MIDI port and channel on a particular MIDI instrument track, or any track for that matter... you are only able to specify the OUTGOING MIDI port and channel in the object inspector. As far as I am aware, no incoming MIDI data will be recorded by Logic unless the Physical Input port of the device in question is connected to the Sequencer Input in the environment. I understand that users are able to use Logic without ever touching the Environment and that it's supposed to be a "back end" feature but absolutely everything that exists in Logic's arrangement does have a corresponding object in the environment and it is still required to make the system work... again, unless I am misunderstanding something fundamental about how Logic works. Here's a link to a screenshot (sorry I can't figure out how to embed the image in the post, I don't have hosting) https://drive.google.com/file/d/1StOeQu_9ItgW42_Hlsm_S4WAkjAZ1x4i/view

Bypassing control surfaces didn't do anything. This is all to do with MIDI CCs controlling track parameters, eg any hardware device which sends CC#7 and whose physical input is routed to Sequencer Input in the environment will control the volume of the selected track, which is what it's supposed to do so there's nothing wrong there per se. However, if a physical input is NOT routed to the Sequencer Input, then you can't record any MIDI data into the arrangement, again, that makes sense. If I record MIDI from a hardware synth into a MIDI track in the arrangement which is set up to route that MIDI back to the originating synth, thats fine and things are operating as expected... but then later if I have a different channel in the arrangement selected, and I turn one of the knobs on the first synth, I am sending CCs to a different track or a different synth, and I risk "breaking" the patch on the other synth. Surely there must be a way to prevent this?

I'm having trouble with hardware MIDI routing in the environment, hopefully someone can help... I have my template set up whereby I route incoming MIDI from my hardware synths into a monitor and then a switch, which either routes the MIDI data to the sequencer input so I can record MIDI notes and CC, or it bypasses and goes nowhere. Let's take the Voyager as the case study for this but it applies to any incoming MIDI from hardware... What I can't figure out is, how do I route the MIDI of the Voyager's ports and channel ONLY to it's corresponding MIDI instrument channel in the arrangement, and prevent that MIDI data from controlling other tracks in the arrangement? In this case, my Moog Voyager sends troublesome MIDI CCs into Logic's sequencer which causes tracks to be solo'd, changes track volume and so on. I have tried setting up the cable destination to route directly to the Voyager's MIDI instrument object in the environment, but this still results in MIDI activity going to the Sequencer Input and thus sending MIDI data to whichever track is currently selected in the arrangement. I have tried this using an External Instrument software instrument track and also with just a regular MIDI instrument object created in the Environment. Both of these tracks do successfully send MIDI data to the Voyager... Hopefully I've explained the problem properly.

Understood... Just crazy. It means creating a separate control track just for sending automated CC data to the instrument. I also notice it doesn't seem possible to have multiple Modulation MIDI FX plugins on an instrument channel I'm not a fan of cluttered arrangements. Where's Apple's LPX feature request page? Is there even such a thing? Thanks for your help Jordi.