Building Sampler PC

[blob]

Hi
I´m going to build another PC, but this time it would be only for sampler playback (VSL).
I´ve read somewhere (can´t find it any more) that sample PCs gain more from RAM and CPU speed than from CPU cores?

Would be enough to go for Core duo or should I invest in a quad core.
Thank you in advance

blob

[Animus]

All of the above. Sampling will take RAM, clock speed and cores. Get the max you can afford.

[Daryl]

Hi
I´m going to build another PC, but this time it would be only for sampler playback (VSL).
I´ve read somewhere (can´t find it any more) that sample PCs gain more from RAM and CPU speed than from CPU cores?

Would be enough to go for Core duo or should I invest in a quad core.
Thank you in advance

blob
I would go fast quad core, 32GB RAM and XP64.

D

[blob]

Thanks guys.
Daryl, I´ve got no experience with XP 64. Any quirks to watch for?

Thx

[Daryl]

Thanks guys.
Daryl, I´ve got no experience with XP 64. Any quirks to watch for?

Thx

The only quirk is being careful that all your hardware has drivers. I have no problem with RME.

D

[musicpete]

As Daryl said: Invest some hours (OK, more like days) to surf around and read about EACH hardware component of your new system and drivers for it. That really pays off.

I built by XP64 system in fall and it works like a charm. Can run loads of VSTs, no hickups, no problems at all. A dream come true. Also using a RME card here.

[Jcschild]

HI,

1) Core i7 is the only system you should consider.
2) you will most likely NEVER use 32gig of ram 12G if you are lucky.
3)most samples are NOT 64bit ready
VSL, East West play are 2 well known ones. there are others
4) alot of effects are NOT 64bit ready.
5)main sequencer. now some will deabte this one but there is no true 64bit ready DAW.

most install Cubendo in 32bit mode on 64 OS. hoping Cubase 5 wil be it!
the issue that creap up due to bitbridge in overwhelming.

Scott
ADK

[Daryl]

HI,

1) Core i7 is the only system you should consider.
2) you will most likely NEVER use 32gig of ram 12G if you are lucky.
3)most samples are NOT 64bit ready
VSL, East West play are 2 well known ones. there are others
4) alot of effects are NOT 64bit ready.
5)main sequencer. now some will deabte this one but there is no true 64bit ready DAW.

most install Cubendo in 32bit mode on 64 OS. hoping Cubase 5 wil be it!
the issue that creap up due to bitbridge in overwhelming.

Scott
ADK
I don't agree with point 2), as my working template is a modest 17GB.....!

The poster says that it is a sample machine only, but even if the sequencer was on the same machine, he doesn't have to worry about the VST bridge when using Cubendo 32bit because VSL uses the memory space outside of the host. Obviously any other VST effects or instruments would use the host's memory space.

D

[musicpete]

Hi Scott, nice to see you chiming in here!

When it comes to DAWs, listen to that guy. He knows his stuff.

However I'd like to elaborate a little on some points you brought up (By all means: correct me please if I say something wrong):


2) you will most likely NEVER use 32gig of ram 12G if you are lucky.
It really depends on the style of music and how large your template is. When doing a larger project with loads of VSTS, using multiple mike positions and so on it is easily possible to get to 8-10GB. Nice to have some GB overhead in that case.
I agree on 32GB being a little overkill though. But we don't know what future sample libraries might bring: Maybe we all will be using 20GB samples loaded in 2 years? 25GB in 4 years? May be worth investing now since RAM prices are rumored to raise in 2009?


3)most samples are NOT 64bit ready
VSL, East West play are 2 well known ones. there are others
Well, VSL have their "Ensemble" host which is able to use as much RAM as you throw at it. And last time I checked PLAY was also 64bit capable.
However there is the big question of HOW WELL it really works! Here I agree with what you imply: it may NOT work very well, since the technology is quite new. It may be better to build on 32bit software in a 64bit operating system (That is what I am doing right now).



5)main sequencer. now some will deabte this one but there is no true 64bit ready DAW.
Well, AFAIK Sonar 8 is native 64bit. However there are loads of issues! You must use the bitbridge to access 32bit plugins, which is a major PITA. Also, it's the first 64bit version of Sonar (I may be wrong on that!) so you'd expect loads of 1st generation software's problems. So beware!


most install Cubendo in 32bit mode on 64 OS.
That's what many professionals do. That or going for MacPro. Right now it seems to be the best solution. With some workarounds I am able to load huge templates. Of course you have to live with some drawbacks. But I agree with Scott: That's the way you should head.

[Jcschild]

VSL on a box as standalone is the only instance i can think where one could possibly approach more than 12gig 17G?? good lord man...

when testing VSL we got tired of attempting to use that much ram.

one would have to be scoring films to reach this level or samples use.

oddly VSL backed off thier use a xeon and 32-64 gig of ram to use a core with 8-16 for each set.

in order to maintain any type low latency this is the ideal choice.

you start to reach a saturation point (memory bandwidth ability) with a Xeon and 32 gig ram

i am guessing with 17gig or samples loaded your latency is far from ideal.


HI Pete:D

Scott

[Daryl]

VSL on a box as standalone is the only instance i can think where one could possibly approach more than 12gig 17G?? good lord man...

when testing VSL we got tired of attempting to use that much ram.

one would have to be scoring films to reach this level or samples use.

oddly VSL backed off thier use a xeon and 32-64 gig of ram to use a core with 8-16 for each set.

in order to maintain any type low latency this is the ideal choice.

you start to reach a saturation point (memory bandwidth ability) with a Xeon and 32 gig ram

i am guessing with 17gig or samples loaded your latency is far from ideal.


HI Pete:D

Scott
I'm mostly working at 128, but there are times where I have to raise the buffer to 256, which is not ideal. However as my Samplemodeling instruments don't function at less than 256, I can live with the slight inconvenience.

I don't really think that it is overkill, as I only load the instruments that I use all the time for orchestral stuff. I don't want to waste time loading articulations just because I've decided that I want a snap pizz, for example.

D