Greg Wynn

I actually crank up Audiogridder sometimes because it catalogues all of the VST’s quite well and makes them quickly searchable.

Love the review but they REALLY need to get the name of it right !

The more recent updates have absolutely optimized Sonar - I remember using it the first time after the update and the difference was immediately discernible. And if there is even MORE optimizations then bring it on !

All the outputs go to “none”

Agreed , odd as I deleted the Fractal ASIO driver and yet the message comes up if Sonar is running and then I power up the Fractal, eh ? I I say to add it it then reverts Soner to 48k and completely remaps all my track and bus I/O’s. However now I can have the Fractal powered up before instantiating Sonar and it’s fine whereas previously Sonar would attempt to add it. EDIT - to answer the question - yes I was hoping to exclude the message. Thx for responding, @Noel Borthwick !

FIXED (sorta) - Spent some time on the Fractal forum and this has been an issue with Fractal and Cakewalk/Sonar going back to like 2010. To be clear I’m sure it’s more an ASIO specification issue rather than a Fractal or Sonar issue. Lots of trying different things and finally settled on uninstalling the Fractal ASIO driver which to my surprise didn’t resolve the issue (perhaps the Fractal was grabbing my MOTU interface drivers ? Dunno). Finally settled on cranking up Sonar with both interfaces on and the deselecting all the Fractal drives in Sonar prefs. However I’ve done that previously but… So here is the where I am I’m cool with it. Before if I turned on the Fractal while Sonar was running Sonar would then ask to grab the Fractal which would change everything to 48k and wreak having on every track and buss input/output. Frustrating. So now I can have the Fractal powered up BEFORE starting Sonar and it’s fine which before would cause Sonar to act like I turned it on after Sonar was substantiated. I can live with it Thx to all who helped ! @msmcleod while I am comfortable delving into the Registry, I elected to go the route I did but if things get wonky I’ll try your suggestion.

@mettelus found it - thx !

I don’t see it on my iPad. I’ll try from a PC.

Gonna give this a whirl as well. http://forum.cakewalk.com/Tell-Sonar-to-ignore-audio-interface-Solved-m3309613.aspx

@mettelus how do I edit it ?

Thx @msmcleod ! I’ll try that. I should know this but how do I edit my initial header “How can exclude a midi device (Fractal AxeFx)” to a more accurate “How can I exclude a Fractal AxeFx from coming up as an audio adapter in Sonar?”

@Amberwolf you are absolutely correct - I’ll change the title to a more accurate “How can I exclude AxeFx as an audio interface” ? Thanks for the feedback - you’re spot on.

So I record at 44.1k and ONLY have midi to my AxeFx to utilize the softwares that controls it (Axe Edit). The AxeFx only outputs at 48k however I don’t record via USB and only via straight audio (L and R out into my MOTU interface L and R in). Because of this I have to be careful to first start up Sonar and once it’s initialized then power on the Axe Fx. After that I get a message asking if I want to add the Axe Fx - which I respond no because if I do everything tries to reset to 48k - which is hugely problematic as I ONLY use audio from the AxeFx and no midi or USB functionality. So is there a way to permanently “exclude” Sonar from trying to add the Axe Fx ? Thanks !

And likewise I wish “record” didn’t reset to “comping” rather than “sound on sound”.

Tracked for many hours last night and tonight as well as got some mixing in. Everything is working great ! Thank you !