Atlas007

Many people reported various issues running LP10.8.1 with macOS Ventura that got solved by upgrading macOS to Sonoma… Anyhow, the first step I would try (before macOS upgrade) would be to "Bypass All Contro. Surfaces": Choose Logic Pro > Control Surfaces > Bypass all Control Surfaces. If that (temporarily) solves your issue, chances are that you have some rogue control surface that got installed in your Control Surface Setup (window). Deleting same should normally solve the issue permanently. If that doesn’t help, chances re that your project (template) got somehow corrupted. One easy way to sort this out would be to create a fresh new project (without using a project template). If the issue is then gone in that new project, the corruption is most likely the source of the problem. In such a case, the solutiom would be to rebuild the project.

… or they simply switched to another app for that specific purpose…😏

I would use the Space Designer plugin to import those IR file. The method is described here.

I would think that, indeed, you would have to indicate that audio file’s new location (in your laptop drive’s) to the Playback, otherwise Mainstage’s plugin won’t find same. But for clarity sake, what do you mean by "without losing the path"? IIRW, Concert is at the highest hierarchy level, encompassing songs, which encompasses patches, which could be grouped into sets… Depending of the circumstances, if that fulfill your needs, there is no restriction in that configuration. Patches/channelstrips that are located in concert level will be available for all songs.

Rest assured that you’re not alone…🥴

Quick way (temporary solution) could be to "Bypass All Control Surfaces" : Choose Logic Pro > Control Surfaces > Bypass all Control Surfaces. Longer method (idealy definitive solution): Hunt to find out what MIDI data your controller (m-audio hammer 88 keyboard) is sending to trigger the unwanted freezing command, spot it in the Controller Assignment window to finally delete that entry. The second method would be useful to undergo if the first (Quick) way provided a (temporary) solution to your issue.

That is indeed a more elegant method!

That is an interesting question… If possible, could you try reverting to before importation and opt for enabling that "Keep Bus Number" option? Besides, I wonder if the "Automatic Bus Assignment Uses" setting in Audio>General Logic’s Setting could be at stake (one way or another) in your issue?

My first thought would be to experimenti with Smart Controls. Alternately, I would make the automation (as CC if possible/needed/applicable) and use fader object in the Environment. The Vector fader object might prove being quite useful here… Eventually an hybrid approach of the above… (admittedly, that is uncharted grounds to me)

For the benefit of other eventual users seeking for a solution to a similar issue, would you mind marking my former post as such?

As described by @David Nahmani, : simply remove the checkmark before the Varispeed option in the LCD menu:

That is a definite no! no! That will likely corrupt your opened projects (possibly both of them). And chances you won’t notice it until late enough not to remember when that might have happen. Instead, rebuild your project by importing the data from one to the other, while having only the new one destination project opened.

Oops! I wasn’t aware…😳

That is very humane, which we are all… Aren’t we?

If that occurs, it might be worth making this as a sticky to entice new comers to participate… Perhaps reiterate the poll on a yearly basis could reveal the tendencies…