Hi guys! =) I am currently building a new system to venture into video editing with. I'll be using Creative Cloud for my entire workflow because, well, a student sub to CC is cheaper than buying other people's products individually, haha. Marketing success!
Anyway, I have done so much reading about video editing with Premiere / AE (including Harm Millard's guides) and wow, this process has been enlightening (and brain-exploding). I never knew building a PC could feel so complicated. But, I have basically everything selected for my system now. The place I'm held up is in the disk structure — this is really not something I want to mess up!
I'm not asking you to tell me exactly what to buy, instead I want to make sure I can select the right products myself. I want to make sure I correctly understand the different potentially-conflicting I/O that goes on during PP and AE. I've read the white paper, Tweakers' Guide, etc. but some aspects still feel uncertain or vague to me.
I'm sorry if these questions feel really lame / naïve, I'm a creative person but not a very analytic/technical one so some of the nuances of hardware & software operations go over my head (even if they seem obvious to you, haha).
My current understanding of PP & AE I/O pathways is that all these categories of files can potentially conflict for disk access:
Windows / OS system files.
Premiere application data (the installed program)
Source media / Raw footage
- AE application data (the installed program)
- Project files
- Source media / Raw footage
- Media Cache
- Persistent Disk Cache
I have some naïve questions about this, a few things are still slightly vague for me:
- In this context, does 'Project files' refer strictly to the actual project save (like *.pproj), or is it a catch-all term for all 'files' used in the current 'project' (like audio samples, Illustrator files, etc.)?
- Are 'Previews' and 'Renders' the same thing referred to in different ways, or are they actually distinct operations — ie, you could hypothetically have 1 disk for 'Previews' and another disk for 'Renders'?
- Alternatively, is the 'Render' directory synonymous with the 'Export' directory? Or are these two distinct concepts?
Next — my understanding of the Adobe recommended disk configuration (based on the white paper) is this:
- OS, programs
- Media Cache / Scratchdisk
- Source media / Raw footage
- Renders / Exports
I'm still uncertain about where some file types into that scheme:
- Which drive would Previews go on?
- Where would the Persistent Disk Cache go? Is it OK to put it on the same drive as the Media Cache?
- Where do 'Project files' belong?
To clarify, I have seen guides like Harm Millard's and the white paper suggesting configurations for some of these (like putting Projects with Source Media, or Previews with Exports, etc) but unlike the "Adobe four" above, different forums and websites recommend different places for the 3 I'm confused about. That's why I'm asking — no one seems to agree on where Previews & Projects should go, and I can't tell whether 'Persistent Disk Cache' is lumped in with 'Media Cache' as a catch-all term in reference guides.
Especially, about 'Project' files, I'm not sure exactly how they're 'used' by PP / AE:
Are these accessed constantly (like the Media Cache) or only in short burst operations (reading once when loading the project, writing once when saving/autosaving)? Like does PP just read all the 'Project' data when you load it up (to know how to switch all the different settings like you had it saved) and then ignore the Project data while actually working (until it gets saved again)? Or is it constantly checking the project data while working?
Do Programs and Cache on the same SSD create access conflicts?
I ask because someone had mentioned in a thread that I Google'd up, that Programs & Media Cache don't conflict with each other because disk access for the program files ends once PP / AE finish loading, while the Media Cache only begins access once the program is fully loaded. This sounds odd to me because I would think the program is accessing its code constantly while working, but then I'm not very smart when it comes to the guts of software so I'd rather ask than assume. =)
Thanks guys, for any insight you can provide. I've spent weeks and weeks researching hardware/software/disk stuff (I know the difference between "socket" and "chipset" now!), and I've learned a lot, but these last few gaps are holding me up on making the final hardware decision (storage setup) before I start building. =)