How does Melodyne organise files?

[chagzuki]

I haven't had to pay too much attention to what Melodyne is doing in the background, in the limited amount I've used it it's worked fine.
However, I'm going to have to reorganise some projects and I don't know what associated files Melodyne is creating.
I've located the 'transfer' folder, and there's only 5 files in there, so I assume that these files are only created when not using ARA?
How does/or does Melodyne distinguish different edits of a project? I.e. if I make changes in one edit, will those changes propagate to previous versions based on Melodyne having a single shared file for that segment of audio, or does Melodyne create multiple edits unique to each iteration of a project?
The 'Separations' folder appears not to exist for me, I was imagining I'd find that folder with a load of stuff in it.
I'm using the Assistant version. I gather that some versions have a folder panel on the left, but that doesn't appear to be there in my version.

[olifrost]

I recently read a tip to change your transfers folder to your project folder, for each project. Couldn't find a preference for it though

[chagzuki]

I recently read a tip to change your transfers folder to your project folder, for each project. Couldn't find a preference for it though

A bit of digging wit CoPilot tells me that transfer files are only used when not using ARA:

"when using ARA integration, the changes you make in Melodyne are stored directly within the DAW project file. This means that all your edits, including pitch corrections, timing adjustments, and other modifications, are saved as part of the project. This integration ensures that your Melodyne edits are preserved and recalled whenever you open the project in your DAW."

I guess Melodyne must be using a fair amount of system resources to do this processing in real time.

[olifrost]

I believe that's right. I don't use ARA.

[jens]

I recently read a tip to change your transfers folder to your project folder, for each project. Couldn't find a preference for it though

A bit of digging wit CoPilot tells me that transfer files are only used when not using ARA:

"when using ARA integration, the changes you make in Melodyne are stored . This means that all your edits, including pitch corrections, timing adjustments, and other modifications, are saved as part of the project. This integration ensures that your Melodyne edits are preserved and recalled whenever you open the project in your DAW."

I guess Melodyne must be using a fair amount of system resources to do this processing in real time.

Yes and no. The transfer-files are only neccessary when not using ARA indeed (the are created when you literally press the "Transfer"-button, which doesn't even exist when using Melodyne via ARA.

But it's not correct that it's all "stored directly within the DAW project file". Melodyne creates temp-files on the fly which are stored seperately on your system (in Windows under documents/Celemony/Separations (it's a cache the size of whoch can be set in Melodyne under Settings -> Preferences -> Audio-Cache)

If you delete these files, Melodyne will create them again the next time you open the project that uses them - it will only increase the loading-time for the project and not cause other problems.
So when you switch machines, you don't have to worry about them.

Yes, it uses quite some ressources, but a modern machine shouldn't break a sweat.