Bub

CakeAlexS

Works for me. Update guitar rig software and sound device drivers.

I'm sure you've done this already Sharke, but Alex is right about the Guitar Rig update.

When Guitar Rig 4 first came out, it did have some problems that were fixed with an update.

I use Guitar Rig 4 Pro extensively. I use it on Vocals, Drums, Guitar, Bass. I haven't had a crash with GR4 since the first update, and I think there were 3 after that IIRC.

I'm not doing the 'it works for me' thing, you know me way better than that. What I am saying is, I have seen problems with GR4, and I was able to fix them with an update, but that was quite some time ago.

..........................

I too have also seen problems with projects going bad after a certain age. One thing that helped was using Auto-Save, and every once in a while, opening up the Auto-Save file, then saving it as the main project name, thus overwriting the main project while not losing any work. Hope that makes sense. You have to be quick about it, if you open up the Auto-Save project, then you'll have an Auto-Save copy of an Auto-Save file, and the file names get really long and confusing. You have to do this from the very beginning of the project ... if you have an existing project and then turn on Auto-Save, you're just copying the problem, if that makes any sense.

It sounds like a pain, but it's not a big deal at all really.

Good luck!

I've finally turned auto-save on. I was previously just CTRL-S'ing like a madman, but I guess another layer of protection can't hurt. 


Yes I have Guitar Rig updated. I visit the Native Instruments control center every now and then and update all my NI stuff. 


I don't know what it is that makes Sonar projects seem to collect garbage and corruption along the way. Another one that hits me occasionally is I'll get that "the following synths are routed to silent outputs" message whenever I open the project up. The synth it specifies most certainly isn't routed to a silent output, and there don't appear to be any actual problems with it, but it's just another one of those annoying things that makes me wonder what the **** is going on, and causes a great deal of anxiety as I get the feeling that other weird stuff is going to happen.



I had similar kinds of things happen to me in Pro Tools. I lost a few days work one time after PT decided to inform me that a project had corrupted MIDI data in it and was unopenable. I had to ditch it and I was gutted. I'm always nervous of stuff like that happening again. 

Anderton


This thread made me aware of something I'm doing wrong, so I thought I should comment.

I used to have the same "master pro channel crash" thing happen, but it stopped after I installed X2a. But, here's what I'm doing wrong.

I have very limited time in my life, so I often update a bunch of stuff at the same time while I'm in that mode. As a result, I don't know specifically what fixed the problem, so now I can't say "The problem went away when I..." But I did something that solved that problem...wish I could tell you what, but all I know was that it was around the same time as the X2a update.

Obviously the right approch is to do an update, run the program for a while, do another update, run the program, etc. 

Doh. And good luck!

Yeah often laboratory conditions are required to get to the root of a computer problem. It sucks but it's true.