New Premiere Pro Still "Not Responding" During h.264 Imports
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.
