Scope's onboard RAM

at0m · Post by **at0m** » Fri Feb 01, 2002 2:25 pm

http://groups.yahoo.com/group/pulsar-sc ... sage/31652

I quote Nicolas Choukroun, asked about Scopes onboard RAM:
""I know I've seen that in papers but in reality, I've never
seen 1k of RAM on board since I'm programming it.. It was supposed to be
used for Delay lines stuff, but in reality, delay lines are going to the PC
ram thru the PCI. That's why we have so much PCI overflow issues.

Nikko""

!?

atomic.

<font size=-1>[ This Message was edited by: atomic on 2002-02-01 14:55 ]</font>

subhuman · Post by **subhuman** » Fri Feb 01, 2002 2:31 pm

Sure it does if the programmer uses it. Just DSPdev doesn't use it. What's the issue?

at0m · Post by **at0m** » Fri Feb 01, 2002 2:55 pm

As such, RAM activity caused by genuine Creamware delay fx requires these specially programmed Delay Fx that only run on Scope's RAM?
Doesn't Scope use the same Delays as we do? Or is there device lines that Pulsar users cannot load?
Of course, some developers keep tools for them, as secret weapons

Vil · Post by **Vil** » Sun Feb 03, 2002 9:57 am

there is no special delay line atoms for Scope's RAM . At least I can't find them on Scope DP software.

Neutron · Post by **Neutron** » Sun Feb 03, 2002 10:13 am

how do you know that the onboard ram is not used first automatically?

i do not think so though because my pc geiger shows pci activity on the first reverb i load.

the ram could also be some kind of buffer or cache.

kimgr · Post by **kimgr** » Thu Feb 07, 2002 12:04 am

I'm afraid that not even Creamware's own developers know of any way to address the ram on the Scope card... REALLY annoying