Hello!

I was on the Celemony Melodyne "DNA" trial (under Cubase 5) until a few weeks back - excellent, by-the-way, just the problem of 'application-within-an-application' workflow to sort out: it's cumbersome, IMHO!

Regardless, having de-installed the trial version last Sunday, as I was informed it had now expired (within a work-in-progress Cubase Project I'd been working on over Christmas) I found Cubase would not open with Melodyne residing in my VSTPlugIns folder.

I have tried reverting back to my original Melodyne "Plug-In" - which I understood would reside harmlessly in the 'background' until the "DNA" trial ended and not be in any way disrupted, either by the installation, use or de-installation of the trial - in an existing project, a new project, without opening a project at all. All to no avail: Cubase will NOT open.

I have been unable to use Cubase and/or the Melodyne "Plug-In" since de-installing the "DNA" version and am plagued with "libguide40.lib" and "libiomp5md.dll" issues (see below and the attached JPG screenshot file):-

"OMP abort: Initializing libguide40.lib, but found libiomp5md.dll already initialized.
This may cause performance degradation and correctness issues.
Set environment variable KMP_DUPLICATE_LIB_OK=TRUE to ignore
this problem and force the program to continue anyway.
Please note that the use of KMP_DUPLICATE_LIB_OK is unsupported
and using it may cause undefined behavior.
For more information, please contact Intel(R) Premier Support."

as well as various other related messages. At one point Rob Papen's Blue VSTi plug-in (under Cubase 5; the standalone worked fine) seemed to be affected too, but a de-install and re-install of that particular VSTi cured this issue (Cubase could not detect the plug-in despite it being present and working in standalone mode).

[I'm no developer ... so where on Earth does bloody Intel come into all of this!? Steinberg, Celemony, Rob Papen/Linplug or even some other plug-in; but Intel? - Ed.]

I have de-installed Melodyne, re-installed it, performed this process with various re-boots ... and had no success whatsoever. I am working on a group vocal project which should have been completed today ... and have had to let the client down!

Not good!

Had I known there would be issues with an existing and working copy, I would not have participated in the trial on my live system. As it stands, I am trying to port everything from Cubase into ProTools M-Powered - which I am NOT familiar with - using the Melodyne freebie in there, and then exporting everything back.

Help. Please. ASAP.

Thank you.

I'm a brand new user, and I just had a similar problem, and maybe I have some information that will help you. I'm running Windows 7 Ultimate and Pro Tools LE 8.0.3. I had played around with Melodine Esential RTAS version 1.0.9 a few weeks ago, but today when I tried to load the plug-in, it crashed my Pro Tools session with the "OMP abort:Initializing libguide40.lib, but found libguide.lib already initialized." DOS box error. Searching around, I found this thread: http://www.celemony.com/userforum/viewtopic.php?f=13&t=2757 mentioning the a fix by setting an Environment Variable. They also mentioned that the problem happened after bouncing to disk, and I had bounced to mp3 in this session.

I restarted Pro Tools (without adding the environment variable) and was able to add and use the plug-in without a crash, so maybe it did have something to do with bouncing first in the session. I'm reluctant to add the environment variable as it will potentially effect everything else on this system, but I'll give it a try if it keeps crashing. So far, so good though . . .

tgold,

This makes an awful lot of sense as my particular 'failure' happened around the same time (if not precisely the same time) that I loaded ProTools M-Powered onto my system and started to try and use Melodyne 'lite', or whatever the included version is called by our new-found friends at "AVID is Digidesign" (I take it that this is their new company name!!! ?)!

I'm actually more concerned with why I didn't put 1 and 1 together and come up with summat around 2!!! This avenue for investigation is rather obvious ... now that you've pointed it out!

Anyways, let's just hope the Celemony guys read this and take a look into it on our behalf as I will not be altering a systemwide variable with pre-acknowledged consequences ... even if it appears to resolve this particular problem. A case of lessons learned, and all that .

In fact, the ONLY reason I have not yet gone for the paid upgrade to Melodyne DNA "Editor" is solely because this problem remains unresolved and I am not one for compounding problems or trying to fix them by applying so-called 'upgrades'. Therein lies the devil .

Once again, cheers - I'll have a play with removing Celemony 'Lite' and see what I come up with.

Cheers,

Steve.

Hi Steve,

Great, I hope my post helps! I did end up adding the environment variable because I also found out that if you use the plug-in and then bounce to disk, that the problem occurs then too. Seems like if you bounce you need to restart Pro Tools before using Melodine, and if you use Melodine, you need to restart Pro Tools before bouncing, or at least I do.

I decided to set the envrionment variable after encountering another problem. While exploring the Essentials Plug-in, I clicked on the Monitoring Synthesizer button (page 52 in the manual). As soon as I did, my system slowed to a crawl with the mouse moving every few seconds. I couldn't even get it to take clicks and ultimately had to reboot to get out. I rebooted, set the environment variable and finished my project with no other troubles, but then I didn't try the Monitoring Synthesizer again either so I'm not sure if I fixed the problem or just avoided it.

The plug-in is just magic when it works, so I'm willing to play around to see if I can get around the issues. And I'll quickly say that it may not even be the plug-ins problem. I'll report back when I know more . . .

Terry

Hello all,

You can safely do the alteration of the Environment Variable without harming your computer elsewhere.

Nils

Nils,

Thanks for posting. Respectfully, however, I regret that I have to disagree that there is no risk of "...harming your computer elsewhere.". Here:

http://software.intel.com/en-us/article ... uide40dll/

we have this:

"3) Set KMP_DUPLICATE_LIB_OK=TRUE environment variable to ignore the library conflict, which is not really recommended to do though."

and here:

http://software.intel.com/en-us/article ... itialized/

we find this:

"Solution:

Please remove one of them and keep only one OpenMP runtime library.

We recommend using and distributing libiomp5md.dll (located in the \bin directory), as libguide40 will be obsolete.

For the third-party library or custom dll which have used the libguide40.dll from pervious MKL version, in order to avoid such kind of issue, we strongly recommend rebuild your library with libiomp5md.dll."


The actual solution seems (according to all sources I've come across) to be this:

"Root Cause :
Both libiomp5md.dll and libguide40.dll are Intel OpenMP Runtime library. The libiomp5md.dll is new Intel OpenMP* Compatibility library while the libguide40.dll is legacy OpenMP library. The Intel® IPP 6.x and Intel® Compiler 11.x threading libraries are switching from the legacy OpenMP* run-time library (libguide*) to the compatibility library (libiomp*).

The dynamic library, libguide40.dll, is still included in the current releases for backwards compatibility and will be removed in a future release.

The error is caused by multiple OpenMP libraries were linked in same application. For example, if a application link the libiomp5md.dll from IPP 6.x, at the same time, it also link other software, e.g. third-party library, which link libguide40.dll, then the error arises because of the duplicate initialization of OpenMP Runtime library

Resolution :
Please remove one of them and keep only one OpenMP runtime library."


The main point, from all I've read - but, importantly, explicitly according to Intel themselves - is that only ONE OpenMP runtime library should be present on any system at any one instance in time: "Please remove one of them and keep only one OpenMP runtime library" and: "3) Set KMP_DUPLICATE_LIB_OK=TRUE environment variable to ignore the library conflict, which is not really recommended to do though" in order to mitigate against any form of 'confusion' amongst the apps which employ this runtime and/or system-wide issues.

Guys, I am no Windows developer, merely an IT techy who employs a healthy degree of common sense; however, when someone like Intel (et al) makes a clear, unequivocal statement such as this, I tend to sit up and listen until I receive an adequate answer/solution elsewhere. One thing I have learned though is that 'papering over cracks' is simply asking for trouble later on when another, apparently un-related issue raises its ugly head and the first 'correction' has been all-but-forgotten.

If this is OK:



then how do you reconcile that statement with the definitive information released by Intel as recently as September 2009?

Many thanks in advance,

Steve.

Hi Guys

ProTools is using this libguide40dll when exporting to audio as mp3. This can lead to conflicts with Melodyne and other plug-ins, resulting in this error message discussed in this thread.
If you come across the problem you may want to contact the Avid support about this, since they probably have already changed this in a newer version or will do so in the future.
However, as long as the problem persists on your machine, you have to use this workaround:


The Intel recommendation, quoted in this thread, to better use a different libguide, is without doubt true, as this would be the best solution to avoid such problems permanently. However, the workaround mentioned above does work.
You may also want to search the DUC about this, where many users report the problem and also report that the above workaround is a proper fix.

Best
Stefan

.

With the utmost respect, I think that:

i) taking 2 months to respond;

and then

ii) responding with such a non-response

is a highly questionable approach.

Simply put: there's nothing new here. The evidence - oft-quoted facts from Intel, no less - say one thing; whereas Celemony's response:

"the above workaround is a proper fix."

with no citations, evidence, explanation or justification is found wanting. I am sure I am not alone in stating that I can have little confidence in such advice.

Cheers,

Steve.

My pc is a protools-free zone!!

I know I am late to this thread but I just ran in to this problem. A quick search of the net shows complaints to Celemony about this date back to at least 2009. When are they going to address this properly?

I will not do the suggested patch work-around as there may be unforseen consequences. I find it hard to believe that a company that could come up with a program as complicated as DNA cannot fix a problem which is at least 2 years old.

Doesn't bode well for future purchases or upgrades.

Agreed!

After using Melodyne Editor with few problems, I now have the same error and crashing described above. Using Sonar X1 in Windows 7, both 64-bit.

I did just install Z3ta-2 from Cakewalk, which I know updated the runtime library (?) and that seems to have screwed it up somehow.

The error message comes up on a DOS window - weird - and crashes Editor and X1.

However, stand-alone seems to work, but I don't use it standalone.

Just giving this a bump - no clue what to do now.

Hello,

it seems, the installation of the new software has changed your scenario. It worked before, didn't it.
I recommend doing a reinstall of Melodyne editor.

This same issue has surfaced with the launch of Presonus's new Studio One Version 2, which features Celemony's new ARA technology, i.e. Melodyne is actually built in to S1. I bought the Pro version and soon found that my IK plugins wouldn't work, i.e. Amplitube 3 and TRacks3 Deluxe. When I attempted to use one as a plugin I got the crash described above (quick DOS window) and crash of S1.

There's been a lot of discussion of this over on the Studio One forums as users began to encounter it. A clever poster got a screen capture of the momentary DOS window and that enabled him to trace the issue to the abve Intel web pages where the 'fix' is described along with caveats about it not being a totally correct solution. I applied the fix and all seems well, but I'm not technically au fait so I'm a bystander when I see debates about whether it's valid or not.

My opinion is that there is supposed to be a common standard for plugins and it's not satisfactory for parties involved to stand back from this and leave the user responsible for a solution. I've had a constructive response now from IK on their forums who say they are going to talk to Presonus about it. I believe Celemony should also. It's the ARA technology that introduced the issue, i.e. Amplitube or TRacks can't be plugged in because Melodyne has already taken a resource that they need. But having said that, NI's Guitar Rig works ok in Studio One 2, so maybe IK should put a fix in their products. I dunno, as I said, I'm not technically qualified. I think all involved should sort it out together, Intel, Celemony, IK, Presonus.

Hello Skyline.


Well, not really. What's built into Studio One is just the ARA plug-in extension. Melodyne is still a separate product that needs to be installed next to Studio One.


How do you know it is the ARA technology? Have you tried uninstalling Melodyne to check if that avoids the crashes? If your plug-ins still crash, then this is something to be solved by Presonus. However, if this is really a problem with the interaction of Melodyne and Studio One, then our developers have certainly already be informed by Presonus.