STS and windows RAM access

[lagoausente]

To can allow STS load a 600mb piano I had to make a trick on msconfig. My T400 has 4GB of Ram. XP only sees 3GB (there is info on google I totally don´t understand about PAE). Question is that I got the low memory message with the 4GB laptop, but no on the old laptop with 1GB of ram.
So i tried going to msconfig/boot/advanced and set the max memory to 1GB, and voila!, I could load the 600mb of the piano.
Now question is.... why??
This is important because is seems that the way Xp is managing the RAM, allow STS more or less memory avaible, so it´s unlogigal that setting a limit to 1GB can get more samples than with 4GB.
It maybe means that the max setting is for the OS? so I have more free RAM for apps? but if so, but why the hell can load near 700mb on my old laptop that has a total of 1GB?
Can anyone give me a light here?

[erminardi]

Consider the use of Kontakt.
Then, if U want, use i.e. softclip or similar in his rig to fatten his sound...
STS seem to be a little old as concept (yes I know that's still a good instrument, but only for little banks suitable, not for huge instruments).

[lagoausente]

Consider the use of Kontakt.
Then, if U want, use i.e. softclip or similar in his rig to fatten his sound...
STS seem to be a little old as concept (yes I know that's still a good instrument, but only for little banks suitable, not for huge instruments).

yes, I know that, but I have already converted some drums and a pair of pianos. I´m not sure if latency feeling will be as good, so I could use STS por playing and native sampler (muted) for recording, maybe. I have to check both. The good of STS is that is midi-jitter free (have measured it and is rock solid). Haven´t tested Native yet with a modern cpu, but with an Athlon 1.6ghz on the past was not so wonderfull feeling to play.

[lagoausente]

One question about kontakt, if is used as VSTi inside cubase, will suffer aditional latency as VSTi? or something related to the latency compensation that Cubase introduce to the tracks?
Any advantage of use it as standalone?
Have read about the Scope wave drivers high latency, but they are the ones used by Asio4all, isn´t? Although someone have just told on this forum the 24 bit was broken so they real convert to 16bit.
There is the aditional posibility of using a second soundcard for standalone apps,so take the digital output and re-record them on Scope.
I don´t know if this have some sense or if just performs the same directly as VST on Cubase, and routing from it to Scope card.
On Scope is easily to send Asio channels and re-record them on the routing window, or is there any other easilly to record the VSTí outputs directly inside Cubase (any virtual Asio driver maybe)?

[garyb]

the latency for the vsti will be the same as the ulli setting times 2. in other words, if the latency is set to 4ms, you get an 8ms latency, which is nothing.

[lagoausente]

the latency for the vsti will be the same as the ulli setting times 2. in other words, if the latency is set to 4ms, you get an 8ms latency, which is nothing.

mmm, the input midi latency is independent of ULLI, or I´m wrong? So really should be ULLI 1 time plus the input Midi latency what I think is even less then 4ms. So in theory should be less than 8ms.
But my question was about the delay compensation or if the Vsti has some buffer on it´s own. I know that there are Vsti´s that adds latency but don´t know about Kontakt. In the other hand, the latency or delay compesantion does not affect realtime? I think Cubase had a window where showed the Vst buffers or latency or something like that, don´t remember.

[garyb]

delay compensation only happens in playback. it has nothing to do with realtime.

8 ms because the midi signal goes to the sequencer to trigger the vsti at the same latency as the audio driver. then the sound is generated and is heard after the audio driver latency. 4 ms to the sequencer for midi and 4ms back from the sequencer for audio. even if the midi driver goes at it's own rate, there will be the latency involved in transmitting the midi to the sequencer through a non-realtime operating system and processor and then the audio driver latency. it's not actually that big of an issue in reality.

[lagoausente]

delay compensation only happens in playback. it has nothing to do with realtime.

8 ms because the midi signal goes to the sequencer to trigger the vsti at the same latency as the audio driver. then the sound is generated and is heard after the audio driver latency. 4 ms to the sequencer for midi and 4ms back from the sequencer for audio. even if the midi driver goes at it's own rate, there will be the latency involved in transmitting the midi to the sequencer through a non-realtime operating system and processor and then the audio driver latency. it's not actually that big of an issue in reality.

Fine! I didn´t know that.

[garyb]

well, i'm not that big of an authority. if someone knows better...