Skip to main content
jasonvp
Inspiring
November 4, 2019
Frage

New Premiere Pro Still "Not Responding" During h.264 Imports

  • November 4, 2019
  • 7 Antworten
  • 2176 Ansichten

Hey folks -

 

There are a number of threads about this same topic as it relates to previous version of Premiere.  With today's release and the improved h.265/h.265 handling, I was hoping it would be alleviated.  It hasn't.  It may have been improved a teeny bit, but it's still an issue.

 

Problem: Importing a 5.5 - 6GB h.264 file (4K/59.94 FPS) causes Premiere to go "Not Responding".  The import dialog box stays up, the status bar doesn't move, and both the dialog box and Premiere's title bar say "Not Responding".  While this is happening, one core of my OC'd 7900X goes right to 100%.  Another core is around 50-70%, and the rest are at or near idle. 

 

This lasts for approximately 1 minute and 20 seconds per file imported, give or take.  I can't do a single thing with Premiere while the import is happening; I have to just sit and wait for it to respond to the operating system again.

 

Once the file is installed, I have another lag associated with putting it on the timeline.  Putting that large file on the time line does NOT cause Premiere to go unresponsive.  But I can't do anything with the timeline until... something finishes.  I'm not sure what Premiere is doing, but it again sends a core (or two) to 100% while I wait.  This one lasts for far longer than 1:20; sometimes it's four to five minutes.

 

Yes: I know h.264 files are highly compressed.

Yes: I know that using a transcoded (and significantly larger!) file format would potentially smooth things out.

No: I don't want to, nor should need to transcode.  I didn't need to worry about this previously.

 

The system specs are here:  https://www.jasonvanpatten.com/gaming-rig/   

Storage is set up as:

  • HDD mirror - media pool/imports
  • SSD mirror - project files
  • M.2 drive - scratch space
  • NVMe (sys drive) - export drive

 

It doesn't matter where I put the import media.  I can even put it on the super-fast NVMe drive and it makes no difference at all.  I've run the new System Compat Report in Premiere and: nothing found.  I'm kinda at a loss here.  This didn't used to be a problem with Premiere.  I'm still suspecting that there's some poisonous interraction between Premiere a fully-patched Windows 10 OS, but that's just a hunch.

 

Dieses Thema wurde für Antworten geschlossen.

7 Antworten

R Neil Haugen
Legend
January 1, 2020

Jason,

 

Thanks for posting info here. Your testing is always so clean and controlled ... and has enough details to understand what you're talking about. Solid.

 

I routinely work with a number of colorits and 'hang' on LGG and a couple other places. The new Mac is intriguing, as like any of these tools, there's quite a number of options as to what to get. And they all have implications that aren't necessarily obvious going in. Fascinating discussions, but in general a pretty good machine. Some frustrations I've heard to do with

Apple banning Nvidia in toto of course, as some folks still could use Nvidia for certain apps better than AMD. Ah well.

 

Neil

Everyone's mileage always varies ...
jasonvp
jasonvpAutor
Inspiring
January 1, 2020

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."

jasonvp
jasonvpAutor
Inspiring
January 1, 2020

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.

jasonvp
jasonvpAutor
Inspiring
November 5, 2019

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.

jasonvp
jasonvpAutor
Inspiring
November 6, 2019

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.

Kevin J. Monahan Jr.
Community Manager
Community Manager
December 10, 2019

Hey Jason,

Oh, glad they finally got to you. Let me go "pile on" to this bug....adding customer comments, forum threads helps amp it up. First, I gotta find it! 🙂

BTW, got the Datsun running again....

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin J. Monahan Jr.
Community Manager
Community Manager
November 4, 2019

Jason,

This appears to be a known issue with very large files.

I'm going to try and press for a fix here.  If you want to appeal to the fastest growing segment of video editors and potential users of our tools, you need to optimize your software to handle Long GOP Variable Rrame Rate streams of various lengths, including those files that are very large. 

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
jasonvp
jasonvpAutor
Inspiring
November 4, 2019

Thanks Kevin, I appreciate the help.

R Neil Haugen
Legend
November 4, 2019

Anyone else experiencing this, please go to the link to the UserVoice report by Jason and post your own details.

 

Neil

Everyone's mileage always varies ...
R Neil Haugen
Legend
November 4, 2019

Easy misunderstanding of their system. EVERY filing on UserVoice gets looked at by engineers. If they want additional details they will post replies.

 

But their accessing the post doesn't show from the user end ... because it isn't accessed internally by the forum. It's gone directly into their incoming issues que.

 

Neil

Everyone's mileage always varies ...
jasonvp
jasonvpAutor
Inspiring
November 4, 2019
R Neil Haugen
Legend
November 4, 2019

Please post all this on their UserVoice system. That goes directly to the engineers and they want this sort of data in detail.

 

I spent some time here at Adobe MAX yesterday with Program Manager Patrick Palmer and the newish stability/performance head engineer Ivo.

 

He wants this information anytime any user has such an issue.

 

Neil

Everyone's mileage always varies ...
jasonvp
jasonvpAutor
Inspiring
November 4, 2019

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.