A suite of tools for formatting and editing Instant Replay clips, both in-game and out.
Use customizable hotkeys to instantly trim clips to any length you choose (defaults to Alt + 1-9
for 10-90 seconds), or enter the length yourself using your number keys (defaults to Alt + 0
). Requires FFmpeg.
Prematurely saved a clip? Instantly concatenate the last two clips together (defaults to Alt + C
). Requires FFmpeg.
Merge your system and microphone audio tracks together if you have "Separate both tracks" enabled in ShadowPlay (defaults to Alt + M
). Requires FFmpeg.
Undo your last edit using backups of your most recently edited clips (defaults to Alt + U
). Access your backups anytime with a folder structure that mimics your videos folder.
Rename clips as they're saved using a highly customizable naming format. Allows you to set aliases for games while renaming, e.g. "Left 4 Dead 2" becomes "L4D2". A handful of common aliases are included by default.
A highly customizable tray menu that can be accessed at any time that offers all of the same features listed above. Edit, play, and explore any of your recent clips (not just the latest one!), while getting to see key information about each clip. Offers customizable left-click and middle-click actions.
GitHub will be checked for a new release every time you launch Instant Replay Suite. If you're using the compiled release, you'll have the option to automatically download/install the update straight from GitHub.
Plays (yes, customizable) .WAV files in real-time to give you audible feedback for various actions being taken, even while in-game.
On first launch, you'll have the option to add all existing clips in your video folder. This includes renaming any clips using ShadowPlay's naming format to match your desired format.
Instant Replay Suite does not simulate any keyboard inputs. It only reads them, making it safe to use online. The cost is that you have to manually save clips yourself and then use separate hotkeys to edit them, but this in turn allows you to save clips and worry about editing them later.
See the executable
folder for details on how to compile (it's REALLY easy).
- If you're new to contributing in general, you can use this guide.
- Follow the seven rules of a great commit message.
- Try to match the style of the code surrounding your addition. Don't let your code stick out like a sore thumb.
- Code should be as self-documenting as possible, but comments, docstrings, and type-hints are welcome.
configparsebetter.py
is off-limits (part of a separate project).- Avoid introducing new, heavy dependencies where possible.
- Avoid relative paths (use
CWD
for the root folder andpjoin()
for creating paths). - Be mindful of
REPOSITORY_URL
when making commits if you change it while testing.