As some of y’all may have noticed - there is a new @ROFBot@fosscad.io - I’m developing it myself.

Will eventually open source. But it’s a bit of a buggy mess right now.

Please be patient with the bot, and take results with a grain of salt for now.

Attached is an image you would get commented on your post.

I’m playing around with the backend to use different strategies.

There is this GUI that u/schlarpc made: https://schlarpc.github.io/rof-gui/

It uses similar envelope detection, but a manual fixed threshold. It also reports the whole RPM of the clip along with mean/median burst rates. The downside to this is it caps out at a minimum spacing of 50ms per shot (~1200 RPM)

We’re taking a different approach, attempting to comb through peaks and find shot audio, while filtering out echos/ejection noise.

It’s buggy. But i’ve seen median error rates as low as 2% over my test data, but when it fails it fails hard.


Long story short, bot reply might be full of crap, but all the data gathering helps!

  • unexpected
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    but when it fails it fails hard

    That sounds like a good thing. I guess that would make it easier to tell when your result is crap?