you could probably do that with the "custom move / resize" action:
1 Like
Hi Andreas, I run into unnormal crashes with LogicPro, as I installed the Alpha today and followed yesterday instructions to block F1-F12 keys via BTT
there might be a relationship? It is fully reproducible.
What: Creating a blank new session (no plugins from any developer inside) -> select Logic's Drummer = crash.
Also: Any project opened, go to Files -> Import and choose any of the menu entries (e.g. Import from other session) = crash.
How can I delete the Alpha version and go back?
I deleted the activation group to block F1-F12 already. I used that Apple Script from Max to get the SideCar activated. I think, inside there was nothing to trouble Logic.
Holymoly! 
Crash Report Number 8:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Codes: 0x0000000000000001, 0x0000000000000020
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1615]
VM Region Info: 0x20 is not in any region. Bytes before following region: 4342497248
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 102d54000-104b64000 [ 30.1M] r-x/r-x SM=COW /Applications/Logic Pro.app/Contents/MacOS/Logic Pro X
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Perplexity says:
The crash report indicates that Logic Pro X (version 10.8.1) crashed on macOS 15.3.1 due to a fatal error triggered by the application calling the abort() function. The crash occurred in the main thread, with the termination reason being “Namespace SIGNAL, Code 6 Abort trap: 6.” This suggests that the application encountered an unrecoverable error, likely related to dynamic type casting or memory handling.
Key Details from the Report:
1. Crash Cause:
• The crash was caused by a dynamic type cast failure in Swift (swift_dynamicCastFailure), as indicated in the stack trace of libswiftCore.dylib. This typically occurs when an object is being cast to an incompatible type.
• The issue may stem from a specific function or plugin attempting to access or manipulate invalid data.
2. Application-Specific Information:
• The abort() function was explicitly called, which is often used by developers to terminate the application when a critical error is detected.
3. Potential Contributing Factors:
• Third-party plugins: Crashes during initialization or scanning of plugins are common in Logic Pro if a plugin is outdated or incompatible with the current macOS version.
• Compatibility issues: macOS 15 (Sequoia) has introduced changes that may cause older software or plugins to malfunction.
6. System Context:
• The system was recently booted (470 seconds uptime), and System Integrity Protection (SIP) was enabled.
• No specific hardware issues were noted, but software compatibility remains a likely culprit.