Save to new folder - Melodyne edits lost

[js1]

In moving to my new Mac from my last PC box, I want to save the last version of the songs, and leave behind all the intermediate versions and no longer used audio files.

I have the two machines networked together, so I open the song on the PC, then do a "Save to a New Folder", and save it to the Mac. When I reopen it, the Melodyne files are there, but all the edits done after the original detection stage are gone.

Any idea where those edits are kept so I can manually move them across?

 

[Wolfger]

This is what the Ceremony help center has to say about passing studio one projects on:
don´t know why it wouldn't work as expected. maybe contact ceremony support?

Saving, archiving and passing on your songs​

Thanks to ARA, when saving and archiving your work, it is not necessary to give special thought to Melodyne, because all the files used by Melodyne (which it will need again when the song is next opened) are stored in the Studio One project.

If, however, you are passing on your Studio One project to third parties – for remixing, for example – you do then need to make sure that the recipient also has at their disposal Version 4 (or higher) of Melodyne. Which actual edition of Melodyne the recipient possesses is not relevant. If, for example, they only possess the “small” Melodyne essential, where you have been working with the “big” Melodyne studio, they will still hear all your Melodyne editing exactly as if they too had the studio edition. Naturally, if they propose to modify or add to your Melodyne editing of the song, they will be limited in in the actions they can perform to the function set of the edition they possess.

If not, it cannot hurt to render your tracks before sharing your work with others. This may be advisable for other reasons too, such as any use you may have made in your project of third-party plug-ins.

 

[Craig Anderton]

On Windows, there's a folder on your C: drive with the following path: C:\Users\[name]\Documents\Celemony\Separations. It stores temporary files that are created during the audio processing and editing tasks. Try moving the files in the Separations folder to the equivalent folder on your Mac. The folder is typically located in the Library directory under Application Support. Hope this helps! Circle back and let us know if this solves the problem or not.

 

[js1]

Thanks, Craig. As best as I can determine, there isn't an equivalent to the Separations directory on the Mac. Couldn't find it, so I created a new song, recorded a 10 sec vocal and did some Melodyne edits on it. Did a search in finder for new files, and didn't see anything that looked Melodyne related (I did enable "show hidden files"). I then reopened the song, did a few more Melodyne edits then saved. The only file that changed was the main .song file. So, I'm guessing that it's in there (on the Mac). Of course, if someone has real info, please speak up!

I have my suspicions, and ideas for a possible workaround. More testing to follow..

 

[Wolfger]

Thanks, Craig. As best as I can determine, there isn't an equivalent to the Separations directory on the Mac. Couldn't find it, so I created a new song, recorded a 10 sec vocal and did some Melodyne edits on it. Did a search in finder for new files, and didn't see anything that looked Melodyne related (I did enable "show hidden files"). I then reopened the song, did a few more Melodyne edits then saved. The only file that changed was the main .song file. So, I'm guessing that it's in there (on the Mac). Of course, if someone has real info, please speak up!

I have my suspicions, and ideas for a possible workaround. More testing to follow..

That´s exactly what is described in my post in the first paragraph from the Melodyne webpage.

 

[js1]

That´s exactly what is described in my post in the first paragraph from the Melodyne webpage.

I appreciate you pitching in. I was already aware of the Melodyne info, which was always how I thought it worked. But, the fact is, edits are not being carried over properly from PC to Mac when doing "Save to a new folder". If the edits were solely in the .song file, they should have worked.

Craig mentioned the Melodyne separations directory on the PC, so I thought it worth exploring.

Ultimately, I'll be opening a ticket with Presonus. Still hoping to find a workaround aside from having to freeze all the Melodyne edits.

 

[Craig Anderton]

FWIW I checked my Mac and it has a Library > Application Support > Celemony folder. However, it's a pre-Apple silicon Mac so things might have changed. The file extension on the files in Windows is .nff.

 

[Wolfger]

There is also user-->Name-->Music-->Ceremony--> Transfers
But this isn´t used for ARA and is always empty on my system.
I also would open a ticket with celemony.

 

[js1]

The Library>Application Support>Celemony folder has 2 files called MelodyneCore-xxx.sbb. That does smell of being part of the application itself. The transfers directory is empty on mine as well.

 

[Wolfger]

I have found the cache folder which only is visible as a whole path in the preferences when starting the Melodyne app:
user/your name/Library/Caches/com.clemony.melodyne/Separations
I think that´s the one Craig was talking about:


There is a lot of data in it on my system. Whether it´s the data needed for your transfer or not I don´t know:

Also I don't know if those .nff files are interchangeable between PC and Mac, worth a try for sure.

 

[js1]

It's something else that's going on. If I create a brand new one track song with a vocal on the PC, and edit it with Melodyne, it does open correctly on the Mac. I tried to trip it up by flipping between V6 and V7 on the PC, rendering it on the PC and converting back to real time on the Mac - it all seems to work.

However, as part of this debug, I reopened some songs on the PC. And, on some of those songs on the PC, when I try to open the tracks with Melodyne, I get something like "File corrupted and repaired by Melodyne - please check your edits". I'm guessing it's those files that are causing me grief on the Mac.

So, my original issue may be off base.

But, there are some other issues with V7 and Melodyne on the Mac. I tried rendering Melodyne on the Mac for the above test file. It didn't work (i.e. there was no rendered file created). After that, Bounce Selection stopped working. Then, this...



Anyways, I'm going to put debugging aside for a bit. I think I know the safe sandbox to stay in that will let me actually do the fun stuff. Later in the week I'll put together what should be a reproducible test case for Support. Thanks for the help!