bdinfo-rs - very fast single-binary drop-in replacement for BDInfo

[bdinfo-rs]

Announcing bdinfo-rs, a Rust re implementation of the classic .NET BDInfo we all know and love.

https://github.com/agentjp/bdinfo-rs

Features at a glance:
- pure Rust single static binary, drop-in replacement for BDInfo
- one file under ~1MB, no runtime/DLLs/install (way smaller than the .NET tools)
- at least 1.5x faster than the existing .NET forks on the same disc
- fully cross-platform: Linux, Windows & macOS, on x86-64 and arm64 (incl. Apple Silicon)
- reads BDMV folders and .iso images directly (in-house UDF 2.50 reader ported from libudfreader)
- byte-for-byte deterministic output across platforms
- also runs in-browser via WebAssembly, nothing uploaded (https://bdinfo.hyperslop.dev) <-- world's first
- usable as a Rust library (bdinfo-rs-core), not just a CLI
- installs via Homebrew, Scoop, cargo, Docker, apt/dnf, npm, or prebuilt binaries (and hopefully soon, via winget and AUR, waiting for approval)

Examples:
  # Scan a ripped disc folder; pick playlists interactively, writing the
  # report back into the same folder.
  bdinfo-rs /media/MY_MOVIE

  # Scan a disc image. A .iso has no folder to write into, so name a
  # report destination explicitly.
  bdinfo-rs MY_MOVIE.iso /tmp/reports

  # Print the playlist selection table and stop, scanning nothing.
  bdinfo-rs /media/MY_MOVIE --list

  # Scan exactly the named playlists, in the given order.
  bdinfo-rs /media/MY_MOVIE --mpls 00800,00801

  # Scan every playlist the table lists.
  bdinfo-rs /media/MY_MOVIE --whole

below the demo I realized to show the capabilities of the WASM module.



NOTES
BDInfo is a 18 years old app, originally developed in .NET.
I thought it could get some love, so I decided to have some fun and port it to Rust, to see the results of LLM closed-loop development (I used both Opus 4.8 and Fable 5 while available).

sharing it wasn't the immediate plan, but after seeing the results I decided to make it a proper repo and share it with the world. the app is completely open source with LGPL-2.1-or-later license as the original BDInfo (CinemaSquid), you can do whatever you want with it.

I'd love to see your results against your collections, compared to the traditional BDInfo, both in correctness and performance.
let me know if you have any questions. my goal is to just maintain this small piece of software, so whatever bug or issue you find, please open a GH issue using the appropriate template and I will look into it. even though Blu-rays are a dying breed, I am pretty sure the need to retrieve info from discs will be relevant in the distant future as well, so it makes sense to have another modern implementation, and the WASM module could enable advanced scenarios for existing and future apps.

have fun with it and enjoy!

P.S.: I'm also on reddit as /u/bdinfo-rs if you wanna reach out.

[Columbo]

You need a native windows gui. Your browser thing is asking permission to upload 208 files. That's not gonna happen. Yeah, you'll say that's not true but the prompt clearly says "upload".

IMHO, this thing is unattractive for windows users without a native GUI. The original BDinfo is fine.

I understand this is an LLM flex and "the process is the product". But then why would anyone want to use it?

Your claim that BDinfo is "mostly dead code" is absurd.

Blurays are a dying breed?! How else can you get 4K sources for your movies? Blu-ray isn't dead because streaming compresses the picture and rents you the movie, while a disc gives you full quality you actually own. Studios still press thousands of 4K titles a year, and collectors keep buying. It's the new vinyl.

YMMV

[bdinfo-rs]

hey Colombo, I'll try to answer your concern

• while the original UniqProject BDInfo does indeed have a GUI, I intentionally stayed away from that. nowadays BDInfo has a CLI version (https://github.com/tetrahydroc/BDInfoCLI) and that's what I wanted to do, not redo a single platform GUI, since BDInfo already exists (I would have duplicated something that already existed).
• the browser WASM is not a replacement for the GUI, it's just a WASM module. this allows for advanced scenarios, you can stick to the binary.
• about the "upload" thing, this is hilarious no, I haven't setup a cloud infrastructure to ingest your 50GB discs ahahah. you can trivially verify nothing is leaving your computer before using it. (remember, that's a DEMO, you shouldn't really rely on it).
• the code for parsing and reading Blu-ray is "dead". the reasoning is that there will never be a new (super)UHD format. if I am doing this, you might think I like Blu-rays so this is about code: yes the code for UDF etc.. is dead, no one has ever updated it in years.

so, I hope I clarified every doubt you have on the Rust reimplemtation of BDinfo. it's about being cross-platform, single-binary, and faster than existing implementations.

I'll leave one thing open though: for how I organized the Rust package, creating a GUI would be kinda trivial. I am not saying I will do a cross-platform GUI, but in the future, if there is enough interest, it may be done.
or maybe someone else could develop a GUI, the bdinfo-rs-core library can be imported in any Rust project.

in your case, I would only use the binary and see if it's better/faster. the CLI flow is pretty straightforward, with playlist selection prompt.
but I understand a GUI could be useful.