Speeding Up Footage Results in Lost Frames

Participating Frequently

Hello, thanks I guess... If it is fixed it is long due...

Tested a simple speed ramp at 3000% speed, with a clip h265 4k 10bit 420 50 fps interpreted to 25fps with and without proxy (low bitrate mp4) also at 25fps (interpreted in media encoder from 50fps to 25fps to match interpreted source footage).

It worked. No weird frame skipping. Finally!!!

I can only know if it works all the time with further testing.

When will it be available in main version?

By the way... the files i use are from Fujifilm XT3 (h265 4k 10bit 420 50 fps Long GOP). these files make premiere and computers struggle a lot! Davinci Resolve handles it smoothly but not perfectly.

I believe ALL-I are supposed to have smoother playback, but in my testing this ALL I fujifilm xt3 files are even worse or at least equal in performance.

Is there any plans for improving h265 performance in premiere?

M

Michael Grenadier

Legend

not sure I understand. when you talk about ALL-I, you're talking about every frame being discreet? If so, I don't think they could be Long GOP (bwdik)

creophoto

Known Participant

This is NOT the fix and it is ludicrous that this glitch continues to this day.

https://s3.amazonaws.com/uploads.uservoice.com/assets/223/071/286/original/speed%20changes%20issues%20and%20problems%20in%20adobe%20premiere%20cc%202020%203mbps.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJF4UXUF6KJMEJFQQ%2F20200911%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200911T131814Z&X-Amz-Expires=1800&X-Amz-SignedHeaders=host&X-Amz-Signature=905e2d7b84123684d011eea763578d722e2d843c6ca327cbce4489719860ed90

Participating Frequently

No it is not.... Its a shame that after several updates this problem isn´t fixed.

creophoto

Known Participant

Seriously. I'm sick of using Premiere 2019 because of this one issue. I use speed ramps for every single project and this is the one holdup preventing me from using 2020.

If anyone from Adobe sees this, someone else has already uploaded a recording of the glitch. "Dropped frames" isn't really an accurate description. It only happens on clips ramped up to speeds greater than 799%. As soon as you hit 800%, it displays random frames while playing the time remapped clip.

How on earth is this an acceptable output for a professional product?

Participating Frequently

This method worked for me. I was having the same problem, when changing speed to faster rates, trimming the clip randomly and preventing me to expand it to the totality of the footage. This is a major bug, since nowadays everybody uses editing techniques based on speed changes and speed ramping, timelapses, burstlapses and so on. Adobe has to address this quickly. But it is Adobe we are talking about, they fix and upgrade some things and cripple others that were right to begin with...

Participating Frequently

Well... It worked once... now i cant get it to work again

Vincent.

Inspiring

That didn't work for me.

Seth Pleasants

Participating Frequently

I've tried this, it doesn't work.

Seth Pleasants

Participating Frequently

Still having this issue with Premiere Pro 14.2

I can't believe this has gone on this long. I thought for sure it would be fixed in this latest update. Sad

M

Michael Grenadier

Legend

are you sure both source and sequence frame rates are 24 fps. People often shoot in 24p which is actually 23.976 fps. If the source and sequence don't match exactly, it might be a source of the problem. Are you cropping and scaling your source footage to fit in a 1080x1080 sequence? As a test, maybe try matching the sequence settings to your source and try the speed adjustment to that... Might be an issue combining the scaling with the speed change... What you're doing is not a standard workflow (not that there's anything wrong with it) but just trying to narrow down where the problems happening...

Participating Frequently

Source and sequence frame rates match.

I did notice that if I imported coth clips shot at 60 fps and 24 fps into one sequence, I have to change the intrepretation settings of the 60fps in in the project bin.

It all seemed to be working, but alas, Premier feeds off my sanity and I'm having the same issue yet again. Tried removing any motion adjustments and/or key frames but to no avail.

Participating Frequently

Alright, what seems to be a solution:

I have zero idea why, but for last resorts I always just try nesting the sequence which seems to give clips a fresh start. Pretty much cut the clip and mapped speed as I would have wanted the final product to look. After I figure out how I want the cuts and speeds to look, I set the clip that was speed ramped to 100%, nest it, then speed ramp it to what I wanted it to be.

Don't know why it works and hopefully it isn't a one off solution.

But seriously adobe, you're better than this. Work arounds aren't actual solutions and now I have an extra step in my work flow I don't need.

Participating Frequently

Has anyone solved this problem? I'm still having it and it's driving me crazy as I have client projects due. Adobe this bug should have been fixed MONTHS ago - all of the threads I'm finding are from November but I haven't found a solution that works.

M

Michael Grenadier

Legend

Looks like this is your first post in this thread. Please tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card. And your source properties and your sequence settings. There is a post in this thread that's labelled as correct answer. Did you try what it said?

For me, these issues are usually solved by changing the time interpolation settings. Optical Flow is pretty amazing. The fact is that speed changes may always be problematic depending on the frame rate and how the motion falls against the frame rate. Tweaking the speed change can sometimes make a big difference. If the problem is premiere based, you might try after effects or davinici resolve...