Wouldn't have a clue from this.
It does help a ton to get actual hard data to start puzzling through a trouble shoot ... OS/CPU/RAM/GPU/vRAM, the number-dot-number version of PrPro (as so often it says it's up to date when it isn't), the number & type of drives used, the media used, how it was created (camera, device, screen-capture, what?), any effects used, any plug-ins or third-party apps involved.
Also ... from Task Manager, how many processes are running when you have PrPro open and are working?
There are the computer specs. Using Premiere 2017 build 11.1.2 (22).
I am using a newer 5TB Seagate 7200rpm hdd to edit on (applications are stored on SSD)
This is the footage information. Shot with Blackmagic Ursa Mini 4.6k.
There are no plug-ins on the desktop I am using. I have closed every other application and no background processes are running.
[Moderator note: moved to best forum in hope of assistance]
Just wanted to chime in and say I'm seeing similar issues, and also with a very large number of audio files that need rendering for what is a fairly simple 1080/60 sequence, and another I've done recently.
System: 5820k @ 4.5ghz, 32gb ram, 1080ti, Win 10 Pro 64bit.
Footage is in h264 .mkv format with multi-channel audio stored on a NAS with both that and my editing rig using 10gbe. System usage is 10% cpu, 10GB ram, 1.5Mb/s drive write to local SSD cache, 40Mb/s~ across the network.
Stuck rendering at the moment (audio previews!) so will update with PrPro version, but do have auto-updates enabled and run the CC app whenever the PC is on. This seems to be a recent issue.
The estimated time doesn't actually show anything scary, about 20mins. But it stays at that for a good 2 hours on this particular sequence which claims to have 258 audio previews.
as a work around has anyone bounced their sequence audio out to Audition and then re-imported back into Premiere?
Having the same issue here, insane long render times for a 7 minute sequence. In my opinion this is a fatal flaw, I don't understand how anyone can actually use this to get work done under deadline. And this has apparently been a problem for years.
Does bumping the audio to audition and then re-importing it back into Premiere eliminate the problem?