Request help troubleshooting PLparEQ3/SONAR issue

Hi All,

For those who got in on the $20 deal and are using PLparEQ3 and SONAR 5.0.1, I am trying to duplicate cpu maximization and stuttering issues I am experiencing in a very specific use of PLparEQ3. Basically, I have observed that PLparEQ3 will cause a CPU bogdown regardless of steady-state CPU utilization if it is used on a softsynth playback track(behavior duplicated with Dimension Pro and Sytrus). This bogdown typically happens right at the start of the audio playback of the softsynth or about 10 seconds after playback form the softsynth starts(ie: when audio data stops going to PLparEQ3). I have been spending my afternoon trading emails with David McClain of Refined Audiometric Laboratories trying to sort this out and for anyone with PLparEQ3 and SONAR 5.0.1, if you could run the following test, it would help to see if this problem is only on my particular system. ThanX.

Need those of you with SONAR 5.0.1 and PLparEQ3(version 2.07 if you've been keeping up with the updates) to create the following project file:

New project with one stereo track playing back anything(make it at least 2 minutes long please)
Create a stereo track for softsynth playback
Create a midi track for softsynth playback
Activate an instance of Dimension or Dimension Pro and link it up with the second audio track and the midi track
Set your latency to about 61msc
At about the 20 second point into the song, record something complimentary(or not!) to the playing track(track 1) for about 10 seconds on the Dimension instance. Yes, your latency will make it sound bizzare...it doesn't matter, I am setting the latency for consistency.
Now playback and make sure the Dimension track works.
Now add a PLparEQ3 instance on the Dimension audio track. Enable a LPF in PL mode.
Now playback your project and observe.

Please post back here your initial CPU utilization, soundcard and whether you observe any stuttering and/or CPU meter going into the warning zone. Negative AND positive responses desire.

ThanX guys. The workaround is to freeze the synth track but that is obviously not desired. I just want to see if anyone else is seeing this issue.


BTW, I am posting this here because it only happens in SONAR...can't duplicate the behavior in P5(my only other playback engine)