Adobe Community
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
jasonvp
Advocate
jasonvp
Advocate
Activity
‎Jul 09, 2020
09:31 AM
1 Upvote
Yep, I know about the playback and editing ease with ... "other" NLEs. It's one of the main reasons I've let my CC sub lapse and am no longer editing in Pr.
... View more
‎May 07, 2020
04:16 AM
1 Upvote
What do you mean? CUDA cores aren't used to produce output, they're used for rendering. The hardware encoder on the NVidia card is what's used for output.
... View more
‎Apr 15, 2020
09:06 AM
2 Upvotes
Hm. I seem to have found chfilm here as well as on the MacRumors site. Remember what I've promised: switch to Resolve. We have cookies. The likely answer to "Why isn't Adobe..." is that: it's a monumental effort to completely rewrite their NLE, or create a new one from scratch. It's what's needed, of course. The code base that Premiere is built from is cruft. Pure and simple. There's no breathing a surge of performance back into this old app; it needs to be forwarded to /dev/null and we start new. The problem with that is: during said design, development, QA, etc, how will Adobe keep folks subscribed to the Creative Cloud? Right now, they do so by pushing out new features (aka: feature bloat) for the app. That takes development time and effort, but it also keeps the money coming in. Throwing dev cycles at an entirely new NLE means the feature creep of Premiere stops. And it risks folks looking elsewhere. I don't envy their position here. I think they've painted themselves into a financial corner with the Creative Cloud thing, and it's not paying off for the end users. I've written long treatises about the performance of Adobe's software on a Mac. The basic summary is: it's not good, and hasn't been good since the late 2000s or so. Perhaps even before then. Mac users have a few choices, and neither one is an easy decision to make: If you're stuck with Premiere and the rest of the Adobe suite, consider switching to Windows. Ugh. Windows sucks beyond sucking, but Premiere sucks less on Windows than it does on MacOS. Changing your work environment is less trouble than changing your application, but I'm not in any way trying to minimize how difficult it is to change your environment. Just that it's harder to switch NLEs, for instance. Do the dirty, and switch NLEs. FCPX performs infinitely better on a Mac than Premiere does in either Mac or PC. By a long shot. But, FCPX's UI is... shall we say: challenging. Resolve, on the other hand, is an easier NLE migration to make because it's far more traditional in its layout. And its performance on Macs and Windows (and Linux) is astounding. Vastly better than anything Adobe is pushing out these days. Really: Resolve is the right way to go. Keep spending more and more money on expensive Macs, over and over again, and continue to get awful performance. I have to imagine that the "easy" path to take is the third one. It requires no effort. But at some point, even big movie houses who insist on the MacOS environment are going to have to take stock of the amount of time their editors are wasting waiting for Premiere to do a thing. And time being money as it is, I'd assume they'll come to the same sort of conclusion and re-think options 1 or 2. Ultimately, I don't think we should expect Premier to suddenly "get better" on a Mac. That will require a ground-up rewrite, and Adobe hasn't the cycles to do that (it seems). To that end, migration is my answer. Resolve is just that much better, in every way possible.
... View more
‎Apr 08, 2020
06:08 AM
You're running into a known bug with Premiere Pro that was introduced early last year in one of the 2019 updates. Adobe knows about this issue as of Fall, 2019, and are still working to remedy it. No ETA has been given on said fix. Your work-arounds are to transcode to a different format (which you shouldn't have to do), or just sit and wait for Premiere to finish the import. The import will finish. It just sends one of your cores up to 100% while it decodes the h.264 file; the slower your processor, the longer this process will take. The longer the file, the longer it'll take as well. But it will ultimately complete and you can begin editing it. Some of the documentation put forth suggests that this is due to "Variable Frame Rate". That's simply not the case in the least. This happens with VFR and CFR files of a certain type.
... View more
‎Mar 29, 2020
07:17 AM
Please read the OP. Then re-read it. When you're done with that, re-read it again. Just to summarize, the author already knows that this is a problem between Promise and Premiere. He got that from Adobe chat support. If that's not enough: https://community.adobe.com/t5/premiere-pro/premiere-pro-could-not-find-any-capable-video-play-modules-please-update-your-video-display-drivers/m-p/10862082?page=1 Note the "Correct Answer" given by Adobe employ Mitch_W.
... View more
‎Mar 29, 2020
05:20 AM
I'm not really sure how many different times I have to say this and why it's not getting through: this is a known problem with the interaction between Promise drivers and Premiere Pro on the Mac. It has absolutely nothing at all to do with permissions or any such thing. End users can't solve this. Developers at the respective companies have to. Full stop.
... View more
‎Mar 28, 2020
08:07 PM
I run Premiere on a Mac all the time, and don't have admin privs for my main user. That's a security risk. Pr runs just fine. Further, the article has NOTHING AT ALL TO DO with the problem at hand. The OP even stated in his original post what the problem is and why he's facing it. There are no "GPU drivers" for MacOS and there haven't been for a very long time. The error that Pr is throwing is very misleading, and in fact has nothing at all to do with the graphics subsystem of the Mac. It's a known problem with the Promise storage drivers and Premiere. I'm not having the same problem because I don't use Promise's overly expensive hardware or their badly written drivers.
... View more
‎Mar 28, 2020
07:43 PM
Administrator rights aren't necessary to successfully run Premere on MacOS. That article is full of misleading and/or inaccurate suggestions. The issue at hand here is the interaction between the latest set of Promise storage(!) drivers and Premiere. This has been a known issue since December or perhaps January. Promise has older drivers available that may (I can't emphasize MAY enough) work, you'll just have to find them and try. Ultimately, unless the OP is using a specific aspect of the Promise RAID stack, there's probably no reason to have the drivers installed at all. MacOS will see each of the drives in the RAID array, and you can assemble them into a software RAID set, bypassing the (very badly written) Promise drivers. Other than what I just suggested, there's nothing that can be done at the moment.
... View more
‎Mar 16, 2020
03:13 AM
1 Upvote
"As to why the Adobe engineers haven't assigned basic encoding to the GPU ... my guess is they figure a lot of the users are using GPU accelerated effects on their exports. Which ... depending on the effects used ... may or may not peg the GPU for the things already assigned to GPUs." I don't think that's it. Adobe has steadfastly refused to use hardware encoding on the GPUs since they've been made aware of it several years ago. NVidia's hardware encoder is on a completely different level than Intel's, but Adobe won't code to it. AMD's isn't as good as NVidia's from a speed perspective, but is catching up. Both produce stunning results in a fraction of the time it takes to do software encoding. CPUs are just completely inefficient when it comes to encoding h.264 or h.265. The code is there for Adobe to do it. The APIs are freely and readily available from both AMD and NVidia. This goes for both encoding and decoding; the GPUs are infinitely faster at both than the CPUs are. And they do it without affecting other aspects of the GPU, as well. The hardware encoder on the GPUs has no affect on the shaders (eg: CUDA cores, et al) that are used for the rest of the video processing in Premiere. Meaning you can hardware encode an h.264 while you're scaling it and applying other accelerated effects; it won't matter one bit. And Neil, I appreciate your fondness for the UserVoice, but in this case it's a "go nowhere" path. I've done the UserVoice thing. I have a more direct path to Adobe's developers as well, and have submitted a request for hardware encoding/decoding. It's gone nowhere. They simply don't have the resources (or interest) to do it.
... View more
‎Mar 13, 2020
07:23 AM
I think Canon provides an RAW application that you can transcode into something Pr can understand. And you'll have to do that until Adobe gets that RAW format grokked by Pr. Just understand that when you do that, you'll lose all of the RAW controls that you would normally have in Pr; everything will have to be exposed/white balanced/etc in the Canon app.
... View more
‎Mar 11, 2020
11:24 AM
1 Upvote
I rented a C500 Mark II last weekend which produces similar RAW Light files. I don't know if they're 100% identical to what comes from the C200, but I suspect they're close. On my monster Mac Pro (2019) with the 16-core Xeon, the simple act of trying to play the footage sent all cores to 100%. Playback was basically impossible. I don't know if the same thing is happening on your rig; you might want to watch your system's CPU load while you're trying to play the files. Does your rig go right to 100% on all cores? If so, uh... game over.
... View more
‎Mar 06, 2020
10:40 AM
1 Upvote
"Shame on Apple for telling people to deprecate a superior technology. The onus is on them to bring their Metal tech up to par, if not exceed what they're telling people to diminish." I'm not sure that's exactly what's going on here, though it may seem like it from the end user perspective. Rather, Apple is abandoning a GPGPU tech that the market didn't latch onto very well. That being OpenCL. Unfortunately, this sudden "context switch" to use a computer geek term, caught a few application developers by surprise. See: Adobe. The resulting appearance is that things are all amiss in Apple-land. Metal appears, for all intents and purposes, to be far superior to OpenCL. For... well... everything. But it's going to be up to the app developers to step up and re-code to the Metal APIs. That means Adobe and company have a lot of work cut out for themselves. For better, for worse. And it certainly also appears as though Apple didn't warn the developers this was coming; truth be told they've been making noises about this for some time. Metal is the way forward on MacOS. It's up to the app developers, not Apple, to step up.
... View more
‎Mar 05, 2020
11:34 AM
The "shutdown" vs "reboot" thing will depend on what's actually crashing. And this would require digging into the system logs, which I'm more than happy to do had I access to them. 🙂 It's sorta "my thing". That said, it's an easy test to do. Watch temperatures during the import. See what happens before the reboot. And transcoding long-GOP files is, of course, doable. But the whole long-time benefit of using Premiere over other NLEs (of past) is that it's not required. And shouldn't be. As soon as this bug is addressed and fixed, it'll be less of an issue, thankfully. In either case, it's up to the OP to try that test.
... View more
‎Mar 05, 2020
11:21 AM
I'm going to go way out on a limb here: the filetype is h.265 or h.264, long-GOP. Correct? How big are the files you're trying to import? Measured in several gigabytes in size perhaps? The reason I'm asking is that there's an annoying bug with Pr when it comes to importing long-GOP (h.264/h.265) files in that only one CPU core is used, and it's pegged to 100% utization during that. It happens in both Windows and MacOS. (Yay, consistency? ...) Can you watch the temperature of your CPU during the import? I'm wondering if your iMac is getting worked so hard during the import that the CPU is hitting its "Oh crap, save myself!" temperature, and rebooting the rig? It's just a theory, but one worth looking into.
... View more
‎Feb 19, 2020
06:49 PM
1 Upvote
While it's common practice to blame VFR, that's not the culprit here. First and foremost: OBS produces honest-to-God CFR files when the end user tells it to. Secondly, Premiere inhales VFR files just fine; and has for a couple of years now. I've already gone through with the developers to make sure that's the case 2-3 years ago or so; can't remember when exactly. Ultimately, let's stop blaming VFR please. OBS and a few other game recording apps (and some cameras, and some other apps) are doing something to the h.264 files that Premiere's decoder just doesn't like. It's unclear what that is. Transcoding to another CODEC, or even re-transcoding to h.264 will work around the issue. Also: just waiting will work around the issue. Premiere will import the file, ultimately. It'll just take a while as only one of the CPU cores is put to work.
... View more
‎Feb 17, 2020
07:00 AM
2 Upvotes
There's nothing you can do in Premiere that will fix this bug. There are no settings to change, no caches to reset, etc. All of the usual tutorials and videos and whatnot don't apply to this problem. It's code related; something accidentally introduced into Premiere back in early 2019, and isn't fixed yet. You have a few options: Live with it. As you found, the files will ultimately import. The bug involved causes Premiere to send only one of your CPU cores to 100% while the import is happening. The rest are untouched. So you're basically waiting for one core to complete the import. Transcode to something other than h.264 after you've recorded your game play. Lots of CODECs you can use and choose from; Handbrake on the PC is probably helpful here. Transcode from h.264-->h.264 in Handbrake. I can NOT confirm this will work properly on the PC; it doesn't work properly on the Mac. The Mac Handbrake version is ... not really usable. But the PC version may be. The goal here is to write an identical h.264 file out that Premiere will work with. Same resolution, same frame rate (CFR), same bit rate, etc. Something OBS does to the h.264 files is poison to Premiere, but Handbrake may be able to fix it. You'll have to test it out. Use Resolve to edit your game play footage vs Premiere.
... View more
‎Feb 15, 2020
10:36 AM
OBS (and a few other apps) is doing something to the h.264 files that Premiere just doesn't like. This changed in Premiere sometime during early 2019; it's a bug that was introduced in the app, and is known internally. What isn't clear is why OBS' h.264 files trip Premiere up so badly. As far as I can tell, there's no setting to change within OBS to get around this. Using a different CODEC such as Ann suggests isn't really a good alternative since it drastically increases the load on the system while recording. The whole idea behind using NVENC while recording is to avoid any loss in in-game frame rate. Using any other CODEC will introduce lag and loss of FPS while playing. No go. I've been working through some work-arounds outside of OBS recently, and it looks like transcoding from h.264 to h.264 in another application will do the trick. That sucks because it takes a bunch of time. But until this bug is fixed within Premiere, it's one work-around. On the Mac, I can't use Handbrake. For some reason, Handbrake on the Mac refuses to write CFR files, even when you clearly set it to do CFR. So that's out. But it may work on PCs, I simply don't know. On the Mac, I can use Compressor to inhale an OBS-produced h.264 and output another h.264 with the same settings. That new file is inhaled into Premiere immediately without any hiccups. I can not tell what the difference is between these files that would make the difference. I can look at their output in MediaInfo until my eyes bleed, but there's nothing obvious that jumps out. This is where the devs at Adobe need to jump in and figure out Whiskey Tango Foxtrot is going on. In the mean: Find an app that can transcode h.264-->h.264 and retain CFR Just import your OBS-produced files natively and waaaaaaaaaaaaaaaaait. The import will complete, eventually. The longer the file and the slower the processor, the longer it'll take. But it will import. (Use Resolve to edit)
... View more
‎Feb 14, 2020
05:56 AM
2 Upvotes
This is a known bug within the newest versions of Premiere Pro, introduced sometime in early 2019. Long-GOP formats such as h.264 will lock Premiere up on import in a lot of cases. Files produced by OBS Studio are one example. The file WILL import ... eventually. You'll just have to wait for one of your processor cores to finish processing it. While you wait, Premiere will go "Not Responding". But, it is processing and is importing. The longer the files, and the slower the processor, the longer this will take. Adobe knows about the bug; they've reproduced it internally. No ETA on a fix.
... View more
‎Feb 12, 2020
11:19 AM
2 Upvotes
This is a known issue with the latest versions of Premiere Pro, assuming you're importing h.264 long-GOP file formats. Premiere locks up while it's trying to import the files, sends one of your CPU cores to 100%, and sits there as if it's doing nothing. It IS processing the files. It just takes a while. And given how old/slow your CPU is, it's going to seem like forever. Try importing a single clip at a time and see how long it takes. The longer the file and the slower the CPU, the worse it's going to seem. But based on my experience with this bug, it will complete the import.
... View more
‎Feb 04, 2020
07:22 PM
This is a known bug with Premiere and at the moment there isn't a known work-around. It was introduced into Premiere sometime in 2019, and the team at Adobe knows about it, have reproduced it internally, etc. But there's no ETA for a fix. In all cases, Premiere will recover. You just have to sit and wait for it, depending on how fast your CPU is. The process involved is entirely single-core bound. Faster processors will get through this issue easier.
... View more
‎Jan 30, 2020
12:44 PM
No, not at the moment. The HEVC files that the iPhone produces will load into Premiere Pro on the Mac ... eventually. There's a lag in importing them and it seems like Premiere has crashed because it's gone "Not Responding". But it does eventually load them in. Whether those same files will load into the version of Premiere on Windows is unknown to me. It sounds like a lot of folks have failed at that. Apple does something to the iPhone's HEVC files that throws the Windows version of Premiere off. It's not VFR; that has nothing to do with the problem. The issue is something else. For now, Handbrake them into CFR h.265 files and Pr should import them.
... View more
‎Jan 28, 2020
05:59 PM
1 Upvote
I installed the trial for Bandicam and am able to reproduce this with Premiere. I can't quite tell the difference between the resulting h.264 files; at least nothing that's blatant or obvious. I am surprised that I absolutely can not get Bandicam to produce a CFR file. Even though I tell it to specifically do 60FPS/CFR, it comes out variable. OBS has absolutely no problems maintaining a solid 60FPS constant. Either way, the Bandicam vid gets imported into Premiere in a snap, but the OBS one takes a moment. And Premiere goes "Not Responding" while doing so, per the bug that's filed.
... View more
‎Jan 24, 2020
04:12 PM
2 Upvotes
Actually, NVidia's encoder is the champ. Far and away; signficantly better quality (and faster) than Intel's or AMD's. They've been doing it much longer than either of the other two companies and have vastly more experience with it. The issue is that Pr isn't using it or the one on the AMD GPU. That's an Adobe decision.
... View more
‎Jan 24, 2020
03:13 PM
2 Upvotes
Let's make the waters murkier still, Neil: All modern-day NVidia and AMD discrete GPUs have hardware encoders and decoders built into them for h.264 and h.265. Unfortunately, at the present time, Premiere Pro won't use any of them. They would help the application significantly insofar as handling of the long-GOP formats by: Speeding up the importing and decoding of them (NVDEC for NVidia, and AMD's VCE) Speeding up the exporting of them (NVENC for NVidia, and AMD's VCE) These pieces of "extra" hardware, if you will, have absolutely no effect on the GPU's performance when it comes to other tasks like displaying data, or even CUDA computing. They're extra pieces of silicon sitting on/in each GPU that are basically: idle. It just takes an API call from the running application to activate and access them. When it comes to encoding with them, there are trade-offs. They're able to achieve their hitless encoding of h.264 and h.265 (highly compressed files) by: stupidly compressing. They don't have the intelligence to properly compress the data, so they just: remove detail. Dumbly. That means that the results, for instance, of a 10Mbit/sec NVENC h.264 will look like trash compared to a 10Mbit/sec CPU-encoded h.264 file. Answer: crank the bitrate up. Disk space is free, right? Once you do that, you end up with a much larger file, but the creating of said is literally a snap of a finger. Yeah. The hardware encoders on the GPUs today are incredible. So are their hardware decoders. And I think that's what our OP sort of wants with Premiere. Unfortunately, he's not going to get it right now. At least, not with NVidia or AMD.
... View more
‎Jan 24, 2020
03:04 PM
1 Upvote
Premiere Pro currently utilizes the discrete GPUs for the list of accelerated effects that Neil posted. Further, it'll use the GPU to scale a video up or down during export; GPUs are quite good at doing that. Everything else is handled by the CPU including importing, decoding, rendering, and encoding during the export. There are aftermarket, non-supported plugins that will allow you to use the NVENC encoder on your discrete GPU to export a video much faster than your CPU can do it. But, you're on your own (as far as Adobe is concerned) if you install it. Fortunately, the developer of the plugin is awesome, and he has his own forum for support, suggestions, etc. Check it out here: https://www.voukoder.org/ If your source footage is h.264 or h.265, or some other long-GOP format, then without the help if your iGPU, it's all CPU-bound. So the faster the CPU you have, the smoother the playback. However, as I suggested earlier, take a look through your settings and see if the hardware options is enabled or disabled. I don't remember where it is, exactly. I think it's in the Project settings, not the General ones.
... View more
‎Jan 24, 2020
02:45 PM
1 Upvote
There's some confusion in terminology here and that may be part of the issue. Rendering is not encoding. As it turns out, the Intel iGPU has QuickSync available, and last I knew, Premiere will use QuickSync to encode and decode h.264 files. I'm not on my Windows rig at the moment, but if I'm not mistaken, there is a way to disable that. I think it's "on" by default though. I strongly suspect that if you have the hardware encode/decode option checked, then Premiere will just use the iGPU and not the discrete GPU you have installed. Someone from Adobe might need to correct me on that one. If that's the case, it's why your discrete GPU isn't doing much. Also of note: Neither NVidia GPUs nor AMD ones are used for encoding or decoding. At all. They are used for rendering, if and only if you're using accelerated effects; that's what Neil was trying to tell you. But for encode/decode, that's all either CPU based, or Intel iGPU based depending on your project settings.
... View more
‎Jan 23, 2020
10:00 AM
This is actually really interesting. I've been tracking a bug with Adobe on the handling of h.264 (long-GOP) files that was introduced into Pr sometime last year. They're still working on fixing it (no ETA) but it's interesting that you're seeing the behavior only with OBS-produced files. As it turns out, OBS is what I use, as well. There's gotta be something specific about the h.264 file that OBS is writing that's tripping Pr up. I'll ping Kevin so he can add your post to the list of reports regarding that bug. I'd also love it if there was any way you could post up the Bandicam vid somewhere? I'd like to DL it and see if Pr inhales it quick, very much unlike all of my OBS footage. Do you have an S3 or Dropbox account or something?
... View more
‎Jan 22, 2020
02:37 AM
You have a fairly low-end PC, as you noted. You're not going to be able to get Premiere to utilize your NVidia card for simple editing and playback of your source material. Everything you're doing is CPU-based at this point. So like the others suggested, create proxies. It should speed things up a bit once they're created and you're editing with them. But they'll take up more disk space; bear that in mind.
... View more
‎Jan 21, 2020
01:36 PM
What kind of source footage are you editing? And what kind of rig are you running Pr on?
... View more
‎Jan 21, 2020
09:24 AM
It might be. As much as I love Apple and MacOS, their latest few OS updates have been ... challenging. I most certainly would not be willing to dive head-long into beta testing for them. I'd back-grade and try again with Premiere. I can run Pr on 10.15.2 without any issues.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices