• SONAR
  • Sonar as Installed is Never Going to Work for Me
2013/06/23 16:49:57
konradh
I have had constant issues for two years since I got a V-Studio 700, Sonar X1, and a Creation Station PC from Sweetwater (along with a lot of software, a desk, etc.).  I am convinced this is never going to work and the only solution is to buy a new PC from someone else, reinstall this huge collection of sample libraries (Vienna, Hollywood, Ivory II, etc.) and start again, either with Sonar or a completely different DAW.
 
Sweetwater thought that the V-Studio interface was the problem and sold me a MOTU; however, the issues I see are clearly related to Sonar. (In fairness, they gave me a great deal on the MOTU, but that isn't the point: the $15K system has never worked.)  Some of the problems:
 
• Recorded waves disappear.
• More than 6-7 soft synths cause all soft synths and sometimes all audio to cease.  The only solution is to delete a soft synth and reboot.  (I have an 8-core machine and 12GBs of memory.)
• Audio goes off and I have to reboot.
• Melodyne locks-up the machine.
• Inputs and outputs of tracks suddenly change; that is, when I open a saved file, they have changed.  I have to reset them one by one.
• Audio meters on interface but does not meter and cannot be heard in Sonar.
 
I can see how one or two things could be interface related, but not all of these—and Cakewalk doesn't think they are interface-related.  KEY POINT: I cannot find any other V-Studio user who has these problems, which makes me wonder how it could be an interface problem.
 
Right now, I spend far more time rebooting and messing with issues than with recording or mixing and I am in the horrible position of 1-taking many months longer than I should to finish a project, redo lost work, etc. or 2-taking even more time and spending more money trying to set-up a new system.  A new PC, interface, and DAW would not take long to set-up (although it would be expensive), but I have to consider the installation and configuration of all the virtual instruments, plus the time needed to import work, redo projects, etc.
 
The situation is getting desperate.  Actually, it was desperate a year ago, but I tried to stay calm and work through it.
 
My theory is that Sweetwater configured something incorrectly initially and that I have a corrupted platform.  The technician who originally set up the system had never done it before and was in training.  At one point, I sent the system back to Sweetwater for a redo, and that same tech started the uninstall and clean.  I found out, made an emergency call, and a senior tech took over.  Still, I am not confident something was not missed.
 
2013/06/23 17:22:56
Shambler
Hi Konrad, do you think there is a hardware fault with your PC?

If not I would install a fresh hard drive and reinstall everything.
2013/06/23 17:25:14
John
Before I did anything I would talk with Jim.
2013/06/23 17:41:24
AT
It seems like it is computer related.  Or the way Sonar was installed.  I'd hate to chuck a whole system when only one part is at fault.
 
Have you tried hooking up a different computer - not putting in all the vienna etc., but hooking up the 700 and sonar through another PC?  I only had the VS 700 for a short while (for testing) but it ran fine on my 2nd computer (older/slower).
 
Another thing is each addition of software is a chance to screw up a perfectly fine system.  It ain't an iLok horror story really, but my system has been flaky lately.  It seems that certain projects that I used my Nomad stuff on would freak out and crash the project or wouldn't load - sporatically.  As you know, this is a real bit ... bear, to track down.  When I tried opening an old project the other day to use as a template for the same band, one of the Nomad packages wouldn't load, wanted authorization and didn't find the iLok. I had time today to track down the problem.  I had some of the Nomad packs, but also authorization for their complete package.  It was the older packs that were blocking things since their authorization was dead, but they had been put back on the iLok.  Only by going to ilok and downloading their new software and deleting the old packs could I get things running.  The funny thing is I had not been to ilok in a year or two, but they just changed their software and when I had my computer hooked up to the internet for updating it must have done something w/ ilok without me doing anything.  This has been going on for about a month and I hope I solved the problem.  My point is not to cry in my beer but just that stuff does happen that don't make sense. 
 
Before I'd chuck a $15000 investment I'd replace the computer.  I run my system on a $700 HP, but I'm sure Jim or somebody could make you a computer, load in everything and make sure it was right before sending it back to you.  Sweetwater is cool, but they are not the first company I'd pick to do me a computer.  Id' rather use somebody I knew and who knew SONAR.
 

2013/06/23 17:45:49
soens
It does sound like a hardware issue. Even a rogue video card can mess things up like that.
2013/06/23 18:03:41
konradh
Interesting thoughts, guys, thanks.
 
1-Which Jim do you mean I should talk to?
 
2-I wouldn't toss out all the expensive software, of course, but reinstalling everything on a new PC is basically starting over, which is what I think I need to do.  I already have the MOTU interface in my rack (in addition to the V-Studio) so it would just be a matter of a new PC; but I have two albums that are so late it's ridiculous and rebuilding everything and reloading all the software on a new PC is an overwhelming task.  I may have to, but it would be nice to find a simple root cause. 
 
Given the history, I think it is some registry or driver issues, but I am not qualified to know or to chase them down.  I like the people at Sweetwater and don't want to turn on them, but there is no excuse for leaving me in this situation for two years.  I offered to cover the flight and hotel for a tech to come here for two days, but they didn't want to do that.  They have tried to analyze things remotely and, as I said, at one point I sent the system to them for a fresh install, but none of this helped.
2013/06/23 18:05:22
gswitz
Do you always use project templates? I almost never do. Yesterday, I decided to use one and I've encountered some trouble since. Just a wild guess, but maybe try starting a project without using one of their templates and then import Pro Channel templates etc. I have never encountered having to unplug my interface until today, and it's happened more than once today. Unplugging my interface and then re-launching Sonar has seemed to patch things for me, but I'm getting TONS of weird behavior.
 
For example, I copied a project I wanted to use as a template, opened it, clicked ctrl+a and delete. Clips on 3 of the selected tracks did not delete.
2013/06/23 19:12:10
CoteRotie
One possibility here is a bad memory DIMM.  That can cause problems very much like you're describing.  Google Memtest86, and do a thorough test on your memory.  If that's the problem, the fix is as easy as plugging in a new DIMM module.
 
Good Luck,
 
John
2013/06/23 19:19:36
Beepster
I'd be PO'd if I ordered a fancy DAW system and they let a rookie build it unsupervised. Letting him have a crack at it AGAIN afterward would be unforgiveable. I was looking at those Creation Stations before I decided to just build my own. Glad I didn't go that route.
 
And I think John means Jim Roseberry from StudioCat.
 
Hope you get it sorted. That sounds like a nightmare.
2013/06/23 19:51:45
soens
My last few DT systems I built myself. The last one wound up with a bad DIMM module which I determined by inserting them one at a time and booting up. They replaced it for free and it's worked great since.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account