Out of static RAM message - Kyma Forum

Out of static RAM message

Post New Topic Post A Reply
profile | register | preferences | faq | search

next newest topic | next oldest topic

Author	Topic: Out of static RAM message
Phi Curtis Member	posted 14 September 2006 00:22 Hi, I'm looking for information about the "Out of Static RAM" message and how to avoid it. Of course, it says to reduce frequency trackers, oscillator banks, etc., but I'm wondering if, in a timeline, the limit to static RAM applies to simultaneous SRAM-using objects, or if the limit is a hard limit to the amount of such objects that can be in the same timeline. I'm afraid it's the latter, but wanted to check. thanks, Phil IP: Logged
SSC Administrator	posted 14 September 2006 08:07 The amount of SRAM required is that needed by simultaneous Sounds. Two possibilities are that: * If your Timeline is running out of realtime, several Sounds are getting scheduled on the last processor and there is not enough SRAM on that one processor for all those Sounds * You have a very large number of Hot values. Hot values are stored in SRAM and they remain active for the entire Timeline IP: Logged
Phi Curtis Member	posted 14 September 2006 10:22 The timeline I'm working on is going to be a 6 hour installation - but I'm reusing the same hot values from sound to sound. There probably will be between 150-200 hot values in the whole thing. I thought maybe it was that all the SRAM-using objects in the entire timeline that were causing the problem, because the time it cropped up (so far - I'm only a half hour into the piece), I combined several consecutive frequency tracking sounds into one long sound extending the entire timeline, and that fixed the problem (for now). Is there any direct way to monitor how much SRAM and sample ram you are using at in given time/in any given sound? I thought it was in get info, but I don't see it after compiling the timeline. Any tips for conserving resources in such a long timeline? thanks, Phil IP: Logged
SSC Administrator	posted 15 September 2006 08:27 Unfortunately, there's no way to monitor SRAM and RAM. If you find that you adjust some of the hot values and leave them at a fixed value, it will conserve SRAM to capture those hot value positions and leave them as constants. It is not the duration that taxes the resources but the number of hot values. IP: Logged
garth paine Member	posted 15 September 2006 19:42 Just wondering, given the cheapness of RAM these days (2GB RAM key for less than US$50) - could future designs of the DPS board allow for user installed RAM? One could forsee a Capy with many GB of installed RAM this way - just a thought... :-) Garth IP: Logged
tuscland Member	posted 16 September 2006 04:31 Hi Garth, This is not conventional DRAM. In the Capy SRAM is used (Static Random Access Memory). This memory doesn't need to be refreshed like standard DRAM does, this is why this kind of memory has lower access timings. This speed is critical in order to get the DSP run at their better timing. Using DRAM instead would require an entirely different design and most, it would not guarantee time-critical applications. Cam [This message has been edited by tuscland (edited 29 September 2006).] IP: Logged
garth paine Member	posted 28 September 2006 23:32 Thanks for the ewxplanation Cam. Oh well with your help I can now run parallel Capy's using OSC - wowww man I am DSP hungry ;-) IP: Logged
cristian_vogel Member	posted 10 October 2006 12:50 i always run into outOfStaticRam when I try and work with the excellent sounding crossfilter sounds.... I can't find anyway around it - sometimes reducing the samplerate to minimum gets the sound through compile stage to sound, but I can't even record crossFilter sounds to disk at higher sample rates cos I get the OutOfStaticRam message... I have tried reducing capture duration to a fraction of 'maximum' to no avail ..... EDIT. I have just found out that if you are receive this message using CrossFilterLong, then you can execute the sound by using ResponseDuration maximum and only ONE hotvalue... then it works at 441000 on my base capy [This message has been edited by cristian_vogel (edited 10 October 2006).] IP: Logged
SSC Administrator	posted 10 October 2006 14:35 For the CrossFilter, try reducing the ResponseDuration. In practice, I rarely use response durations longer than 3 to 5 seconds max. You may even discover that a ResponseDuration of 2 s results in a more interesting sound than a response duration set to 'maximum'. If you don't care about actual times, you can also do arithmetic on the default, for example, you could try: maximum * 0.25 in the ResponseDuration field. (Also, if you have Stereo checked, try unchecking it to see whether you still like the result). IP: Logged

All times are CT (US)	next newest topic \| next oldest topic
Administrative Options: Close Topic \| Archive/Move \| Delete Topic

Contact Us | Symbolic Sound Home

This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.

Ultimate Bulletin Board 5.45c