Inspiring

Answered

Rendering and Exporting With Wrong Edits

Forum|Forum|7 years ago
July 2, 2018
3 replies
8923 views

I have run into a conundrum. I have a project that is literally edited one way, but exports or renders with clip cuts in a different way altogether, and I am not sure how to fix this. I tried restarting premiere, after deleting all the render files. But every time I render or export, it ignores what I actually have, and exports with the video shifted (time wise) under the edits I've made. So the edits are in the right places, but the underlying clip has shifted so the edits fall in the wrong spots.

I've searched and searched this board for an answer, so forgive me if I missed it.

This topic has been closed for replies.

Correct answer FlannelDuck

All. I am not the brightest here. I figured out what the issue was here: Proxy Workflow with Interpreted Footage // THE ANSWER

To save clicking:

"If you're shooting at 120fps and you want your footage to look like it's playing back in slow motion, you have to tell Premiere to treat the footage like it's playing back at the timebase of your sequence, say 23.976, by going to Clip/Modify/Interpret Footage, then entering in the timebase of your liking.

However, if you try to create proxies from these interpreted clips, Premiere sends the clips to Adobe Media Encoder flagged with their original frame rate. The resulting proxy is out of sync with the interpreted footage because it's playing back at its native speed rather than the interpreted speed, rendering it useless."

The issue was both that I am using interpreted footage, and proxies. The proxies are out of sync with the original clips. I only noticed this when I went to toggle off the proxies to see what it looked like that way, and suddenly saw that all the cuts are out of sync with the originals like that. Oh boy. Guess I gotta head back to a clean timeline anyway, and scrap all the proxies for the slow motion stuff.

Thanks for all the help.

F

FlannelDuckAuthorCorrect answer

Inspiring

All. I am not the brightest here. I figured out what the issue was here: Proxy Workflow with Interpreted Footage // THE ANSWER

To save clicking:

"If you're shooting at 120fps and you want your footage to look like it's playing back in slow motion, you have to tell Premiere to treat the footage like it's playing back at the timebase of your sequence, say 23.976, by going to Clip/Modify/Interpret Footage, then entering in the timebase of your liking.

However, if you try to create proxies from these interpreted clips, Premiere sends the clips to Adobe Media Encoder flagged with their original frame rate. The resulting proxy is out of sync with the interpreted footage because it's playing back at its native speed rather than the interpreted speed, rendering it useless."

The issue was both that I am using interpreted footage, and proxies. The proxies are out of sync with the original clips. I only noticed this when I went to toggle off the proxies to see what it looked like that way, and suddenly saw that all the cuts are out of sync with the originals like that. Oh boy. Guess I gotta head back to a clean timeline anyway, and scrap all the proxies for the slow motion stuff.

Thanks for all the help.

Jeff Bugbee

Community Expert

Ah yes, that would explain it. I'm hoping they do more upgrades to the Proxy workflow regarding issues like this. At least throw up a warning that there's a sync issue due to proxies.

Also, tag your reply as Correct in case anyone else runs across this thread.

F

FlannelDuckAuthor

Inspiring

Yeah. This seems like something they should have thought of. And it also explains why my proxies appeared to have large segments at the end that were just one frame, frozen. The proxies were the full length of the underlying full-res media, but since the proxies were created at 60 FPS without being interpreted, they were shorter. So, to make up the difference, PP just extended the final frame out, to match the length of the full-res clip. Not exactly and elegant way of handling that.

ill tag that reply as soon as I’m back at my PC. I wasn’t sure what the etiquette on that was around here so I hesitated.

S

SAFEHARBOR11

Participating Frequently

More info please, help us to help you.

Mac or PC, and Premiere version?

What format of clips, from what camera?

Variable Frame Rate clips as found on many cell phones these days can do weird things with timing.

Screen grab of Export Settings panel?

Thanks

Jeff

F

FlannelDuckAuthor

Inspiring

Mac running OS X 10.13.4
Premiere CC version 12.1.1 Build 10

Canon 80D, .MOV All-I, 23.976 FPS, constant framerate

The issue isn't just relegated to export. It first showed up while just rendering either selection or work area. I thought exporting might produce the right video. It produced the same thing as the previews even though "Use Previews" was unchecked. I don't think a screengrab of the export settings will matter since the issue also rears its head with rendering. Any rendering.

R Neil Haugen

Legend

In your preferences, find where the media cache and cache database are located ... close PrPro. Manually delete everything in those folders. Reboot, re-launch, and see if that helps.

Neil

Everyone's mileage always varies ...

F

FlannelDuckAuthor

Inspiring

Ok. Here is the sequence of events after following your instructions:

1. Checked sequence to make sure that it was still edited correctly. CHECK
2. Rendered work area. CHECK (It's worth noting that, originally, the thing would render something like 506 frames. this render only had to render a little more than 400 frames).
3. Played back preview, preview was now not only cut incorrectly, but two clips showed up as the Media Pending screen.

4. Deleted renders again

5. Re-rendered. This time got a Rendering 506 frames, frame count. So the formerly missing video was clearly back.

6. Re-rendered preview still edited incorrectly.

7. Deleted renders again.

8. Observed timeline was still showing correct edits.

9. Got more frustrated.

R Neil Haugen

Legend

I rarely need to render a sequence, though I know others do quite a bit. And therefore I don't normally use previews in exports either.

Are you having playback issues?

Neil

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded