you won't have enough physical RAM for this (2 x 2,8 = 5,6) - i'd say you can use up to 2.8 GB for one of them or for both in total.
christian
christian
and remember: only a CRAY can run an endless loop in just three seconds.
-
I've found that GVI will crash out long before you have tapped all the available memory. I've been trying to use GVI alongside with VSL in Forte, V-Stack, Ploque and Albeton. So far GVI will crash at a certain point even when the task manager shows 1.5 gigs available.
After a number of complaints, Tascam fixed an issue with multi instances of GVI in Bidule, but there still is a memory usage issue going on with GVI. I contacted them and the tech I spoke with was clueless about LAA and LaTiDo. I explained the situation and asked that they please look into it.
-
every 32bit operating system can access max. 4 GB. you have to subtract a certain amount even from that for PCI address mapping and VGA. i'm usually getting 3,75 GB usable RAM.
adding the options /3GB /USERVA=2750 to the boot.ini gives me this space (2,75 GB) for applications running in userspace
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
@Dom said:
I'm running 5 instances of GVI on Bidule (I made it LAA with LaTiDo and I'm using the 3GB switch) and I get 2.7 GB working fine, but I guess once it's combined with Vienna Instruments it gets more problematic.
I've had luck getting 4 GVI up on forte or V-stack. I haven't been using Bidule because of a latency issue when I try to use ASIO. What driver are you using?
It seems that when you mix VSL with GVI, there is an issue. They can't seem to share all of the available memory.
-
/USERVA defines the amount of userspace and is recommended to be set always alongside with the /3GB - there are a several articles in the MS knowledgebase, most of them are referring to certain applications.
first check out how much physical RAM in MB your XP is in fact using (this varies depending on motherboard, BIOS settings and installed devices), then subtract 1024 MB for the kernel-mode and a few MB more as *buffer* to calculate the maximum possible value.
NOTE: you should always create additional entries in the boot.ini instead of changing a single boot option to make sure you have an alternative configuration to start from if something goes wrong.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
@Tripit said:
I've had luck getting 4 GVI up on forte or V-stack. I haven't been using Bidule because of a latency issue when I try to use ASIO. What driver are you using?
ASIO. I can go down to 128 sample buffer at 44.1kHz. With Gigastudio 3 I used to get 64 sample buffer on the same machine. I'm using a RME Hammerfall DSP card.
-
@Tripit said:
I've had luck getting 4 GVI up on forte or V-stack. I haven't been using Bidule because of a latency issue when I try to use ASIO. What driver are you using?
ASIO. I can go down to 128 sample buffer at 44.1kHz. With Gigastudio 3 I used to get 64 sample buffer on the same machine. I'm using a RME Hammerfall DSP card.
It's been a while since I tried Bidule, so maybe the issue I was having has been resolved. I have both RME and Wavecenter cards, and I have had all running at 128 with G3. When I went to Bidule, I had a choice between ASIO and MME or one of the others, forget which one, but one gave me clean audio with 1200 ms latency and the other, ASIO was giving me distorted audio at 256, but better latency. This was on 4 different PC's - 3 - P4's 3.0 with 3 gig each and one Dual Core. So it was something that happened on all the machines.
Anyway, I gave up on Bidule at the time (also because it wouldn't allow for multi instances of GVI) and kept using V-Stack and Forte.
Maybe I should look into Bidule again. I know Tascam fixed the multi instances issue for Bidule in that last release.