• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Why is the footage moving/trimming itself?

Engaged ,
Sep 08, 2024 Sep 08, 2024

Copy link to clipboard

Copied

Question: Why is the first (only so far) layer of footage in my comp moving or trimming itself by a frame as soon as I add Roto Brush? Is that supposed to happen, or is it a bug? How can I make it stop?

 

Specs/info:

Windows 10

AE 24.6.1, comp 30 fps

(Dynamic Link comp from Premiere Pro 24.6.1, sequence 30 fps)

Footage: Prores 30 fps

Rotobrush 3.0

 

Please see screen recording: https://vimeo.com/1007529137/4f4cd7638a?share=copy

This is "Why is the clip moving/trimming itself?" by Jeff M on Vimeo, the home for high quality videos and the people who love them.
TOPICS
Dynamic link , Error or problem , How to

Views

146

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Engaged , Sep 23, 2024 Sep 23, 2024

@Ishan Y thank you and sorry for the confusion. I forgot to update this thread. The problem was operator error... I thought I was working with a 30 fps comp, but it turns out I was not. I just made a mistake. As soon as I made sure the footage, the original Pr sequence, and the Ae comp were all 30 fps, then the problem went away. *disappears into bushes like Bart Simpson*

Votes

Translate

Translate
Adobe Employee ,
Sep 23, 2024 Sep 23, 2024

Copy link to clipboard

Copied

Hi there,

Sorry for the issue. Could you try the latest beta and let me know if you still see the issue? If you do, could you share a sample source file with me through a private message? I'll try to replicate the problem on my system and share it with the engineering team. 

 

Thanks,

Ishan

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Sep 23, 2024 Sep 23, 2024

Copy link to clipboard

Copied

@Ishan Y thank you and sorry for the confusion. I forgot to update this thread. The problem was operator error... I thought I was working with a 30 fps comp, but it turns out I was not. I just made a mistake. As soon as I made sure the footage, the original Pr sequence, and the Ae comp were all 30 fps, then the problem went away. *disappears into bushes like Bart Simpson*

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 30, 2024 Sep 30, 2024

Copy link to clipboard

Copied

LATEST

I'm glad to hear you found a solution to your problem! Thanks for updating us. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines