David Nahmani

Duly noted. I'm sure everyone can make an effort to avoid this as well. Thank you for being understanding, I appreciate it.

@Frankenhaus No personal attacks or name calling in this forum, we're all better than that. This forum is neither a place for blindly worshipping Logic Pro, nor a place to bash Logic Pro. Neither is constructive. Quick recap on what this forum is about. We are here to help each other use Logic Pro. When someone brings up an issue, we can collectively put our minds together to try and figure out how to resolve it. If the issue cannot be resolved, we try to figure out the easiest way to reproduce the issue, and report our findings to the software developers in order to help them fix it. We've offered to have a look at a file that shows an example of the issue you're describing. I've suggested you first make a copy and simplify the file to make it easier on whoever is going to have a look at that file. If you don't want to take the time and effort to do that, you could post your file as is, and sometimes a brave soul is willing to take the time and effort for you! Simplifying a project file for troubleshooting purposes doesn't imply you should simplify your workflow when actually using Logic Pro, this is just a troubleshooting process. Allowing others to experiment with an actual Logic project file that displays the issue and trying to remove variables in order to pinpoint the culprit is one of the most efficient troubleshooting methods we've used in the 25 years this Logic Pro community has been active. When we do not follow any kind of troubleshooting methodology, all that's left is ranting and conjecturing, which often leads to arguing. That's not constructive, and that's not the purpose of this forum. Let's focus back to the issue at hand.

One of your channel strips' output is set to Surround (the 6th from the left on your last Mixer). Set it to Stereo Out instead.

No. By default, that Expression routing in the Mod Matrix isn't routed to a target, which means it isn't doing anything. That means that the status of the 'Inv' button does not matter at all. But that Expression routing is unnecessary for Expression to work as expected: you can leave that Expression routing the way it is, or you can turn it off, or you can completely remove it from the Mod Matrix, and Expression will continue to work as expected in all three cases. If you download the Logic project file I shared, where I have an Expression ramp up using the factory patch as is, you'll see that it works as expected.

The 2i2 3rd gen is certainly a great quality/price ratio. In that price range, you can also consider Arturia which makes great products, or even the Universal Audio Volt 1, or some of the Presonus interfaces. I'm personally not a big fan of the M-Audio interfaces, and would recommend staying away from Behringer. But all in all, if the 2i2 3rd gen meets your needs then I wouldn't overthink it and go for it, it's a fine choice. 🙂

Great! Good to hear. 🙂 And thank you for letting us know what resolved this for you, this is very helpful for others with the same issue who will find this later.

No, you want it set to Keep so that's good. Do you see your tempo changes being recorded in the global tempo track?

Is your tempo mode set to Keep (below the tempo value in your LCD display)?

Expression is not disabled and should work out of the box. It does here. Try just drawing Expression data in the Automation pane of your Piano Roll and it should work as expected. I've attached the following Logic file if you want to try it: Expression-test.zip That Inv button in Sampler's Mod Matrix inverts the modulation source: Inv button: Invert the effect of the modulation Source. A negative value becomes positive, and vice versa. (Source: Use the Sampler Mod Matrix in Logic Pro for Mac) However that particular routing isn't actually complete: there is no target selected. Therefore it serves no purpose at all. You could turn it off (On/off button on the left hand side of the Ctrl#11 (Expression) label) or even remove it (select and press delete) and the patch would behave exactly the same.

Can you repeat this lag when editing if you quit Logic, and reopen it and open a brand new empty project with only one software instrument and one MIDI region?

Then I think that must be it, because I'm still in 14.1.2 here and ... I don't see the Drummer description pop-ups, even after unchecking and rechecking help tags. So I think there must be some incompatibility between how those descriptions work in Logic Pro and Sonoma 14.1 versions. Thanks for updating this thread with your findings! 🙂

Could you share the project? Use google drive or wetransfer.

Drummer uses MIDI articulations that determine the opening of the hi-hat notes. In order for the MIDI notes to react to mod wheel, you need to remove the articulations. In the Piano Roll, select all the hi-hat notes, Control + click a selected note and choose Articulation > - (dash symbol).

Yes unfortunately, I've noticed that here as well, and there's no way around it other than to restart the entire poll. 😞

Ko-fi offers a free (pay what you want) sizzling distortion plug-in, Ham-Burger: https://ko-fi.com/s/6e7ded34dc - I tried this one and it's actually pretty cool! 😄