KVR Audio

Kingston · Post by **Kingston** » Tue Aug 31, 2004 4:41 pm

So what does this bug do? How serious is it?

Any workarounds? How do you deal with it?

DevonB · Post by **DevonB** » Tue Aug 31, 2004 5:04 pm

You mean if you have 2 gigs, how you work around it? I believe you needed to do a maxmem setting in the boot.ini to work around it. If you mean you have 3 gigs, and want to access it all, you can forget about it.

I just read a thread on here not that long ago about the problem. Do a forum search.

Devon

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Tue Aug 31, 2004 5:10 pm

[DELETED]

DevonB · Post by **DevonB** » Tue Aug 31, 2004 5:11 pm

Here we go!

Memory Issue

Devon

DevonB · Post by **DevonB** » Tue Aug 31, 2004 5:12 pm

ttoz wrote:
Kingston wrote:So what does this bug do? How serious is it?

Any workarounds? How do you deal with it?

the only thing it affects is the "digital mixdown" or "glue" of AUDIO parts. it wont affect a realtime bounce if you wish to do it that way. it happens with over a gig of ram and the best solution with 3 gis is, yes, remove 1 gig. it's a stupid BUG and emapple should have had the decency to fix thatat least for the windowz people.

Which bug? If you have 3 gigs bug, or 2 gig bug?

Devon

Kingston · Post by **Kingston** » Tue Aug 31, 2004 8:28 pm

Ah so it's good news in the end.

I've never used digital mixdown anyway.

In fact, I never quite understood its function. It just seems like like something from the digital stone age.

Care to enlighten on this?

Why not stick to the original regions in the first place?

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Wed Sep 01, 2004 6:20 am

[DELETED]

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Wed Sep 01, 2004 6:22 am

[DELETED]

DevonB · Post by **DevonB** » Wed Sep 01, 2004 1:07 pm

ttoz wrote:
DevonB wrote:
ttoz wrote:
Kingston wrote:So what does this bug do? How serious is it?

Any workarounds? How do you deal with it?

the only thing it affects is the "digital mixdown" or "glue" of AUDIO parts. it wont affect a realtime bounce if you wish to do it that way. it happens with over a gig of ram and the best solution with 3 gis is, yes, remove 1 gig. it's a stupid BUG and emapple should have had the decency to fix thatat least for the windowz people.
Which bug? If you have 3 gigs bug, or 2 gig bug?

Devon
typo, i meant with 2 gig remove 1 gig

No, best solution is to set maxmem in boot.ini down a few megs, and try it again. Problem fixed, and you still have 1.9 gigs of ram or so still.

Devon

Kingston · Post by **Kingston** » Wed Sep 01, 2004 5:31 pm

well it can be useful to glue multiple audio parts into one contiguous file

well that figures. luckily I've never needed that in 6 years, so this bug isn't gonna bother me.

stag · Post by **stag** » Wed Sep 01, 2004 9:20 pm

in order to overcome this situation you have to install service pack 2 and edit boot.ini as follows :

multi(0)disk(0)rdisk(0)partition(1)\WINXP="Microsoft Windows XP Professional" /3GB /fastdetect /noexecute

of course this to a single boot sistem provided that
your boot partition is c:\.

Logic PC, 2 Gb memory bug, what does it mean? Help!