| 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
|
|
|
|
|
|
|
|
| Re: I can't say anything awful about cubase.net ever again [message #78918 is a reply to message #78917] |
Wed, 24 January 2007 09:53  |
Deej [4]
Messages: 1292
Registered: January 2007
|
Senior Member |
|
|
There's a major war happening here with my new Gigabyte
mobo/Cubase4/Synchrosoft dongle/3 x RME cards with the most recent beta (32k
buffers) drivers and UAD-1 cards. It's a beautiful cluster**** so far which
has taken a perfectly functioning OS and trashed it completely. I'm getting
it sussed though and I've learned a few things about this mobo in the
meantime, such as the *assignable* IRQs ain't so assignable after all, that
certain slots in this mobo just absolutely hate to see a Magma host card and
that I may need to use an IRQ affinity tool in order to assign one core of
the CPU to the UAD-1 cards in order for tese cards to work. Also, I learned
that though Norton Ghost *says* you can restore a drive image from a smaller
drive to a newly formatted larger one, in practice, restoring an image that
was created on a 40G drive and restoring it to a newly formatted 100G drive
may not be such a foolproof scenario. Also, it's a very good idea to
uninstall any superfulous AC97 audio drivers from your system before you
install Cubase 4 because (on my system) it will inevitably see these and
hang on initialization. It seems to hate these onboard drivers.
The good news is that I now have the RME cards all on IRQ's 17 & 18 and all
of the UAD-1 cards recognized in the Device Manager (though they are still
not functioning) and on IRQ 19. These IRQ's aren't sharing with anything
that would cause a trainwreck so a major hurdle has been cleared. As long as
I don't have IRQ conflicts, everything else is possible.
Also Cubase 4 with the new RME beta drivers seems to have *much* better
performance than Cubase SX 3.1.1.994 and the old RME
drivers......soooooo.........I'm back in configuration hell. I feel right at
home. I'll let you guys know what's what after the smoke clears. then I'll
probably configure Cubase 4 on another drive image with the Creamware
drivers and get to encounter Thad's particular joyful experience.
mmmmmmm...........more coffee!!!!!!
;o)
"Jamie K" <Meta@Dimensional.com> wrote in message news:45b797e9@linux...
>
> Congrats! Those little quirks can be big time wasters.
>
> I just discovered a conflict between a particular vid cam and my MOTU
> firewire interface. There should be no conflict, yet there is. The mystery
> is now in the hands of tech support. I have a workaround and a hope for a
> real fix down the road.
>
> Cheers,
> -Jamie
> www.JamieKrutz.com
>
>
> TCB wrote:
>> 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
|
|
|
|
|
|
|
|
| Re: I can't say anything awful about cubase.net ever again [message #78933 is a reply to message #78920] |
Wed, 24 January 2007 14:05 |
chuck duffy
Messages: 453
Registered: July 2005
|
Senior Member |
|
|
hehe
filemon would have shown you the bizzare searching, but I guess only that
NG post would have told you why :-)
"TCB" <nobody@ishere.com> wrote:
>
>Ha ha, I _was_ using the regmon! Mark Russinovitch is a deity. It just didn't
>cross my mind that the VST path would matter that much so I was looking
for
>things that were Scope/OS related.
>
>Great tools for sure, though.
>
>TCB
>
>"chuck duffy" <c@c.com> wrote:
>>
>>Hey thad,
>>
>>My goto set of tools for diagnosing this type of shit is sysinternals.
>Whenever
>>an app is taking way to long to start I run filemon and regmon. This gives
>>me a detailed chronological listing of exactly what the app is trying to
>>do in regards to the registry and the file system.
>>
>>I can't begin to tell you how many problems I have solved with these two
>>tools.
>>
>>Chuck
>>
>>"TCB" <nobody@ishere.com> wrote:
>>>
>>>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
