Forums > MaxMSP

Cascade~ bug

October 29, 2008 | 2:42 pm

Hello all,

I’ve found a bug in cascade~; it looks a bit like this is being caused by denormals… see the example patcher, instructions within.

Stewart

– Pasted Max Patch, click to expand. –

October 29, 2008 | 4:08 pm

StewartH schrieb:
> I’ve found a bug in cascade~; it looks a bit like this is being
> caused by denormals… see the example patcher, instructions within.

No problem on a PPC. So you might be correct as denormals happen only on
intel… ;-)


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


October 29, 2008 | 4:51 pm

Nice patch.

Thanks – I see it on Intel and will log it.

-A


October 29, 2008 | 5:56 pm

No problems with PPC cpu behaviour here as well on tiger, ibook g4, max 5.05 (demo).



pm
October 31, 2008 | 1:57 pm

Same problem on my machine (MacBookPro, 10.4.11, Max 5). It’s sad since cascade~ provides an easy way to deal with graphical interfaced multiple band EQ. (I don’t specially like to just have dials to control the EQ’s parameters.)

I did post something about that problem, and I’ve got answered that this may be caused by numerical errors…

http://www.cycling74.com/forums/index.php?t=msg&th=34447&rid=4289&S=925f81481ddb0cdd92e9d1845946793f

notice that if you send a "clear" message to Cascade~, everything get back to normal…


Viewing 5 posts - 1 through 5 (of 5 total)