Skip to main content
R
Ralf22499295i98j
Participating Frequently
April 30, 2024
Answered

Automation Blocks No Animations

  • April 30, 2024
  • 3 replies
  • 1919 views

I recently bought me the Automation Blocks extension, because it seemed promising to simplify my work with Premiere Pro. Unfortunately, no keyframe based automations, for example the Ken Burns automation, wouldn't work. Other non-keyframe based automations like renaming files work properly. So I don't think it's a general problem with the extension.

Any recommendations about this problem are appreciated.

 

Cheers, Ralf.

 

Mod note: Please tag Automation Blocks questions with the "SDK" label. Thank you!

    This topic has been closed for replies.
    Correct answer Mathias Moehl

    I am looking for ways to make AB more compatible with different UI languages. Currently it is such that tools writen in English Pr might not work on systems with other languages. Most tools work fine, but the one which access clip parameters like "Scale" or "Opacity" don't work, because they have other names in other languages of Pr. So you can write a tool in German Pr, for example, which manipulates the "Skalieren" of a clip, but if you wrote a tool in English Pr which manipulates the  "Scale", Automation Blocks does not know that it should look for "Skalieren" instead of "Scale".

     

    You can change the UI language of Pr quickly as shown here, without the need to reinstall it:

    https://www.youtube.com/watch?v=W9yg88C6g44

     

    1. in Pr use the keyboard shortcut to open up the console window:

        Mac:     fn + command + F12

        Win:     ctrl + F12

    2. in the Console, make sure the Debug Database view is open:

     

    3. search in the Console for "ApplicationLanguage" and set it to "en_EN" for English

    4. restart Pr


    UPDATE: I just published Automation Blocks for Pr 1.1.001, which fixes the language issues and now also supports non-english Pr versions properly.

    3 replies

    Mathias Moehl
    Community Expert
    Mathias MoehlCommunity Expert
    Community Expert
    May 27, 2024

    Hi Ralf, are you able to share your project with me such that I can take a look? Either share it here or if you don't want to share it publicly open a support ticket at https://aescripts.com/contact/?direct=1&product_id=2279 (which will also be assigned to me).

    Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
    R
    Ralf22499295i98jAuthor
    Participating Frequently
    May 28, 2024

    Hi Mathias,

    I just sent you the project via the Aescripts support form.

    Thanks for your help!

    R
    Ralf22499295i98jAuthor
    Participating Frequently
    June 1, 2024

    Thanks to the great support of Mathias the problem could be solved.

    The problem was my German version of Premiere Pro. When Automation Blocks wants to change parameters in the Effect Controls panel, it looks for the English label of the effect. And certainly can't find it in the German version of the App. Changing to English as App language solved the problem.

      Mathias Moehl
      Community Expert
      Mathias MoehlCommunity Expert
      Community Expert
      May 1, 2024

      Hi Ralf,

      do you get any error messages? The more details I know, the quicker and better I am able to help.

      Also, it would be very helpful to see at which block the error happens.

      When you open the block code, during the execution of the tool the currently executed block is highlighted (you can see that is a kind of flickering on the blocks while the tool runs) and when it stops at some block with an error, this block stays highlighted.

      Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
        R
        Ralf22499295i98jAuthor
        Participating Frequently
        May 2, 2024

        Hi Mathias,

        thanks for your reply. Wenn I open the block code and run the script, the comment block is highlighted. No step of the script is being executed, but no error message is displayed either. I just get a "done" message in the main window of the extension.

        Greetings, Ralf.

          Mathias Moehl
          Community Expert
          Mathias MoehlCommunity Expert
          Community Expert
          May 2, 2024

          Hi Ralf,
          could it be that the tools you tried only process the currently selected clips in the active sequence and you forgot to select clips?

          Because this sounds like the tool finished successfully without any issues.

           

           

          Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
            R Neil Haugen
            R Neil Haugen
            Legend
            April 30, 2024

            @Mathias Moehl  any comments?

            Everyone's mileage always varies ...
              Terms & ConditionsAccessibility statement
              Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices