mendel lee

I'm using the sigmund object for pitch detection and i'm encountering an issue that may be a testing-only bug but i wanted to understand it and address it anyway in case it comes up again in live performance or for future projects.

I created a quick YouTube video exemplifying what's happening (it's 40s long):

In a nutshell: i've created a WAV export of a piece of music to help test drive the patch's various machinations and in the example above, there are instances in which moving from an eighth note 64 to a stac. eighth note 72 is creating an artifact of 62 in the space after the stac 72. This doesn't happen all of the time in the WAV, but it does consistently happen in this portion of the WAV.

Can someone explain what's happening here? Is it an overtone series thing?

I'm using the sigmund object for pitch detection and i'm encountering an issue that  may be a testing-only bug but i wanted to understand it and address it anyway in case it comes up again in live performance or for future projects.

Hi there,
I'm using the sigmund object for pitch detection and i'm encountering an issue that  may be a testing-only bug but i wanted to und

sigmund-issue

Maybe add a gate~ before going into your pitch detection to cut any lingering resonance?

Maybe add a gate~  before going into your pitch detection to cut any lingering resonance?

yeah, after diagnosing further i think something like that is for sure the answer - it turns out that the pulsing longer duration notes sometimes don't diminish enough in energy to trigger a new sigmund read, and the literal audio signal freq of the F was close enough to the previous note that it didn't trigger it either.

For the MIDI i just changed the duration of the note in question, but in live performance this may be an issue, so i will probably do some sort of gate~.

sigmund issue