BUG: Premiere Pro 2019 "Unresponsive" During Imports
I stopped editing for several months and recently came back to it. What I noticed is that Pr seems to have some issues importing the same types of footage that it previous had no issues with: 4K/60 h.264 files that are 5-6GB in size. Previously, Pr would just import them in with no issue. Now, Pr seems to lock up during the import, and again when I try to put that footage on the timeline for the first time.
During this "lock up", one CPU core from my 7900X is pushed right to 100%. The rest of them are at or near idle. It's a different core each time that goes to 100%, but it happens every time.
Windows 10 Pro v.1903
Core i9 7900X OC'd (and water cooled)
2 x nVidia 2080Ti GPUs OC'd (and water cooled)
64GB DDR4 OC'd
SSD pairs in RAID0
HDD pairs in RAID0 (7200 RPM)
Scratch space on an M.2 drive
None of the resources are being taxed except that single CPU core. If there's any other info I can provide that might help get to the bottom of this, let me know!
Petr Hotovec commented
has this issue be solved somehow ? i have the same problem
Of course you can contact me on the website https://autokroma.com/contact/
Is there a way I can DM the link to you?
i'm investigating the possibility of improving Adobe importing process so it could be useful for me!
Thanks for the offer; according to Adobe this is a known bug with Premiere's handling of long GOP files.
Okay, indeed weird! If you send me the footage I could try to replicate your issue maybe?
I misunderstood what you meant about "Previously" in my other post; sorry about that. Previously meaning when I was editing earlier this year. Some time in Feb was the last time I did any serious editing and took a long break till Oct this year. In that time, I know Premiere was updated once or twice, but so was Windows.
Weird. Is it easily reproducible or at random ?
" Previously" as in CC 2018 ?
Took a quick screen grab of the Windows Resource Monitor while importing. You can see Premiere has gone "unresponsive" and one core has jumped to 100%.