Skip to content

Latest commit

 

History

History
61 lines (45 loc) · 2.54 KB

README.md

File metadata and controls

61 lines (45 loc) · 2.54 KB

Video Duplicate Finder

Video Duplicate Finder is a cross-platform software to find duplicated video (and image) files on hard disk based on similiarity. That means unlike other duplicate finders this one does also finds duplicates which have a different resolution, frame rate and even watermarked.

Features

  • Cross-platform
  • Fast scanning speed
  • Ultra fast rescan
  • Optional calling ffmpeg functions natively for even more speed
  • Finds duplicate videos / images based on similarity
  • Windows, Linux and MacOS GUI

Binaries

Daily build (You need to download FFmpeg and FFprobe yourself, see below! Please note the attachments of this release are automatically created and replaced on every new commit.)

Requirements

FFmpeg & FFprobe:

Windows user:

Get latest package from https://ffmpeg.org/download.html I recommend the full (GPL) shared version. If you want to use native ffmpeg binding you must use the shared version.

Extract ffmpeg and ffprobe into the same directory of VDF.GUI.dll or into a sub folder called bin. Or make sure it can be found in PATH system environment variable

Linux user:

Installing ffmpeg:

sudo apt-get update
sudo apt-get install ffmpeg

Open terminal in VDF folder and execute ./VDF.GUI You may need to set execute permission first sudo chmod 777 VDF.GUI

MacOS user:

Install ffmpeg / ffprobe using homebrew

Open terminal in VDF folder and execute ./VDF.GUI or if you have .NET installed dotnet VDF.GUI.dll You may get a permission error. Open system settings of your Mac, go to Privacy & Security and then Developer Tools. Now add Terminal to the list.

Screenshots (slightly outdated)

License

Video Duplicate Finder is licensed under GPLv3

Credits / Third Party

Building

  • .NET 7.x
  • Visual Studio 2022 is recommended

Committing

  • Create a pull request for each addition or fix - do NOT merge them into one PR
  • Unless it refers to an existing issue, write into your pull request what it does
  • For larger PRs I recommend you create an issue for discussion first