Patrick Keenan

Has anyone used the minpower parameter in sigmund~ before? I have tried it as a message and as an argument but it doesn't seem to make any difference to the env or notes output as it is supposed to. If i set minpower to 40 then any sound coming in at a volume lower than 40 should not output anything from the env or notes output but i cant get it to work. Below is the patch, if anyone has any ideas it would be very helpful.

Has anyone used the minpower parameter in sigmund~ before?  I have tried it as a message and as an argument but it doesn't seem to make any difference to the env or notes output as it is supposed to.  If i set minpower to 40 then any sound coming in at a volume lower than 40 should not output anything from the env or notes output but i cant get it to work.  Below is the patch, if anyone has any ideas it would be very helpful.

sigmund-minpower-problem

This is exactly what I'm wondering about too. The @minpower attribute seems to be totally broken on this object. If you go into the inspector and try to change it manually, you can see that anything you enter just reverts instantly back to 0, EXCEPT numbers between 0 and 1 which seemingly randomly either change into 2 or -36893488147419103000. Very strange and very unfortunate.

these are two different things: patrick's post is a few years old and refers to the original sigmund~ object by miller puckette.

what you are describing probably goes back to an oversight in the first version of the 64 bit port of the object that i made available, which has long been fixed.

i guess you are on windows. so, it's likely that the windows port of the new sigmund~ object that alfonso santimone kindly provided, was done before this fix.

back to the original question for help with the minpower attribute: yes, there might be problems with it in miller's original object, which subsequently are still there in the new version, as i didn't change anything about this.

on the one hand, i was a bit reluctant to change the functionality, as many people might rely on a specific behavior of the object.

on the other hand, i haven't really had the time to look into this more closely, but might get back to it.

these are two different things: patrick's post is a few years old and refers to the original sigmund~ object by miller puckette.
what you are describing probably goes back to an oversight in the first version of the 64 bit port of the object that i made available, which has long been fixed.
i guess you are on windows. so, it's likely that the windows port of the new sigmund~ object that alfonso santimone kindly provided, was done before this fix.

back to the original question for help with the minpower attribute: yes, there might be problems with it in miller's original object, which subsequently are still there in the new version, as i didn't change anything about this.
on the one hand, i was a bit reluctant to change the functionality, as many people might rely on a specific behavior of the object.
on the other hand, i haven't really had the time to look into this more closely, but might get back to it.


Yes, I am using 64-bit Windows. I got it from

https://github.com/v7b1/sigmund_64bit-version/releases

A fix for this would be excellent, but it can be worked around. An excellent object nonetheless.

Sigmund~ minpower problem