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 can be buffered there, and more data must be handled via the slower hard disks. This means access takes longer. Under normal conditions, Windows 2000 and Windows XP can use up to 2 GB RAM and Mac OS X, Windows XP x64 and Windows Vista 64 can address up to 4 GB in connection with Steinberg’s current Cubase/Nuendo versions. More RAM definitely does good things for your system’s overall performance."
On scope driver disk there are only 16 and 32 bit drivers (for win 98, xp, MacOS). Where can it takes 64 bit driver for Scope ?????? People HELP !!!!
Win XP 64 (or Vista) driver for Scope. 4 Gb of RAM win32 bug
sorry, that is bare nonsense - and I really mean NO SENSE
we're almost 10 years after streaming technology has been introduced by Nemesys, later aquired by Tascam - so people should have done their homework... meanwhile...
you need only as much Ram as the number voices multiplied by buffersize plus number of 'attack sounds' (which have no time frame to be delayed) for immediate access - probably not even half a gig for an orchestra.
Data access in RAM by poorly written code may well be SLOWER (!) than by a smart disk engine, for example like the ones found in database servers.
It's a dull approach to load every nuance of an orchestra into memory and then make use of (say) 10% at best.
cheers, Tom
we're almost 10 years after streaming technology has been introduced by Nemesys, later aquired by Tascam - so people should have done their homework... meanwhile...

you need only as much Ram as the number voices multiplied by buffersize plus number of 'attack sounds' (which have no time frame to be delayed) for immediate access - probably not even half a gig for an orchestra.
Data access in RAM by poorly written code may well be SLOWER (!) than by a smart disk engine, for example like the ones found in database servers.
It's a dull approach to load every nuance of an orchestra into memory and then make use of (say) 10% at best.
cheers, Tom
In my opinion, you really shouldn't be expecting new drivers for you scope-environment soon, since the platform has been in a "recovering" state for years now. The resources needed to create new drivers for the exixting Scope cards are prolly not there - yet.
Or put in in other words, you have to work around this problem, maybe bounce tracks instead of having all your libraries loaded all the time?
Would a different sequencer solve your problem? Not all sequencers are as resource consuming as Nuendo.
People have worked around problems like yours for years, so look around for alternative solutions, instead of expeting drivers that prolly wont arrive anytime soon.
Good luck.
Thomas
Or put in in other words, you have to work around this problem, maybe bounce tracks instead of having all your libraries loaded all the time?
Would a different sequencer solve your problem? Not all sequencers are as resource consuming as Nuendo.
People have worked around problems like yours for years, so look around for alternative solutions, instead of expeting drivers that prolly wont arrive anytime soon.
Good luck.
Thomas
-
- Posts: 130
- Joined: Wed Sep 20, 2006 4:00 pm
Hi Prototype,
I use EastWest Platinium (EWQLSO), its very good. I have to spread the load over two machines... I use FXTeleport for this...
Machine 1: Q6600@3.4 -- 2G RAM (vst only)
Machine 2@ P4@3.2 -- 2G RAM ---> 2xPII, 1xLuna and Lynx 2 (ad/da and vst)
Works really well... if you have another PC? You could do the same??
Laters
CGF
I use EastWest Platinium (EWQLSO), its very good. I have to spread the load over two machines... I use FXTeleport for this...
Machine 1: Q6600@3.4 -- 2G RAM (vst only)
Machine 2@ P4@3.2 -- 2G RAM ---> 2xPII, 1xLuna and Lynx 2 (ad/da and vst)
Works really well... if you have another PC? You could do the same??
Laters
CGF
Maybe this would be the best choisestardust wrote: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 connection to a straight 32 bit scope DAW with decent specs.
