Having a native AV format that comes from ANSI, pre-rendered via FFmpeg, is the missing link for <video> support.
That seems to optimise for usability/complexity ratio, while completely throwing coolness under the bus. But this is a ASCII video generator, I would've thought coolness was the point? I can't imagine a practical usecase for it...
> Local AI & LLM Ready: By reducing complex pixel streams into structured logical strings, ASCILINE acts as a perfect bridge for AI. Instead of feeding heavy computer vision models, lightweight LLMs can process semantic video summaries.
In what way is this semantic/structured?
> Bypassing Browser Constraints: Modern browsers aggressively throttle autoplay videos, and ad-blockers restrict traditional media frames. To the browser, ASCILINE is simply "JavaScript updating a canvas"—completely invisible to media restrictions.
So... just render the video to a canvas? What does ASCII have to do with it
> Bypassing Browser Constraints: Modern browsers aggressively throttle autoplay videos, and ad-blockers restrict traditional media frames. To the browser, ASCILINE is simply "JavaScript updating a canvas"—completely invisible to media restrictions.
The permission granted by this license explicitly EXCLUDES the right to use this software, in whole or in part, for the purpose of serving, delivering, or displaying digital advertisements, sponsored content, or any form of commercial marketing to end-users. Any such use immediately terminates this license.
Funny to see the avatar on the GitLab project https://gitlab.com/uploads/-/system/user/avatar/32369523/ava... ASCII-person :-D
Just 2 files .. that is nice .. https://gitlab.com/here_forawhile/tcom/-/tree/main .. it's pretty readable too.
FYI: I ran and installed deps (excluding numpy) and then performed the audio/video loopback test, and that worked - perfectly nice :) (might want to zoom on my face automagically, for facial-cues, as my resolution was low). While running in iTerm2 on macos the main menu, after this, it complained about blocking scrollback-history clearing attempts, and then became unwilling to show typed digits - only for the deps + loopback test phases was it willing to show them. ENTER was processed, and the menu rightly said "invalid choice". Still, good work! Here's a video:
Cheers!