Melodyne ARA locked?

I received a huge, pre-edited Project for mixdown. Several tracks contain melodyned signals. Audio plays as expected. I see that ARA icon in the corner, I can open the related editor (Melodyne, in that case), but I can’t do anything. All elements are locked. I can’t even change to Note Assignment Mode.

The same happens when I add a new event to Melodyne via ARA.

Track isn’t locked, Event isn’t locked.

What went wrong?

Windows 10, Nuendo 12.0.70, Melodyne 5.3.1.018.

Hi,

Sorry, I’m not Melodyne expert at all. Aren’t there multiple editions of Melody (monophonic/polyphonic)? Isn’t the source using higher edition in comparison to the one you have installed by any chance?

Good point, but I’m using Melodyne Studio since 1999. :sunglasses: Melodyne Studio 5 is the most recent top edition.

The people who did the edit use pretty much the same setup, and it worked over there (obviously).

Any other ideas, anyone …? Especially the fact that I can’t add new Events to Melodyne either (… but only in this Project! I just checked.) makes me suspect that it must be a problem with the transfer of Projects between machines.

Hi,

How did you transfer the project, please?

By means of an NTFS-formatted USB-3 drive between two Windows machines with the complete Project folder on it. About two hours of audio from a live gig, but only around 30 tracks or so.

Ahhhhh! The plot thickens. The ARA-folder is write protected, but I can’t change that in Windows Explorer. As soon as I apply the unlock it’s set back to locked, although I have Admin rights on this machine.

Any suggestions how to change that behaviour…?

2 Likes

“NTFS hard disk” is indeed the decisive info:

The problem always occurs when HDs with NTFS and administrator rights are put into operation on “other”, “new” or “foreign” computers.

(… translated from here)

… now if I only knew if that is really the underlying problem … :stuck_out_tongue:

1 Like

I was going to say that the files / folder / etc. are locked. The only “easy” way is to ask them to resend, but unlocked, with zero permissions on their end.

Else, you have to have ROOT ADMIN rights to permanently change permissions.

This is why I only ever have one user account, and it is the “master.” No guesswork.

1 Like

Thanks - that’s what I finally found out, too. :+1: Seems as everything is working as expected now.

… what a stupid way to waste a whole evening … :stuck_out_tongue:

1 Like

Hi @Dietz ,

just in case you might find one more possible method useful:

as a long-time Windows user (all MS-DOS based, all NT and quite a few server versions), and whenever I need to send any data (that were saved to an NTFS file system) to some other person via the web, I’d use a “file attribute washing machine”, which is either a USB stick or an external USB hard disc, formatted as exFAT (FAT32 might not suffice, due to file size restrictions).

So in case I wanted to send someone an entire Cubase project folder, I’d copy it to that “washing machine”, and it would immediately be liberated from any NTFS journal entries / permissions / attributes. Then I’d zip that folder (- either to a single archive file or, if there are also considerably larger files, as numbered archive parts -), and then I’d send the result from that “washing machine” via the web to the repicient. If that person is also a Windows user, and once they’d unpack the ZIP archive, their NTFS file system would treat any newly unzipped files as if they themselves had created them on that same local machine. User permissions and attributes would be standard again (of course depending on what that specific user might have, in terms of local account permissions).

HTH

Best wishes,
Markus

2 Likes

Thanks for the hint! AFAIR, data transfer via FTP should do the trick, too.

2 Likes