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-proxies/td-p/13050078 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.OCF ingest into Premiere (via Media Browser).Proxy Attach to OCF.OCF interpreted from 59.94fps to 23.976fps.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.

Rustic Media

Known Participant

Answered

Proxy with Offspeed Footage

Forum|Forum|3 years ago
October 18, 2022
2 replies
713 views

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-proxies/td-p/13050078

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.

OCF ingest into Premiere (via Media Browser).
Proxy Attach to OCF.
OCF interpreted from 59.94fps to 23.976fps.
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.

This topic has been closed for replies.

Correct answer R Neil Haugen

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

R Neil HaugenCorrect answer

Legend

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

Everyone's mileage always varies ...

Rustic MediaAuthor

Known Participant

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?

R Neil Haugen

Legend

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

Everyone's mileage always varies ...