I was given an incredible upgrade offer that I couldn't resist. It's installed and works like a charm as a VST 3 in X3d. All good here. Thanks Cakewalk for the fix and Antares for the fix and great special.

I'm very glad to hear this is fixed in X3d... have most other Antares stuff but hadn't updated them to 64bit as they took so long to go 64... and the $99 AVOX4 upgrade expires tomorrow... wasn't gonna do it based on this thread but thanks, Mike... and you are now responsible for me loosing another 10lbs... as I won't have any food in the fridge next week. 
 
(hmmmm... I could stand to loose another 10lbs....)

Hello Mike, Byrdlander, et.al,
I just found this thread regarding the new Antares 64bit plugins. I have the same issues.
Up to now I used the 32bit version of Harmony Engine EVO which did a good job in Sonar. Recently I upgraded to the new 64bit VST3 version and I also bought the 64bit Autotune Live VST3 plugin.
With the X3d update the plugins started to work but with a poor audio quality. I experience frequent click noise and drop outs, even at very large buffer sizes.
Do you face the same behavior? Any ideas what to do next?
 
Thanks, best regards, and a great start in 2014!
 
Peter
 
__
Intel Core , 8G RAM, 256 GB SSD, W7pro64, Focusrite Scarlett 18i8
 

I would like to raise this issue again, while the 64bit AVOX no longer crashes Sonar X3d, they are still not useable.  Clicks and dropouts, exactly the same as I experienced with Auto-tune 7 and Auto-tune Live.  It is easy to reproduce, no matter what buffer settings I have, there is no change.   There is something still not quite right.  Please advise.
 
 

Please provide the following info:
 
Sonar Driver Mode, Sample Rate, Record Bit-Depth, Total Roundtrip Latency, Record and Playback Buffer Sizes
 
Audio Interface model, driver version, Sample Rate, ASIO Buffer Size
 
Just want to see if there is anything with your settings that might contribute to your dropout/crackle issues.
 
Thanks, 
 
Bob Bone
 
 

Wow - I have to say - I looked at the Antares forum, to see if I could find info on this issue.
 
What a dismal forum - looked like nobody bothers to post there.
 
Thank you Cakewalk folks, for popping into these forums so frequently.  I hadn't realized how much of a luxury that kind of support can be. :)
 
Bob Bone
 
 

Hi Bob,
 
Sonar Driver Mode = ASIO
Sample Rate = 48000
Record Bit-Depth = 24
Total Roundtrip Latency = 13.9 msec, 666 samples
Playback I/0 Buffer = 256
Record I/O Buffer = 256
 
Audio Interface = M-Audio Profire 2626, Firmware 1.0.10,
Driver Version 6.1.1 , Control panel version 5.10.0.5084 1.0.9.1
Sample Rate = 48khz
ASIO Buffer size = 256
 
Thanks for your reply and offer of assistance!
 
 
 

OK - I am going to suggest you try to adjust a couple of things, from your above response with the requested info.
 
This is for a test - if it works, cool, if it does not, you can change to other settings or back to what you posted above, so not to worry.
 
I think the 48 k Sample Rate is fine, and it is good you match between Sonar and your interface, as that can cause nasty things to happen if they differ.
 
I would like you to try:
 
1.  Adjust your audio interface ASIO Buffer Size from 256 down to 128.  After making this change, power cycle the interface, to get a nice clean set of buffers and fresh memory.  Making this change will reduce the latency within Sonar, and you can see this in Preferences>Audio>Driver Settings.  You want to try to be at or a little below 10 milliseconds for your Total Roundtrip Latency value.
2.  In Sonar, change your Record and Playback I/O Buffers from 256 each to 512 each, then click apply.  (You can hold off on this one until after testing the above change, if you would like.  Some folks report better audio quality at 256 - which is the new default - and some others get better quality at 512).
 
So, for sure try the first change to your audio interface, then fire up Sonar and you should see your reported latency values improve, by going down some.  See what this change does to your sound quality.
 
IF all is well, then you can skip trying number 2, otherwise, go ahead and also change those buffers to 512 and click Apply, and see if that helps further.  I do not recall if you have to close and open Sonar again after changing those buffers - I would start by not cycling it, you can always cycle Sonar to be sure or if you aren't seeing the improvement.  I do not know what Sonar does when it is running and sees new buffer sizes.  It's just a matter of making sure those new buffers are utilized, so not to worry either way about hurting anything.
 
Please review and apply one or both of the above, and post back.
 
Bob Bone
 

Bob,
 
Have tried all of the above, with no change in the behavior when the plug-in is enabled.  However, it did bring my latency down and playback is still good otherwise.  
 
I am noticing something very odd with the AVOX SYBIL plugin now.  I had noticed previously that my CPU usage went UP when I disabled the plugin, which I thought was weird.   After these changes, turning off the plugin is causing the first core of my CPU to redline and nothing but static comes out.  Turning the plugin back on removes the static, but the dropouts remain.   Weird.

Can you please post back with what it ended up reporting for your latency values after the changes?
 
Also, it is certainly possible that there is some issue with the 64-bit plugin.
 
I do not know what else to have you try, but will let it bounce around in my head for a bit and see if anything comes to mind.
 
Bob Bone