Error Message when making objects into subpatch

[anon5189335]

Hey

Well, I am working on a masterpatch and I just made a melody line intended to be a subpatch. It works fine when the melody is not a subpatch. But as soon as i make that melody line into a subpatch the masterpatch won't compile. I get this message:

I have been trying for many hours with troubleshooting but keep getting same result. Any ideas what the error message is about?

Thanks

[alex]

is the patch really huge?
it seems to run out of memory.
are you using delays, tables?

[thetechnobear]

using too much ram, try reducing delay lines/table sized... move them out of voices etc
(also look to using SDRAM versions)

Compilation failures

Overview Errors that might occur when you take a patch live, you will see a RED error message at the bottom: Compiling patch failed (~Documents/axoloti/mypatches/test.axp ) If you then look a few lines up, will see the cause of the error, listed before are the common ones and how to resolve. Errors CCMSRAM overflowed by 85792 bytes The Axoloti board has a finite amount of memory (like us all) called SRAM. If you compile a patch that uses too much, it will give the above error (number wil…

[anon5189335]

is the patch really huge?it seems to run out of memory. are you using delays, tables?

Huge:
Yeah it is pretty huge. It has got a lot of sequencers, objects and subpatches but still only reach 33%. I would call it complicated patch but not DSP busting.

Delays:
I am using 2 delay Read/write delay lines, both in subpatches and both are working when the melody line is not a subpatch. But as soon as I put the melody line in the subpatch I get the SRAM owerflowed......Even though the melody line subpatch does not contain any delays that should take up RAM, only 3 oscillators some envelopes, etc..

But in general the patch is at a point I can not really work with it. Most of the times just moving an object without changing any cables or etc... Makes the patch uncompilable. I can't really do anything to it ATM.

I think I am going to try on my other computer too, to check what the result of that might be
I don't get why moving those oscillators to a subpatch will overflow the SRAM?

[thetechnobear]

this is not your computer... its the compiler saying its too much RAM for the axoloti board.
(and its nothing to do with CPU busting etc)

if you don't want to share the patch (which is obviously fine), send it to me via PM, and I'll look to see what it is that using the SRAM. (its unlikely to just be quantity of objects)

[anon5189335]

using too much ram, try reducing delay lines/table sized... move them out of voices etc(also look to using SDRAM versions)

Yeah I hit that wall a few times :=) I have two delays a 1.36sec and a 682ms delay line. Is that above limit of Axoloti?

BTW I am using sdram delay line for both of them and they are in each of their own subpatch.

How do I move them out of voices?

[thetechnobear]

ok, so some feedback... as I've seen the patch, and got it working....

two lessons for others to possible learn (one thats not been mentioned before!)

• table/alloc , always use "alloc 8b SDRAM" over "alloc 8b" there is much more SDRAM that SRAM avaliable.

• lots of subpatches...
  each subpatch stores modulation sources, and presets ... by default this is 8 presets with 32 controls, and 8 modulation sources. (patch settings) ... per instance!!!
  when you start creating alot of subpatches, and memory gets tight, these start to add up to a quite a bit of data, so get into the habit of triming back these to what you need... e.g. often utility patches don't need any modulation or presets, so set them to zero.
  (I'll add this to the precious resources thread later today)

thanks @jaffasplaffa , as always interesting to see how others are using axoloti, and the problems that crop up