This would be a useful function to have for live performances. I have two ideas off the top of my head, but am not too optimistic about them:

1. subtract a loop of the 'quiet' room from the live input. This is simple but probably wouldn't work too well because, if there is any irregularity at all in the recording, this will create an audible pattern.

2. take the 'quiet' room recording and put it into a [sigmund~]. Keep the highest amplitude value in the loop for each frequency band and use this to set the strength of a notch filter for the respective band. I've got a bad feeling about this idea- like it'd work well with clear, isolated pitches, but probably not with noise (which is going to be the main thing you want to filter!)

Thanks, @whale-av

I've actually used Asio4All before with this same setup and had some issues of noise and not being able to connect without restarting/replugging, Though these were ntermittent problems.

As for just using the AudioBox driver, I've downloaded the latest version of Universal Control from here and still experiencing the issue. Maybe this is just a PreSonus problem and not a PD one... It says here that the AudioBox iTwo should be supported, so no idea...

hey @whale-av any ideas about this?

The PD Load meter always shows around or over 100 cpu load even when I have no patches open (windows 11 task manager shows 10% cpu load)

Also, when I try to close PD it takes a while to close and sometimes I have to force quit.

The odd thing is that, despite all this, patches do seem to run fine. But it would be nice to be able to know if I'm pushing PD's cpu limits or not. Here's a screenshot of the load meter and my audio settings:

[cputime]'s help file says it doesn't work on W98, though I remember it working fine on Windows 8 / 10 before...

@jameslo Hey, thanks for that! It attenuates them more than the vcf~ method... but between the overtones and noise, the string sound is still recognizable... and the range of the filter is so wide that normal speech ends up sounding very thinned. I'd assume you're supposed to be able to set the width of the filter range, but anything above 0 immediately opens a big notch.

@s.elliot.perez said:

@whale-av Do you ever find yourself unable to close or save a patch if you turn off DSP while using ASIO4All? This happens consistently, even when ASIO4ALL is working, and I have to do a force quit.

@whale-av Do you ever find yourself unable to close or save a patch if you turn off DSP while using ASIO4All?

I tried lowering the q to 10, but this didn(t seem to help.

I also tried setting an osc to be subtracted, but the osc sound ends up persisting.

Yeah, I'd be willing to put up with some latency- please share your method?

I have a violin that sends both audio and midi to the computer and am also using another microphone in the same vicinity. I'm trying to use the midi note value of the violin as a notch filter to filter out the sound of the string's acoustic vibration:

I can hear that this attenuates the sound a little bit, but not by that much. Any ideas for improving this? I tried adding additional vcf~ for overtones, but that didn't make a noticeable difference.

@whale-av

OK, after hours of messing with this, the solution is quite simple... as you can see in the screenshots of my previous post, the block size in Pure Data is 64 while the size in the ASIO4All settings is 1024. Making sure these values match (in the Presonus control panel too) and setting them to 512 seems to work (setting it lower doesn't seem to work, the webcam audio is probably holding the other devices back) . Thanks for giving me some ideas!