Large Array Memory Problem (FIXED)

by **trogluddite** on Thu Sep 08, 2011 3:16 pm

He he, yes, so often when my assembly is broken, it's because of a spelling mistake.

This case was so weird - I never would have thought that a duplicate variable name would have caused a problem for a whole schematic, and because it was just a copied line (not meant to be there at all), it didn't break the code in its own primitive (it is one of very few that DON'T have an array in there!).

I know I have my 'what should happen to SM' rants every now and then, but I really am impressed with Malc's determination spending three days examining my dodgy workmanship to find the solution; and also to put a 'safety net' on his 'to do list' so that I can't accidentally do it again!

by **infuzion** on Thu Sep 08, 2011 5:55 pm

trogluddite wrote:I know I have my 'what should happen to SM' rants every now and then, but I really am impressed with Malc's determination spending three days examining my dodgy workmanship to find the solution; and also to put a 'safety net' on his 'to do list' so that I can't accidentally do it again!

+1

by rl on Fri Sep 09, 2011 6:24 am

trogluddite wrote:..impressed with Malc's determination spending three days ...

so, punk, you're telling us you are responsible for another 3 days delay on the implementation of a proper timing system? ;-)

by **philter5** on Fri Sep 09, 2011 8:44 am

rl wrote:
trogluddite wrote:..impressed with Malc's determination spending three days ...

so, punk, you're telling us you are responsible for another 3 days delay on the implementation of a proper timing system?

LOL

by **trogluddite** on Fri Sep 09, 2011 8:55 am

He he he he he he he!!!

I realise now that SM would be the most powerful DSP tool in the universe, if only it weren't for my atrocious keyboard and proof-reading skills!

I suppose I ought to go through the forum and delete all of the modules and tutorials I've posted - who knows what havoc I have been wreaking with all of your schematics and SM installations! 3:)

by **aliasant** on Fri Sep 09, 2011 9:03 am

trogluddite wrote:He he he he he he he!!!

I realise now that SM would be the most powerful DSP tool in the universe, if only it weren't for my atrocious keyboard and proof-reading skills!

I suppose I ought to go through the forum and delete all of the modules and tutorials I've posted - who knows what havoc I have been wreaking with all of your schematics and SM installations!

LOL!!

by **philter5** on Fri Sep 09, 2011 10:32 am

hahaha so trog you´re the one that hides a little module in every of your OSMs that remotely switches theese trigger
bugs in our SM installations on and off randomly, 3:)

sitting in front of hundreds of screens and watching all the SM user going crazy ROFL

by **trogluddite** on Fri Sep 09, 2011 10:55 am

The developers of SynthEdit, MaxMSP and Juce pay me a lot of money for it you know! 3:)

by **philter5** on Fri Sep 09, 2011 11:08 am

...i knew it...damn...do you think they are interested in my Flowstone Audio&Video Observation System which i use to spy out other users ? i really need some money hehehe

Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Re: Large Array Memory Problem (FIXED)

Who is online