Luke Humphrey
Member
- Joined
- Nov 24, 2012
- Messages
- 16
- Reaction score
- 0
- Points
- 0
I have a Premiere project (latest updates) with maybe 50-70 6k Dragon R3D files. I also have maybe 40 time-lapse sequences (JPG with 500+ images each).
I have several problems that are getting in the way of the creative process here:
1. Opening the APP project takes a long time, several minutes. Wouldn't be a huge deal if Premiere didn't crash so often.
2. Saving takes several minutes. This really disrupts my editing flow if I save every 5-10 min. If I don't save I risk data loss upon crash (happens frequently enough).
3. Actually loading the R3D files takes a long time. Meaning I'll see them in the timeline after Premiere has "loaded" everything, but I have to wait up to 5 minutes to get them to actually be playable.
I've done a couple things to try and isolate the problem:
1. I started a new project and just added the time-lapse stuff. Save and load is pretty quick with just these. Once I add the R3Ds it seems to slow down significantly.
2. I've run sysinternal "Process Monitor" to see what's going on during these long saves/opens. Here's an example of what happens on open (this is a quick open with a paired down project, usually it's much worse):
--For about 94% of the open time, the project file (just the project file) is being read thousands of times
--For 3% of the time other APP program files are being loaded + each individual JPEG in the time-lapse sequences
--For only 2% seconds the R3D files are loaded
--For the 1% of the time the media cache files are loaded
Saving is 99% thousands of writes to a temporary project file. I don't understand why it's not one write after everything as been sorted in memory. I also don't understand why only the diffs from my last save are processed on subsequent saves, which should take milliseconds (e.g. a small change in an edit, which is probably represented by moving/changing a couple XML nodes/values).
Sample of what happens when opening file-wise. It's over 90% small reads on the project file.
Hardware: i7-5820K 3.3Ghz, 64GB DDR4 2133, Nvidia GTX 980, RAID array SATA w/900 MB RW or RAID array SSD with similar speeds.
Thoughts/insight? I really can't wait this long to save - I end up spending 10 minutes editing, 3-5+ saving. It's very hard to get into a flow. Also I don't quite understand why the r3D files take so long to load in the timeline before I can play them after Premiere has said "everything is loaded". And then if I don't continuously work with them, the loading process starts again and sometimes APP hangs.
Thanks,
Luke
I have several problems that are getting in the way of the creative process here:
1. Opening the APP project takes a long time, several minutes. Wouldn't be a huge deal if Premiere didn't crash so often.
2. Saving takes several minutes. This really disrupts my editing flow if I save every 5-10 min. If I don't save I risk data loss upon crash (happens frequently enough).
3. Actually loading the R3D files takes a long time. Meaning I'll see them in the timeline after Premiere has "loaded" everything, but I have to wait up to 5 minutes to get them to actually be playable.
I've done a couple things to try and isolate the problem:
1. I started a new project and just added the time-lapse stuff. Save and load is pretty quick with just these. Once I add the R3Ds it seems to slow down significantly.
2. I've run sysinternal "Process Monitor" to see what's going on during these long saves/opens. Here's an example of what happens on open (this is a quick open with a paired down project, usually it's much worse):
--For about 94% of the open time, the project file (just the project file) is being read thousands of times
--For 3% of the time other APP program files are being loaded + each individual JPEG in the time-lapse sequences
--For only 2% seconds the R3D files are loaded
--For the 1% of the time the media cache files are loaded
Saving is 99% thousands of writes to a temporary project file. I don't understand why it's not one write after everything as been sorted in memory. I also don't understand why only the diffs from my last save are processed on subsequent saves, which should take milliseconds (e.g. a small change in an edit, which is probably represented by moving/changing a couple XML nodes/values).
Sample of what happens when opening file-wise. It's over 90% small reads on the project file.
Hardware: i7-5820K 3.3Ghz, 64GB DDR4 2133, Nvidia GTX 980, RAID array SATA w/900 MB RW or RAID array SSD with similar speeds.
Thoughts/insight? I really can't wait this long to save - I end up spending 10 minutes editing, 3-5+ saving. It's very hard to get into a flow. Also I don't quite understand why the r3D files take so long to load in the timeline before I can play them after Premiere has said "everything is loaded". And then if I don't continuously work with them, the loading process starts again and sometimes APP hangs.
Thanks,
Luke
Last edited: