Well, I've been looking into Melodyne for a while and was considering hitting the buy button, but not now.

It's a simple fact that the current Melodyne plugin should load and play nicely with other "Up to Date" programs and plugins - without crashing.

It's also a simple fact that Melodyne 1.3 is using an outdated and obsoleted library which is causing this issue.

It's also a simple fact that the newer replacement library is backwards compatible and could be very easily linked in the 1.3 version.

I am astounded to see the response that version 1.3 will not be updated with the current (as of a couple of years ago) library. In "my humble opinion" (and I'm qualified to say so), this is a really poor show from this company, so instead of buying Melodyne this month, I'm investing my time to scrutinize the other options like Antares.

It's unfortunate that some software development companies can't seem to be bothered fixing what are nothing less than "Glaring Faults for which they are Ultimately responsible to fix", and instead take the line of "upgrade to the next version".

No other industry would get away with such poor service and attitude toward their customers.
And that is the volumes that a fiasco like this cry out.

Any programmer can tell you, this is a simple fault to fix - the suite has to be recompiled with the new library, a very simple job in terms of programming if you please. I would challenge the developers to come up with any substantial reason this cannot be fixed for the current version !.

In fact I do ... I challenge the developers to state why it's apparently not feasible from their view point to fix this "Out of Date Library", by compiling with the current new library.


I'm off to check Antares, and see if they do any better ?.

Cheers - Cliff

Hello Cliff,

Thanks for sharing your opinion. However, you are referring to the old Melodyne version 1.3. The current Melodyne singletrack version is 2.0, and it actually uses the latest Intel library. So we have already fixed the problem in the meantime. As a new customer, which I understand you are, you won’t run into any dll incompatibility issues described in this thread.

Claudio,

Did you read his post? He is very obviously talking about fixing 1.3, which a heck of a lot of users (including me) still have and cannot use because of this problem.

Your response is typical of your company's mindset. Customer service is not in your vocabulary. I too am looking at Antares. You have lost me, and I suspect a lot of other folks, as a future customer.

jgarland,

Yes, I read cliffr’s post, and I’m sorry if I misunderstood him. But apparently he is not a Melodyne customer yet – at least that’s what I read in his post and that’s what his profile says. So even though he talks about the 1.3 version, I was just trying to mention that the problem discussed in this thread is relevant for existing Melodyne users only, not for new ones.