Helo community!
When I opening the cubase, I don't now why but the cpu (VST performence) is always going crazy,
it looks like it unstable, and when I'm loading some projects it goes even more...
the computer is new and in general everything works fine.
can someone help?
thanks!
CPU issue in cubase 5
Re: CPU issue in cubase 5
Are you opening projects created on another computer / on a different version of Cubase?
What process get very busy? Cubase, I imagine? Is the disk whirring lots too?
Is this specific to Cubase on that machine? Do other DAWs (Reaper for example) suffer the same fate?
What process get very busy? Cubase, I imagine? Is the disk whirring lots too?
Is this specific to Cubase on that machine? Do other DAWs (Reaper for example) suffer the same fate?
Not because it is easy, but because it is hard...
Re: CPU issue in cubase 5
thanks Eanna for the quick reply!
I open projects only on that computer and only with this version of cubase.
in the beging, when I'm only opening the cubase without any project the cpu is unstable and when I'm loading some projects it goes even more...
I don't use other DAW and the disk is not whirring, but if it does what is that mean?
what should I do?
thanks.
I open projects only on that computer and only with this version of cubase.
in the beging, when I'm only opening the cubase without any project the cpu is unstable and when I'm loading some projects it goes even more...
I don't use other DAW and the disk is not whirring, but if it does what is that mean?
what should I do?
thanks.
Re: CPU issue in cubase 5
By "whirring", I mean does the disk seem very busy when the problem is happening... Is the disk light lit solidly while this problem is happening?
If you open Task Manager (by the Ctrl-Shift-Esc shortcut), click the "Show processes for all users" button, and click on the CPU column, is it the Cubase processes that's max'ing out your CPU?
It's worthwhile to download and try Reaper too, to see if its a problem with the Audio/Midi subsystems of your Windows installation or PC hardware.
For me, you probably may need to raise this on Cubase forums... I'm not a Cubase user, so unless others here can chime in with their own Cubase experiences, then I'll only be able to help you narrow down the problem....
If you open Task Manager (by the Ctrl-Shift-Esc shortcut), click the "Show processes for all users" button, and click on the CPU column, is it the Cubase processes that's max'ing out your CPU?
It's worthwhile to download and try Reaper too, to see if its a problem with the Audio/Midi subsystems of your Windows installation or PC hardware.
For me, you probably may need to raise this on Cubase forums... I'm not a Cubase user, so unless others here can chime in with their own Cubase experiences, then I'll only be able to help you narrow down the problem....
Not because it is easy, but because it is hard...
Re: CPU issue in cubase 5
on the task manager it looks like the cubase making this problem...
but I did the next thing:
my ULLI was set to 2ms (the sample rate is 96khz), as I set the ULLI to 6ms the cpu decreased significantly.
now I understand that the problem is from the scope, why? (is it the driver?)
and I do whant to keep using the 2ms, what shuld I do?
thanks.
but I did the next thing:
my ULLI was set to 2ms (the sample rate is 96khz), as I set the ULLI to 6ms the cpu decreased significantly.
now I understand that the problem is from the scope, why? (is it the driver?)
and I do whant to keep using the 2ms, what shuld I do?
thanks.
Re: CPU issue in cubase 5
no, it's a matter of how busy the CPU is and what is running in the backround and in Cubase. resources are always limited.
Re: CPU issue in cubase 5
ok, but the issue is that there is nothing in the background, maybe the winamp, and in the cubase the project is new without any plug-in and yet, the vst performance is unstable.
Re: CPU issue in cubase 5
that is a function of your whole system. if it's setup correctly, it will work correctly.
cracks? if so, give up ever having it work right.
what processor/motherboard are you using? what is in the Cubase project(vsts)? if the cpu is overtaxed, you have to increase latency. a cpu is not a realtime device. it always works in the past. clicks and pops, or dropouts, occur because the cpu has many jobs to do, calculating each plugin in Cubase, keeping the audio and midi aligned, managing the screen redraws, checking for usb traffic, etc. an irq is an INTERRUPT request. the cpu starts on it's first job and then is interrupted to do the next task, and so on. everything is great as long as it can make it back to the first task in time, before something else is supposed to happen. if it can't make the cycle in time, you get a click or pop, which is the result of missing data in the stream of data that is the sound you are listening to. this is what cpu clock speed is about. in any case, it's a limited quantity.
you may or may not be getting all the performance that you should from the system. there's no assurance that you can use 2ms latency in any case, especially at 96khz samplerate when you are using double the dsp, cpu and hard drive resources.
a Scope card is a realtime device. NOTHING else in the computer is realtime. that's why the card cannot share an irq with the video card. the Scope card can't wait for something else to use it's interrupt when it needs to talk to the cpu.
it's not just a matter of bad programming either Cubase or Scope. both work about as perfectly as any complicated program can, especially Scope. there are plugins in Scope that don't work in certain circumstances, but the driver is not the issue.
cracks? if so, give up ever having it work right.
what processor/motherboard are you using? what is in the Cubase project(vsts)? if the cpu is overtaxed, you have to increase latency. a cpu is not a realtime device. it always works in the past. clicks and pops, or dropouts, occur because the cpu has many jobs to do, calculating each plugin in Cubase, keeping the audio and midi aligned, managing the screen redraws, checking for usb traffic, etc. an irq is an INTERRUPT request. the cpu starts on it's first job and then is interrupted to do the next task, and so on. everything is great as long as it can make it back to the first task in time, before something else is supposed to happen. if it can't make the cycle in time, you get a click or pop, which is the result of missing data in the stream of data that is the sound you are listening to. this is what cpu clock speed is about. in any case, it's a limited quantity.
you may or may not be getting all the performance that you should from the system. there's no assurance that you can use 2ms latency in any case, especially at 96khz samplerate when you are using double the dsp, cpu and hard drive resources.
a Scope card is a realtime device. NOTHING else in the computer is realtime. that's why the card cannot share an irq with the video card. the Scope card can't wait for something else to use it's interrupt when it needs to talk to the cpu.
it's not just a matter of bad programming either Cubase or Scope. both work about as perfectly as any complicated program can, especially Scope. there are plugins in Scope that don't work in certain circumstances, but the driver is not the issue.