Excalibur consistently forces a crash

adamjrichman

DESCRIPTION

Every time I invoke the shortcut, ⌃+space, Premiere crashes and requires a force quit and produces the classic "Serious Error" warning on its way out. This seems to happen with at least one specific project I'm working on, as if I start a new project and trigger Excalibur it seems to load fine (tested in Premiere 2020).

I've read in another thread there's a debug version of Excalibur I could load and then send a report. That seems the best way to get useful information, as it literally triggers every time I open it.

SOLVED IT BY

Solved this by changing shortcut to HYPERKEY (capslock) + A. 🤷‍♂️

I don't have anything else in the system bound to the other shortcut so dunno what the issue is, but this is working for now!

ENVIRONMENT

Excalibur version: Latest 1.1.2
Premiere Pro version: 2020 and 2021 produce the same result within this project file
Operating System and version: macOS 11.2.2
Accessibility options properly added (including the fix from another thread where you uncheck, then restart, then check again and load Premiere)
New world scripting enabled.
The project file is a mere 15.7mb and includes mostly prores footage. 🤔
Other plugins and extensions loaded in Premiere include: Beat Edit 4, Transcription, Premiere Composer, Frame.io, Arrow, Compass, and Watchtower. Have tried hiding/closing all non-Knights plugins and same result.
Two monitors if that's relevant.
Mac Pro, 3.2ghz 16-core Xeon W, 96gb RAM, Radeon Pro W5700X 16gb

Sir_Ivan

Interesting. Beat Edit might have a conflict with Excalibur, the former needs New World Scripting off.
The fact that you fixed the problem with assigning different shortcut to Excalibur is strange.
What if you create an empty project, add sequence with couple of clips there, select on of the clips and try to call Excalibur (set it back to ⌃+space).

You said you use Hyperkey, so you have Karabiner installed?

letins

Sir_Ivan

Hello, Ivan,

I just installed Beat Edit mid-project, it disabled New World Scripting and now I can't use Excalibur.
I would like to know how to revert the changes I have done (no idea how to do it, tried quick google search too, but I'm out of time), I rather have Excalibur than Beat Edit.
Now I'm forced to save project every minute because my muscle memory goes straight to custom shortcuts, that causes instant crash and loss of work I have done ☹️

adamjrichman

Yea, Beat Edit prefers it off, but will function (very slowly) with it on. Frustrating because everything else wants it on. And yes, using Karabiner Elements for my Hyperkey.

Will see about testing that out when I get a break from this project. Still finding my way around Excalibur! I did use it to solve an issue with my Loupedeck CT — the dials just would not function at all to adjust scale, motion, rotate, etc as advertised. So I programmed some keys to the +10 and -10 position, etc trick and then bound those keys to the dials. Works quite well, although a bit laggy since it's gotta move through the dial command and then Excalibur, but still much better than clicking into the little blue numbers or double-clicking the "motion" text within the Effects Panel like a chump. 😂

Sir_Ivan

Hahah, I like how you use one 3rd party tool to work with another 3rd party tool!

Sir_Ivan

letins Excalibur should prompt you to enable New World when you open Premiere.
If this doesn't happen, then do this:

Press cmd+F12 (ctrl+F12 on Windows)
Premiere Pro console will show up (be careful to not do any changes there)
Switch view to Debug Database View (click hamburger menu near panel name “Console")
Type in search “world” and check if those settings are enabled:
ScriptLayerPPro.EnableNewWorld
AME.ScriptLayer.EnableNewWorld

If any of those are disabled, turn it on and restart Premiere Pro.

letins

Sir_Ivan Thank you so much for this. Silly me didn't notice that before when I tried to press ctrl+F12 I was activating different programs shortcut (DeskPins) and it did not bring up console in PP.

All good now 😃