Description
Currently, ReClip primarily defaults to MP4 for video processing. While compatible, the MKV (Matroska) container is often preferred for preserving high-quality streams (like VP9 or AV1) and handling multiple metadata tracks more efficiently.
Additionally, extending metadata support to include embedded thumbnails—both for video files and audio-only MP3 extractions—would significantly improve the user experience for library management and playback.
Proposed Changes
- Container Support: Update the download logic to support the
--merge-output-format mkv flag.
- Thumbnail Embedding:
- For Video: Integrate the
--embed-thumbnail flag into the download command.
- For Audio (MP3): Ensure that when audio-only extraction is selected, the thumbnail is embedded into the ID3 tags of the MP3.
- yt-dlp Integration: Ensure the backend utilizes the following flags to maintain high-quality archival standards:
--add-metadata--embed-thumbnail--restrict-filenames
- UI/UX: Provide options in the interface for users to toggle thumbnail embedding and choose between
.mp4 and .mkv.
Use Case
Many users utilize custom yt-dlp workflows to ensure their media is "plug-and-play" with metadata-rich environments like Plex, Jellyfin, or mobile music players.
Description
Currently, ReClip primarily defaults to MP4 for video processing. While compatible, the MKV (Matroska) container is often preferred for preserving high-quality streams (like VP9 or AV1) and handling multiple metadata tracks more efficiently.
Additionally, extending metadata support to include embedded thumbnails—both for video files and audio-only MP3 extractions—would significantly improve the user experience for library management and playback.
Proposed Changes
--merge-output-format mkvflag.--embed-thumbnailflag into the download command.--add-metadata--embed-thumbnail--restrict-filenames.mp4and.mkv.Use Case
Many users utilize custom
yt-dlpworkflows to ensure their media is "plug-and-play" with metadata-rich environments like Plex, Jellyfin, or mobile music players.