Saving and After Save Command

Saving and the after-save command

ShadePlay guide › Advanced settings

The advanced Saving page: fast start, the clip info file, and a command ShadePlay can run after each clip is saved.

Fast start

Fast start (on by default) moves the MP4 file's index to the front, so clips start playing sooner when they are streamed or uploaded. It costs one extra pass over the file while saving, in the background. Leave it on unless saving speed matters more to you than that.

Clip info file

Write a clip info file (.json) next to each clip (off by default) saves a small text file with details about each clip next to it, for scripts and tools: the game, the program that was in front and its window title, times, codec and audio tracks (what it holds). Off, the clips folder holds only the clips.

The file is always written while an after-save command is set (below), even with the box unticked, because the command gets its path.

Run a command after each save

Under After a clip is saved, Run this command takes a command line that ShadePlay starts every time a clip is saved, for example to copy it to a backup drive or hand it to an upload tool. Leave it empty to run nothing.

• {path} is replaced by the clip's full path and {json} by its .json clip info file's path. Both are quoted for you. While a command is set, the clip info file is always written, so {json} always names a file that is there (unless writing it failed; the log then says why).
• The command also gets the environment variables SHADEPLAY_CLIP and SHADEPLAY_JSON with the same two paths.
• It starts without a window, at below-normal priority, and ShadePlay doesn't wait for it.

The page shows three examples:

C:\Tools\upload.exe {path}
powershell -File C:\Tools\upload.ps1 {path} {json}
cmd /c copy "%SHADEPLAY_CLIP%" D:\Backup

Commands that go through a shell (cmd /c, powershell -Command) should read %SHADEPLAY_CLIP% and %SHADEPLAY_JSON% ($env:SHADEPLAY_CLIP in PowerShell) instead of {path} and {json}, because game names in the path can contain characters such as & $ ( ) that a shell would interpret. The page warns you when a shell command uses {path} or {json}.

Good to know:

• The command runs as you, with your rights, for every clip. Only put a command there that you trust.
• The log notes only the program's name, not the whole command line, so a token or password in the command doesn't end up in a log you might share.
• If the command can't be started, the log says why; the clip is saved either way.

---

Next: YouTube helper

See also: Clips, folders and names · Settings file, logs and command line · Privacy