bothaggsigym1988/frameglide

Source
GitHub
First trending
Category
Media
GitHub stars
808

This page introduces an external open-source repository. It is not an HDATF product.

What it does

This project describes interpolation of console remote-play video on a Windows PC. It targets users seeking smoother presentation of low-frame-rate games. Documented input is a PS5 remote stream or experimental capture source, and output is interpolated video and replay recordings. The README describes generating intermediate frames with RIFE and TensorRT from chiaki-ng frames. It also describes upscaling with FSR 1 or RTX Video Super Resolution. Windows, a supported GPU and console connection setup are required, with some device paths marked experimental. Interpolation does not improve the game's own response rate and may add latency and wobbling interface text. The inspected repository contains only a README and download-button image, without core source or a license file. Features and performance remain documentation claims, and the installer was neither executed nor safety-verified.

License

No license No license file found. Without a license, reuse of the code is not permitted by default.

More in this category

  • sourmitocand1987/VividFrame-GPU
    This project describes GPU enhancement of video during playback on Windows. It targets viewers of low-resolution or noisy footage. Documented inputs include local files, captures and remote streams, with an enhanced display or exported video as output. The README describes a DirectX 12 chain combining super resolution, denoising, HDR and frame generation. Effects can reportedly be configured as a list or nodes. Windows 11 x64, supported GPUs and separately installed drivers are stated requirements. Offline export from node mode is explicitly unsupported. The inspected repository contains only a README, license and download-button image, so the core implementation could not be examined. These features remain documentation claims, and release-file safety and actual performance were not verified.
  • Vincentwei1021/video-shotcraft
    Video-shotcraft is an agent skill and production toolkit for teams that need editable product demonstrations rather than generated footage of imagined interfaces. It takes actual product screenshots, approved copy, visual styling and audio, then guides Claude Code or Codex through shot selection, storyboarding and Remotion animation to produce source projects and MP4 videos. Its shot recipes describe camera movement, transitions and timing, while the inspected example implements screenshot placement and animation as deterministic React compositions. The example workbench manifest imports the composition's timing tables and declares separate shots, captions, transitions, audio and editable property schemas. Motion Workbench imports that manifest into browser editing tracks and renders edited clips through Remotion, but a project needs its own manifest and exposed properties for meaningful structured editing. JianYing export preserves some caption and audio tracks while internal scene animation remains baked into video clips, so it is not unrestricted conversion of React animation into native editor objects. The workflow requires an agent environment, Node.js, Remotion rendering tools, access to source screenshots and suitable media tools, with separate checks for Remotion and audio licensing. Frame review and independent agent review are prescribed procedures rather than proof of automatic quality enforcement, preview effects can differ from final rendering, and neither rendered quality nor editor compatibility was independently tested here.
  • nexu-io/openmotion
    OpenMotion is a local video workspace for creators who want to adapt reference videos without losing editable source. Users provide a reference clip or link, a script, brand materials and media. An external agent rebuilds scenes as HTML, CSS and JavaScript, while Motion.md records shot order, timing and replaceable assets. Studio edits the same project files and exports MP4 together with reusable source and media. The package declares Node.js 22.18 or newer, while the current README recommends Node.js 26.11.1 for source development. Preview and rendering also require Chrome or Chromium, FFmpeg and FFprobe. Optional media generation uses the user's provider accounts, so local project storage does not mean every generation step stays on the device. The export verification source checks encoding, duration, decoding and seeking, but leaves creative review to people, and social publishing remains planned rather than implemented.
  • kajisho5/ffmpeg-skill
    ffmpeg-skill gives coding agents structured tools for editing local video and audio instead of inventing FFmpeg command strings. It accepts source media, cut ranges, caption files and delivery settings, then produces edited files and JSON reports. Its 42 tools cover cutting, joining, silence removal, aspect changes, captions, overlays, sound processing and platform exports. The prescribed workflow measures the source first, edits without reencoding where possible, and measures the result again. Tool input schemas are derived from the same argument parsers used by the scripts, while an MCP server translates tool requests into script arguments. Output checks cover measurable properties such as duration and loudness, and contact sheets support a separate visual review. Local operation requires Python 3.10 or later and FFmpeg 6.1 or later, while speech transcription requires an additional local engine that may initially download model weights. The tools do not identify subjects or decide which scenes are interesting, and technical verification does not guarantee correct framing, readable captions or an acceptable sound mix.
  • hitkeeen/blender-ai-mcp-addon
    This project documents a Blender assistant with visual chat and an MCP server, a standard interface through which external AI clients call tools. It describes tools for inspecting scenes, creating and editing objects, assigning materials, searching assets and exporting scenes. A separate Studio window presents conversations, viewport snapshots, approvals and a task board. Connections cover supported cloud providers, local Ollama models and custom endpoints using specified protocols. Team mode assigns planning, execution and review to separate roles and processes scene changes sequentially. One correction attempt is allowed before a second failed review stops the chain. Built-in operation approvals and undo support do not make Python execution a security sandbox, and external clients control their own approvals. The inspected repository contains documentation and images but no implementation source, so these capabilities are documented claims rather than independently verified behavior.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.

View on GitHub (opens in a new tab)