PRV -> Quantize -> Audition causes a crash in Platinum Everett

I am using the PRV for the first time.
 
I normally record audio and add drums using the Step Sequencer. In the past I have had some issues with SS so this time I decided to try to use the PRV. I have never done this before so I read up and watched some videos.
 
I downloaded the AD2 template and drum maps (there was a thread about it a while back). I started a new project and used the AD2 template.
 
I selected view PRV, added some notes but there were no sounds. I noticed that the outputs of each note were being sent to something other the AD2 map so I went through, one by one, and reassigned each note to AD2. This time I got the drum sounds. I added some notes (kicks and snare for now).
 
I wanted a swing feel, so I selected the notes and went to the menu Process->Quantize and then pressed audition. Sonar said it was not responding and then shutdown. I re-started Sonar. When I clicked in the PRV on the individual notes, I heard sound but when I pressed play there was no sound. I went into preferences->midi->drum map manager and clicked around (not knowing what else to do) and when I went back to PRV and pressed play, I heard the drum beats again. Not sure what I did.
 
I selected the notes and went to Process->Quantize and pressed audition and sure enough Sonar crashed again.
 
Am I doing something I shouldn't do?
 
When I had problems using SS I was told to use PRV. It is not working out to well for me lol
 
Should I just go back to SS? Hopefully I won't run into the issues I have had with it in the past.
 
Thanks for any guidance you can give me.
 
--Edit--
I took the dogs for a walk. When I got back and re-opened up the project, there was no sound again. I went to preferences->Drum map->Manager and selected a drum and re-set it to AD2, I got sound. I read somewhere about a drum map bug. Is this it?
I selected my notes and tried Process->Quantize again but this time I did not audition. I just hit OK. It worked. I guess it is just audition that doesn't work for me.

Doktor Avalanche
Suggestion, see if any of these scenarios stops the behaviour....
 
Upgrade to Everett.
Try performing a VST reset, specific instructions here (must be RESET then rescan):
https://www.cakewalk.com/Support/Knowledge-Base/2007013315/SONAR-X3-Full-VST-Rescan-Recommended-for-Upgraders
Try a different plugin/soft synth in case the plugin is buggy..
Try running Sonar as Admin.
Update your audio interface firmware and drivers.
See if you can repro on a brand new project...
 
Ta.....

Oops. I meant Everett. I updated the title.
 
I am running Sonar as Admin.
 
My interface is no longer supported. The last drivers they put out were for Windows 8.0 and I have 8.1.
 
I can try again with a new project but it was a new project.
 
I will try again a re-scan and try the audition in this project and see if that makes a difference. If not, I will try again with a brand new project. I was not far into the new project so it should be easy to reproduce.
 
Finally, I will try a different plugin. Do you think it matters if it is another drum program or not? It may have something to do with loading this template? I will try on a different template too to see if that narrows it down.
 
Thanks!

Hmm looks like buffers and latency now.
Try upping the ASIO buffer size.
Also try upping the buffers under Preferences -> MIDI -> Playback and recording -> Prepare using..
(You could experiment with values).
 
Also try disabling 64 bit double precision engine.
Also check your driver settings in preferences...Ta...

Hello. I think the root of your problem may be elsewhere.
I vaguely remember an old post about this... I was looking for
info on the same problem.
 
Don't quote me but I THINK that when you audition from
the quantize page, Sonar auditions through the Windows
kernel.
That means if you {have/don't have?} {the same/another? (E.G. internal card, yes I know that sucks)}
interface set for Windows audio
there will be a conflict(ASIO). WDM might be a workaround if that is true.
 
Try setting Sonar AND the Windows audio to the same interface
then try audition;
 
Then try audition again using 2 different interfaces.
hopefully one of these will work.
 
Not at my DAW, so can not test 4 U.
 
Mel 

yes that is what I meant.
 
I have edited my original post to reflect that I suspect the opposite
of my original suggestion might also be a possibility.
Again sorry I cannot test.
 
Mel
 
Edit: I know for sure I have used another interface to solve this issue
in the BROWSER/audition since the X series.
 

I notice our systems are similar;
will test when in the studio and report.
 
Mel

> I am running Sonar as Admin.
 
OK try not running Sonar as Admin. That's my last guess .
You might want to look at the Windows event viewer for more detail.

I finally got a chance to call Cakewalk and they were able to reproduce this problem. I am hopeful they will fix it :-)

I tried it and don't get a crash but if i use a drum map like you there is no sound - if i remove the drum map the sound is back. The problem seems related to drum maps - or maybe we're are not using this option properly.
 
For the crash - is you HD Audio activated (windows device manager) - if so disable it to see if it solve your crashes
 
Good luck!
 
PS. i'm using the latest Everett update

FWIW I tried Process->Quantize->Audition in Foxboro and I have the same issue. Sonar locks up and has to be restarted.