needle VS pyroscope-rs

I used this wrapper to implement an opening and ending detection tool for “fun” [1].

However, it seems that many programs opt to instead shell out to the ffmpeg CLI. I think it’s usually simpler than linking against the library and to avoid licensing issues. But there are some cases where the CLI doesn’t cut it.

[1] https://github.com/aksiksi/needle

I've developed a command line tool that can do this for you: https://github.com/aksiksi/needle. You can try it out by downloading the latest version for your platform from here: https://github.com/aksiksi/needle/releases/tag/v0.1.5.

I’ve been working on needle[1], a CLI (and associated library) that can detect openings/intros and endings/credits across TV or anime episodes. It decodes audio, fingerprints it in chunks, and then compares chunks across files to find common sequences.

Right now, it works pretty well as a CLI app. However, the eventual goal is to wrap the library in a Jellyfin plugin (C#) that handles skipping intros. I think I’ve figured how to call a C library from C#, but there is a lot of work to do to actually get a functional plugin.

[1] https://github.com/aksiksi/needle

A general purpose profiler: https://github.com/pyroscope-io/pyroscope-rs

If someone is interested in this space, feel free to reach me!

I feel some of the OP points. I was working on a profiling agent lately, and one of the issues was running it on multiple platforms (just the four big ones linux/mac-x86/arm) on FFI (because it'll be run directly from python/ruby/etc...) and preferably having the thing just work without having to install or configure any dependencies.

Like OP I hit two walls: libunwind, and linking. For libunwind, I ended up downloading/compiling manually; and for linking there is auditwheel[1]. Although it is a Python tool, I did actually end up using for Ruby (by creating a "fake python package", and then copying the linked dependencies).

It was at that time that I learned about linking for dynamic libraries, patchelf and there is really no single/established tool to do this. I thought there should be something but most people seem to install the dependencies with any certain software. I also found, the hard way, that you still have to deal with gcc/c when working with Rust. It does isolate you from many stuff, but for many things there is no work around.

There is a performance hit to this strategy, however, since shared dynamic libraries will be used by all the running programs that need them; whereas my solution will run its own instance. It made me wonder if wasm will come up with something similar without affecting portability.

Finally, the project is open source and you can browse the code here: https://github.com/pyroscope-io/pyroscope-rs

[1]: https://github.com/pypa/auditwheel

Version 0.5 is now live!: https://github.com/pyroscope-io/pyroscope-rs

Working on https://github.com/pyroscope-io/pyroscope-rs A profiling solution for Rust and other languages.

Thanks to the maintainers at pprof-rs for helping us figure out how we can modify their profiler to create our rust agent (https://github.com/pyroscope-io/pyroscope-rs).