| I can't say anything awful about cubase.net ever again [message #78911] |
Wed, 24 January 2007 09:22  |
TCB
Messages: 1261
Registered: July 2007
|
Senior Member |
|
|
Just a funny story. As y'all might expect, I know a little bit about Cubase.
But on my fancy new Core 2 Duo desktop it was crashing. Every time. Like
clockwork. I spent all kinds of time, many, many hours working on things.
I remembered there being problems with the (incredibly annoying) copyright
dongles and voodoo for what order the updates had to be installed/run. Finally
I started going through the crash logs and looking for info from the M$oft
knowledge base for the error codes/memory addresses that were failing. Checking
versions and internal names of various files in the system32 directory against
pristine XP SP2 installs. Generally doing all of the heavy geek shit I would
do if a server patch blew an application out.
Then, after practice last night I happened to do a search for a dll that
happened to link to a Cubase.net post with almost exactly the same problem
I had. Some kind hearted soul who definitely deserves dinner on me pointed
out that sometimes the VST path in HKLM -> Software -> VST is set to c: and
then SX scans the entire drive for plugins and eventually crashes. Changing
that entry to 'c:\...\Cubase SX\VST Plugins' fixed everything. I think it's
a Creamware thing that set that reg key but I'm not positive.
So, no more bad things about cubase.net from me. And yet another reason to
love open source software. I'd have spotted the problem in no time at all
if I could have turned on some reasonable level of error logging. Similar
stuff happens all the time with perl apps and it's just a matter of reading
the crash logs and finding the line in the app that doesn't work or calls
something from the wrong place.
TCB
|
|
|
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
