Can Melodyne open files of any size or is this determined by the amount of available RAM?
[editor, assistant, essential, plugin]
The RAM consumption of Melodyne editor, Melodyne assistant and Melodyne essential strongly depends on the files you are using. With melodic or percussive files you will notice that these editions need even less RAM than Melodyne plugin. On the other hand, with polyphonic files in Melodyne editor the RAM usage can be higher – this is depending on the musical content of the files and can therefore not be foreseen in any MB-per-minute calculation.
Whenever you encounter any RAM shortage on your system, there are a few strategies you can use to minimize the RAM consumption. First off you need to know that during and shortly after each transfer the RAM consumption is much higher than a while after the process. Therefore multiple simultaneous transfers temporarily increase the RAM usage a lot. A workaround for this would be to transfer tracks one after the other.
Often there is no need to transfer a track from the very beginning to its very end. Instead it is much more efficient to transfer only the part you currently want to edit. Even when you end up with having transferred the whole track in the end, you will have lower peak values of RAM consumption when you do it part by part and track by track.
And one last tip on saving RAM: certain DAWs will have a growing RAM usage simply because you are using them over hours. Therefore it’s a good idea to save, quit, and restart your DAW from time to time.
With Melodyne studio, Melodyne plugin and other older Melodyne editions, the amount of available RAM affects the speed of the detection process and in this way has a bearing upon the maximum overall length of an audio file. The precise amount of RAM needed for this detection process depends upon the playing time of the file and its sample rate. It is NOT dependent upon the wordlength of the samples (16, 24 or 32 bits); NOR is it dependent upon the number of channels (mono or stereo).
For this reason, any calculation of the amount of RAM needed has to be based not on the size of the file but upon its duration and sample rate.
The following table offers an overview:
|512 MB ||1 GB ||2 GB ||3 GB or more |
|44 kHz||5 minutes ||10 minutes ||30 minutes ||40 minutes |
|96 kHz||3 minutes ||6 minutes ||18 minutes ||24 minutes |
|192 kHz||1 minute ||3 minutes ||10 minutes ||13 minutes |
The lengths given refer to the length of one file (not the total time of all the files used in an arrangement). If, according to this table, your computer possesses insufficient RAM for a given file, it will need to use your hard disk to make up for the shortage of RAM, and do so perhaps several times for individual segments. This will result in the detection process being drawn out to an inordinate extent.
As you approach the maximum values listed in this table, there will be a tendency for the system to slow down and even become unstable and crash. To avoid this, we recommend breaking up long files into smaller units that can then be detected one after the other. This will make the entire procedure more fluid as well as more secure.