"OS Version:            Mac OS X 10.15.3 (19D62e)"   Did Apple release 10.15.3 yet?  Or is this a beta/pre-release version of the OS? ... View more

I have one of the new Mac Pros and Premiere works on it for me.  Others have been having some crashing and lock-up issues, but I haven't (yet?) experienced them.  Mind you I'm only editing h.264 files, so my experiences are a bit limited.   I don't own the Afterburner card because it's only good for ProRes decoding.  And since I don't now, nor ever will use ProRes, it made no sense for me to invest in that.  Further, from what I understand, Premiere doesn't (yet) tap into the Afterburner while decoding ProRes.  That could possibly change in the future, but your guess is as good as mine when that might happen.   As for the GPU: it seems to, just fine.  Accelerated effects get accelerated as they should.  It also can use the AMD hardware encoder to output h.265 files in real time (eg: 10 minute 4K/60 video takes 10 minutes to export).   ... View more

There's no need to use Handbrake to convert files.  OBS Studio has all of the same "guts" to it as Handbrake does.  They're both built on top of the most excellent FFMPEG libraries and application.  The answer here is, ultimately to tell OBS Studio to create CFR files versus VFR files.   ... View more

When the machine gets into this "funk", have you tested with other CUDA-enabled apps to see if they work properly?  This is smelling like an NVidia driver issue, potentially. ... View more

> Premiere isn't that good at working with mulitple GPUs.    Unless something has changed over the past few years, that's not correct.  Premiere is exceptionally good at scaling across multiple, independent GPUs.  In fact, it's stunningly good at it, as we all learned with the Premiere benchmarking.  What does throw a monkey wrench into that is SLI'ing two of them together.  The only issue there is that Premiere stops seeing two GPUs and only sees one.  And only uses one.  It otherwise works fine.   But, our OP has four, and NVidia has long-since gotten rid of > 2-way SLI.  So he's not running SLI; that's not the issue here. ... View more

Lots to write here between bites of my late lunch.  Let's see...   Your GPUs aren't being used by Premiere for playback of h.264 footage or any other footage for that matter.  Premier would use the GPUs if you had accelerated effects on your timeline, but you're not there yet.  For raw playback of the footage you have, it's all CPU.  Adobe could and should go a long way to include access to AMD's VCE and NVidia's NVDEC for handling h.264/h.265 files, but, sadly, they've avoided doing that.  These hardware encoders/decoders would make handling playback of h.264 much faster as it'd all be done in: hardware.  However, regardless of that, your older AMD GPUs don't have those encoders/decoders, so that rant is pointless. 😉   Your Mac is the reason I stopped editing on Macs for almost 7 years(!)  Apple stepped on a land mine with the Mac Pro 6,1, and it's just a very limiting device in so many ways.  Even the top of the line GPUs are weak, and all of the hardware in the device is poorly cooled.  Further, there's the challenge of storage and add-on devices.  Right now, you're not using a good solution for storage.  USB 3 drives, even SSDs, really shouldn't be used for direct editing unless you're in a crunch.  Yes, use them to move media around.  And definitely use them to back things up.  But when editing, you want to take advantage of all of those Thunderbolt-2 ports on the back of the Mac.   Bear in mind, Tbolt-2 has a max throughput of 20Gbits/sec; that's four times what USB 3 can do.  To give you an idea, NVMe drives are capable of an absolute max of 32Gbits/sec; and there's little out there you're going to find, storage wise, faster.  Where I'm going with that is: if you need BIG STORAGE on top of the 1/2 terabyte on your system, I'd look to a Tbolt-2 enclosure that can let you install a few SSDs or NVMe drives.   After you perform the test that Meg suggests, you'll know whether your system is adequate for your needs.  Assuming you're OK with the time it takes to transcode before editing, then you'll definitely want faster storage for your newly-expanded ProRes (and it's gonna be big, too...)  Given that, I'd be hunting around for an enclosure and some drives.   Aside from that, you have the option of going to a PC for editing.  That's what I did 7 years ago.  I'm now back on a Mac, but it's because I could afford a monster Mac Pro (2019).  It doesn't need transcoding or any such thing, it munches on h.264 without any issues.  I can't really recommend a good PC for a given price as my PC goals are usually different than others'.  I was building combo editing and gaming boxes, which need a lot of very fast cores (overclocked), and very expensive GPUs that can also overclock.  There are bunches of others here that can guide you if that's the route you want to go. ... View more

With your current storage limitations, I'd hold off on this one.  ProRes is going to munch on a lot of your free space, and you'll likely be forced to use more of that Samsung drive, not less of it.  That means more pulling/pushing media across that USB 3 link.   Sub-optimal.  Let's figure out where the problem actually is, first. ... View more

OK, that's not the shot of the Activity Monitor I was hoping to see.  You can see the individual core usage.  In Activity Monitor's menu bar:   Window --> CPU Usage   Or just hit CMD 2.  Another window should pop open showing you 12 bars (6-core CPU with hyperthreading).  Play your footage in Premiere and watch that new window.  Do the bars start kissing 100% or so?  Do some of them?  None of them?   As for storage, USB3 maxes out at a theoretical 5Gbits/sec throughput.  That's theoretical; rarely do USB 3 attached drives even hit that.  5G might seem fast, but... it's not.  Not for storage.  Do you have enough room on the internal drive to temporarily store the media while you're editing?  I'd try that, too. ... View more

Sure: transcoding to ProRes is probably one solution our OP can do.  But before that, let's figure out where the challenge really is.  If they transcode to ProRes and it's a storage slowness problem, that may make things even worse. 😉 ... View more

Your machine isn't really set up well to deal with large long-GOP formats like h.264.  It can do it, but it's going to do so slowly.  I suspect you're running into a combination of CPU and storage issues.  Call up the Activity Monitor while you're trying to play back the media in Premiere.  In Activity Monitor, Window-->CPU Usage.  This will bring up a graph of each of your CPU's cores.  Now play the media and see if your cores all jump to or near 100%.   If they don't, then your storage is not helping.  USB 3 isn't... fast.  At all.  It's a lot faster than USB 2 of course, but it's still pretty limited in speed.  The next test should involve moving the media to your internal SSD and seeing if that helps. ... View more

Glad you had a great Christmas trip and your Datsun is up and running again.  Here's what I was doing during my Christmas break: getting this monster integrated into my work space. 🙂     ... View more

Neil -   Thanks for the kind comments.  I'm more than happy to help as much as time allows of course; seeing as how this isn't my day job, as it were.  Heh.  But, long 2-week vacations give us time to play around.  🙂   This new Mac is a monster, and I've made it even more so from a storage perspective, which I'll get to.  The AMD Vega II GPU is an excellent GPU for work-horse stuff, assuming your software supports it.  Apple's FCPX does, wonderfully.  Pr doesn't seem to have a problem with it either.  32GB of RAM that I quickly upgraded to 96GB at a fraction of Apple's cost.  16-core Xeon humming along under the covers.  And the 1TB hardware RAID0 system drive that... is sorta slow.  Heh.  I can get maybe 3GB/sec throughput out of it according to the BlackMagic disk test.   I call that "slow" with a chuckle because I added two x16 PCI-E cards from HighPoint to the Mac.  Each has 4 2TB Samsung NVMe drives on it.  Both cards are working together in a hardware RAID01 setup, and I can get ~10GB/sec(!!) throughput on reads, and a little less on writes (since it's doing 2 copies).   Yeah... that should be fast enough to edit... anything.  😉   It does suck that Apple and NVidia had their falling out.  And I don't ever expect that to be patched up given the respective companies' stubbornness.  Both are at fault, and neither is willing to say, "Sorry, let's kiss and make up." ... View more

I just got a new 2019 Mac Pro and migrated all of my editing to it, away from my PC.  Sure enough, the long-GOP lag problem exists on the Mac version of Pr as well.  The same thing happens: Pr goes "not responding" while it's first importing an h.264 file it hasn't seen.  As soon as it finishes inhaling the file, all is well. ... View more

I don't imagine it's easy to get parts for that model, no.  I'm glad you have the patience to do a rebuild like that.  I suspect I'd just assemble interesting combinations of my favorite 4-letter words and announce them all for my neighbors to hear.  🙂   I'm glad to hear that the processes are moving internally.  My correspondence with the support folks was quite pleasant and useful, and it's good to know they got all the stuff they needed from me/my PC/etc.  I'm happy to help as and where I can.  And it's definitely a positive to see acceptance of the gaming/streaming/YouTube profession.  Many still may not believe it's an actual profession, but a lot of those guys (and gals) make way more money per day than most of us might in a year.  Which is silly, but, a reality.  That, by definition, makes them professionals.   The first good step in this direction was the work we did a year or two ago getting VFR videos in Pr.  While VFR is poop for the most part, it's just "a thing" in this world.  And with Premiere now able to work with them (and I had some small contribution to that... ;-)) that's a good thing.   You should have a small collection of PMs already waiting for you. ... View more

Awesome, glad to see the Datsun is functioning properly. 🙂   As time permits (I do have a day job, of course) I'll find related threads and DM them to you. ... View more

Seems like an overly-cynical and, to be frank, not very useful comment.  A company can't keep its customers paying a monthly sub for products that are consistently broken.  Bean counters understand that just as well as the developers do.  They can't fix things they don't understand are broken.  It's why I spent hours of my own time last month helping demonstrate the MP4 problem (that our OP mentions) to them.  And they got it.  I did those things instead of logging into Adobe's user forums and spreading cynicism and doubt everywhere.   Am I annoyed that it's broken?  Yep, slightly.  Can I work around it with some of the help they gave me?  Absolutely.  And I'll bet once they figure out what it was they broke in the code, they'll fix it.  They're not dumb; they know Resolve is starting to pose a threat to Premiere, Audition, and even AE.  Leaving Premiere permanently broken will push folks to other NLEs, and Adobe knows that. ... View more

Regarding your first main issue: the import of long-GOP formats, specially files that are pretty large in size, is a known issue with the latest Premiere.  It was reproduced internally by Adobe last month, so they know about it.  There's absolutely no word on its fix.   ... View more

Are your files long-GOP format, such as h.264 or h.265?  If so, this is a known issue with the newer versions of Premier and is something the support folks have reproduced internally. ... View more

And if you let it sit for about 3 minutes, does it eventually complete the import? ... View more

Another update on this: the crew at Adobe's Teir 2 have reproduced the issue.  So I'm glad to know I'm not crazy.  Or... at least... not as it pertains to this topic. 😄     Way too early to know about an ETA to a fix/patch/etc, of course.  But we got past the first step which is Adobe reproducing it.  Cool. ... View more

Is Premiere actually crashing or just taking a while to import the file?  What are the actual file sizes and what kind of files are they? ... View more

Update on this:  Thanks to Kevin, Adobe's L2 tech support folks contacted me directly this morning and pulled some debugging info from my PC along with an example file that trips Premiere up.  They were clearly able to see Premiere going "Not Responding" while trying it on my machine (screen sharing).  Let's see if they can repro it in-house. ... View more

Thanks Kevin, I appreciate the help. ... View more

Yep, you got it.  And yes with YT, although they're not transcoding to h.264.  Rather their own internal webm format. ... View more

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38955043-bug-premiere-pro-2020-not-responding-during-h-2   Second filing on the problem. ... View more

I've already done it Neil; I did that last week or so and it's received basically no views.  While I understand the goal of the UserVoice system, I think there's way too much going on there for Adobe to pick everything up. ... View more