vhs-decode VS ld-decode

No, I’m using an ADC modified for use with LD captures [0]. I did this because it’s cheaper in theory, although with the amount of time I’ve dumped into getting it working and keeping it working, the $500 or so for the Domesday Duplicator may well have been a better choice.

[0]: https://github.com/oyvindln/vhs-decode/wiki/CX-Cards#what-is...

For NTSC, also check out https://github.com/oyvindln/vhs-decode

I'm very happy to make the announcement we are migrating not only FM RF but as time permits many full demo sets (RF+TBC+Video+Audio) and full re-masters of tapes from our community and userbase of including but not limted to lost media.

Your going to want to use vhs-decode and FM RF capture standard video captrue has long been supassed in terms of archival and resulting decoded quality.

There's VHS-Decode as well, a small fork specific for VHS, Beta, Video8, etc.

Directly capturing the output, without converting it, will provide the best results. With modern open-source decoders, you can even connect directly to the drum head signal, and capture with no further loss than what occurred during recording.

Furthermore, there are projects that seek to preserve (as accurately as can be sorted out) all of the information that is contained on any given VHS tape, such as this one: https://github.com/oyvindln/vhs-decode

Have a look into VHS-Decode, arguably the best way as its true raw capture and also probably the cheapest for the quality you get, but requires soldering and basic Linux skills. I've mostly stopped bothering with other methods.

But here have a look at Some CVBS Samples the source TBC files can be easily viewed with ld-analyse with the ld-tools for windows too.

There is only one way in the 2020s VHS-Decode & HiFi-Decode

> 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 another ill-suited application", then this advice will likely work for you.

If you're the kind of dude to write ld-decode¹ (not me), then it will likely not.

[1] https://github.com/happycube/ld-decode

RF Capture time! then run it all through [ld-decode](https://github.com/happycube/ld-decode/)

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 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.

The way to really see what's going on with chroma sub-carrier in a composite video signal is to display a test pattern like a zone plate. This page shows an example. The bottom image shows the original test signal, while the top image shows the chroma artifacts composite encoding can introduce.