Just wondering if anyone else is having problems with Melodyne and X3? I love Melodyne, and in particular it's new integration into x3. I have, however, always found it problematic, and X3 is no exception.
 
It seems to work fine in smaller projects with relatively few plugins. In larger projects, with more plugins and audio files of various bit lengths, it will cease working and crash Sonar.
 
Has anyone else has had issues? I have searched the forum - given the consistency of this problem there are relatively few threads.
 
Please don't chime in if Melodyne is working brilliantly for you! As thrilling as that news is, I would really like to hear from others having issues to try and isolate the cause.
 
Thanks all!
Bruce.

Since X3's release, I have been one of those people you don't want to chime in.  Melodyne has worked brilliantly, and is an incredible piece of software, especially with the upgrade to editor.
 
Until yesterday.
 
I had done some vocal edits the night before, mainly as special effects, but when I opened X3 the next day, the vocal tracks played back unedited.  The clips still showed as region fx clips.  When I launched Melodyne it showed the audio all in one line, as if it was using the percussion algorithm.  Nothing worked in Melodyne, no buttons, menu options, etc.  Over an hour of editing lost.
 
I had a student coming round at any minute to work on this track, and had to madly rush to get it re-edited.  In my panic I neglected to check my other versions of the project (I have versioning ticked) to see if they still worked.  I will have a look later.
 
I'm sure I have seen other threads about this saving issue, but didn't find them just now.
 
 
I also think this may have happened to me before, in a much smaller way, but I had put it down to pilot error.
 
I'm not sure if it has crashed X3 - I've had a few crashes (far fewer than on most new versions of Sonar), but don't think they were Melodyne related, but I suppose it's possible.

Yeah, I've had problems that I think are associated to melodyne but I've had to go away and have not had chance to fully check.

Mine started when working on the vocals on my latest track.

After applying the region effect it sounded like more than one track was playing so I deleted the top track to find there was another underneath. Much like with vvocal. This happened on every edit and sometimes I had to delete multiple times before getting a clear region .

This is a pretty intense project for my set up, so had lots of pro channel.

I used multiple regions then I had a hard drive full error when trying to save after doing many region edits. The hard drive is only half full.

That project is now completely corrupt and won't open even in safe mode.

I do have a back up but lost a full days work.

I can't necessarily blame melodyne but it does seem the most likely candidate.

Also, I am using windows 8.1. I had no intention of installing it yet and thought I would just download it to install later , unfortunately downloading also installs. Unless I missed something. Windows 8 was flawless. But I hadn't used melodyne then.

I too have had a Melodyne project that crashed after saving and then became unusable. I sent in the crash dump report. In my case I had started with an X2 project, deleted VVocal, and then applied Melodyne.
 
In another case entirely, a Melodyne RFX on a cloned track would refuse to keep its edits/settings across a save and reopen. That's been acknowledged by CW development. Maybe it will be fixed today.

Thanks for the replies folks! It's comforting to know that I am not alone:) I have had similar issues with files corrupting and becoming unusable - again only on larger projects. There sems to be an issue here, though not terribly widespread:( I didnt have these issues at all in X1d, Occasionaly in X2, and frequently in X3b. Lets hope stability in large projects (with Melodyne in particular) improves in X3c.

Can any of you guys throw me a few step by steps to reproduce some crashes? We are definitely interested in fixing/resolving any and all issues but we need to have some sort of way to reproduce issues.  Do you guys have projects you can send me?
-DG

Hi Dan.
 
Thanks for the response! The problems have been very erratic. In one project (started in X2, problem developed in X3) after saving version number 74, applying melodyne to any segment would cause Sonar to crash, saying that the plugin failed to load. I then re-opened earlier versions of the project untiI I could succesfully use melodyne. I had to go back to version 36. I immediately resaved version 36 (unchanged) as 36b. When I attempted to use Melodyne in the new version, it immediately crashed sonar! I spent the next 12 hours trying to find any kind of consistant element that would cause the project to fail, but could not.The only thing I could emulate was that in any of the project versions that melodyne wouldn't run in, auditioning various loops or one shots would cause an 'out of memory' error message. This would also happen if the same 'corrupted' project was opened in X2. Not much to go on I know, but all I've got at this stage! I will keep working at it and let you know if anything comes to light.

I'm not at home at the moment Dan but I'll happily send you the corrupted project file when I get home if you would like?

trnfoot
Hi Dan.
 
Thanks for the response! The problems have been very erratic. In one project (started in X2, problem developed in X3) after saving version number 74, applying melodyne to any segment would cause Sonar to crash, saying that the plugin failed to load. I then re-opened earlier versions of the project untiI I could succesfully use melodyne. I had to go back to version 36. I immediately resaved version 36 (unchanged) as 36b. When I attempted to use Melodyne in the new version, it immediately crashed sonar! I spent the next 12 hours trying to find any kind of consistant element that would cause the project to fail, but could not.The only thing I could emulate was that in any of the project versions that melodyne wouldn't run in, auditioning various loops or one shots would cause an 'out of memory' error message. This would also happen if the same 'corrupted' project was opened in X2. Not much to go on I know, but all I've got at this stage! I will keep working at it and let you know if anything comes to light.

 
This definitely sounds in depth, I would love to just open up the .cwp file to see what I get on my end.

STinGA
I'm not at home at the moment Dan but I'll happily send you the corrupted project file when I get home if you would like?

Sure! Please do, I will check on it tomorrow morning when I'm back at HQ.  Feel free to PM if I'm not online.
 
-DG

I will send it on Saturday night when I get home. I'll PM you when I get back.