Hi folks,
I've noticed something strange about Autotune 7 (vst64) in Sonar. In both X2 and X3 I would sometimes add AT7 to a project and when the plugin UI opened it would just be blank. This did not happen on every project and I can't seem to find a good recipe, but I do have project for which it is the case every time.
 
I've just built a new computer and a new install of Sonar under a new OS (went from win7 to Win 8.1, both 64 bit) and the behavior has persisted. Anyone else seeing this with AT7?
 
My specs:
Sonar X3 x64
Occurred on two different systems. Replicated with both a Lynx AES16e and now an RME HDSPe MADI Fx.
 
Thanks,
Dean

Intermittently, yes I have the same issue. I've most commonly seen it happen when I've had multiple instances of it in a project.
 
greg

Hi Greg,
Thanks for responding. Ya know, come to think of it, multiple instances in a project seems to be an indicator here as well....hmm.
 
Anyone else? I'm planning on giving the folks at Cake a call or something, but I'd like to get as much info as I can first so I can help them get to the bottom of whatever is going on...
 
Dean

Hunh...well this is interesting. It looks like the problem is caused when a project uses lots of RAM and there is more than one instance of AT7. I've replicated it with just a couple of synths that use a total of about 13GB of RAM. Once that happens, if I add a couple tracks of AT7 I get the blank screen.
 
The fun part, though, is this: I'm one of the folks around here that uses more than one DAW in my joint. For kicks I thought I'd see if I could replicate the behavior on other DAW's, and sure enough, the same thing happens in Reaper 4.55 and Cubase 7, in fact, in those hosts it just outright crashes the DAW. Haven't tried in PT yet, but since it's not a VST in PT it's probably not apples-to-apples.
 
Anyway, sounds like I'm off to contact Antares support. Figured I'd post this for posterity.
 
Dean

very interesting... please report back any feedback from Antares!