sonar x1d expanded & Automap 4.3

please, anyone with sonar x1d expanded and Automap 4.3, would you please check:
 
As soon as a automapped plugin is instantiated twice in a session, sonar crashes...
 
Can anyone confirm?
 

I can confirm this as well. If I add the automap version of the vst plugins the second instance opened crashes sonar. I first experienced this with rapture, but also reproduced it with dimension pro. I'm using Sonar X1d and Automap 4.3. 64 bit versions of sonar and plugins. If I create tracks using non-automap plugins, I do not run into this issue.

Same here.  I thought it was only Rapture, but Dimension does it too.

Automap has made the generic ACT control surface attractive, which is something I really didn't think was possible.

FWIW - Focusrite are the authors of Automap and, based on that, I have sworn to never buy one of Focusrite's audio interfaces.  If they can't get Automap right, I shudder think how badly they could screw up drivers.  They make M-Audio look positively competent by comparison.

It reminds of the old "In Living Color" sketch where mediocre beauty products came with an ugly person to stand next to you so you would look good by comparison.  Perhaps that's Automap's real purpose in life.

That's useful information about the drivers.  I have been eyeing the 8i6 but have been very reluctant to go there because of my experiences with Automap.

I agree that M-Audio is pretty bad with drivers.  I have slowly been divesting myself of M-Audio gear.  The last piece is my FW-Solo which took forever to get good drivers for (but they work now).  I just want to make sure I end up in a place that is at least as painless as where I am now (but with more inputs).

I have just received this message from Novation so hopefully we should have a resolution soon. Happy days  :)


"I have tested this problem over the last two days and replicated this crashing. The good news is that it has been addressed in the next update of Automap, 4.4. As soon as a Beta version is available I will post on the Cakewalk forum thread you passed on to me."

Ah good.  I'm having lots of trouble using AU 4.3 in X1 64bit.  ;>

Now that's support. I like your style, Ben.

I dont seem to get crashes with 2+ instances but AU just doesn't work for me here (or at least very stuttery)

I have another question concerning Automap and Sonar:

How to RECORD events (faders, knobs, switches) on track, when you use "automapped" plugin?
I noticed, that I can use my Nocturn to edit plugins (ie. synths) parameters, but I can't record changes....
Anyone?

I have Nocturn and Automap because I really hate Sonar's ACT, but it's a joke, or something...

Are you talking about problems recording the synths automation or sonar's actual track automation when you have a an automapped synth attached to the track?

Alright, scrap that. I fixed that issue. So, no crashes. And I can indeed write automation and save automation in contrast to Adrians post. HOWEVER!! The automation writing on plugins has a dreadful resolution. I can drag the knobs on the plugin with the mouse and they write fine. I can write track things like pan and volume with the controls on the Novation just fine. However, when I try and use the Novation to write Plugin parameters, barely any nodes are recorded. The knob in the plugin GUI appears to be acting fine but I get barely any nodes, resulting in random, square shaped automation.

Forgive me - do you mean you're changing the default mappings? I would have thought 'MIDI learn' is something that doesn't get used with automap. If I want to change the settings in automap, I press Save As Default for This Client or something like that...Client being a particular plugin, or the Sonar mixer. Then that will become automaps new default mapping. If you change a setting in automap and don't press that it will indeed be lost.

Fog


 

but the novation stuff (same company really) , I've not been so happy with , the nocturn OK, launch pad "ok" but the SL mk2 , problematic .. partly the build quality, considering the high cost. automap does work ok in other things, but  the relationship between them and cakewalk I don't get.. solely because they don't exactly go out of their way to give info properly. Cakes site has stuff that changes the config (to work better with ACT) and in turn that messed up things I use that are none cake. Trying to get it to factory reset has proved impossible also. 
 
I do hope people from the companies read this, I am / was a customer of there's and such antics really does make me go elsewhere. I'm not trolling etc.. I am a customer of them, just it gets tiresome when you want to make music and spend time faffing about writing emails etc.

fog, I've had some mixed but mostly good results with novation controllers.  I did have driver issues that just hosed a whole laptop when I was trying to put together a little portable vacation rig based on the xiosynth, but I have had great results using an SL Remote to control the pro-channel. It took a bit of work - automap doesn't do it, but with a custom (SL) template on the other midi channel and a custom ACT preset I can use either with one touch of the controller.  I looked at the stuff on cake's site re: ACT setup for the SL, but really, it's woefully incomplete to the point of being just wrong, as it leaves the novation unit in a state of diminished functionality that would lead me to a bad evaluation of it had I not already worked it out another way.  If I'm pinning a tail on any donkey here, in terms of the difficulties between sonar and novation/automap, it would be cake.  Other than controlling sonar, automap has worked famously, and in setting up the non-automap side of the novation software to work with ACT, I was impressed with the conceptual quality of the whole software/firmware scheme.  It did take some imagination to see how to fit it all together, but when it clicked, I thought it was really nice.   Also it did take a few days of trying things to get it going.

Another poster here has also had good results, too, and provided me a lot of encouragement when I started in at this. 

re-reading your post one last time, I think you might need to make sure you are doing the ACT stuff on a a midi channel/ SL template other than the Automap one.  Be glad to share what I did if you think it'll help you.  Which novation ctlr do you use?

(also I read somewhere that people were staying with older (3.x?) automaps with sonar, but that may be a whiskey memory from late one night.  I know I am on a much older version of automap. But really, the trick is getting automap out of the way in situations where it it isn;t going to play, as in with anything cake that isn't VST - PC or sonar proper)

use the shell to vst utility and create vst version of waveshell ....