Nikolas K

I crated a gen~ patch, to substitute a CPU heavy abstraction patcher inside a larger patch! By it self it works all right, and all the other abstractions work all right.

The issue is that when I pass the gen~ outputs from a cascade or pfft~, tehy block the signal?!

The gen~ outputs straight to dac~ fine. I can see and hear the gen output which is fed to the cascade~, but no output from the cascade~. I revert to the original abstraction patch I used at first, and everything sounds fine...

I crated a gen~ patch, to substitute a CPU heavy abstraction patcher inside a larger patch! By it self it works all right, and all the other abstractions work all right.
The issue is that when I pass the gen~ outputs from a cascade or pfft~, tehy block the signal?!
The gen~ outputs straight to dac~ fine. I can see and hear the gen output which is fed to the cascade~, but no output from the cascade~. I revert to the original abstraction patch I used at first, and everything sounds fine...

What could cause this ?
Has anybody else had a similar problem ?


gen-thru-cascade-weird-behavior

Could you post a patch? Also make sure you don't have any NaN coming out of 

Could you post a patch? Also make sure you don't have any NaN coming out of gen~ (using fixnan), filters don't really like those.


Yes, that was my thought after i made the post. It works OK now. It was just weird because if i connected the output the the dac, i heard the signal (but with some clicks). That was caused by a param for panning inside gen~ wich could get values bigger than it should. fixed it and it is ok.

Yes, that was my thought after i made the post. It works OK now. It was just weird because if i connected the output the the dac, i heard the signal (but with some clicks). That was caused by a param for panning inside gen~ wich could get values bigger than it should. fixed it and it is ok.
Thank you very much!
Nikolas


gen~ thru cascade~, weird behavior