digital flinching bigtime

menno · Post by **menno** » Fri Jul 16, 2004 6:37 am

I have a similar problem with my new setup, and an ATI Radeon 9200 card. At the moment I have got round the problem by switching off the hardware acceleration. This has stopped all glitches.

Not sure how to resolve the issue properly though.

mrvinyl · Post by **mrvinyl** » Thu Nov 18, 2004 6:58 pm

hello, i'm re-opening this post because my original problem still haunts me.

basically everything works fine apart from cubase sx 2

i'm running p4 3gig pulsar 1 with hyperthread disabled, i disabled it from some of the suggestions on this post, but it hasn't fixed my problem.

all other programs work fine and can handle for instance dozens of reverb units with ease

but when i use cubase, one vst with release turned up and reverb on a tad it blows it top and pc overload bigtime ahhhhhhgggg!!!

pulsar dsp load reads only using 2 of the 4 dsps, its gotta be something cubase internal

but why? I never had problems before with my old 500mhz machine, this is worse than that ever was

any tips grateful
cheers
going bald not much more hair to tear out mr vinyl

interloper · Post by **interloper** » Fri Nov 19, 2004 11:49 am

Might be a memory leak in SX. What version are you running?

Try uninstalling, rebooting & reinstalling SX.

But at this point it's safe to say that it's not related to SFP.

mrvinyl · Post by **mrvinyl** » Fri Nov 19, 2004 12:38 pm

HMM THATS WHAT I THOUGHT SFP SEEMS TO BE FINE WITH EVERYTHING ELSE (im running v4.0 sfp by the way)

tried re-installing sx (v2) still no joy

is there any recommended tests that i can try with the drivers etc within sx

basically the system dies as soon as I apply some processor caning fx, when really a 3 gig p4 should handle it lovely

confusing really because eveything else seems to be fine, just sx aint happy

thanks for any help

interloper · Post by **interloper** » Sat Nov 20, 2004 4:29 pm

I don't think it's the drivers, but I presume that you've got ASIO Scope selected in SX.

If you are applying effects and it craps out, that's related to native processing in SX.

You could try running an older version of SX to isolate the bug to a version. If not, try running another sequencer and see if you get the same problem whilst effecting.

mrvinyl · Post by **mrvinyl** » Sun Nov 21, 2004 12:21 pm

yes defo got asio scope drivers selected disk buffers 4 buffer size 128k ive played with these and it makes no difference.

i've reinstalled sx 1.0 and 2.0 on the same machine and yes it craps out as soon as any decent fx is applied

other progs dont seem to have the same problem, they can handle the pressure no probs, so its got to be native processing within cubase hasn't it?

anything else you recommend I could try, i'm running out of ideas, and thinking im not gonna be able to use cubase, which is what i use most

interloper · Post by **interloper** » Sun Nov 21, 2004 6:29 pm

are you playing back a large number of tracks via audio?

if you had a spare machine, you could install sx on that and go through the same steps. that would isolate the problem to the application if it persists.

if not, then you'll know your pc has a problem, in the OS potentially..

mrvinyl · Post by **mrvinyl** » Sun Nov 21, 2004 7:38 pm

10 tracks audio and midi

tried out sx on another machine and that seems to be able to cope with about 6 vsti's with the release on full and loadsa reverb

test machine was 1ghz p3 with soundblaster card

my p4 3ghz cant handle more than 3 vstis without overloading, why is it??? nightmare

interloper · Post by **interloper** » Mon Nov 22, 2004 11:02 am

Ok, in a sense that's good to know. There are a couple of scenarios:

1. SX went corrupt on your P4 machine, and has left some junk in the registry. Uninstalling SX and cleaning out the registry would help, if this is the problem.

2. Part of your OS is corrupt. A fresh install usually clears up weird anomalies that I've had in the past. SX seemed to work fine on your other machine, so you know that the application alone can't be the problem.

3. There is a hardware problem. If the fresh install doesn't work, this would point to HW issues. Longshot, but hopefully not the case.

When's the last time you performed a fresh install?

<font size=-1>[ This Message was edited by: interloper on 2004-11-22 11:03 ]</font>

<font size=-1>[ This Message was edited by: interloper on 2004-11-22 11:03 ]</font>

mrvinyl · Post by **mrvinyl** » Mon Nov 22, 2004 11:08 am

did a fresh install not that long ago

i'm going to do one now, seems like the best idea then i can test from scratch

be back in an hour hehe
fingers crossed

interloper · Post by **interloper** » Mon Nov 22, 2004 12:53 pm

If you can, don't install ACPI, even though that's more specific to problems with SFP.

mrvinyl · Post by **mrvinyl** » Mon Nov 22, 2004 3:47 pm

one word 'fuming'

right i re-installed windows, didnt get your message about acpi so i've installed it in that mode

anyway my cubase sx is the same as ever one plug in with the release turned up freaks the cpu out and overloads

god damn i'm so fed up

im using xp with service pack 1
p4 3.0ghz with hyperthread enabled
cubase sx 2.02 build 33
sfp 4.0 (background proj set at dynamixer with wave and asio going into channels 1-4 and analog out)
latency in cubase is set at 24.5 with asio scope drivers selected
also i test reason rewired with over 10 modules and get practically zero reading on the cpu meter in reason

my old p3 500mhz was 3 squillion times better than this, im so frustrated help me before the devil convinces me its all bad and i'm never gonna see the light

interloper · Post by **interloper** » Mon Nov 22, 2004 3:54 pm

I don't think ACPI is related to this, it just would have been cool to eliminate.

What plug are you turning the release up on? Is it a verb?

You might have mentioned this earlier, but have you tried disabling hyperthreading?

mrvinyl · Post by **mrvinyl** » Mon Nov 22, 2004 4:35 pm

I haven't tried disabling the hyperthreading in bios, do you think i should try it?

I have tried the pc running in standard mode a while back but it made no difference

ive just been toying around testing, and cubase can handle stacks of audio tracks, but plugins are useless

its fine up to about 3 plugins
z3ta
refx vanguard
vstation

but try to do anything with them half decent and then the pc overload creeps up and glitches out

when i used to have a stable pc (back in the day)
i was running pulsar software 3.1
could it be sfp related prob? but then surely reason and other progs would glitch out under the pressure then though?

by the way not that it makes much difference but when i select pulsar multimedia drivers they wont load, and cubase cant run that test it likes to run

strange, im really running out of things to try now

answers on a postcard, and a reward will be given to anyone who can fix this for me

mrvinyl · Post by **mrvinyl** » Mon Nov 22, 2004 5:06 pm

just tried disabling hyperthreading in the bios and it made no difference

interloper · Post by **interloper** » Mon Nov 22, 2004 8:15 pm

Did you say your meter creeps up until it blows out? I've had this problem before in earlier versions of Cubase, where one plugin has gone bad & eats away at the performance meter until there is no more headroom left. It was some type of reverb or delay, I can't recall.

Let's try to isolate the problem to a plugin, if possible. Don't load the one you've been adjusting the release on. Load as many others as you can. Try different combinations until you find one plug that causes the instability.

mrvinyl · Post by **mrvinyl** » Wed Nov 24, 2004 2:58 pm

Right well I've tested it with the standard vst plug ins like A1 synth and a few steignberg reverdbs and delay turned up full and on the audio of the a1 synth track, and it reads about 1/4 on the vst performance level.

so maybe it is down to the plugins im using

but that doesn't explain how it used to be fine quite a while ago when i first upgraded my mobo and chip, and my friend who has a very similar set up to me can use the plug ins fine on his system?

would xtc mode have anything to do with it do you think?

interloper · Post by **interloper** » Wed Nov 24, 2004 3:41 pm

Very cool. You made some significant progress by going through the motions, reinstalling the OS included.

I really don't know what the reason is, all I know is that sometimes VST's go nuts on my system.

They're like, "Hey, we're going to F*#$ with your track a bit."

There might be some interaction with the VST and the OS that is causing problem, making it hard to isolate.

Once you mentioned that the performance meter crept up until going bust, I had a flashback of that very same problem.

Some VST's aren't coded to well, either, sometimes causing memory leaks. If the plugin won't work, you might opt for others in the interim.

Glad you were able to isolate it somewhat. I always use SFP in the full blown mode, so I can't speak to the mode you are using, but I doubt that's the problem. All signs point to native processing issues.

mrvinyl · Post by **mrvinyl** » Mon Nov 29, 2004 6:30 pm

well ive moved my pulsar card to re-assign irqs just in case and it hasnt made any difference.

its a few processor hungry plugs that are causing me probs, but ive tested these plugs on other machines and they can handle it no probs, and should be able to on my p4 3 gig system, any other tests I could try? im totally out of ideas

thanks

next to nothing · Post by **next to nothing** » Mon Nov 29, 2004 7:25 pm

just a shot in the dark, could this have something to do with the old denormalizing issue? i guess recent versions of the misbehaving vst-plugs would fix that.