KWILD: I know this doesn't help your issue, but I had so many problems with UAD 6.4 that I reverted back to 6.3. I of course lost 64 bit plug support, but I don't get anymore crashes and all is back to normal thank God.

-Danny

After removing the Novation Automap from UAD Plugs (and some other brands to be honest!) 6.4 seems working fine with Sonar X2a x64 , take a look :

http://forum.cakewalk.com/tm.aspx?m=2757878

KWILD


After removing the Novation Automap from UAD Plugs (and some other brands to be honest!) 6.4 seems working fine with Sonar X2a x64 , take a look :

http://forum.cakewalk.com/tm.aspx?m=2757878

So maybe it wasn't Cakewalk's fault after all :-)

Best Regards
Ludvig

O.K. -
This is a new one for me... So forgive me if I'm running behind on this one.

I'm running all x64 plugins, so no Bitbridge, but this is the first I've read about auto-mapped VST's.

How do I determine which plugins are automapped?



The one error I've been getting has to do with placing a plugin between two UAD plugins in a track or bus. Apparently, UA doesn't like that for latency timing...


Random crashes might be related...

Thanks!

@drummaman an automapped plugi-in is a .dll  that work as wrapper/bridge for the real vst.If you want to automap a plug to take control with any Novation midi controller (is a kind of Cakewalk ACT) you must create (with the Automap application) that .dll for the plug,so for example if you want to automap Cakewalk "channel tools.dll" a new .dll named  "channel tools (Automap).dll" will be created by the Automap application and Sonar load that .dll as a kind of bridge to the real plugin.
Take a look :

http://www.youtube.com/watch?v=-BAhKohE0rA

Thanks K - 
That explains why I've never seen it...

So I can check that one off my fault list - I'm not using it!

Cheers,
MG

This is exactly the reason I wait to install the latest version of CAKE.  I am not blaming the bakers because there are way too many permuations of hardware/software potential conflicts to test them all.

If it is their issue, they will fix it in time (most of the time).  Then when the hotfix comes out, I upgrade.  I don't have a lot of time to work on music and when I do, the last thing I want to be doing is chasing PC problems.

Sorry to hear you are having issues.  One of things that I noticed with UAD x64 plugins, is a really strange delay, inserting plugs in real time while project is playing back.  Use to work instantly, now the system goes dead for a few seconds (audio) and then pops back in.  This has caused a crash a few times when the added plug didn't have enough UAD2 juice (all the DSP was used up).  So, I need to lose the habit of inserting plugs while listening to tracks (even though this makes sense in my mixing metaphor).

One of the changes UAD made to in the x64 version, was to recompile the plugs to work with Apollo in super low latency mode.  Each of the plugs had some global change made to them to have near zero latency in the APOLLO realm.  Perhaps this is causing the new UAD behavior issues in Cake?

Jim

"Apollo super low latency mode"?

 The new low latency feature explains the error pop-up if I sandwich another plugin between two UA plugs.
 That no doubt messes with UA's latency time reporting to the DAW.

6.4 gave us 64 bit, and I'm thankful for that.


I'm sure both UA and Cake are giving it their all, so I just need to learn how to work around the issues for now.


Hmm... Note to self:
Options now are - Use only UA plugins or group all UA plugs in the FX bin, or just don't use them...


...at least we have options...


Now if Cake can just figure out that audio/MIDI timing thing during loop recording...


MG

Yep!Audio/Midi that goes completely out of sync when looping is there from years and i think it's really embarassing for a DAW!!They are still thinking to bells and whistles and completely ignoring things like that!

The new vocal rider is vst3 as far as I know.  Cakewalk has refused to adopt vst3, so going forward we will slowly see more of these type of issues as companies focus on vst3.