Hi everyone.
 
Updated Kingston yesterday and back into my current project, only Melodyne Editor is now not working properly. It seems hit and miss. Open current project, (has AD2 tracks, most instruments done, no synths except drums, still in recording stage and currently doing vocals). Been working on it the last two weeks without any real issues. Decided to do some more vocal takes today to try for a different melody, and then re-pitch for the vocalist to learn the new notes better, using Melodyne, and..
 
Suddenly being asked to activate Melodyne for this PC. It's been working fine for a couple of years now.
 
Save project. Get out, open again. all good with registration, except I can no longer hear any changes to the notes in Melodyne Editor. Useless really, as I can only guess where to drag the note. Nothing I can find will give me audio. Shut down the project again, re-open, wants to activate again. Shut down, open a past project, asks for activation. Shut down, reopen, all good again? Try to edit with Melodyne, working fine, hearing audio. Close, reopen current project, asks for activation, close and reopen, it's OK again, except, I cannot get any audio whilst editing the notes for the life of me.
 
Been at this now for hours and getting nowhere. Does anyone have any idea what to look for or try? Should  I reinstall Meloydne?
 
It worked fine yesterday before the latest update to Kingston. My PC is fully up to date with hardware and software, running Win10.
 
Thanks. Dave.

I got a lot (and different problems) with Melodyne and latest Kingston update (and update 1) crash like hell!
Im trying to investigate further but thats really a shame,i can't barely work!!

Well, Ive got around the problem, but this is not good.
 
Melodyne has been problematic for me since Splat. My workaround since has been to only Melodyne short clips at any one time, and bounce them to the clip when done, before moving onto to any other work. Otherwise I suffer multiple crashes. Fine. I can live with that.
 
This time, I had left one very short Melodyne'd clip in my bass track. Thought I had bounced the entire track to clip, but missed a bit at the end. About 2 bars. Once I bounced it to clip, Melodyne starting working again properly. I found this by deleting each track until a change occurred, and then looked at length into the track to determine the above.
 
Another afternoon lost in fault finding  

The problem of strange crashes or other crazy behaviors like empty clips when you render melodyne region fxs,impossibility to duplicate with CTRL+drag a clip with melodyne region fx,and already mentioned suddenly crashes,seems more prominent when you work with complex projects with a lot of VST/VSTi's coming from older versions of Sonar (X3,X2 or older) and modified with Sonar Platinum.
Anyway yesterday i got a Melodyne crash even with a fresh new project with barely 4 tracks a bunch of vsts and no vsti's!!
Seems the bakers need to investigate more about melodyne integration with sonar!
 
 
 
 

I have had many problems with Melodyne Editor until I started running SPlat with administrative startup, even though I am the administrator of my machine. 

Im with administrative startup too,so that's not the behaviour...

I'm sure you guys already know this but simply having administrative users rights is NOT the same as specifically right clicking the program .exe and choosing "Run As Administrator"

yes,im talking (and im sure wolfstudios53 too) about running Sonar checking the option "run as administrator".

Good stuff.

Yep, I too had a history of Melodyne issues with Sonar until I got rid of some VST2 .dll files, and up until recently I was okay, then a couple of days ago I used Melodyne in a project started from scratch within Splat and I got crashes when creating RegionFX and/or opening a project with active Melodyne instances.  <Sigh>
 
Ultimately it seems to work better when adding Melodyne as a plugin effect and capturing the vocal in real time, then doing the necessary work, then bouncing to a new clip and completely deleting everything Melodyne related before saving.  (Which typically means recording a track using the comping feature, then bouncing that comp to a new track, using Melodyne on that, THEN bouncing THAT to a new track.)
 
Ultimately I can live with it because Melodyne Editor is such an awesome and useful tool, and although tedious and annoying, thus far these issues haven't killed any projects, but man.  It would be great if this persistent issue (at least for some of us...I know some people haven't experienced any of these issues at all) was finally put to rest.
 
I'm still on JP and haven't bumped up to Kingston yet, so given the history of issues I've experienced from X3 through to JP, I wouldn't think there's anything Kingston-specific causing the problems the OP is facing.