BeatEdit V2 for Premiere Pro is a very useful plug in for editing to the beat

Post published:April 9, 2021
Post category:Adobe AEscripts BeatEdit Creative Cloud JonahOnPremiere New World Scripting Premiere Pro
Post comments:0 Comments

For the editors who aren’t musicians or just want a quick speed up to their editing workflow, BeatEdit V2 is a Premiere Pro script from mamoworld tools available at AEScripts (which I will talk about in the future).

BeatEdit detects the beats in your music and generates markers for them in your Premiere Pro timeline. Create automatic edits in sync with the music, or let BeatEdit assist your manual editing process.

This is an awesome and quick to use tool. Great for creating an edit of photos or just to give you edit points on the beat.

Any time you are editing to the beat this will speed up your workflow, and the $99 will be worth it in a few jobs.

BeatEdit is in the Window Menu Extensions

This is the window. You select a music clip in your timeline and hit load music.

This will load the track and after a few seconds.

The drop down at the top lets you chose sequence or clip markers.

And here you select how many beats get markers, I chose every 4, but should have done more.

You then hit the create makers button.

And you get this result.

There is much more it can do and this video will explain the rest.

I have run into a problem with the script though having to do with the new world scripting engine of Premiere Pro, so to use it you need to switch to the old scripting engine (which will stop the text entry script Excalibur from working) and unfortunately it doesn’t have a way to quickly turn new world on and off.

So you will have to activate the old scripting engine and restart to get it to work, and to get any extensions working that use the new New World Scripting Engine.

First hit command -F12 to call up the Premiere Pro console.

Then from the dropdown menu at the top select Debug Database view.

Now type in “newworld” and it will show the following 2 commands, AME.ScriptLayer.EnableNewWorld and CriptLayerPPro.EnableNewWorld and make use to set them both to true. A quick restart later and you will have re-activated the New World Scripting Engine.