PlanetZ forums - scopeusers.com

Mr. Sub,

According to the article you posted with regards to VCache, Win98SE/Me handles VCaching much more efficiently than 95 therefore is not necessary or even not recommended to fix any limits (with exceptions to certain criterions, of course 512MB RAM, handling files equal to or larger than RAM....).

When I took out the Min/Maxboundaries, I get wordclock drops all over the place, no illegal ops, though... So I imposed another limit, this time, fixing at 12MB. So far everything is going well - no errors, no wordclock problems....

My question is, reading through various articles regarding VCache, there seem to be varying recommendations on fixing the limits.

Reading through Anton's artilcle (formerly a Creamware Tech Support), Set the min to 1024 and max to 4096 (or more in increments of 1024)
Another article (Audioforums.com) suggests that the Min and Max must be the same....
As mentioned earlier, I read somewhere that setting Vcache Max greater than 64MB makes the system unstable (that I proved as I had mine set to 64MB and was getting those Page Fault errors).....

And then, the article you gave me last time tells a different/ tale.....

So, I suppose there is no definitive rule of thumb when fixing VCache?

Thanks again for your expertise!

Salut!

My rule was to not even worry about that setting as it didn't effect the number of channels I could play back nor my latency at all... which is why, although it can be helpful in some cases, I didn't add it to my guide posted here.

If I don't set it (which is unusual as I didn't have this fixed in my last config.) I get those wordclock drops on tripleDAT... Not really sure if vcaching actually affects I/O on HD R/W transfers...

If I don't set it (which is unusual as I didn't have this fixed in my last config.) I get those wordclock drops on tripleDAT... Not really sure if vcaching actually affects I/O on HD R/W transfers...


Oops! My Error.

<font size=-1>[ This Message was edited by: The Z Station on 2002-04-27 13:59 ]</font>

Hmm ...
Does it mean that CW write anything wrong in own manual (support section) ???
-
<I>VCACHE parameter
Particularly in connection with hard disk
recording, having this entry in your
SYSTEM.INI file will improve
performance. To determine the best value
for your computer, divide your installed
RAM amount in MB by 4 and multiply the
result by 1024. (Example: 128 MB RAM
-> 128/4 = 32 -> 32 x 1024 = 32768).
Add this entry under the section [vcache]
in SYSTEM.INI ( Start -> Run -> type
"Sysedit<Enter> -> select SYSTEM.INI,
make the modification as shown below,
SAVE the modified file!)
[vcache]
MinFileCache=32768
MaxFileCache=32768</I>

Not sure, but, in my case, having my VCache fixed at 32MB/64MB seem to give me dll errors, but, not fixing VCache amounts to wordclock drop?! That is an enigma.

Even at 16MB VCache, it still gave me an error, but certainly not as much as when I had it set at higher limits.... So far, my boundary is fixed at 12MB and still holding - No dll errors or worldclock drops so far!

Pulsar is very comfourtable on the XP Pro side, I haven't even encountered any problems at all, and, XP isn't even tweaked for audio! Imagine that! I even have a network on XP and Pulsar still runs magnificently!