You said this:daviencrow wrote:flugel45 wrote:Yep, exactly my point!lawapa wrote:Quote<Dedicated DAW that is not connected to the internet. (Making most of your tips unnecessary)>quote
One for Sonar, P5 and one for Vegas 6 and SoundForge 6 An audio DAW and a Video DAW. Neither one has ever seen the Internet and was custom built for each application. This is the perfect solution. The DAW is isolated. Not a single Game or any fun stuff installed out side the intent. Doing audio doing video. The maker knows the software and all the tweaks. And test runs at high CPU. This might sound extreme to some but it has the benefit of little or no surprises when doing your software. Bugs happen but if you expose your self to the Internet these high CPU apps get crabby.
Hey, good to see you, Larry. (I'm a semi-regular at Digifreq, and we've exchanged a couple of emails a while back).
JD
No I said or implied (either way you misunderstood) Sonar 5's installation and 4.0.3 - 4.0.4 patches caused the Mess that needed to be cleaned up .. especially the problems with the plugin manager and VST adapters. And most of the cleaning up suggestions were to people who don't know of wonderous things outside of the acsessories > system tools program menu.
"HOWEVER the crash was caused by Several Factors NOT A SONAR 5 Bug..." and a ton of other stuff that most readers are likely to skim over, barely getting the gist of it...
If somewhere in all of that you stated it was Sonar's fault, then I apologize.
Thanks anyway for the detailed notes. I'm still on v.4 now, but when I do go to V5 I'm sure these tips will come in handy.
Having said this, I disagree with your statement about "all of your tips being necessary" (you are kidding, right?). Many of us choose to stay off the internet for good reasons (mentioned by others in this thread) and I'm not going to turn this into a debate about that, so I'll just say --
Regards
JD