Adobe Premiere Pro Dropping Frames

[brianjoseph401]

hey everyone can you please help me out here I just did a custom built PC here are my specs

windows 10 home

32gb ram 3000 ddr4

8700k I7 not overclocked

1070 ti graphics card

1 500 ssd Samsung hard drive

it seems that adobe is still playing back footage and dropping frames like crazy and it isn't stabilizing the footage fast at all can someone please help me

I would love for it to stop dropping frames when I play back the footage and there is also a long delay from when I press the play button until it actually plays I got have cc monthly cloud if someone can please help me before I cancel it.

[R Neil Haugen]

What media made by what, what is the drive it's stored on and connections to the mobo, and what effects are you adding?

Neil

[dukeeastwood]

It'S CC 2018, it's a horrible broken mess that 100% DOES NOT WORK, it's not your computer your footage or you, it's Premiere's incompliance.

Reinstall CC 2017 and try that.

[brianjoseph401]

can I still get CC 2017?

[dukeeastwood]

in creative cloud find Premiere in the list and click the down arrow to the right of "open."

then under other version you can choose CC 2017 (11.1.4) to install.

[R Neil Haugen]

PrPro for H.264 runs best with 8-10 cores 3.8Ghz or above, with up to 10GB of fast RAM per core. That's the latest from the major builders.

Looking over your computer specs, that's a pretty decent CPU, only 6 cores (like mine) but they're ​fast​ cores (faster than mine), which is very good. The RAM could be improved, you're running just over 5Gb/RAM/core.

There is something that might significantly help ... you seem to be running a single SSD drive for OS/programs/media/cache ... adding an m.2/Nvme SSD drive to that, and moving media & project files to that would be probably a significant uptick in performance for you.

Adding another SSD for a cache drive to split things up over a third drive after adding the project/media drive might give some additional performance boost.

I would suggest first trying the m.2/Nvme project/media drive.

Neil

[dukeeastwood]

except if you read the forums that you yourself responded to, you'd know that even users with 8-10 cores, 3.8Ghz or above, and with up to 10GB of fast RAM per core still have the exact same problem.

When are you going to understand that your theoretical take on what works with Premiere is wrong?

[R Neil Haugen]

It's not a theoretical take on PrPro.

When are you going to get off the kick that EVERYONE has to have exactly the same issue you're having?

Are there issues ... well, of course. Never said otherwise. Is everyone having horrible troubles? Well, actually ... no. Not opinion at all. I'm personally doing ok, and know some others with all kinds of gear who are also doing fine. I know a couple with good gear who are having troubles.

This forum over the years has been a good bell-weather. When there are issues, the daily posting here can sky-rocket. We've had many days where within an hour, there are three to four pages of new posts. Most new releases have been like that. This last release ... nothing like the previous ones. Yea, some issues popped up for sure. But again, compared to past releases, not even in the same ballpark.

Recently we've had days where there are a page and a half of posts ... for a full 24-hour period. That's a dramatic drop in trouble posting here, at the same time the user numbers are up. So that would seem to be solid indication that the percentage having horrible issues ain't that high.

Which, as again I've stated many times, doesn't mean that if you're the one with the screwed up workflow, it's any less painful. Nor does it mean that it's your fault and not Adobe's PrPro program ... some bugs affect only a very small sub-set, and those are typically the nastiest ones to get sorted. Like, duh. And if they can't get it working on your gear, they don't deserve your money.

I've seen way too many folks here and on the hardware forum that have taken steps with gear and had their machine start working as expected to accept the crap that no one can. They do. Not everyone, but the vast majority. Most of the problems posted here over years for performance have been issues entirely predictable given the OP'S gear, media, and workflow. And were solvable by basic knowledge of what just works (as opposed to "this SHOULD work") and trouble-shooting 101.

Setting up a one-drive machine like the original poster has is problematic, and always has been. Just three years ago, for decent processing, we all went for a pretty standard five-internal drive setup. Os/programs; cache; project files; media; previews/exports was a typical setup.

That's now changed ... two good internal SSD's can give nearly the same sustained throughput, especially if the second one is the m.2/Nvme type. Heavily tested for hard data by Bill Gehrke, the tech guru of hard data, and by many other users. Add a third drive for cache/preview files, you've get a setup better than the old 5-drive systems.

There's nothing about that which is opinion, it's data based. And tested across many systems.

What puzzles me is why you are so needing to rant and rant and rant across numerous posts. I understand being ticked royally when an app screws you up. PrPro, SpeedGrade, Me, and AfterEffects have all dumped on me at times too. And yea, I certainly posted the odd rant and complaint. But then went about either fixing the issue or moving on.

Resolve is out there ... the new 15 version is off public beta, you can get it free or (as I have) the "studio" paid version. You're most welcome to use it if it does better for you. If so, cancelling your CC subscription is a great way of participating in the great test that is a free market ... Company X doesn't make a product that works for you, stop buying from them and go with who does. Try Avid. If you're on a Mac, try FCPx ... which has the advantage of being setup for Mac users in a way non-Mac video apps can't do things.

Neil

[rodneyb56060189]

may I offer you a nice hot cup of green tea ??

[R Neil Haugen]

Um ... not really ... but you got an oatmeal stout there, I'm all yours!

Neil

[gvsuk]

Agree. Its a glitch in Premiere and they do not know how to correct it. Basically its something that CS6 can do without any problems, but CC is where the issue starts. I have been trying to sort this since early July after upgrade. DO NOT let anyone tell you its your Spec or your Media format. It is a Bug and I have proved it many times to the Muppets at Adobe. Give them your money, thats all they want to know about!

[brianjoseph401]

Im thinking about going all the way back to CS6 but I’m unsure about it and if not then I’m going to purchase resolve.

[brianjoseph401]

I can’t believe I had to go all the way back to cs6 can anyone help me with the stabilization why does it take forever for like 10 second clip it shouldn’t take that long. Like 4 mins

[rodneyb56060189]

I'm sorry that you are having trouble. As you know this forum is just users of the program helping each other to try and fix stuff or give advice.

I personally think for your problem you'll have to be patient and give all the information possible regarding your problem ( I don't know what dropped frames means). I don't know what sources you are using, what you are exporting as, and basically don't no nothin. There are smart people here who can help but they need info to get started if they have the time.

There is a link somewhere about " how to ask for help" somewhere here... which is a guide to supply as much info as possible cause that is relevant to solving issues.

Good luck.

[megacinn]

No , not at all.

You don't have to go back to CS6,.....going back to at least 12.0.1 (the january 2018 version) is sufficient enough.

Try it, it takes you maybe 10 min installation time..no risk....I'm 90% sure that all your problems about stuttering, export/import problems will be gone. it will work super smooth.

And I totally agree with all those who completely reject these always occuring idea :

"give me your specs ....'ummm I see your rig is not perfectly suited for that type of media .....16GB Ram ...you should have much more....your SSD is not of a perfect typ...use M.2 from a special manufacturer .......

...thats (as said before) theoretical nerd stuff.  I'll guaratee , that , if you follow that advices , and invest a big bunch of money........nothing will change your situation  ....except ....reinstall an older CC-version up to 12.0.1 !

I asked one of the highest adobe representatives for a clear hardwarerequirement for our needs.

That means at least 4Kp30 in H264 and/or HEVC , with 2 tracks in full quality in realtime (playback).

what did I get as an answer:

a multicore processor at least from the Intel 6th gen (thats it ...no refence to .how many cores , which Intel I7 and XEON ? and I9 ?

a decent graphics card with at least 4GB of VRAM (thats it .. no refence to any special Nvidia or ATI chip )

so, if that is enough ...your rig is more than enough.

tell you what ....

I'm working on an ImacPro with 32GB of RAM . During my projects, which all are 4kp30 H264 material 100Mbit , and MP4 wrapper with h264 codec, even with HEVC on my timeline ...

.....I can run at least 2-3 tracks smoothly at the same time !

Nearly all of the footage is stabilized by the warpstabilizer (works for 2 years now perfectly even on much less powerfull macbookpro's ).

If I have a look at the memoryconsumption , there is under no circumstances, more then 50%used.

what is the difference ... I have been used CC up to version 12.0.1 ....

....starting with the totally messed up version 12.1.1 nearly nothing worked nearly as good as before. To document these problems to adobe, I switched installations between these 2 versions for 3 times....reproduceable .... it is clearly the changed hardwareacceleration in 12.1.x

that was the reason why I already quitted my subscription.

Adobe was so ....cannot tell this in decent words.... and refused any single problem ...

Therefor I cannot recommend anyone staying patient and wait.... I'm not sure that they are willing and able to change that developmentline in the near future !

It seems that the only force by what they are driven right now, is currently to make the biggest possible money out of the situation before the adobe hype goes down ....

don't complain anymore .... either try working with the 12.0.1 , or make your decision to find a much better suitable way to work....mine is now for the next 1-3 years ..resolve 15.

and @ Neil    we really appreciate your always present and technically substanciated help. But wouldn't it maybe one step better to investigate the real needs and userproblems.

Sometimes , if someone asks for a HighQuality-but-LowBitrate-Codec, isn't it  quite a bit oversized ,giving him advices for an Intermediatecodec (LowBitrate-poor quality)......just an example from another thread.

or , has PremierePro become an offline-Editingsystem (or why repeatedly telling about Proxyworkflows)

...it is not always the hardwarespecs

[brianjoseph401]

I really cant thank you enough version 12.0.1 is prefect YOUR A LIFE SAVERRRRRRR.

[R Neil Haugen]

Loved your post.

The data on what works best for hardware in general right now wasn't from Adobe folks. It's from guys building and testing rigs built for serious video post, like Puget Sound Systems and Safeharbor Computing.

Along with the information from Bill Gehrke's ppbm8 testing with many results from different users all exporting the same carefully designed project file while logging apps record real time data on every computer bit.

Hard data. Not opinions.

How many can afford the flat out best design machine? Yea, that's a good question. A lot of us can't. I'm running a 6 core i7, 32GB of DDR4, and a GTX1060/6-GB. With all SSD drives for my internal discs used within PrPro.  I'm looking for my next build. My long time builder of custom systems for me moved away so I'm getting bids to see what I can afford.

Probably an 8 core at or OC'd to around 4Ghz. 32 to 48GB of RAM. And cringing at the bill. Ah well.

The performance record of the 12.x builds is odd. All over the place. I'm running pretty decent 1080 or 4k, but I know of guys with more hardware that ain't. And someone else with nearly identical setup to the guy who's running for crap, is screaming along.

So one can easily say "this is the gear that generally performs better", as it clearly does. Real world, not what it should theoretically do.

And one needs to understand there are some factors we can't figure out causing similar systems to perform radically differently.

For some, no 12.x build runs good. For others, 12.1 is great but 12 1.2 is horrid. And for the majority of users 12.1.2 is fine.

As another user I've no clue why. If any of us knew that, well ... we'd all be happier.

The QC engineers are aware of the problems some are having, as they have posted in a few threads here both asking for projects to test and such. But naturally  ... they never share with us any information on anything until they release a new patch build.

So ... work has to get out. If that means using 12.1, 12.0, 12.1.2, 2017, or Resolve or Avid ... each user needs to do what gets their work done.

Neil

[gvsuk]

I have rolled back to each version and even 2017. the problem is still there and after one and a half hours of remote link with a Senior Technician from Adobe he could not solve the problem. I have 3 PC's here and we linked to two of them that both have Prem 2018 latest build and both have the same issue of dropping frames, but unfortunately he had very little success in solving the problems. However, my 3rd PC has CS6 and NO cuda card fitted, yet it is lightening fast and played everything we threw at it. We put about 8-10 dissolves which showed up Red (needed rendering) but it just played as if they were already rendered. Eventually the Tech tried some .MP4 footage on his super duper computer with Premiere 2018 cc on it and had the same issues as me.... Dropped Frames at Dissolves! He said he was going to take it to developers. If you want to take advantage of the new features that have been introduced after CS6 then I would suggest maybe waiting until (if ever) Adobe fix the bug.

[R Neil Haugen]

Painful ... big ouch.

Hope that senior tech gets some action on that.

Neil

[getho]

i've been banging on about a time-remapping bug for several years now.  I mention this randomly as the direct approach has failed.

[R Neil Haugen]

Time remapping can be tricksy. Especially going from one NLE to another as they all handle it so differently. The best person I've read or heard explaining remapping in PrPro points out first a ton of mis-conceptions as to what actually happens, then a ton of gotchas to avoid.

Doesn't seem like it should be that complicated.

So ... I'd love it if you filed more UserVoice reports on that. The more, the likelier we get an easier and more expectable process.

Neil

[getho]

I've done screen caps, had it confirmed on this forum by other users and sent it to adobe, I get one or tw replies, then tumbleeds.

[brianjoseph401]

I just couldnt handle it anymore I moved over to Final Cut pro x and very happy so far. Creating proxies are so easy

[dukeeastwood]

we all need to do this... FCP needs to make the jump, release a version that runs on windows and Premiere will be gone by the end of 2019... Adobe is garbage.

[rodneyb56060189]

It's nice to see compassion expressed freely, as it often leads to telling good stories. Like "Hamlet" and so on.

thanks