# The night someone ruined 20 discs, someone built a tool that needs only one disc: how disc-probe got to 131 stars · GitHub open source project

> Source: https://stringers.io/en/github/gh_Ashley-QwQ__disc-probe.html (Stringers / 什么值得做, generated 2026-11-20)
> Stringers tracks which small products suddenly took off each day, investigates why one by one, and distils playbooks from them. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these investigations and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools feed (daily breakouts) / plays (playbooks) / hot / products / data. Setup: https://github.com/komako-workshop/stringers (the user signs in with Google at stringers.io/en/start.html to get a personal URL). Site index: https://stringers.io/llms.txt

> It solves the parent project's most expensive pain point (10–40 wasted discs per calibration). It posted to the issue tracker the day the parent went viral, earned trust with pre-registered criteria and raw data, then ran a call for real-world reports that turned users into testers and advocates.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-13

Ashley-QwQ/disc-probe · Ashley-QwQ

# The night someone ruined 20 discs, someone built a tool that needs only one disc: how disc-probe got to 131 stars

**What it is** A Python command-line tool. It lets an ordinary optical drive read a disc and records when each sector finishes reading. From those timings it works out the disc's spiral geometry and calibrates DiscImageStudio for burning images to discs, without photos or repeated test burns.

**Why it took off** It solves the most expensive pain point of the parent project's users: calibrating once can waste 10–40 discs. It was posted to the parent project's issue tracker the day the parent went viral, backed by preregistered acceptance criteria and raw data, and then the author opened a call for test reports, turning users into testers and recommenders.

**C** **How you could follow it** Learn its parasitic launch: wait for the next project that gains a thousand stars in a day, pick a pain point its issue tracker complains about most that the maintainers won't address soon, build it separately within a day or two, and post a data-backed result to the parent's issue tracker the same day.

Grade C: the playbook is clean and worth learning, but the calibration space around DIS, GUIs, and macOS have already been taken. The whole niche tops out at 1–2% of a parent project that is cooling off, so chasing it isn't worth it. Whispers in the niche

Data (updated daily) · Repo created 2026-11-03 · 165 stars · 7 days +45

GitHub · stars

Data 2026-11-07 → 2026-11-20 (14 days, 14 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

In 2026 Nov 3, in the issue tracker of the open-source project DiscImageStudio (which lets you burn an image onto a disc's data surface and was gaining 2,700 stars a day that week), a user posted a disc burned off-center. The title read: "Bad luck, the more I calibrate the worse it gets… already used 20 discs." Six hours later, the disc-probe repo was created. 30 minutes after that, the author posted in the same issue tracker: "Burner only, no photos, no point-plotting: automatic DVD calibration, first-burn bend about 0.1°." 11 days later it had 131 stars, with no ads and no big-account tweets. Below: what it solved, where its stars came from, who's competing, and how to get the same stars next to someone else's hit.

### The hardest step in disc burning: calibration

DiscImageStudio (DIS below, about 9,900 stars on GitHub) works like this: with an ordinary burner, you burn an image into the data layer of a DVD or CD. When you look at the disc against the light, a picture appears on the surface. The catch is that the program has to know exactly how this disc's spiral track winds: the inner radius and track pitch. Be a little off and the image comes out twisted. It varies by brand, and even between batches of the same disc model. The author's launch post gave an example: two discs both marked `RITEKF1` differed by about 73 turns in geometry.

DIS's built-in method is: burn a calibration target → photograph it with a phone → click 12 to 20 points on the photo → back-calculate parameters → burn again. Every attempt wastes a disc. Complaints in the issue tracker cluster: #65 wasted 20 discs, #71 burned 4 DVDs and never got an image, someone downstairs tried 40 times and spent 20 hours, #40 wasted 6 discs. A Bilibili DIS tutorial is titled simply "Why one image burns almost 20 discs."

### What it is

A Python command-line tool under GPL-3.0. It runs on Windows and Linux, and someone else has ported it to macOS.

The principle in one sentence: while the disc spins at constant speed, the moment a sector finishes reading is the moment it passes under the read head. Read two sectors in turn and measure the time difference in milliseconds, and you know how many degrees apart they sit on the disc. Measure level by level from the inner edge outward (about 22 levels for DVD, 36 for CD), and the whole spiral is solved. The measurements can be exported directly as a DIS preset, or added to DIS's preset list with `--install`.

For users, the change is: no photos, no point-plotting, no test burns. Grab any disc from the same batch, including the one you ruined, and let the drive read it for a few to a few dozen minutes. The author quotes first-burn grid bend of about 0.1°, only 0.08° off from a parameter set that the community carefully calibrated with the photo method (DIS #53).

It has hard limits too: the drive has to be constant angular velocity (CAV) and support bypassing the cache when reading, which many drives don't. CD also has one parameter that can't be measured, so you need to burn another calibration disc. The README has a whole section titled "not recommended for now."

### Where the stars came from: entirely on the parent project's turf

GitHub daily stars:

| Date | star | Added that day |
|---|---|---|
| 11-07 | 23 | — |
| 11-08 | 38 | +15 |
| 11-09 | 48 | +10 |
| 11-10 | 60 | +12 |
| 11-11 | 90 | +30 |
| 11-12 | 109 | +19 |
| 11-13 | 120 | +11 |
| 11-14 | 131 | +11 |

Almost every traceable source sits right next to DIS:

- **DIS issue #72, launch post.** Posted 11-03 22:37 (UTC), bilingual Chinese and English, with the title stating the result outright. The first screen is a TL;DR, followed by something that reads like a paper: acceptance criteria committed to the repo before burning (`docs/PREREG_remeasure.md`), a commit hash attached to every claim, error and goodness-of-fit numbers, and an honest list of prior work on similar techniques (SecuROM's copy-protection detection, a Philips patent from 2002 years ago). The DIS maintainer replied the same day saying they would "test and evaluate, then try to integrate." At the time DIS was at a peak of over two thousand new stars a day, and its issue tracker was one of the busiest spots on all of GitHub.

- **DIS discussion #107, call for test reports.** 11-04 the author closed #72 and opened a new thread: "Photo-free calibration by timing reads, does your drive work? Call for test reports." By 11-13 it had 63 replies: someone posted a macOS port, someone tested an old scrapped drive, someone said cheap discs "never passed three rounds of coarse-then-fine calibration until I switched to disc-probe and got it perfect." The author replied to almost everything, posted numbers, fixed bugs the same day, and wrote each result into the drive-compatibility table in the README with credit. Within a week it went from "one drive works" to about 25 drives.

- **Repeatedly recommended in DIS help threads.** 19 DIS issues mention it (GitHub search, 11-14), mostly as answers to "calibration failed, what now?" There are also several community disc presets contributed to DIS that were measured with disc-probe.

- **4chan /g/ DIS thread.** Starting 11-05, multiple anonymous users recommended it: "works flawlessly and only took 1 disc" and "disc-probe solves the calibration bs." One posted their full command.

- **A Reddit showcase post with credit.** A user on r/FractalPorn posted a fractal image they'd burned onto a DVD (297 upvotes, around 11-07 views). The body read: "use discprobe by Ashley-QwQ do automatic calibration… around 20 minutes." On r/Portal, someone burned a Portal logo and also said they measured the disc with it. How many stars this brought is unclear.

- **Cited downstream.** DIS 1.5.0(11-07) credits in a third-party notice that it ported a piece of its DVD read rules; two other small projects say they're based on it.

What I couldn't find: Hacker News, X, press coverage. Outlets that covered DIS (IT之家, PC Watch, 少数派, and others) and the Bilibili tutorials don't mention it. Which source drove the +30 on 11-11 is unknown. DIS itself gained 315 that day, so it may just have been spillover.

One shape worth noticing: DIS's star count peaked at 11-03 and then slid steadily, down to just over 160 a day by 11-14. disc-probe, on the other hand, only started climbing steadily after 11-07. It isn't feeding on the crowd that gawked at DIS at launch, but on people who actually burn discs, get them wrong, and go looking for a fix.

The Windows portable build v0.1.2.1 has 301 downloads, and roughly 400 across all versions (GitHub, 11-13). The number of people actually using it is about the same as the number starring it, which is uncommon on GitHub.

11 days, 300+ commits, 5 contributors, and a dozen-plus external PRs (burning without admin rights, Linux support, Blu-ray experiments, and more). The author's other public repos are research on AI agent tooling. Such a high commit rate plus a string of self-filed bug reports looks like heavy use of a coding agent (inference).

### Who else is building

| Project | Launched | star(11-14) | How it differs |
|---|---|---|---|
| DIS's built-in calibration aids | 1.4.0,11-04 | What follows DIS | Coarse, boundary, and fine steps are still burn target, photo, point-plotting. The maintainer said photo-based calibration is the priority for now and timing-based calibration hasn't been merged in. |
| DIS built-in and community presets | Since 1.3.x | Dozens of disc types | If you buy the right disc you don't need calibration. It breaks for cheap discs and batch changes. Many community presets were measured with disc-probe. |
| HiroGitea's automatic calibration from photos (DIS PR #62) | 11-03 | Not merged | Still requires photos, residual distortion 10–20°, one to two orders of magnitude worse |
| POPCORNBOOM/Discratcher | 11-07 | 34 | Uses its timing method, wrapped in a cross-platform GUI with community calibration data. The author credits disc-probe in an issue. |
| NaiveTomcat/discprobe-macos | 11-04 | 6 | Its macOS port |
| arduinocelentano/cdimage | 2022-07 | 765 | CD only, parameters tuned by hand |

From 11-03 to 11-07 over those few days, it was the only option for "calibrate without photos." Anything that came after is either a port of it or uses its method. A string of small projects building plugins around DIS already exists (a macOS version, a Linux GUI, preset import/export tools), each with single to dozens of stars.

### Its ceiling

The users disc-probe can reach are only the part of DIS's users who actually burn discs, haven't found a ready-made preset for their disc type, and happen to have a supported drive. 131 stars is about 1.3% of DIS. DIS itself is cooling off. If DIS ever merges timing-based calibration into the main program, disc-probe's standalone value shrinks sharply. By 11-14 there was still no such merge; DIS's commits after 11-08 were for other features.

### If it were you

**Verdict** : C. The project shows a clean playbook, but following it isn't worth much. The calibration slot is already taken, and GUI and macOS versions have been built by others. The ceiling for the whole niche is 1–2% of a parent project that's cooling off, roughly a hundred-odd stars.

**Who it suits** : developers who can ship a working tool within hours to a day and are willing to spend the day in other people's issue trackers answering questions. Builders of hardware, measurement, and scientific computing tools fit best, since "let the data speak" works especially well in those circles.

**Who it doesn't suit** : anyone wanting to build another calibration tool or GUI around DIS (too late). Anyone expecting a project to reach thousands of stars (a project that rides a parent is capped by the parent's size).

**How to do it** , ranked by how worthwhile:

1. **Learn the playbook, wait for the next hit** : watch GitHub's daily trending list. When a project gains a thousand stars in a day, go through its issue tracker sorted by most complaints, pick a pain point the maintainers don't plan to address soon and that you can finish in a day or two, and build it as a separate repo. Say in the name and description who it's for ("a ××× for ×××").

2. **Stay next to DIS, fill the empty slots** : for example, a public geometry database organized by disc model and batch (which disc, which batch, measured parameters, who measured them), or an automatic check that says "burn one image first and I'll tell you how it's skewed." Before deciding it's worth it, check whether anyone is still burning with DIS in December.

3. **Try the same move in another hardware niche** : the idea of using the device's own readings instead of photo-based calibration also works in circles like 3D printing, laser engraving, and embroidery machines, where people also burn through test material. Look for hit products there.

**How to get users** : on the day you release, post a results thread in the parent project's busiest issue tracker, with the title stating the result rather than the feature ("first-burn bend about 0.1°"). Use both Chinese and English. The next day, open a "call for test reports" thread, write every user's success report into the README with credit, reply with a link whenever someone asks for help, and ship a portable build that runs with a double-click.

**When is the window** : the approach has no expiry. The window is the first day or two after the parent goes viral. disc-probe launched the same night. If you want to take the second path, do it before the end of November, while DIS's heat is still up.

**What it means if I got it wrong:** ① December disc-probe still holds 10+ stars a day, or DIS gets another wave. Then disc printing isn't a one-off trend, and there's room in the accessories. ② Someone builds a new tool on top of DIS and passes 300 stars in a month. Then the ceiling is higher than I estimated. ③ The reverse: DIS folds timing calibration into the main program and disc-probe's star growth flatlines. Then skip the second path.

### Data and sources

GitHub: Ashley-QwQ/disc-probe repo page, README, commit history, release download counts, daily stars (11-07 to 11-14); DiscImageStudio issues #65, #71, #72, discussion #107, v1.4.0 to v1.5.0 release notes and commits after 11-08; star counts of similar repos (11-14). 4chan /g/ thread 110227209. Reddit r/FractalPorn and r/Portal user posts (I couldn't get the dates and upvote counts for the r/Portal post). Anything marked "inferred" is inference.

[GitHub repo ↗](https://github.com/Ashley-QwQ/disc-probe)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| DiscImageStudio's built-in assisted calibration (coarse / boundary / fine) | Open source | 2026-11-04(1.4.0) | rides on DIS's ~9,900-star user base | requires printing a calibration target, photographing it, plotting points, and repeated correction; users report wasting 20 discs; the maintainer said improving photo-based calibration comes first, and timing-based calibration was never integrated |
| built-in and community-contributed disc presets in DIS | Open source | Since 1.3.x | dozens of disc types, with ongoing contributions | if you buy the right disc type you skip calibration, but no-name discs and different batches of the same MID break the preset; many community presets were themselves measured with disc-probe |
| HiroGitea's automatic photo-based calibration (DIS PR #62) | Open source | 2026-11-03 | PR not merged, very small sample | still requires photos, residual distortion of 10–20°, one to two orders of magnitude worse than disc-probe's ~0.1° |
| POPCORNBOOM/Discratcher | Open source | 2026-11-07 | 34 stars | uses the same timing-based calibration method, wrapped in a GUI app with community calibration data |
| arduinocelentano/cdimage | Open source | 2022-07 | 765 stars | CD only, calibration parameters tuned by hand through repeated trial |
| Yamaha DiscT@2 / HP LightScribe | Big-company features | 2002–2005 | Discontinued | the firmware of dedicated drives knows the geometry, so ordinary drives can't use it |
| DPM (SecuROM) / redump forum FUA rereads / Philips patent US7538787B2 | Other | 2000 era; 2025 | not a user product | same principle as earlier work; disc-probe is an open-source, reproducible implementation on consumer drives, with uncertainty estimates and DIS preset export |

Where users come from

- **Verified** **Posted on the parent project's issues** : DIS #72,11-03, posted 22:37 minutes after the repo was created at 30 UTC, in English and Chinese, titled with the result: "No photos, no point plotting, first burn about 0.1° warp". Attached a pre-registered re-measurement and a 0-shot finished disc. The maintainer replied that they would consider integrating it.

- **Verified** **Solicited measurements in the parent project's discussions** : DIS Discussions #107,11-04 grew 63 levels from its start, with about 25 drives reported. The author replied to each and added them to the README compatibility table.

- **Verified** **Repeatedly mentioned in DIS help issues** : a GitHub search finds 19 DIS issues mentioning disc-probe, such as #65 (20 discs wasted), #140, and #171 (presets measured with it).

- **Verified** **DIS threads on 4chan /g/** : starting 110227209,11-05, several anonymous users on /g/ recommended it: "only took 1 disc", "disc-probe solves the calibration bs".

- **Verified** **Credited in Reddit output posts** : u/LTVA's r/FractalPorn post (297 upvotes, about 11-07) says "use discprobe by Ashley-QwQ"; u/nimaid's r/Portal post says it used disc-probe. How much traffic it brought is unknown.

- **Verified** **Downstream projects link back** : DIS 1.5.0 THIRD-PARTY-NOTICES, HoloStudio3D, and Discratcher all credit it.

- Inferred **HN / X / press / ads** : no hits in the hackernews library or Algolia, x-radar has 0 posts, and neither the press coverage of DIS nor the Bilibili tutorials mention it.

## Why disc-probe (Ashley-QwQ/disc-probe) worked

> Channel: GitHub · Research day 2026-11-13 (data card refreshed 11-14) · Conclusion first

### Bottom line

disc-probe is a calibration plugin that lives off the hit product DiscImageStudio (DIS, about 9,900 stars). DIS users' biggest pain is calibration: every disc burns 10–40 blanks before it comes out right. The author shipped a bilingual issue on DIS (#72) on the second day DIS blew up, 30 minutes after building the repo, and then opened a discussion thread (#107,63 replies) asking for real-world drive tests. The result, "burn one random-data disc, let the drive measure itself, and it's right on the first try," was posted with pre-registered acceptance criteria and raw data. Almost all the traffic came from DIS's issue tracker, its discussions, and DIS threads on the 4chan /g/ board. It reached 131 stars in 11 days, about 1.3% of the parent project.

### What it is

- A Python command-line tool (GPL-3.0) that works on Windows and Linux, with a third-party macOS port. How it works: when a disc spins at constant speed, the moment a sector finishes reading is the moment it passes under the head. Reading two sectors alternately and measuring the milliseconds between their completion times gives the angle between them on the disc. Measuring from near to far, level by level (DVD 22 level, CD 36 level), recovers the spiral geometry of the whole disc: track pitch u and v, with optional quadratic and cubic corrections. After measuring, it can write an image ISO, export a DIS preset, or install directly into DIS's preset list with `--install`. (README: [github.com/Ashley-QwQ/disc-probe](https://github.com/Ashley-QwQ/disc-probe))

- It replaces DIS's built-in loop of printing a calibration target, photographing it with a phone, plotting points, and back-calculating. Users only burn one random-data disc and let the drive read it for a few to a few dozen minutes. Discs from the same batch that have already been burned can also be measured.

- The author's accuracy claim: timing-only geometry gave, on the first burn, about 0.1° peak-to-peak warp and 0.03° rms, differing from the community photo-based calibration (#53) by 0.08°. The acceptance criteria were committed to the repo before the disc was burned (`docs/PREREG_remeasure.md`). (DIS #72: [github.com/JiaFeiMiao-K-Cat/DiscImageStudio/issues/72](https://github.com/JiaFeiMiao-K-Cat/DiscImageStudio/issues/72))

### Data

| Metric | Value | Source |
|---|---|---|
| Repo created | 2026-11-03 22:07 UTC | GitHub API |
| star | 11-07 23 → 11-10 60 → 11-11 90 → 11-14 131; +108 in the last 7 days, peak single day +30 (11-11) | Our GitHub library / data card |
| fork | 8 | GitHub API |
| Commits | 300+ runs in total; 11-04 had 48, 11-07 had 90; 5 contributors (Ashley-QwQ 235 commits, domerawind 63, dhao2001, WindowsNoEditor, bczhc) | GitHub API |
| issue / PR | 43 in total, including more than a dozen external PRs (IMAPI2 without admin rights, Linux SG_IO, Blu-ray experiments, boot console, and others) | GitHub API |
| Release downloads | v0.1.2.1's full-win64 was downloaded 301 times, core 48 times; all version packages combined about 400 downloads | GitHub API |
| parent project DIS | 11-03 +2,702 → 11-14 +164/day, total 9,902 | Our GitHub repo |
| solicitation discussion DIS #107 | 11-04 open, 63 levels, people still replying as of 11-13; the measurement table in the README covers about 25 drives | GitHub GraphQL |
| stargazer breakdown | the API returned 404 / 0 entries for this repo, with no timestamps available | GitHub API (cause unknown) |

Compared with DIS: DIS's star growth peaked at 11-03 and fell steadily afterward, while disc-probe's has climbed continuously since 11-07 (11-07 to 11-13, +10 to +30 per day). That suggests it's feeding on the long tail of DIS users who actually burn discs, get them wrong, and go looking for a calibration fix, not the crowd that came for DIS's launch spectacle.

### Competitors: who else does the same thing (disc geometry calibration for data-side burning)

| Name | Where | Launched | Scale | How it differs from disc-probe |
|---|---|---|---|---|
| DIS's built-in assisted calibration (coarse / boundary / fine three-stage) | open source (parent project feature) | 1.4.0,2026-11-04 | rides on DIS's ~9,900-star user base | requires printing a calibration target, photographing it, plotting points, and repeated correction; DIS #65 has a user saying they've "already spent 20 discs". The maintainer replied in #72 that photo-based calibration comes first for now, and timing-based calibration was never merged into the main program |
| built-in and community-contributed disc presets in DIS | open source (parent project feature) | Since 1.3.x | dozens of disc types, with people constantly contributing in DIS issues (#74, #171, #222, #298…) | buy the right disc and you skip calibration; buy the wrong type, or hit a no-name disc or a different batch with the same MID, and the preset breaks. disc-probe fills exactly that gap, and many community presets were themselves measured with disc-probe (#140, #171) |
| HiroGitea's photo-based automatic calibration (DIS PR #62 / #123) | Open source | 2026-11-03 | PR not merged; the author said "the sample is very small", with residual distortion of 10–20° | uses a calibration target with built-in coding plus phone photos to solve the radius automatically, but still requires photographing, and its accuracy is one to two orders of magnitude worse |
| POPCORNBOOM/Discratcher | Open-source desktop app | 2026-11-07 | 34 stars | copies disc-probe's timing-based calibration method into a cross-platform GUI offering "one-disc automatic calibration + community calibration data"; the author credits "your read-timing calibration method" in disc-probe #9. A follower / downstream project |
| NaiveTomcat/discprobe-macos | Open source | 2026-11-04 | 6 stars | a macOS port of disc-probe, with a signed and notarized helper |
| arduinocelentano/cdimage | Open source | 2022-07 | 765 stars | CD only, calibration parameters tuned by hand through repeated trial, no automatic measurement |
| Yamaha DiscT@2, HP LightScribe / LabelFlash | Big-company features | 2002–2005 | Discontinued | the firmware of dedicated drives knows the disc geometry, so no calibration is needed; ordinary drives can't use it |
| DPM (SecuROM anti-copy), redump forum FUA rereads, Philips patent US7538787B2 | Other (prior tech) | 2000 era; 2025 | Not a user-facing product | Same principle; the author lists it as prior work in the README. disc-probe is an open, reproducible implementation on consumer optical drives, adding uncertainty estimates, live grid validation, and export of DIS presets |

Verdict: the real competitor is the parent project's own photo-based calibration and presets. For "zero-photo calibration for everyday people," 11-03 through 11-07 it was the only public option. Discratcher, which came later, uses its method.

### Growth: where users come from

1. **Posted in the parent project's pain point (confirmed).** 30 minutes after the repo was created, the author opened #72 on DIS (11-03 22:37 UTC), bilingual, with the result in the title: "Burn-only, no photos, no tracing: DVD auto-calibration, first-burn bend about 0.1°". The post had a TL;DR, pre-registered re-tests, prior-work credits, and raw data links. 11-04 later added a batch of "0-shot" finished pieces (including a Along the River During the Qingming Festival). The DIS maintainer replied the same day that they would "evaluate and try to integrate." DIS was at its peak then, gaining 2,000+ stars a day, and its issue tracker was one of the hottest places on the site.

2. **Launched a call for reports, turning users into testers (confirmed).** On 11-04 the author closed #72 and opened #107 in DIS Discussions: "Does your drive work? Call for real-world tests." By 11-13 there were 63 replies: someone posted a macOS port, someone ran a scrapped old drive, someone used a no-name disc, "three coarse and fine calibrations never passed, disc-probe got it perfect on the first try" (Lakida0). The author replied to nearly every one with numbers, fixed bugs the same day, and wrote results into the README compatibility table. Every report became a public success story on a 9,900-star project's discussion board.

3. **Repeatedly cited in DIS help issues (confirmed).** A GitHub search shows 19 DIS issues mentioning disc-probe, including #65 ("already burned 20 discs"), #88, #190, and #249, calibration-failure requests, as well as #140 and #171, presets users measured with disc-probe and then contributed back to DIS.

4. **DIS threads on 4chan /g/ (confirmed).** In the /g/ 110227209 thread, starting around 11-05, several anonymous users recommended it: "this one was pretty good… it gave results just by reading a cd from a previous failed attempt", "works flawlessly and only took 1 disc", "disc-probe solves the calibration bs", and someone posted their full command workflow. (https://boards.4chan.org/g/thread/110227209)

5. **Reddit users credited it when showing finished pieces (confirmed mentions; traffic unknown).** u/LTVA posted "Symmetrical fractal picture burned on DVD disc" to r/fractals and r/FractalPorn (297 upvotes on r/FractalPorn, about 11-07), with the text "use discprobe by Ashley-QwQ do automatic calibration… around 20 minutes". u/nimaid posted "Aperture Science logo burned to a DVD" to r/Portal, noting the Fujifilm DVD+RW was measured with disc-probe. LTVA's 1 5 µm microscope photo later went into the README.

6. **Confirmed downstream adoption.** DIS 1.5.0(11-07)'s THIRD-PARTY-NOTICES and `DvdReadCompatibilityGuard.cs` credit and port disc-probe's DVD bridge rules; HoloStudio3D (a 3D holographic disc-burning plugin, 8 stars) and Discratcher both state they're built on it. These are backlinks.

7. **HN, X, press, ads (none found).** Our hackernews database and HN Algolia have no disc-probe posts or comments. A local x-radar corpus search for disc-probe and DiscImageStudio returned 0 results each. Press covering DIS (IT Home, PC Watch, Adafruit, Korben, Sspai, and others) doesn't mention disc-probe, and neither do two Bilibili DIS tutorial videos.

We didn't find the source of the 11-11 peak of +30 that day. The parent project gained +315 that day too, so it may just be DIS traffic being split.

### Why it's working

- **Hits the parent project's biggest, most expensive pain point.** DIS makes you want to burn, but calibration burns disc after disc: DIS #65 "already burned 20 discs", a Bilibili tutorial titled "why does one image burn almost 20 discs", and bmenrigh on HN calling disc calibration "incredibly sensitive". disc-probe cuts the cost to one random-data disc, and it can even measure from a data disc that already failed.

- **Timing beat the window.** DIS 11-02 and 11-03 went viral, and disc-probe shipped the same night, 11-03. The DIS maintainers explicitly prioritize camera-based calibration and don't integrate timing methods, so the 「zero camera」 position stayed empty, and only this project filled it.

- **Credibility built like a paper.** Pre-registered acceptance criteria, commit hashes as evidence, σ and χ²/dof reported, independent checks against community photo results, prior work listed openly (DPM, Philips patents), and a string of self-filed [P1]/[P2] bug issues. For hardware hobbyists who have to burn repeatedly to get it right, this persuades better than marketing copy does: "this disc is worth a try."

- **Pulled users in to test together.** #107 and the README compatibility table left a credit and data trail for every person whose burn succeeded. External contributors submitted a dozen-plus PRs (IMAPI2 without admin rights, Linux, Blu-ray, boot console, and more). In a week the tool went from "works on one GH70N" to about 25 drives across three operating systems.

- **The author maintained it around the clock.** 11 days with 300+ commits. Nearly every user report got a reply, a fix, and an updated table the same day. From 0.1.x onward a portable Windows build was also offered (full-win64 downloaded 301 times), so ordinary users could run it.

### Differentiation

disc-probe's difference is that **it measures geometry from ordinary drive read timing alone, with no photos, no tracing, and no test burns** , and it publishes its precision and uncertainty so anyone can check them. The parent project's photo calibration, HiroGitea's automatic photo calibration, and cdimage's manual tuning all depend on a "burn one → look or photograph → adjust" loop. That difference is why it took off: users came to it for one thing, fewer wasted discs.

Its ceiling is also clear:

- It only works with CAV drives that support FUA (or can bypass the cache). CLV drives can't be measured. The README has a section specifically saying it's not recommended for them yet.

- CD has one constant along the track that can't be measured, so you still need to burn one extra calibration disc.

- The users it can serve are only the subset of DIS users who actually burn discs and can't get a preset for their disc type.

So star growth is capped at roughly 1–2% of the parent project.

### Visibility and copycats

- Visibility: **circulating in a small circle.** Discussion clusters in DIS issues and Discussions, the DIS thread on 4chan /g/, and a few Reddit finished-piece posts. No HN, no press, no large X accounts. Revenue is not involved.

- Followers and downstream: Discratcher (34 stars, 11-07, timing calibration repackaged as a GUI app), discprobe-macos (6 stars), frienkie/DiscProbe-GUI (0-star fork), HoloStudio3D (8 stars, built on it). The DIS main program also ported its DVD bridge rules.

### What others can borrow

- "Parasitic launch": find an open-source project that's blowing up, pick the pain point its issue tracker complains about most, build a standalone tool for it, and post results to the parent project's issues and discussions the day you ship. The parent's traffic becomes your distribution, and those users arrive with a specific problem.

- Use a call for reports in place of marketing: ask users to post real measurements, reply to each one, write them into a compatibility table with credit, and treat every success as a public endorsement.

- For hardware and measurement tools, build trust with pre-registration, raw data, and uncertainty figures.

- Opportunity note: this tool is positioned as calibration for DIS. The money is downstream, such as sets of blank discs with measured geometry already done, custom burning services, or a one-click GUI like Discratcher. It's all still very early.

### Still unclear

- The stargazer list API returns 404 / 0 for this repo, so there are no star timestamps. We can't match the +30 on 11-11 to a specific source.

- Reddit blocks scraping, so we couldn't get the r/Portal post's date or upvotes, or data on LTVA's other posts.

- We can't quantify how many stars came from 4chan or Reddit.

- The author's other public repos are AI agent tooling research (tool-residency-bench, dsh-hybrid-toolsearch, and others), with 11 days and 300+ commits and a chain of [P1]/[P2] self-filed issues. It looks like heavy use of coding agents (speculation, unverified). The README acknowledgments say some BD/CD algorithms were co-developed with domerawind and DeepSeek.

- Whether DIS folds timing calibration into the main program: if it does, disc-probe's standalone value shrinks sharply.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.
