Melodyne sends CPU into tailspin

[fsavell]

Anyone else having issues with Melodyne, where in certain sessions, either instantiating, or simply moving an existing instance of Melodyne to a different track causes the CPU (total bar in System usage window) to spike to 100%, rendering the session unusable? Cpu bar essential bounces from 0% to 100% perpetually.

If I simply close the session and re-open it, Protools will still spike the same, even if I open in safe mode (all plugins inactive). Only way to correct the problem is to quit Protools and relaunch.

I have plenty of sessions where Melodyne is working fine, just a few heavy VI writing sessions, where its totally choking the system. Can't seem to find out if its an interaction with another plugin. Anyone seen this?

Forrester

PT11.2.1, HDX2, OS10.9.3, Melodyne 2.1.2 b2

[Stephen Bond]

Melodyne is pretty robust in my opinion and they keep top of any bugs.

Have you other plugs on the vocal chain(s)? Try removing those first.

Stephen

[fsavell]

Originally Posted by Stephen Bond

Melodyne is pretty robust in my opinion and they keep top of any bugs.

Have you other plugs on the vocal chain(s)? Try removing those first.

Stephen

Thanks Stephen, agreed its been great until now. As mentioned have plenty of happy working experiences with Melodyne.

It happens wherever I instantiate Melodyne in this session, so its irrelevant to the particular track's plugin chain. I have heaps of plugins happening due to it being a writing/mixing session. Have yet to sit down and go through the process of removing plugins from my plugin folder to whittle it down till I find the culprit combination, if there even is one.

Just at the "anyone else go this issue stage". It might provide insight and save time, is all.

Forrester

[Darryl Ramm]

And before you try removing plugin files, try trashing preferences.

If it is only happening to this one session it may be corrupt.

Be careful of plugins and denomalization bugs (you can search for that on DUC). With plugins known to have this problem (like Sansamp and others) and especially with them at yhe lead of a chain of plugins (where they see digital zero/very low levels and start thrashing the CPU).

[fsavell]

Originally Posted by Darryl Ramm

And before you try removing plugin files, try trashing preferences.

If it is only happening to this one session it may be corrupt.

Be careful of plugins and denomalization bugs (you can search for that on DUC). With plugins known to have this problem (like Sansamp and others) and especially with them at yhe lead of a chain of plugins (where they see digital zero/very low levels and start thrashing the CPU).

Thanks Darryl. Too late , already spent an hour pulling out plugins and slowly putting them back in. Just trashed all prefs and still have the same issue. It happens on a few sessions, heavy in VI's. Know about the denormalization issue too, but haven't really encountered that as far as I can tell.

So my findings from isolating the plugins folder is inconclusive. Started with no plugs (except the default + Melodyne) and had no issues. Slowly added plugins and found that when I added the Arturia V-Collection folder, the issue with Melodyne occurred. However, if I removed all plugins back to just Melodyne and Arturia, everything works OK. So then I started adding plugins again, and at around three quarters of the list the issue pops up again. I then removed the last bunch of plugins I just added, but still have the issue? Remove the Arturia folder and boom, issue is fixed.
So rather than point the finger at Arturia, I would suggest its memory usage related, ie. when I have lots of plugins happening (irrelevant of manufacturer) the memory usage ticks over to a certain amount, which causes Melodyne to overdrive the CPU. Thats my theory anyway. Basically its not as simple as a single plugin combination in the plugins folder causing the issue.

Have contacted Celemony, still waiting to hear from them.

Forrester

[Bill Denton]

Started with no plugs (except the default + Melodyne)

What is "the default"?

[TOM@METRO]

Originally Posted by Bill Denton

Started with no plugs (except the default + Melodyne)

What is "the default"?

I believe he means the plug-ins that come standard (free) with Pro Tools.

[Darryl Ramm]

Oh well, you would not be be the first person to find CPU burn issues with recent Arturia plugins.

As you pull plugins out, it seems that it can very occasionally matter that you trash prefs after doing that. You might want to try doing that.

[fsavell]

Originally Posted by Bill Denton

Started with no plugs (except the default + Melodyne)

What is "the default"?

Default plugs are the ones PT11 installs automatically when you remove everything from the AAX folder.

So have found that if I remove the Native Instruments folder, or Arturia, it will fix the issue. So again its definitely not plugin specific. As i'm using 5 or so instances of Battery & Guitar Rig, and 2 or 3 Arturia synths, I can only put it down to a memory usage problem, as when I remove one of those VI's plugins, Melodyne works as expected.

Hopefully Celemony can investigate.

Forrester

[ronwasserman]

Originally Posted by Darryl Ramm

Oh well, you would not be be the first person to find CPU burn issues with recent Arturia plugins.

As you pull plugins out, it seems that it can very occasionally matter that you trash prefs after doing that. You might want to try doing that.

I have always had problems with Auturia plugs. Fantastic sounding but even as AU using VEP5 they crash. Just one of those companies that never got it right. I just deleted all of them from my system a while back. Too bad.

BTW - I've recently run 20 instances of Melodyne Editor at once without a single issue. Even did the transfer to each instance from each track at one time. Barely moved the CPU meter.