I am a little bit surprised by that response. I think at this point we should understand the problem really well, especially people on the Melodyne team.

The poster implied that the problem started when ARA was introduced in Studio One. This would be a correct statement simply because what is now happening is that Melodyne is loaded at startup and hence the first plugin you load that is using a different Intel library would crash the host.

Not just that, but there is ample evidence that uninstalling Melodyne in this case causes the crashing to stop (it is documented in multiple places in multiple forums). Why is Claudio even asking this? Is all of this suddenly news to Celemony? I have not been following this issue but apparently Celemony was made aware of this issue sometime in 2009 already.

I am not 100% sure who is to blame here (seems Intel first, then plugin vendors using the outdated libraries), but I am surprised by Celemony's apparent lack of knowledge regarding this serious issue.

SilkTone,

I'm sorry, I didn't mean to be rude, ignorant or anything. I was just trying to isolate the problem and verify whether or not in this individual case the issue started with the installation of Melodyne. Skyline wrote:

See, ARA itself is just a technology, currently implemented in Studio One and Melodyne, but it is not a product. So I was wondering if installing Studio One, but not Melodyne, also brings up the error message.

OK, fair enough. Based on a few forum postings in the PreSonus forum, it sounds like this issue is being addressed in V2 due next month. Fingers crossed...

For what it's worth, on the Presonus forum one of their developers has stated:

"...this problem occurs with S1 v2 and not v1 or Sonar because Melodyne will be loaded on program start. the differing working versions of TRacks or Amplitube will either not use multithreading (and so do not use these libraries) or just use the same version. This is something we can not fix. really only Intel can."

Claudio I accept my earlier error about Melodyne being 'built in' - I'm not a techie! What I meant was the user doesn't have to do anything - you load Studio One Ver 2, you load Melodyne.

Who's at fault:- Well, this debate can run and run. But try and look at it from a user's point of view. Here's all I know just being a spectator who has had to put a kludge fix into his PC to get all his purchased software products to work:

(1) Intel may well be to blame because of the legacy libraries issue they need to address.
(2) IK may be at fault because they should have knitted their plugins around this Intel problem (if they knew about it).
(3) Presonus may be at fault because (a) they should have also knitted V2 around this issue, and (b) they should have found this in beta testing; IK products are not exactly obscure plugins.

From a user's point of view it's not satisfactory for Celemony, Presonus and IK to stand back and point at Intel. Yes, Intel may well be to blame but in the interests of customer service I think the other parties should work something out together so as the user doesn't have to stumble across the issue, search forums and apply an unsupported fix to their PC. On the IK forum one of their representatives has already said that they have "... reached out to Presonus" about this. I think that's a laudable first move.

John

Hello John,

I absolutely agree with you. Users should not be left alone with this error message, and noone should point at anyone else and blame another culprit. But I don't think we do. What I said above was: 1) Can you verify that the crashes are introduced by Melodyne only? And 2), if there is a problem with Melodyne in Studio One, be sure our developers are already in contact with Presonus about it.

I am experiencing the same issue. i7 -Q740, Win7x64 with all updates current. All DAWs and plugs are current.

I started receiving libguide40.dll errors after installing full version of Melodyne editor when using my IK Multimedia plugs (which worked fine previously).

I reinstalled my IK plugs. Removed environmental variable kludge suggested by Celemony as it is not recommended by Intel.

As soon as I drop an IK plug on a track (except Black 76 plug) it crashes Studio One-V2 x64. If I use any IK (other than Black 76) and Melodyne Editor together in a session it crashes Studio One-V1 x64 and Reaper x64.

When I search my system (showing hidden items), Melodyne is the only software that uses libguide40.dll.

Please advise.

The crashes occur if a user tries to use an IK plugin at the same time that Melodyne is also plugged in. So, yes, the presence of Melodyne plugin will mean that your DAW will crash if you then try and load Amplitube or TRacks, because both want to use the same library and only one can be available at any one time (unless you apply the environment variable fix) and this becomes certain in the case of Studio One V2 which loads Melodyne along with S1 V2 as part of the ARA technology. With other DAWs you can avoid the clash by not loading the IK plugins if you've already got Melodyne plugged in, if you've chosen not to apply the fix.

John

Technically that is not correct. The problem is that by default two different plugins can't load different versions of the Intel libraries. Any number of plugins can load the same version of the libraries without any problems whatsoever.

The kludge is to set a flag that tells the library code to ignore the case where it detects that a different version of the library is being loaded after another version has already been loaded into the process.

The real solution to the problem would have been if the libraries were written to peacefully co-exist with different versions in the same process. That ship has sailed though because you can't go back and change shipped versions of the libraries to start working correctly. The next best solution is to get all plugins updated ASAP to use the latest libraries, and then get Intel to fix future libraries to co-exist with different versions going forward.

Hello everybody,

you might like to hear that the issue will be resolved with our upcoming 2.0 update. Stay tuned.

Isn't 2.0 going to be a paid update? What about those of us who stay on 1.3, will there be a fix for that, or will we be forced to upgrade in order to resolve the problem?

There will be no fix for 1.3.

What is the scheduled roll-out of V2?

From my understanding it is going to be sometime this month.

that is unwelcome news. What is the reason their will not be a fix for 1.3?

I am a Studio One Pro V2 User and I wanted to ask. Studio One Pro Version 2 came Bundled with a Full Version of Melodyne Essentials V1.X. It is my understanding that because I registered this product with Celomony after October 1, 2011. I will receive a FREE Upgrade to Melodyne Essentials 2 when released. Will Melodyne Essentials 2 have the fix included as well as Melodyne Editor2?