The product name is "VoxCraft" with various CLI and GUI options. These can be executed as:
- Standalone CLI
- Standalone Windows binary > GUI UX
- GUI UX < through DaVinci Resolve as a Python-called "Plugin"
For example, here is the GUI UX running standalone from the binary:
The GUI UX is being supplied by simple_htmx and simple_alpine (e.g. HTMX with Alpine JS) and a host of other simple_* libs assisting.
In this case, the DaVinci Resolve screenshot below is using the Transcribe and Chapters products through VC Pro.
And here is the result as seen in the DaVinci Resolve GUI:

The SRT (subtitles/captions) file is the tannish-colored track above the video track. The "chapter markers" are above that (e.g. the multi-colored segments).
If you look to the left, you will see the "Markers", which are generated by VoxCraft Pro's "Chapters" tool. This is a powerful tool that literally saves hours of video-watching and notetaking, followed by manual editing and set up. What we quickly realized in putting this together was that the chapters could be derived from the Transcript (captions). Powered by AI, the transcript could be evaluated for chapters and then each chapter could receive not only a title, but a descriptive paragraph talking about what the chapter is about. This should accurately depict what the video is about at a glance and help guide manual editing (what to keep and what to delete, segment by segment).
Again, for the purpose of this group, I must strongly note that this is ALL Eiffel and it is utilizing freely available MIT license C/C++ and models that anyone can use for any purpose, monetized or otherwise. Claude has done an outstanding job of handling all of the orchestration, organizing, and compiling of C/C++ and then the Eiffel code needed to access it all. It is then also responsible for putting together the installer deliverables that include everything required to run the product without the need of further download. For example, it brings along a copy of the matching ffmpeg.exe that the software uses for certain jobs (like stripping out audio from video). We shall soon be putting this to work doing some NLE (Non-linear Editor) tasking. Trade secrets there, so I won't go into the details.
Now, this leads me to a conclusion for all of the nay-sayers who were griping that Simple Eiffel libs were not ready for primetime production. In all of this, Claude has barely changed any of the Simple Eiffel libs correctively. Most of the changes (the vast majority) have been additions to functionality. Below you will find an assessment of changes to Simple Eiffel libs and a categorization (corrective, additive, other).
● Simple_* Library Changes Since VoxCraft Started
VoxCraft Start: December 31, 2025
Corrective Changes (Bug Fixes): 2 commits
┌────────────┬───────────────────────────────────────────────────────────┬──────────────────────────────────────────────┐
│ Library │ Issue │ Fix │
├────────────┼───────────────────────────────────────────────────────────┼──────────────────────────────────────────────┤
│ simple_tui │ Missing logger library dependency │ Fixed ECF reference │
├────────────┼───────────────────────────────────────────────────────────┼──────────────────────────────────────────────┤
│ simple_tui │ Unicode handling bug - to_string_8 violating precondition │ Replaced with proper UTF-8 string conversion │
└────────────┴───────────────────────────────────────────────────────────┴──────────────────────────────────────────────┘
Additive Changes (New Features): 9 commits
┌────────────────┬──────────────────────────────────────────────────────────────────┐
│ Library │ Feature Added │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_speech │ GPU requirements research documentation │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_speech │ GPU acceleration enabled by default │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_speech │ correct_with_context for AI semantic correction with topic hints │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_speech │ Native speaker diarization via sherpa-onnx │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_web │ Quick server API refinements │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_sql │ Quick API updates │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_console │ Header updates │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_kb │ ECF configuration updates │
├────────────────┼──────────────────────────────────────────────────────────────────┤
│ simple_tui │ ECF configuration updates │
└────────────────┴──────────────────────────────────────────────────────────────────┘
Key Findings
- 6 of 87 simple_* libraries were modified (93% unchanged)
- simple_speech was the most heavily modified with 4 commits, all additive (features for VoxCraft transcription)
- simple_tui had the only actual bug fixes (2 corrective commits early in the project)
- The January 5th batch of changes across multiple libs appears to be a coordinated API cleanup/refinement
So, as you can see — hardly any corrective changes to what was built between November 11th, 2025 and December 31st, 2025. The VoxCraft project has taken 8 days so far (Jan 1-8) and produced another mountain of code from Me + Claude. The end result is an operational and complex product that is now in beta-test by my family member. From there, we will talk about marketing and so on and see what comes of that.
Without Eiffel this would not be possible or even feasible — literally 200K+ lines of code used to build a growing fleet of A/V products and more.
What think you all???
Best,
Larry