Atlas007

Imagine if they weren’t… 😏

If I understand well, Logic doesn’t allow queueing scenes while cells are already queued?

To Bypass all Control Surfaces, you don’t need to move the playhead (or "get the cursor back to bar 1"). If you opt to rebuild your project, you don’t need to open the problematic project either. Keep it closed, don’t load it in Logic. Instead: Create a fresh new project (without using a project template). In that new project (gradually) import the data from the (unloaded) corrupted project into the newly created fresh project (do not use any project template). ⚠️Proceeding gradually for that data importation is highly advisable to avoid importing eventually the problematic (corrupted) data. ⚠️Also, avoid (to ever) loading two projects (or more) at once: always close the current project before either starting a new one or loading another one. ⚠️ Dragging data from an opened project to another one is notorious to corrupt opened projects, often insidiously…

I wonder if using text slashes from a special musical font could to the trick… IIRW, I have read somewhere in LPH someone had devised a way to enter customized musical symbols by entering an ascii code (corresponding to the letter/symbol slot) or something like that… Or perhaps using resized re-positioned slash note heads (hiding the note tails)? (just brainstorming here… I didn’t try those… admittedly only weird workarounds)

Many people reported various issues running LP10.8.1 with macOS Ventura which 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 that rogue control surface should normally solve the issue permanently. If the above isn’t pertinent or doesn’t help, chances are 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 solution would be to rebuild the project by mean of (gradually) importing the data from the (unloaded) corrupted project into a fresh new project (not using any project template). ⚠️Proceeding gradually for that data importation is highly advisable to avoid importing eventually the problematic (corrupted) data. ⚠️Also, avoid (to ever) loading two projects (or more) at once: always close the current project before either starting a new one or loading another one. ⚠️ Dragging data from an opened project to another one is notorious to corrupt opened projects, often insidiously…

… 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: