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
‎Oct 29, 2019
03:45 PM
For what it's worth, I filed this last week: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38874376-bug-premiere-pro-2019-unresponsive-during-impor
... View more
‎Oct 29, 2019
03:43 PM
I have the exact, same issue with Premiere Pro as of the past couple of weeks and I'm suspect it's a sour interaction between Windows 10 and Premiere. When I import a similarly-sized h.264 file, I get the "Not Responding" warning in Premiere's title bar. It does eventually clear up after several minutes, but until then, it's unusuable. The same thing happens when I drop one of those MP4s onto the timeline for the first time. This after the PEAKs have all been built. The app just sits unresponsive. The funny thing is, while this is happening, one core of my 7900X is running at 100%. The rest of them are at or near idle. Something related to Pr or Pr's interaction with Windows 10 is suddenly single-threaded (apparently?) and killing my system. The rig: https://www.jasonvanpatten.com/gaming-rig/
... View more
‎Oct 22, 2019
01:48 PM
Neil - I know you didn't mean any offense with your reply and are just trying to be helpful. I do appreciate that. Just beware: some of us have been doing this "building systems" things for decades. Literally: decades. I understand that systems can react differently, as can software on said systems. 🙂 As the phrase goes: This ain't my first rodeo. Project files sit on a striped pair of SATA3 SSDs Scratch space is all on a single 512GB M.2 (not an NVME) drive Some of the footage is on a striped pair of SATA3 7200RPM spinners. Other footage on a stiped pair of SATA3 SSDs. Storage space and speed isn't a concern. The free drive space is measured in hundreds of gigabytes, sometimes a few terabytes; I'm clear there. No problem. There is a very specific "thing" happening with Premier, or with Premiere's interaction with Windows 10, that is causing only one of the cores on my 20 vcore rig to hit 100%. And the moment that happens, Premiere goes unresponsive. If I let it go for several minutes, it will eventually import the file. But I have to go through this same crud the moment I try to place that file/clip onto a timeline. Sit, wait, and wait, and wait, and waaaaaait. This after all of the PEAK files have been created, etc.
... View more
‎Oct 20, 2019
05:33 PM
Are you certain of that? You have Resource Monitor up and watching all 6 cores during an h.264 import?
... View more
‎Oct 20, 2019
03:35 PM
A further follow-up: it seems placing one of these files on the timeline is also a painfully slow, single-threaded operation. Yes, I know long-GOP formats are less than ideal, but I have the CPU to handle it, along with a lot of available cores. Is there no way to multithread the placing of the file on the timeline? Like the import: one core goes straight to 100% and the rest are basically idling.
... View more
‎Oct 20, 2019
04:29 AM
4 Upvotes
I have to agree with Rob. Using Pr 2019 with 4K MP4 files is just obnoxious now and it didn't used to be on my same rig. Clearly something has changed; be it with Windows 10 or with Pr.
... View more
‎Oct 19, 2019
05:28 PM
Right Neil, I believe it. I've simply not been using Pr for some time, so I have no idea when it began.
... View more
‎Oct 19, 2019
04:44 PM
I wish I could offer some useful bits of help or information; all I can say is, "Me too." I seem to recall this not being an issue for Pr. I've not been editing in quite some time and just got back into it recently. And: I've run into this same issue every time I edit. My 4K/60 h.264 75Mbit/sec files are about 5.7G in size, and each one locks Pr up solid for a few minutes while it imports it. During said, one of the CPU cores on my 7900X gets pinned to 100%; one other core is at around 50-70%, and the rest of them are sleeping. This smells like the h.264 import is suddenly single-threaded, and very inefficient. Formerly, Pr would just snorfle the large h.264 files in and go. Windows 10 Pro, fully updated Pr, fully updated OC'd 7900X that can easily chew on 4K h.264 files and spit them out like they're nothing.
... View more
‎Jun 17, 2019
03:45 PM
Kevin-Monahan wrote Said the dude that takes high speed turns on the track with his overclocked 'Vette. LOL. Hey! It's not my fault you like experiencing race tracks in slow motion... 😄
... View more
‎Jun 16, 2019
02:08 PM
1 Upvote
https://forums.adobe.com/people/Warren+Heaton wrote Overclocking should be avoided for a video editing workstation. I'd question that statement and have plenty of years of experience to defend my position. I've OC'd every processor I've ever run Premiere on, and I've never had an issue with it. Proper overclocking with appropriate over-volting AND cooling is perfectly fine for a video editing workstation. And it will speed things up quite a bit, too.
... View more
‎Jun 16, 2019
12:54 PM
https://forums.adobe.com/people/Warren+Heaton wrote Fewer, faster cores are usually the better choice for video and motion graphics. If you think you're going to jump into 3D, then more cores. I definitely wouldn't consider the 28-core (56-vcore) processor if Premiere were the only app I'd be using. The lower-core-count Xeons would be a better choice for sure. If you're doing a lot of H264, that's accelerated via CPU if you're running Intel processors and an up-to-date OS. Not with the Mac Pros; the Xeons don't have the the required hardware for accelerated h.264, as far as I know. Unfortunately, Apple hasn't supported processor upgrades since the G3 and G4 processors CPU swaps aren't supported by Apple, but are readily doable. Anyone with even the slightest PC/computer assembly skills can pop the included Xeon out and replace it.
... View more
‎Mar 06, 2019
08:19 AM
zoranp64457894 wrote Does the Adobe Premiere and After Effects support SLI - two Graphics cards? The last time I checked the NVidia profile for Pr, it's "Single GPU only". So even if you have a pair of GPUs SLI'd together (like me), Pr will only use one of them when it's running. If you want Pr to use both GPUs, you'll have to go into the NVidia control panel and manually disable SLI system-wide before running the app.
... View more
‎Feb 25, 2019
02:28 AM
1 Upvote
RjL190365 wrote With the RTX series, NVIDIA introduced a new technology called Tensor cores, while at the same time began depreciating legacy CUDA performance. NVidia has done nothing of the sort. CUDA crunching is still as important as ever with the new RTX cards. It's just that the tensors were added. Something else is going on with the OP's issue. I can speculate that it may have something to do with the new version of the CUDA libraries that were released with the newer drivers, but again: that's just a speculation. Adobe may need to do some work with Premiere and said new libraries.
... View more
‎Feb 23, 2019
10:08 AM
Back when I submitted my results to Bill for the benchmarks, he mentioned something about Premiere (and other CUDA apps) not allowing my GPUs to keep their memory overclock. Specifically, when I OC my video cards, I not only bump the core clock speed up, but also the memory speed. Here's a quick screen shot of my 2080Ti OC in MSI Afterburner as an example: I've added a +110 to the Core Clock, and a +801 to the Memory Clock. Well, Bill was right. I watched Afterburner one day while I was messing around in Premiere. Sure enough, the GPU's clock kicked back down to its default. Hm. Apparently this is a thing with the NVidia driver, and it can be changed. Obviously: do this at your own risk, etc, etc, etc. But what you're going to need is everyone's favorite NVidia hacking tool: the NVidia Inspector. Releases · DeadManWalkingTO/NVidiaProfileInspectorDmW · GitHub Again: use carefully and at your own risk. You can ROYALLY screw up your NVidia driver with this app if you're not careful. Fortunately all you have to do is re-install the driver to get back in gear. Scroll down to Section 5, and look for the entry: CUDA - Force P2 State That should be "On" by default. Set that to "Off", and then click the "Apply Changes" checkbox in the upper right. Done. Now if you've OC'd the memory on your NVidia GPU, CUDA apps will not kick the memory speed back to OEM.
... View more
‎Feb 23, 2019
09:54 AM
thomasm88119238 wrote I'm considering getting an Intel 9900k and overclocking it, it performed very well in pudget's tests. I'll definitely need to do more research, I don't have much experience overclocking. I don't think you'll go wrong with the 9900K, specially if you can kick its clock speed up. It can take it. There are lots of examples/guides/etc out there on how to do it. The key things to remember are: Cooling Power(!) Increasing the second will keep the chip stable under load, but it'll also significantly increase the chip's heat production and output. Therefore, good cooling is incredibly important; otherwise the chip will get into its "I'm not very happy" temperature zone and start throttling itself for protection. Keep it coooooooool and it should crunch away with no problems.
... View more
‎Feb 19, 2019
06:05 PM
thomasm88119238 wrote My question is, are any of you able to edit 4k h.264 (like from a GH4, Sony A7SII etc) with smooth playback and scrubbing without proxies or transcoding? If so, what kind of hardware are you running for it? Furthermore, which hardware components have the greatest effect on scrubbing performance? I don't have any footage from either of the cameras you mentioned. I do have 4K/60 h.264 (75Mbit/sec) and some 4K/60 h.265 (25Mbit/sec) footage from various video game recordings. My system has very little trouble scrubbing, playing back, etc. I can't really address your AMD CPU and whether or not it's good enough for this kind of role. My system starts with Asus Rampge VI Extreme motherboard, and to that I added a de-lidded, overclocked (4.7GHz) Intel 7900X. I've also OC'd my 64GB of DDR4 to 4GHz. GPUs: 2 x 2080Ti GPUs, in SLI; they're also OC'd lightly. But they really don't come into play much unless I add accelerated effects. My gut tells me you may be throwing too many cores at the problem and not enough raw CPU clock speed. Premiere likes a good balance of threads and speed, leaning more towards speed. You have 12 more threads than I do (7900X is a 10-core/20-thread), but I've got the CPU speed.
... View more
‎Dec 04, 2018
11:13 AM
2 Upvotes
https://forums.adobe.com/people/R+Neil+Haugen wrote That list is just a general list of one's they actually tested, and is nowhere near complete. Ignore it. Match the needed specs and you're fine. I continue to hold that Adobe does potential and new customers more confusion than good by having that list published at all. They really need to get rid of it completely and just list minimum NVidia, AMD, and even Intel specs for GPUs. Then call it a day. See: just about every PC game produced since ... forever?
... View more
‎Oct 02, 2018
01:30 PM
RjL190365 wrote Adobe will only be testing current-generation GPUs (Turing, in this case) for the MPE GPU acceleration. Adobe should consider just listing the chip families as "supported" vs leaving new users to guess, to help prevent this sort of confusion.
... View more
‎Sep 28, 2018
12:03 PM
Ares6 wrote Can i ask to request GTX Titan X with Maxwell architecture add in supported cards in next updates of Premiere? Or its already in "plan"? I hope some experts read this and post answers. The Maxwell series cards should already work fine in Premiere. Including the Titan.
... View more
‎Aug 03, 2018
09:49 PM
This isn't actually focused on video editing or any such activity. But it is hardware related and may be of interest to the hardware geeks here. Before we go too much further: I'm still actually stumped as to what's going on here. I have a long-standing tier 2 case open with NVidia on it for more information, and they've not come back with anything useful yet. Let's dig in. Again remember: this is NVidia GPU related, but not aimed at editors. Just "geek" stuff. Fast Display Back in July, I picked up the new Asus PG27UQ display. This is a 27" 4K display capable of pushing a 144Hz refresh rate. Key for: gaming. That is assuming you have the GPU(s) that can push 4K at high refresh rates. And I do: a pair of overclocked Titan X Pascals. Along with the new Asus, I grabbed 2 LG 4K/60Hz displays, and made it a trio. Cool. Here's where the fun came in. I have a second PC in my office that does video capture. It has an Elgato 4K60 Pro capture card in it, which operates using HDMI 2.0. As soon as I connected that card to the HDMI output of my Titan, the fast Asus display got clocked down to 120Hz. Hmmmm. Interesting. This, mind you, before doing any display capturing or mirroring or anything like that. The mere act of connecting the capture card up (which looks like a 4th 4K display to the Titan) did the trick. It's not the capture card's fault, either. If I disconnected one of the LG 4K/60Hz displays, the fast Asus display would clock itself back up to 144Hz. Some sort of GPU limitation. Hmm. Even more interesting. I un-SLI'd my system so I had 2 independent Titans running. When I did that, I could move one of the LG displays to the 2nd card. All 4 displays would run at their max refresh and resolution. This would further indicate some sort of limitation with the big Titan card. A throughput limitation. Bus limitation? Pixel clock limitation? Math is Hard Let's do some math. This is overly-simplified but it'll hopefully make sense, assuming I did my math correctly. 🙂 The overall throughput of all 4 displays running at their max rez/refresh should be something like this: 3840 pixels/line * 2160 lines/screen * 144 screens/second * 24 bits/pixel + 3 * (3840 pixels/line * 2160 lines/screen * 60 screens/second * 24 bits/pixel) == ~65Gbits/sec What about when the fast panel gets cut down to 120Hz instead of 144? 3840 pixels/line * 2160 lines/screen * 120 screens/second * 24 bits/pixel + 3 * (3840 pixels/line * 2160 lines/screen * 60 screens/second * 24 bits/pixel) == ~60Gbits/sec These numbers are interesting for a couple of reasons: 64 is a power of 2, where 65 is not. I wonder if there's some hard-coded bandwidth limit in the card that happens to fall on a bit boundary? And if the throughput attempts to go over it, the card responds by slowing the display down? PCI 3.0 x16 cards should be able to hit about 126Gbits/sec, give or take. Half of that is an interesting number: ~63Gbits/sec, which is just over my resulting throughput. Both cards are clearly operating at x16, per the BIOS and GPU-Z. But... maybe they aren't actually? Pixel Clock What about the pixel clock? It's not a stat NVidia has published for the Pascal cards. Again, it's all math (I think), and it's similar to the previous math but without the colors: 3840 * 2160 * 144 + 3 * (3840 * 2160 * 60) == 2.687Gpx/sec - full speed if I could 3840 * 2160 * 120 + 3 * (3840 * 2160 * 60) == 2.488Gpx/sec - what I'm actually getting Perhaps there's a 2.5Gpx/sec clock rate limitation? Another GPU To solve my little speed/throughput/whatever problem, I picked up an el-cheapo GT-1030 GPU. It's a single slot, low profile, and very low performance. But it's enough to run 2 4K/60Hz panels just fine, leaving my Titans to focus on gaming. Silly that I had to do it. Thoughts? Did it make sense? Any ideas WRT to the limitations I'm running into?
... View more
‎Jul 30, 2018
09:35 AM
MarkWeiss wrote The parameters are cryptic (even more so than NVENC) and numerous. I'm going to play with it a bit and see what it can do and what the resulting files look like. Thanks for that suggestion. Vouk's working on a complete UI re-design that will probably see the light of day at version 2.0. That should help make the parameters far easier to dial in. I've been outputting HEVC h.265 files with it since I snagged it. The resulting files are teeny (in comparison) and gorgeous.
... View more
‎Jul 30, 2018
09:12 AM
1 Upvote
avwtp wrote How is Vouk's dramatically better? I've had this NVENC plugin fail way too many times for way too many oddball reasons. Vouk's just works. Always. I haven't run into a single reason it doesn't assuming my hardware is doing the right thing. I can't speak to your BluRay and/or DVD requirements. That's not what I'm producing.
... View more
‎Jul 30, 2018
05:44 AM
avwtp wrote No idea how much the 1.12 plugin shares with NVENC mode of Voukoder's plug in but both have the same bad frame parameters I can't answer how much they share or anything regarding the bad frame parameters. What I can say is that Vouk is very active on his user forum and responds to questions such as what you've asked. I've long since abandoned this plugin and only use Vouk's now. It's dramatically better, and the author is quite reliable WRT communication. https://www.voukoder.org/forum/
... View more
‎Jul 29, 2018
11:45 AM
1 Upvote
Actually: I think I figured it out. In the "Manage 3D Settings" tab in the NVidia Control Panel, there's a selection that lets you enable/disable CUDA per card: All I had to do was uncheck the GT 1030 and voila: it's being ignored by Premiere.
... View more
‎Jul 29, 2018
10:46 AM
Hey folks - This might be better sent to the Hardware subsection, but it is about Premiere Pro. If the mods feel like it should be moved, no sweat. For reasons I can describe if folks are interested: I added a low-powered NVidia GT-1030 GPU to my gaming/editing rig, to supplement my two Titan X Pascal GPUs in SLI. Unfortunately, as expected, Premiere did its thing and latched onto that very low-powered card while exporting/rendering, and... well... I'm paying for that. The load on that GPU sky-rockets to 100% and evvvverrryyyttthhiinnnng sslloowwwss dooowwnnnnnn. It really is a pathetic GPU for anything other than powering two 4K/60Hz displays. I need a way to tell Premiere to ignore that card without disabling it in Windows. Is there any way to do that? Thanks.
... View more
‎Apr 17, 2018
06:32 AM
FelixUnderwood wrote I mainly edit :30 spots, so the time gain w/NVENC would probably be negligible. Oh absolutely. NVENC's advantage doesn't really come into play unless you're encoding longer vids. Minimum of about 5 minutes long or so; anything shorter and you're not going to see much of a speed-up.
... View more
‎Apr 17, 2018
06:01 AM
2 Upvotes
FelixUnderwood wrote Are there any 3rd party NVENC encoders out there that play nicely w/Premiere Pro you would recommend or would you recommend just sitting tight for now to see what Adobe might bring to the table in the future? This is one of the newer plugins available for Pr and AME: Releases · Vouk/voukoder · GitHub Installing it is an "at your own risk" sort of thing because Adobe does not support it. And to be perfectly honest, I don't expect them to ever support NVENC. The reason is a belief that NVENC isn't "good enough". This belief stems from the fact that when people try NVENC, they use the same bit rate that they would normally use with a CPU-based encoder (such as x.264). The results: very blurry video with a significant loss of detail. NVENC can't intelligently compress video. It hasn't the capacity for that. All it can do is a "dumb" detail removal in order to hit a target bit rate. So if you try to, say, encode a 1080p video at 7Mbit/sec with NVENC, you're going to end up with a trashy looking output as compared to say, a CPU-based h.264 encoder. But crank the bit rate to 15Mbit or 20Mbit/sec, and the NVENC results will look identical (if not better) than the h.264 encoder does at 7Mbit/sec, and it won't tax the CPU in the least to do it (and it'll complete the encoding in a fraction of the time). The down side: much larger files. My gut tells me that this lack of understanding in how NVENC actually works (and the results it produces) is what's going to prevent Adobe from adopting it. Not because they don't understand it, but because they'll have to spend an inordinate amount of time explaining the difference to users. So with that, I'd just use the plugin "at your own risk" and complete your projects in half to 1/4 the time.
... View more
‎Mar 30, 2018
04:35 AM
1 Upvote
Smielz wrote So i've never had this issue before, but for some reason now when I try to upload a video to youtube that I exported at 1440p...it only shows up as 1080p for youtube. I wouldn't worry too much about it. It's on YouTube's end, not yours. Sometimes it can take days (literally) for a vid to be transcoded up to 1440p or higher. Sometimes it never happens at all. Their transcoding system can be very buggy at times and there's nothing you can do about it.
... View more
‎Mar 23, 2018
08:06 AM
WMK wrote It's struggling to deal with 4K footage and large PrP projects, and I'm considering installing a faster GPU -- and a lot more RAM. Ultimately I don't think a new GPU or more RAM is going to help you with your 4K footage. I'll bet a dollar that it's your CPU that's tripping over itself during playback. It just isn't that powerful at all. For their time, the Westmere Xeon processors were pretty beefy and powerful. But that was 9+ years(!) ago. Today, they're useless beyond serving as a back-room email/web server and little more. They really don't have enough oomph to handle today's high-resolution workloads. If you have to stick with the MacOS/OS X/whatever-Apple-is-calling-it-today environment, your best bet is to buy a new iMac Pro and switch away from the Adobe suite. Adobe's software isn't as efficient in the Apple environment as, say, Final Cut Pro X. But pouring money into that old Mac Pro is, IMHO, just a waste. It's way past its retirement age.
... View more
‎Jan 16, 2018
06:38 AM
https://forums.adobe.com/people/Bill+Gehrke wrote Have you ever watched GPU Loading in GPU-Z to see if you can anywhere near 100% load both cards, and make me eat my words? I didn't watch during my last PPBM run to see if the second card got pinned or came anywhere near 100%. Bear in mind that my system serves dual purposes: I edit and play fast-paced first person shooter games with it. I can get both Titans to start crying "uncle!" when I play a couple of the games in 4K (scaled 150% from 1440p) at 140FPS. They'll both start bumping 70-75% use; this with SLI enabled, mind you. I've more than got my money's worth out of the spend. I'm very satisfied and happy with them, and looking forward to the next gaming beast that NVidia hatches. 😄
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices