Page 1 of 1
Posted: Sun Feb 25, 2001 11:15 am
by Guest
"Dropout" on Cakewalk when I try to record and "no more memory" when I try to play a waw file.
I´ve tried to tune the system.Different buffer- and latencysettings ,but nothing helps.
Does anybody know hoe to solve these problems?
Thanks in advance
Kim
Posted: Sun Feb 25, 2001 11:30 pm
by Guest
Subject: Re: "Dropout" on Cakewalk
Kim,
It seems that this system ran-out to the limit on the memory and CPU resource. Solution is needed faster CPU or/and more memory (just kidding). Of course, you could do some tweaking, try one or more even all of them.
Here we are:
1> Memory: make sure you have the Min and Max cache setting in the system.ini, try to change it about +/- 50% (See pulsar manual)
2> Reducing apps loaded on startup: Run msconfig, go to startup, un-check everything initPulsar (you can uncheck it as well if you don't want it's loaded when the windows just boots-up)
3> Compacting audio: From cakewalk, TOOLS, click "Compact Audio Data" then follows the instruction on windows.
4> Unused audio-track issues: Make sure you have cakewalk V9.03 upgraded that fixed this bug. Anyway, some unsed-audio track must set them as "Archive" instead "Mute" (on TRACK setup), or you must delete form the projects to free-up the CPU performance.
5> Reducing FXs: When you use many cakewalk FX/EQ (FX1~3) could caused CPU over-loaded. And when you have multiple audio tracks you can connect the FX as Aux send/return instead of insert (up to 8 or more can be setup). Each reverb-FX3 is used about 8~15% CPU@500Mhz/256MB.
6> Automation data issues: You can reduce the automation data in case you use them as mixdown or use many MIDI-FX (MIDI enhancements) could causes the problem too.
7> Enable apps priority:
Run Regedit and go to:
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesVxDBIOS
-> In the right hand pane create a new DWORD Value called "CPUPriority" (no quotes)
-> double-click on it
-> check the Decimal box -> type 1 -> click OK to save.
To reset to default-Windows 9x/ME, type 3.
To see your system's real time performance type 0 (NOT recommended by Microsoft!).
Make sure there is a Plug and Play BIOS in system-property. One more thing if this setup doesn't effect at all, go to the BIOS-setup, turn off the APM "BIOS power management feature", also in the control-pannel: Power-setting, set the power-scheme = always-on; turn-off hard-disk = never; system standby = never.
Meaning for this:
"CPUPriority" DWORD valid Decimal values:
0 = The foreground (active) app/game is assigned exclusive CPU cycles (real time priority). WARNING: Use with caution!
1 = All open apps/games (foreground and background) benefit from a few more CPU cycles than loaded Win32 TSRs/DLLs/Runtimes/APIs.
2 = All open apps/games (foreground and background) benefit from even more CPU cycles than loaded Win32 TSRs/DLLs/Runtimes/APIs.
3 = All apps/games/TSRs/DLLs/Runtimes/APIs share same CPU cycles (default, same as "CPUPriority" absent from Registry).
Hope this helps.
Long
Posted: Mon Feb 26, 2001 3:46 am
by Guest
Subject: Thanks LHong
Thank you LHong for taking you time to make such a deepgoing
response to my question. I´ll try to follow your advises step by step.
Best regards Kim