AD2, Melodyne, Dropped Keyboard Shortcuts and Dropped Drivers from System Issues

Hi...few on-going issues that's not looking good for my X3e.
 
1. Melodyne won't update and continues to crash Sonar, unless I mix down the audio - despite recommended buffer, it continues to tell me that it's not enough - confirmed by Support. The latter suggested uninstalling, but I already tried this and couldn't get it back on - backup image. Celemony could not solve this issue. I bought the full program when I had X2...worked okay here.
 
2. Rob Papen's Blade and Blue 2 usage after a time of trying different presets, will make my keyboard shortcuts stop working. Also, presets being used, will jump to another randomly. Support from them did not help.
 
3. AD2 gives me a graphical 'vertical time-line' freeze...ie, the line that keeps pace with the comp, stops - along with CPU graphics - but does not affect sound. It'll start working again after a few seconds. Both projects with AD2 on do this. Freezing the synth stops it. Using AD1 does not have this problem.
 
4. These issue will sometimes cause Sonar to stop working. Restart Sonar after this won't work unless free from processes. It appears to hang...shutting my Roland Quad-Core and Midi keys, eventually sees it disappear from Task Menu. However, Sonar then reports no audio drivers on system. Logging off/on again does not see this change until a reboot.
 
Lots of issues going on here that seem to be slowly accumulating starting with Melodyne. I have a fairly stable system when using AD1, but AD2 seems to have added just another issue to the already several I have.
 
Any ideas from anyone?
 
thanks

dlion16
make sure you have the latest display driver for your gtx590.
 
make sure you have the latest version of ad2. there were problems with the initial version, they issued an update. check your online installer.
 
don't have anything for 1 or 2, but when i run into issues with something specific, i try to isolate that piece, as in, take the clip you want to melodyne or papen into a new blank project, try to process it there. if it works, bounce to tracks and copy to a new track in the original project.

Thanks...yep, latest display, latest version of AD2 - yes their update seemed to improve the dropped keyboard shortcuts, but now have this freezing graphic vertical line - not sure what it's called...normally keeps pace with the comp.
 
Yes, after bouncing a Melodyne track, a project generally behaves well. I'd just like to be able to update it and no-one - including both Cakewalk and Celemony - knows how to solve this.
 
Thanks for your suggestions. 

Anderton
 
Perhaps Melodyne got confused because I had the install from X3 and an old install from Studio One on the same machine...or maybe it was a test to see if I was worthy of Editor 

Craig, take a bow and yes, you are worthy of Editor.  (Now Garage Band on the other hand......)  

Anderton
I don't know if this is the answer to your Melodyne issues, but here's what worked for me.
 
I tried updating to Melodyne Editor tonight...went to my user area, logged in, downloaded the software, and ran it. Melodyne wouldn't update, and if I did a bounce to clip with Melodyne, Sonar crashed.
 
So, from within Melodyne, I went  Help > Licenses and upgraded from within Melodyne. Melodyne upgraded with no problems, but I still had crashing issues. I did a reset and rescan of the plug-ins. I've now put several hours into using Melodyne, and it's working perfectly. 
 
Perhaps Melodyne got confused because I had the install from X3 and an old install from Studio One on the same machine...or maybe it was a test to see if I was worthy of Editor 

Thanks for your response...I must not be worthy. My Melodyne 64bit single editor is 2.1.2 - the latest verison. That's when I start is outside of Sonar. However, when I load it in Sonar, it's 2.1.1. So go figure. It would appear that during the update, it's not updating the Sonar VST...so that would indicate the scan is not seeing the correct installed update?
 
I've tried finding it and as far as I can work out, it should be scanning all the VST's on my system. I think from memory I checked Sonar X2 and it was the correct version...so I'm stumped and feeling unworthy.
 
 
 
 
 

Anderton
So, from within Melodyne, I went  Help > Licenses and upgraded from within Melodyne.

For me, I didn't find the upgrade here.
 
I had to launch Melodyne independently from Sonar and I found the update button under File > Preferences.
 
It said my software was up to date and it was set to check weekly for updates automatically.

<p>

gswitz</p> <p>

Anderton</p> <p>So, from within Melodyne, I went &nbsp;Help &gt; Licenses and upgraded from within Melodyne.</p> <p>

<br />For me, I didn't find the upgrade here.</p> <p>&nbsp;</p> <p>I had to launch Melodyne independently from Sonar and I found the update button under File &gt; Preferences.</p> <p>&nbsp;</p> <p>It said my software was up to date and it was set to check weekly for updates automatically.</p> <p><br />

<br /><br /></p> <p>Yes, mine is up to date here as well...but in Sonar, it's version 2.1.1...and I periodically get sent to the update website from within Sonar, telling me about version 2.1.2. After downloading the update several times and going through the process, it's still 2.1.1.</p>

Some audio interfaces that connect with USB also have power switches and wall power.  Some are USB powered alone.  Unplugging or hitting a power button will reload the drivers in Windows.  Sorry for any confusion.
 
I do not know why Sonar would not see the interface drivers after reloading them prior to restarting Sonar, UNLESS perhaps Sonar went back to WDM Driver Mode for some reason during the crash/hang.
 
Bob Bone
 

robert_e_bone
Some audio interfaces that connect with USB also have power switches and wall power.  Some are USB powered alone.  Unplugging or hitting a power button will reload the drivers in Windows.  Sorry for any confusion.
 
I do not know why Sonar would not see the interface drivers after reloading them prior to restarting Sonar, UNLESS perhaps Sonar went back to WDM Driver Mode for some reason during the crash/hang.
 
Bob Bone
 

My Quad-Core is powered over its USB connection. Unplugging the USB cord effectively drops the drivers from the system. I usually have to do this when Sonar stops working, or freezes and after closing the program - if it is still open - continues to be active as an application.
Going to Task Manager and ending task has no effect, until I unplug the Quad and turn off my Roland USB Midi keyboard. After a time - 5-10 minutes - Sonar is unloaded and is no longer 'active' in TM - Support has called this a driver hang - I can then restart it...that's when I usually get the message there is no audio devices on the system - even though I've turned Quad back on and can play a wave file or MP3, Sonar does not list any audio devices on the system at all.
If I unplug the Quad whilst Sonar is open, I will eventually get a message about it being unplugged and do I want to re-rout blah blah. When I plug Quad back in, I get a similar message, but still no audio device is seen in Preferences.
Logging off and back on does not rectify this...only rebooting does.