Hello,

We are in the middle of a recording project, and the engineer brought his version of Melodyne to the studio for vocal tuning. His version is the plugin Melodyne Studio 3, of which, he used on two sessions so far.
Recently, the studio purchased Melodyne Editor version 1.2 (the stand-alone and plugin) and installed/activated it on both studio A & studio B's computers. The recently installed Melodyne works great!

However, upon opening the sessions that the engineer worked on (with his version of Melodyne Studio 3), we try using our new Editor 1.2 for further editing of his work (since we don't have his iLok). The sessions have three instances of Melodyne on three separate vocal tracks in Pro Tools.

As soon as I open the plugin I get a pop-up of a Melodyne file (in red) that's missing. So I select 'Find Missing Files', select the Melodyne Transfer folder for them, click ok, & a dialog pops up saying that the files were successfully converted to the newer version, & any further changes will be saved, but cannot be reverted back to the previous version, & all seems well.

However, as soon as I attempt to make any edits (regardless of tools) in Melodyne, Pro Tools immediately crashes w/o any pop-up dialog. This happens on both of the studio's computers, both of the project's hard drives (master & safety), and in both versions of pro tools (HD & LE 7.4)
I read that the preferred HW buffer size should be @ 1,024 samples and using only 1 processor, which have been tried (along w/ other variations of Pro Tools' playback engine settings) to no avail.

Here are the studio's spec's:

Studio A:
Computer-PowerMac G5/Mac OSX v10.4.11/PowerPC G5
2 CPU's @ 2.7 GHz
Memory: 4GB
Pro Tools HD3 v7.4
(2) 192 interfaces
(1) 192 Digital interface

Studio B:
Computer-iMac/Mac OSX v10.4.11
Intel Core 2 Duo @ 2.16 GHz
Memory: 3GB
Pro Tools LE v7.4
Digi 002 Interface

External Hard Drives Used:
Avastor HDX-800
500 GB
Firewire 800
Format: Mac OS Extended (Journaled)

Thank You!

Hello sweettea,

welcome to our forum. Could you please doublecheck: was this really Melodyne studio (in which case the tracks would have been transferred with the MelodyneBridge)? Or the product called "Melodyne plugin" that previously came with the Melodyne studio bundle and that is now discontinued?

Hi

I've replied sweettea from our support contact already. As far as I could see, there was no direct link between crashes and the latest version of Melodyne. In the description it is not 100% clear, which edition of Melodyne was used. I'll be back if something new and helpful is coming up.

Nils

Hello,

Thank you for the replies!

I just wanted to specify that we are using the transfers made from the product called "Melodyne plugin" that previously came with the Melodyne studio bundle and that is now discontinued, and trying to open them in our installed Melodyne Editor 1.2

Thank You !