PlanetZ forums - scopeusers.com

yep looks like those RAMPLERS are the memory hogs i was speaking about.

That is obviously SW that is lets call it 'inefficient'.


I then would also suggest that you think about workarounds like a dedicated 64bit 64 Gig RAM 2 Terabyte sampler machine that has a midi overlan and maybe ADAT ...

Hi , CarvinGuitarFreak !

I have almost the same config as yours with one difference.

First Machine Athlon 3,8 x2 - 2 gb (4 gb ram ddr hehe)
Second Machine Athlon 2 Ghz- 512 Mb sd ram (because of its old machine)

And Fx-teleport as a router and already put a part of timbres on second one.

disk streaming always in use. But all built-in samplers like Stylus rmx and Sp Atmosphere uses only ram ! Stylus eats ALL RAM MEMORY

stardust, 4 gig really needed !!!!! I'll wrtite symph orchestra (East and west platinum ed) but already in that project used 1,85 gig. Understand ? Nuendo cant work already, abuses on low memory.

A big problem exists. I have 4 Gb of ram. Bios displays all 4. But in win 32 (XP, 2000) it displays only 3. But really used only 2 in general ! All steinbrg products working with win32 use just 2 Gb.

Below is an extract from Steinberg FAQ.

" you have don’t have much RAM installed, less material ...

'VDAT' partition of pdf manual to Scope cards since 4.0 (as i have). I myself didnt find vdat module in routing window menu. Probably it's only for Scope Professional. But very pity

Full path is illustrated in the Scope Manual pdf file.

Except theory a practice exists (that is our ear). Everybody says that native mixdown is much worse than project playback, it also concerned recording using external rec. plugins such as voxengo or tape-it. I hear myself real difference between voxengo record (at 32 bit float) and simply playback ...

>Converting a 44.1KHz file to 88.2KHz does nothing but waste space! You have to actually create some usefull information to store in it.

Mate, you really didn't understand me! I told about RECORDING AT DOUBLE HIGH SR set in recorder!!! but this is not converting !!! The matter is even when you ...

You're right, but just number of readings per time unit is different, thus converting to 32 bit float at 96kHz or 88 from 44.100 is more precisially describes original wave curve than at 44/32 float format since there are more readings per time unit. Difference between 16 and 32 float bits is in ...

No, bits influent only on gain changes. After recording at 16 bits you always convert to 32 bit float for further maximizing proccess. And then to dither this to 16 bit. Bits is division by Y-axis (amplitude), if quantity of division by X-axis is very high (as in occurance with high SR), then ...

... but still it gives worse quality in comparison with playback in project yet. Tape-It gives little more better result, than Voxengo Recorder, but also is worse than in playback mix in project. PEOPLE, I FOUND ONE AMAZING THING TO SOLVE THIS BIGGGGG PROBLEM. Needs simply to record at high sample ...

2Lima:
I always do so.

erminardi:
I fine know the difference in sound between various sample rates in DAW. It concerned soft VSTi's (using CPU power). But since I just have 3 dsp on my Luna so that there are a very few of dsp power for 96 kHz playback, but the difference in sound of creamware ...

The matter is next. I have Scope home (3 dsp) and load 1-2 xtc synths (lightwave and sb404 for ex.). If in my nuendo 3.2 project has 44,100 kHz, capture of dsp is approx. 70-80%. For each synth is appr. 35%. I do finalizing (track by track recording) on 96 kHz/32 bit. But 96 kHz is overloads 3 dsp ...