[Fixed in X3d] Antares AVOX 4 64bit Plugins cause Sonar X3 to crash

I'm in the process of downloading them. I'll look out for any problems and let you know. Welcome to the SONAR forums by the way.

I've downloaded the Avox 4 trial but it has a corrupt file in it somewhere. Waiting on Antares technology support.

Yep, confirmed here too. AVOX plugs crash X3c every time they're inserted in a project.
 
Dean

I am having the exact same issue when attempting to use the 64-bit version of Antares Mic Mod EFX with Sonar X3c... although the 32-bit version had no issues.
 

This has been reported as being fixed in X3d.  You can read about it in the above thread announcing the arrival of x3d.

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....)

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.
 
 

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
 
 

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
 

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
 

Cakewalk Support, try this:
 
1. Open a new empty project
2. Insert an audio track
3. Drop an AVOX Sybil VST3 into the effects bin on that channel.
4. Switch AVOX Sybil off using it's "power" button
5. See the "Audio Dropout" error message appear.
This simple series of steps is causing the audio engine to stop unexpectedly every time I do it.   Whatever is causing this must have something to do with my other problem. 

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for  0:04:00  (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BYRDSTUDIOS
OS version:                                           Windows 8 , 6.2, build: 9200 (x64)
Hardware:                                             ASUSTeK Computer INC., M4A89GTD-PRO/USB3
CPU:                                                  AuthenticAMD AMD Phenom(tm) II X6 1090T Processor
Logical processors:                                   6
Processor groups:                                     1
RAM:                                                  16126 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   3211.0 MHz
Measured CPU speed:                                   4272.0 MHz (approx.)
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs):   296.922909
Average measured interrupt to process latency (µs):   7.233788
Highest measured interrupt to DPC latency (µs):       293.414690
Average measured interrupt to DPC latency (µs):       1.893250

_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs):              55.742136
Driver with highest ISR routine execution time:       Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%):          0.005129
Driver with highest ISR total time:                   ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Total time spent in ISRs (%)                          0.008136
ISR count (execution time <250 µs):                   19890
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                0
ISR count (execution time 1000-1999 µs):              0
ISR count (execution time 2000-3999 µs):              0
ISR count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs):              387.326690
Driver with highest DPC routine execution time:       tcpip.sys - TCP/IP Driver, Microsoft Corporation
Highest reported total DPC routine time (%):          0.045746
Driver with highest DPC total execution time:         dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%)                          0.094109
DPC count (execution time <250 µs):                   187452
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                43
DPC count (execution time 1000-1999 µs):              0
DPC count (execution time 2000-3999 µs):              0
DPC count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

Process with highest pagefault count:                 taskhostex.exe
Total number of hard pagefaults                       2
Hard pagefault count of hardest hit process:          1
Highest hard pagefault resolution time (µs):          703.663968
Total time spent in hard pagefaults (%):              0.000051
Number of processes hit:                              1

_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       1.555786
CPU 0 ISR highest execution time (µs):                6.152912
CPU 0 ISR total execution time (s):                   0.000052
CPU 0 ISR count:                                      12
CPU 0 DPC highest execution time (µs):                387.326690
CPU 0 DPC total execution time (s):                   0.308322
CPU 0 DPC count:                                      92373
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       0.427797
CPU 1 ISR highest execution time (µs):                31.000623
CPU 1 ISR total execution time (s):                   0.000152
CPU 1 ISR count:                                      27
CPU 1 DPC highest execution time (µs):                88.975086
CPU 1 DPC total execution time (s):                   0.004195
CPU 1 DPC count:                                      659
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       0.318266
CPU 2 ISR highest execution time (µs):                33.170975
CPU 2 ISR total execution time (s):                   0.000370
CPU 2 ISR count:                                      71
CPU 2 DPC highest execution time (µs):                90.826534
CPU 2 DPC total execution time (s):                   0.004006
CPU 2 DPC count:                                      702
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0.355116
CPU 3 ISR highest execution time (µs):                31.132358
CPU 3 ISR total execution time (s):                   0.000432
CPU 3 ISR count:                                      84
CPU 3 DPC highest execution time (µs):                105.493616
CPU 3 DPC total execution time (s):                   0.005209
CPU 3 DPC count:                                      812
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       0.545667
CPU 4 ISR highest execution time (µs):                31.507630
CPU 4 ISR total execution time (s):                   0.003436
CPU 4 ISR count:                                      580
CPU 4 DPC highest execution time (µs):                106.895048
CPU 4 DPC total execution time (s):                   0.021671
CPU 4 DPC count:                                      2349
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       2.421488
CPU 5 ISR highest execution time (µs):                55.742136
CPU 5 ISR total execution time (s):                   0.112731
CPU 5 ISR count:                                      19116
CPU 5 DPC highest execution time (µs):                167.615073
CPU 5 DPC total execution time (s):                   1.011846
CPU 5 DPC count:                                      90600
_________________________________________________________________________________________________________