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

Proxy with Offspeed Footage

New Here ,
Oct 18, 2022 Oct 18, 2022

Copy link to clipboard

Copied

Fergus Hammon - picking up thread from Cined.com - please see documented issue:

https://community.adobe.com/t5/premiere-pro-discussions/multiple-bugs-in-premiere-22-5-when-using-pr...

 

Can confirm this persists in the newest Premiere release 23.0.0 (Build 63).

 

Example:

  • OCF (Original Camera Footage - Canon C500 MkII): 59.94fps (offspeed for slowmotion).
  • Proxies from OCF (matching timecode, fps, aspect ratio, audio channels).
  • Project/Deliverable 23.976fps.
  1. OCF ingest into Premiere (via Media Browser).
  2. Proxy Attach to OCF.
  3. OCF interpreted from 59.94fps to 23.976fps.
  4. Proxy and OCF no longer match frame for frame.
  • 'Workaround' is to apply Clip Speed/Duration in Project panel, in this case 40%.
  • It's a counterintuitive and illogical mismatch of features that demands an entirely different workflow and can be hard for users to catch or troubleshoot.
TOPICS
Editing , Formats , Import

Views

55

Likes

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

Community Expert , Oct 19, 2022 Oct 19, 2022

This is what engineering will typically say: The issue is you're using the effects backwards. Interpret footage was NOT designed to be used as you are using it. Speed/Duration was.

 

So the proper effect for clip speed changes such as slo-mo workflows ... is the Speed/Duration effect. Which will work correctly with proxies.

 

'Interpret' was designed for changing from say one 'cadence' to another. Period. As in, going from 29.97 fps to 24 fps. Which is a more complicated and very different proce

...

Likes

Translate

Translate
Community Expert ,
Oct 19, 2022 Oct 19, 2022

Copy link to clipboard

Copied

Likes

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
Community Expert ,
Oct 19, 2022 Oct 19, 2022

Copy link to clipboard

Copied

This is what engineering will typically say: The issue is you're using the effects backwards. Interpret footage was NOT designed to be used as you are using it. Speed/Duration was.

 

So the proper effect for clip speed changes such as slo-mo workflows ... is the Speed/Duration effect. Which will work correctly with proxies.

 

'Interpret' was designed for changing from say one 'cadence' to another. Period. As in, going from 29.97 fps to 24 fps. Which is a more complicated and very different process.

 

Neil

Likes

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
New Here ,
Oct 21, 2022 Oct 21, 2022

Copy link to clipboard

Copied

Thank you Neil. I have a follow-up question and have conflicting experiences with offspeed media then. I'm cutting a project with Alexa LF footage. 23.976fps. Some shot at 40fps. Imported via Media Browser. 40fps footage reads and interprets as 23.976fps upon import. Why are there inconsistent offspeed workflows that are dictated by the camera system and metadata they each do or do not provide?

Likes

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
Community Expert ,
Oct 21, 2022 Oct 21, 2022

Copy link to clipboard

Copied

LATEST

Was the camera setup using a "project" speed in-cam at 23.976, with a segment recorded at higher speed for slo-mo use?

 

Which is what my BMPCC4K does. I set a 'project' frame rate, and in the menus also set the framerate for off-speed shooting, which is normally faster so that when played back at the project-set speed, it's in slo-mo. Premiere auto-sets that to the same speed on playback as the project speed. So the visual result is slow motion.

 

Which is a typical slo-mo process in pro cams.

 

Is that what you're seeing?

 

Neil

Likes

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