Quote:

I would restate that to say that I reverted the setup to where it was before it crashed, and if that is what you meant we are on the same page. If you meant that I changed something, as in "set up something differently before you crashed" that is not the case.





What I meant was (and I know your IT troubleshooting attitude likely prevented it) when RB stopped working, did you try to 'fix something' before your first reboot? A lot of people would click right away on what they thought the problem was to start trying to fix it. I'd have likely started looking at the soundcard settings and tried a couple things (telling myself I remember what the original settings were).
I may be remembering right, but sometimes I don't, and I was wondering if you rebooted first thing, or tinkered a bit? If you rebooted right away I'd think it was more of a software screwup; a zero got changed to a 1 (and sometimes that means an ASCII 0 changed to a 1 in the text of an ini file in RB!). I've looked at them and have gotten pretty good at figuring out those couple files, along with the interface ini files. I've seen it change for no aparrent reason, or at least I don't remember telling it to make the whole toolbar disappear! No idea why it happened and never happened again, go figger.

Maybe the soundcard drivers got corrupted; have you tried the card in any other DAW software sine the crash? That may give a clue as to why you're having trouble getting it going.

You'll troubleshoot it and figure it out, but as a good habit, now you see now why we all say reboot (or at least restart RB) every so often; huge amounts of temp files and cache in digital audio recording/mixing/editing. I think you are a little more understanding of how it could have 'just happened', cause that's possible. Lose track of one little chunk of data and you could get that friendly warning we all hate.

Last edited by rharv; 12/02/11 04:55 PM.
I do not work here, but the benefits are still awesome
Make your sound your own!