Thanks @indeterminatus, you’re right, the Logic 2 software does not currently have any way to edit the glitch filter after the recording starts. @Collin is right too, the old 1.X software did support this.
Basically, the old software never modified the data that it recorded. The glitch filter was implemented as a filter that sat between the recorded data any anything in the software that tried to access it. It’s extremely complicated. In the new software, we decided to try a much simpler approach - while recording, simply apply the glitch filter to the raw data stream, and store the filtered results. We were able to build this very quickly, but it lacks that important ability to adjust the glitch filter after the fact.
Could you do me a favor, and add a feature suggestion for an after-capture adjustable glitch filter here?
https://ideas.saleae.com/
We use our ideas site to track feature demand and use that information to help plan.
I’d like to allow adjusting the glitch filter after the fact, but I’m not sure which route we should use for it. The “on the fly” glitch filter was extremely complicated, and still has a few bugs to this day, but it provided the most flexibility. We might also be able to support simply re-processing the recorded data with a more aggressive glitch filter, but that has a lot of limitations, and might not be worth it.
Lastly, I think of the glitch filter as a last resort. Have you checked our support page on the subject?
https://support.saleae.com/troubleshooting/seeing-spikes-in-digital-capture
Cleaning up the input signals as best as possible might be able to eliminate the need for a glitch filter.