RealityRipple/Lime-Seed-Media-Player
28.2
Weak · 7 November 2026
41.2k
lines of production code
VB.NET
with C#
4
measurements over time
What this system is
This system is a .NET-based media player and associated utility library, originally established in 2014, that focuses on local media playback and file integration. Its core capabilities include robust thumbnail generation for Windows Explorer, detailed metadata extraction for various audio and video formats, and a compact tray player interface. A significant component is the FFDShowAPI library, which allows external applications to remotely control the FFDShow video decoder via COM interfaces and Windows messages. The codebase has undergone structural reorganizations and licensing updates, settling into a public domain release model while maintaining its focus on media handling and decoder interoperability.
How it got here
2014 — Initial release and metadata enhancement
3 changes.
The period began with the initial setup and release of the Lime Seed media player, establishing the foundational project structure for .NET 4.0 applications. Later in the year, development focused on the GreenThumb component, specifically adding detailed property extraction for various file types to Windows Explorer. This work also included improving the reliability of thumbnail generation through more robust image scaling and error handling.
2016 — New FFDShowAPI library for remote control and configuration
1 change.
Added the FFDShowAPI library, a .NET component that enables external applications to interact with the FFDShow video decoder. This API exposes COM interfaces (such as IffdshowBase, IffdshowDec, and IffdshowDecVideo) and a remote communication mechanism via Windows messages (WM\_COPYDATA) to allow developers to get and set live settings, manage presets, control playback state (play, pause, seek), and retrieve metadata like frame times and subtitles.
2017 — UI and format support expansion
4 changes.
This period focused on enhancing the application's user interface and media handling capabilities. Significant work included implementing new file header parsing for audio and video formats, introducing a compact tray player, and improving error handling. The release was marked by a version bump to 0.8, expanded file association support, and a reorganization of the project structure and UI components.
2018 — Project restructured and licensed under Unlicense
1 change.
The solution has been reorganized to remove the LSFA project and add a new FFDShowAPI\_2010 project, with updated build configurations for both. The .gitignore has been updated to exclude DLL files, and the project is now released under the Unlicense public domain dedication.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 29 → 28 (-0.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 59 → 59 (+0.0)
- Architecture 91 → 66 (-24.9)
- Maturity 20 → 24 (+4.1)
- Readiness 10 → 10 (+0.0)
- Security 85 → 85 (+0.0)
Resolved (9)
- Duplicated block (11 lines × 2) (LimeSeed/Forms/frmMain.vb)
- Duplicated block (13–20 lines × 2) (Seed/Headers/clsMKV.vb)
- Duplicated block (7 lines × 4) (Seed/Headers/clsMPEG.vb)
- Projects may be oversized for their cohesion
- Two methods performing the same action ('lock') have different names: one uses a trailing underscore ('lock_') and the other uses a 'compat_' prefix. The underscore is often a workaround for reserved keywords or conflicts, while 'compat_' suggests a compatibility wrapper. This inconsistency obscures the relationship between the base interface and the compatibility layer.
- Two methods that appear to retrieve the current playback time use different naming conventions: one uses snake_case with a specific context ('get_time_on_ffdshow'), while the other uses PascalCase with a generic context ('getCurrentTime'). This inconsistency makes it unclear if they return the same value or different time sources.
- Two methods with identical names except for a numeric suffix (2 vs 3) suggest an iterative refactoring or versioning of the same underlying logic (likely finding auto subtitle filenames). This indicates a lack of semantic distinction in naming.
- Two methods with nearly identical signatures (accepting an object parameter) and similar names ('getPresets' vs 'getPresetsPtr') likely return related but distinct data structures (e.g., a managed object vs a pointer to unmanaged memory). While the suffix 'Ptr' clarifies the return type, the base name 'getPresets' is ambiguous when paired with 'getPresetsPtr'.
- XML-doc coverage: FFDShowAPI_2010 (FFAPI/FFDShowAPI_2010.csproj)
New (30)
- Projects may be oversized for their cohesion (LimeSeed/LimeSeed.vbproj)
- doc comments repeat the names (FFAPI/FFDShowAPI.cs)
- doc comments repeat the names (LimeSeed/Classes/clsCDRip.vb)
- redundant comment (FFAPI/Properties/AssemblyInfo.cs)
- redundant comment (FFAPI/Properties/AssemblyInfo.cs)
- redundant comment (FFAPI/Properties/AssemblyInfo.cs)
- redundant comment (FFAPI/Properties/AssemblyInfo.cs)
- redundant comment (GreenThumb/My Project/AssemblyInfo.vb)
- redundant comment (GreenThumb/My Project/AssemblyInfo.vb)
- redundant comment (GreenThumb/My Project/AssemblyInfo.vb)
- redundant comment (GreenThumb/My Project/AssemblyInfo.vb)
- redundant comment (LSFA/My Project/AssemblyInfo.vb)
- redundant comment (LSFA/My Project/AssemblyInfo.vb)
- redundant comment (LSFA/My Project/AssemblyInfo.vb)
- redundant comment (LSFA/My Project/AssemblyInfo.vb)
- redundant comment (LimeSeed/Controls/BetterProgress.vb)
- redundant comment (LimeSeed/Controls/BetterProgress.vb)
- redundant comment (LimeSeed/My Project/AssemblyInfo.vb)
- redundant comment (LimeSeed/My Project/AssemblyInfo.vb)
- redundant comment (LimeSeed/My Project/AssemblyInfo.vb)
- …and 10 more
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
RealityRipple/Lime-Seed-Media-Player was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 7 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 0e0e083f7a49c70bb523c93cf1731dae0d204a97 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.