Subject:AcidPro5.0a ... pro? oh really ...

Posted by: tascolas

Date:4/10/2005 7:27:41 PM

Hi all. I was really disapointed to see AP5.0a trial will not recognise more than 2 gigabytes of ram . My system is ASUS P5ADN2-E premium (wireless edition ) ,intel P4 3.8ghz (1 mb L2 cache ) , 4 gig KingstonValue Ram DDRII 533 ram , Sapphire radeon X800 with latest ATI Drivers , Hitachi IDE&SATA hard drives ,LG Multi DVDRW , Nec3500 DVDRW , ,M-Audio Delta 1010 with latest drivers, Win Xp Pro SP2 , .Net framework 1.1 with SP1.My installation is fresh ( no other apps except dx/vst plugins and VSTis ) and running perfectly. I don't know how can anybody ( especially Sony ) claim the ''Pro'' tag with such a main flaw in the app . What i would like to know- if possible- is, if this bug i m experiencing has a work around ,or if anybody in the developing team is trying to solve this. I am really interested in buying the app because i find v.5 features very cool ,but since i cannot use my ram demanding vsti rompler library and my ram hungry 24bit sample libraries to full extent ,frustration leads the way back to AP4(and not payin for something that apparently has no modern approach to ram issues). I apologise if the thread is long but If anyone knows anything about this problem plz plz lemme know. Cheers

Subject:RE: AcidPro5.0a ... pro? oh really ...

Reply by: jwf

Date:4/11/2005 7:22:32 AM

Unless you buy a new 64-bit capable chip and have the yet-to-be-released 64 bit edition of Windows XP ("real soon now" MS keeps saying) or you enable a bunch of magic memory windowing behavior, every application only has 2 GB of addressable memory available to it (the other 2 GB of the 4 GB process address space is used by the OS to map system DLLs into the process). This is a 32-bit intel/amd chip + OS issue, not an application issue. We couldn't change it even if we threw every engineer on the issue.

When 64-bit windows becomes reality and you can actually get some
drivers for your various hardware that work reliably on that platform, I'm sure we'll have great support for you.

This isn't to say that a 64-bit PC today eventually running Windows XP Pro x64 Edition with 6 or 8 GB of RAM wouldn't be great. If you are truly multitasking with several 32-bit apps running, they will page a lot less since the system cache and page tables have a lot more elbow room.

Microsoft XP Pro 64-bit Edition

Subject:RE: AcidPro5.0a ... pro? oh really ...

Reply by: GRVDGGR864

Date:4/11/2005 7:56:35 AM

if your system is that hungry then get rid of XP and go to either 2k or 2k3 and get a opitron chip .........2k3 is fully 64 bit....long with 32..
there is an asus mobo that will handle both 32 and 64 bit long with certain amd chips.......only thing bad bout certain asus mobo's is that you really have to make sure that you sound card is compatable with the board you look at.........and they run very well even under high heat and demanding appz like what you are saying you have............

Subject:RE: AcidPro5.0a ... pro? oh really ...

Reply by: tascolas

Date:4/11/2005 5:18:57 PM

thnx a lot for your answer and postings - i really apreciatte this - i thought i could make a strong
leap forward - seems i have to wait for m audio to have drivers for win64 afterall .... thnx a lot again - now i know whats wrong , i m definetely gonna buy ACID5 pro coz it rox my world hehe - cheers all

Subject:RE: AcidPro5.0a ... pro? oh really ...

Reply by: jumbuk

Date:4/11/2005 11:40:57 PM

Here's a quote from the GS3 forum at Northern Sounds that really helped me understand memory usage:

"Windows XP manages memory so that it divides it into kernel and application spaces. 2GB is the maximum that can be used by the kernel. All applications share the same kernel space. The application space is limited to 2GB per application. So, a single application can see total of 4GB of memory space (up to 2 for kernel and up to 2 for its own use).

If you use multiple applications, it is easy to see that one may use, say 1GB, the other may use 1.5GB and so on. Kernel may use total of 0.1GB or so depending on how it's being used by OS and applications. If you tweak your OS nicely, kernel space would be very small."

I didn't ask permission for the quote, but thanx to the original poster anyway.