• SONAR
  • AD2, Melodyne, Dropped Keyboard Shortcuts and Dropped Drivers from System Issues
2014/05/30 00:57:03
Fabio Rubato
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
2014/05/30 11:23:55
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.
2014/05/30 19:19:20
Fabio Rubato
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. 
2014/05/31 03:25:19
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 
2014/05/31 09:05:42
FCCfirstclass
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......)  
2014/05/31 10:37:24
robert_e_bone
Noticed your sig has X3d in it.  If that is correct, I recommend you install X3e.
 
Also, when Sonar will not restart, was it running with any 32-bit third party plugins when it crashed/hung?
 
Bob Bone
 
2014/05/31 19:55:06
Fabio Rubato
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.
 
 
 
 
 
2014/05/31 20:02:15
Fabio Rubato
robert_e_bone
Noticed your sig has X3d in it.  If that is correct, I recommend you install X3e.
 
Also, when Sonar will not restart, was it running with any 32-bit third party plugins when it crashed/hung?
 
Bob Bone
 


 Hi Bob. I don't think so. I try not to use 32bit plug-ins in my comps. They're on the system, but I rarely need them or use them, if at all. Sonar will eventually restart after it's stops working - usually after I unplug Quad-Core and midi usb - then after a little while, it will disappear from Task Manager...seems to take a bit of time to be flushed out. But in restarting Sonar, it for some reason doesn't see Quad-core drivers, even though they're on the system. There are no work-around to get Sonar to see my audio drivers short of a system re-boot.
 
Alan
2014/05/31 20:06:06
gswitz
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.
2014/05/31 20:57:44
robert_e_bone
Is there any chance Windows is Selectively Suspending (disconnecting) your interface?  It does this by default, and you can change this in Advanced Power Management settings.
 
Also, what happens if you either power cycle or unplug the USB connection of the interface and plug it back in (when things crash/hang).  I am thinking that might reload the drivers and free things up faster than rebooting.
 
Bob Bone
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account