HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
happycube
ld-decode
Jupyter Notebook2016–2025
happycube / ld-decode

ld-decode

Software defined LaserDisc decoder

10Distinct people
12Mentions
0Explicit recommenders
422GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Software defined LaserDisc decoder

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2016-09-24 17:34:28 UTC to 2025-07-21 13:02:18 UTC.

01232016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312

What Hacker News says

12 sources
I’m positive you know this already, but for anyone else, this section [0] of the lddecode project has a wonderful example of all the visible and non-visible portions of an analog video signal. The project as a whole is also utterly fascinating, if you find the idea of pulling an analog RF signal from a laser and then doing software ADC interesting. [0]: https://github.com/happycube/ld-decode/wiki/ld-analyse#under...
In FFmpeg devs boast of another 100x leap thanks to handwritten assembly code
> Lots of truth to this. Just start building. Build for yourself and real people, not imagined profiles of people. I've been doing this for years and all it has done is drill me further down into super-niche rabbit holes that the majority of people don't care about. I mention this because I see this kind of advice all the time on here, but it so often comes bundled with the unwritten assumption that the kinds of things the reader will build won't stray too far from the mainstream. After more than a decade of "building", I can state with confidence that profitable ideas don't spring up from countless hours invested in building e.g. a better comb filter for NTSC. The reality of the situation is that if your interests are things like "doing cool stuff with AI" or "SaaSify yet another thing" or "shoehorn Merkle trees into yet another square h
Read the rest
ole", then this advice will likely work for you. If you're the kind of dude (not me) to write ld-decode¹, then it will likely not. I mean, shit, Donald Graft² has been "building" far longer than I have and yet none of his "building" has led to a business AFAICT. [1] https://github.com/happycube/ld-decode [2] https://www.rationalqm.us/mine.html
In How to get new ideas
They owe you nothing, so if you want to figure something out, searching the web is your best chance. Also, how is it not clear what the project is? First thing I see from the submission link: > Software defined VHS decoder > A fork of LD-Decode, the decoding software powering the Domesday86 Project Which links to https://github.com/happycube/ld-decode and https://www.domesday86.com/ > Software defined LaserDisc decoder and > Domesday86 is a project that aims to recreate the experience of the original BBC Domesday project using modern hardware and software Which leads me to searching what BBC Domesday is, as I didn't know: > The BBC Domesday Project was a partnership between Acorn Computers, Philips, Logica, and the BBC to mark the 900th anniversary of the original Domesday Book, an 11th-century census of England. It has been cited as an
Read the rest
example of digital obsolescence on account of the physical medium used for data storage. Not sure why everything has to be made for/explained as it's made for literally everyone. Some software is for a niche section of programmers/developers/$niche-group, that's perfectly fine. If you're curious, use a search engine like the rest of us.
In VHS-Decode – Software defined VHS decoder
Also, if you're interested, there is a robust community around re-creating the Domesday project with modern hardware [0], as well as capturing LDs via the player's raw RF output, using both bespoke hardware [1] and off-the-shelf [2], then decoding the output in software [3]. [0]: https://www.domesday86.com [1]: https://github.com/simoninns/DomesdayDuplicator/wiki [2]: https://github.com/happycube/cxadc-linux3 [3]: https://github.com/happycube/ld-decode
In Writing an app is like coding for LaserDisc
There are in fact proof-of-concepts similar to what you describe[1] (this one is based off the Doomsday Duplicator[2], a hardware device used for Direct RF capturing off laserdisc players). My (admittedly basic) understanding of VHS vs S-VHS decks is that due to the stricter tolerances required by the S-VHS standard, S-VHS decks typically have better transports than regular VHS decks (lower wow/flutter, better tracking, etc...). And of course many of the high-end decks have a built in TBC. [1] https://github.com/happycube/ld-decode/issues/16 [2] https://www.domesday86.com/?page_id=978
In My Eight-Year Quest to Digitize 45 Videotapes
So he has a $25 RCA-to-HDMI and a $70 HDMI capture card for around $100. A fully assembled Domesday board is also somewhere $100 according to https://forum.lddb.com/viewtopic.php?p=100903&sid=a582ac9ebc..., although I guess it could be higher without a good PCB supplier. The article's Airspy R2 SDR is $169. There's a PAL decoder in https://github.com/happycube/ld-decode/blob/3d5cdeddbaf4515b..., I'm guessing it could be adapted to the article's purposes with some work. https://twitter.com/windyoona/status/1163043586314821635 says she was looking at it.
In Capturing PAL video with an SDR, and a few dead ends

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.