Source Video Render (SVR, formely SDR) is used to record movies for the Source engine. SVR does not have video effects - if you need video effects, see HLAE.
SVR can record faster than realtime for normal videos, or with high quality motion blur.
See Replay Viewer as a substitute for Counter-Strike: Source Source TV demos! The replay viewer will produce significantly smoother videos without teleport lag and server side interpolation.
You can use update.cmd in the SVR directory to automatically download the latest release. The latest SVR will be downloaded to svr.zip. You can extract this folder and SVR is now updated.
Any DirectX 11 (Direct3D 11.3, feature level 12_0) compatible graphics adapter with minimum of Windows 10 1909 is required. Hardware feature support verification will occur when starting the launcher.
Use svr_launcher.exe or svr_launcher64.exe to start the standalone SVR launcher. The launcher allows you to select which game you want to start. The games database is stored in the data/games directory. Here you can create new game profiles if you wish to change the launch parameters or configurations. The following launch parameters are always added by the launcher: -steam -insecure +sv_lan 1 -console -novid.
The menu selection of the launcher can be bypassed by passing in the identification name for a game as a start argument to the launcher. As an example:
svr_launcher.exe cstrike_steam.ini
Once in game, you can use the startmovie console command to start recording a movie and the endmovie command to stop.
The startmovie command should be used like this:
startmovie <file> (<optional parameters>)
As an example:
startmovie movie.mov timeout=30
The above example will produce a video called movie.mov with a render region of 30 seconds. Videos will be placed in the data/movies/ directory.
The list of optional parameters are as follows:
| Parameter | Description |
|---|---|
timeout=<seconds> |
Automatically stop rendering after the elapsed video time passes. This will add a progress bar to the task bar icon. By default, there is no timeout. |
profile=<string> |
Override which rendering profile to use. If omitted, the default profile is used. See below about profiles. |
autostop=<value> |
Automatically stop the movie on demo disconnect. This can be 0 or 1. Default is 1. This is used to determine what happens when a demo ends, when you get kicked back to the main menu. |
nowindupd=<value> |
Disable window presentation. This can be 0 or 1. Default is 0. For some systems this may improve performance, however you will not be able to see anything. |
When starting and ending a movie, the files data/cfg/svr_movie_start_user.cfg and data/cfg/svr_movie_end_user.cfg in data/cfg will be executed (you can create these if you want to use them). This can be used to insert or overwrite commands that should be active only during the movie period. Note that these files are not in the game directory, but in the SVR directory in data/cfg.
It is recommended that you don't edit svr_movie_start.cfg and svr_movie.end.cfg as they may be changed in updates, which would overwrite your changes.
The execution order of the cfgs is as follows: svr_movie_start.cfg > svr_movie_start_user.cfg. Each cfg file can override the previous.
The commands that are placed in svr_movie_start.cfg are required and must not be overwritten. Most notably, the variable mat_queue_mode must be 0 during recording for recording to work properly.
If something is not working properly, please find the SVR_LOG.txt and ENCODER_LOG.txt file in the data/ directory and explain what you were doing and upload it to Discord or create a new issue here.
Due to the nature of reverse engineering games, it cannot be trusted that direct interoperability (with ReShade or HLAE for example) will work because the risk of collision.
All recording settings are loaded from profiles which are located in data/profiles. The default profile is called default.ini and is the base profile of all settings. These profiles are shared across all games and are written in a simple INI format. The documentation for profiles is written inside the default profile here.
The default profile is used if no other is specified when starting the movie. You can override settings in the default profile by creating your own profiles inside data/profiles. When starting your movie you can then specify your new profile (see Recording above).
The default profile is always loaded first, and your custom profile is loaded on top. This allows you to override individual setting without copying the entire profile. To create your own profile, create a file with an .ini extension inside data/profiles/. You can now override settings in the default profile by putting in the settings you want to override.
In this demo an object is rotating 6 times per second. This is a fast moving object, so higher samples per second will remove banding at cost of slower recording times. For slower scenes you may get away with a lower sampling rate. Exposure is dependant on the type of content being made. The goal you should be aiming for is to reduce the banding that happens with lower samples per second. A smaller exposure will leave shorter trails of motion blur.
The X axis is the samples per second and the Y axis is the exposure (click on the images to see them larger).
| 960 | 1920 | 3840 | 7680 | |
|---|---|---|---|---|
| 0.25 |  |
 |
 |
 |
| 0.50 |  |
 |
 |
 |
| 0.75 |  |
 |
 |
 |
| 1.00 |  |
 |
 |
 |
- Extract ffmpeg-n5.1-latest-win64-gpl-shared-5.1 to
deps\ffmpeg\. - Copy contents of
deps\ffmpeg\bin\tobin\. - Build
deps\minhook\build\VC16\MinHookVC16.slnin Release. - Open
svr.sln. - Call
build_shaders.cmdfrom a Visual Studio Developer Command Prompt. In Visual Studio 2022, you can useTools -> Command Line -> Developer Command Prompt.