Edit here: I'm thinking too, this may be some wrinkle in Celemony's registration check, but it is apparent that even if this is the case, it's interacting with Sonar differently based on something different in their 'contract'. What this means is: There is something in Sonar, at the host level, that is preventing Melodyne from coming up normally, like some kind of semaphore or test, however, if you can get Melodyne to open up at all (as I did with opening up GoodMelo and successfully invoking Melodyne), then any other project will no longer be blocked for Melodyne. Now, in same instance open BadMelo, try to grab a region FX and BINGO, Melodyne comes up with nice golden, fully-editable blobs. Step Three: open GoodMelo AND immediately grab a region FX with Melodyne - BINGO, nice golden blobs. Step Two: after closing both projects, open GoodMelo first then in same instance open BadMelo - sadly, both still get greyed-out Melodyne. Step One: With BadMelo already open, in the same host instance of Sonar open GoodMelo, and - uh-oh - now in GoodMelo Melodyne comes up greyed out - GoodMelo gone Bad, I'm a sad man. So my experiment - try to fool Melodyne somehow. and as a point of emphasis, we know the Melodyne license is good because it works on GoodMelo and stand-alone just fine. So tonight I made an experiment - let's say project A is called BadMelo and it is the one where Melodyne comes up greyed-out (functionally inoperative), and project B, called GoodMelo, is the one where everything works fine, nice orange wav blobs, active editing controls.

ya think?) and initial contact from Cake Tech is boilerplate checks so far (but we have much to talk about in our next exchange :) ). Celemony was not very helpful ('must be something in your project'. I've been trying to figure out why Melodyne won't work in one project but works fine in another as well as works fine stand-alone. Select the sequence to be synced, choose any sync options and press Sync.Melodyne Greyed Out Sometimes: Revelation Select the menu item Window > Extensions > PluralEyes Select Install and choose the file PluralEyes 2 Connector for Premiere Pro.zxp

The same extension file works for both Windows and OS X.

The connector file is located within the Extras folder of the downloaded zip file that contains the all the PluralEyes installers. If you haven’t already installed the latest PluralEyes for Premiere Pro, download and install it. Note that in order to use Connector, you must already have installed PluralEyes for Premiere Pro. You have to install “PluralEyes 3 Connector for Premiere Pro” for the feature to be visible inside PremiereĬonnector is an Extension for Adobe Premiere Pro CS6 that makes it easy to use PluralEyes with Premiere Pro.

Pluraleyes 4 extensions greyed out