I shouldn"t do this, but i’ll do it anyway: Ediload is fantastic!
(Disclaimer: I am not endorsed by Soundsinsync.)
Fredo
Curious are you guys that actually conform to the original Location audio files not running into performance issues when referencing alot of these huge file lengths? This might be on account of us trying to run some projects as one full session instead of reels (for convenience) but I am seeing a reduction in performance and long saves etc when there are specifically alot of references to original Location files. All on the same SSD etc. Made worse in N14
Nope. And all of the location recordings are on a NAS over a traditional network.
The loading of the project takes a bit longer, but no performance issues whatsoever.
Last (big) project had 51.000 files of location sound.
That being said, we always start with assembling the episode, which imports all of the tracks from the used takes. During “assembly”, we sift through all of the files and only keep what is needed. I.e. The boom & the lav for each character, the PFX and the alternative mics/angles.
That assembly project (npr) is then the basics to which the BG’s are build. And then the FX, then Foley, etc …until we come to a premix and mix project.
Long story short, you never have all of the location sound, at all times in your project.
Fredo
hmm interesting good to know, thanks for sharing. I will investigate a bit deeper what might be causing it on my end. When I mention performance its not so much peaking CPU or dropouts. Its more like automation lanes can take a second to open, markers can have a small delay after pressing and sometimes zooms can slow down (that is expected a bit )
yeah makes sense I sometimes keep a duplicate of the assembly but I’m thinking once we make all of the selects I will keep an track archive that references it, in case I need to recall something but not saved in the actual session. I do sometimes run a minize file and was hoping to have the ability to add handles to help mitigate this kind of thing.
All of the unused files and tracks from the assembly import and reference AAF from the editor are (hidden) in folders at the bottom of my project. All tracks disabled though.
But that is actually unnecessary, because you can search and fly in any file much faster using the Field Recorder Audio Import.
Fredo