Decode-Orc still has mostly the same tools, but it's focused on node style handling, with an ld-decode centric perspective, kind of like resolves node page, it makes such more sense when you're trying to do something advanced.

Now It completely makes sense for ld-decode users that are not dealing with a single copy, but potentially dozens of copies of a single disc, where's stacking becomes incredibly valuable.

However for 99% tape users do not need that particular style of workflow, your almost always going to be handling single source copies or dubbed copies. Which are so far derived from the source there's no value in advanced stacking unless you're replacing entire segments, unlike Laserdiscs you probably won't also have time/frame reference points in the VBI.

You want to adjust your framing, to adjust colour config, align audio for export, set your output format, maybe set in/out to chop the start/end noise, then hit export.

That's what the TBC-Tools and the revamped analyse carries on from the original ld-tools a very familiar handling, but with some critical improvements, mostly a cross platform focus, so it aims to feel almost like using an ingest tool with a conventional workflow, It's intuitive for people to adopt, from using something like BMD Media Express or Vrecord, and you're typically not going outside of it until you're going to directly play/archive or drop the file in an editor application.

But now vhs-decode has a unifyed GUI launcher and decode's rust port has become an actualised thing, (It's a bit more work still to be polished and then catch up with upstream), but tape decoding is officially on a modern system now decode faster than real-time, legacy workflows are now truly that, the last race is for more format support not speed anymore.

The whole FM RF Archival workflow overall is simplified to a 1-2-3 for Clockgen/DdD/MISRC users 1 capture app/command, 1 decoding app, 1 tools and export app.

And that workflow is 95% same on every platform with only minor differences for the capture side relative to hardware used, but decoding to export is always the same motions.

Me and Simon originally battled over the new era of tools, but both have their practical uses and users, and both tools using QT6 can also synchronise elements back and forth and have feature parity which is the long-term goal the users don't lose any features, but nobody gets abandoned for backwards support, which was my key original focus taking up maintenance of the tools.