Hi all. I've been using Melodyne Studio 4, mainly via ARA inside MC8.5, on many projects for a few years. I only now noticed that I have around 10 GB ![:!:]( "Exclamation")
of *.nff files in a folder called Separations, with opaque names like 00000000_005496_2BEAD4EF-E88B-445B-8949-AB3B122ACE3B.nff . Can I delete these? Or will this mess something up, now, or if I port projects to another machine?
I came across these *.nff file in the process of preparing to back up projects to an external drive, and now it makes me wonder, if I save just the MC project folders and load them on to a new machine in the future, will opening a project cause something to look for these *.nff files, and when it doesn't find them declare there's some kind of show-stopping error?
How do these files get created anyway?
For background: my usual work flow is slicing a recording session of, say, 10 vocal takes into separate phrases -- let's say there are 10 of those, so creating 100 little slices with Control+t; then tuning those that need it with Melodyne; and then, *usually*, remembering to "print" my editing work by rendering the Melodyned bits as new wav files (by selecting and then Control + W), so that Melodyne isn't working except when needed. But I might have forgotten to render some though. Could that or some other aspect of my work flow have caused this?
Fingers crossed, I can just delete them all....![:?:]( "Question")
of *.nff files in a folder called Separations, with opaque names like 00000000_005496_2BEAD4EF-E88B-445B-8949-AB3B122ACE3B.nff . Can I delete these? Or will this mess something up, now, or if I port projects to another machine? I came across these *.nff file in the process of preparing to back up projects to an external drive, and now it makes me wonder, if I save just the MC project folders and load them on to a new machine in the future, will opening a project cause something to look for these *.nff files, and when it doesn't find them declare there's some kind of show-stopping error?
How do these files get created anyway?
For background: my usual work flow is slicing a recording session of, say, 10 vocal takes into separate phrases -- let's say there are 10 of those, so creating 100 little slices with Control+t; then tuning those that need it with Melodyne; and then, *usually*, remembering to "print" my editing work by rendering the Melodyned bits as new wav files (by selecting and then Control + W), so that Melodyne isn't working except when needed. But I might have forgotten to render some though. Could that or some other aspect of my work flow have caused this?
Fingers crossed, I can just delete them all....
Statistics: Posted by lingyai — Sun Dec 15, 2024 9:55 am