Video Recording - Guides - | Virt-A-Mate Hub

Greetings, Creators!
English is not my native language, so please excuse any inaccuracies.
This is a guide for those who want to record video from VaM. Please note there is a plugin that allows you to record video directly from VaM, but it does so by saving a sequence of individual frames that you then need to merge into a video using an external application. There is also a similar guide. Here I will discuss recording using popular Screen Capture Software (SCS).
Everything described here is the author's personal experience and does not pretend to be a complete study. Moreover, much attention is paid specifically to aspects of video recording using very old equipment and aspects of very precise synchronization of video and sound, which may be useless for most users. But! If you want to:

1) at least on video to get the desired 60 FPS on an ancient video card, which barely gives out 30 FPS in real time,

2) learn how to record video and edit it without re-encoding,

3) learn how to record ass-shaking videos with looping and very precise music binding,

4) learn about existing popular capture software (well, some people may know more or less)

5) to laugh at the efforts of a perfectionist to achieve dubious goals.

then this guide is for you!

The guide turned out to be very extensive, so it is structured in spoilers from relatively independent topics, some of which you can skip.
First I give a summary table of the results of few SCS. All tests were performed on my outdated system: Nvidia GTX1050, Xeon E5-2680v3, RAM 16 GB (yes, this is a Chinese revived server kit for 100$). The SCS under test are: Bandicam, OBS, Riva Tuner Statistic Server (RTSS), NVIDIA ShadowPlay, Fraps. There is also a proprietary SCS for Radeon GPU, but I can not test it. Further you can find explanations of the evaluation criteria in this table and my personal conclusions, but before that I recommend you to familiarize yourself with the general concepts.

Criteria/software	Bandicam	OBS	RTSS+x264vfw	NVIDIA ShadowPlay	Fraps
Freeware	10 min, watermark	free	free	free	30 sec, watermark
Encoder settings	enough	comprehensive	comprehensive	low	too low
Logo/effects	logo	comprehensive	-	-	-
Performance drop	-	-	-	noticeable	-
Frame loss/unsync	-	much	huge	much	-
Mouse disable	+	+	+	-	+
Key Frame interval	Exact number	Time interval/ Exact number	Exact number	-	-
Smooth recording start	Freeze, unpredictable delay	Good	Good	A notice visible in the video	delay

Game FPS (Frame Per Second) is a render productivity. In order to record video without jerks and freezes it is very important that the rate VaM renders frames does not fluctuate in time. For this you need to reduce GPU load. This can be done by coarsing visualization settings or by limiting your game FPS. For example, my system produces 35 - 50 FPS in a simple scene, but highly dependent on many factors, then I will choose to limit it to 30 FPS. VaM does not have an setting for FPS limiting, so you can use plugins (see sect. time slowdown) or you GPU driver settings. Many of the reviewed SCSs also allow you to limit the VaM's FPS. The considered SCSs have the ability to select the frame rate of the recorded video, as well as to indicate the current frame rate.

Video Frame Rate (VFR) of the recorded video - this value does not have to match the game FPS. The usual mode for recording video is the mode in which the VFR is the same as the game FPS. All SCSs allow you to set the recording rate at Constant Frame Rate (CFR) mode. It is highly recommended to use CFR with an value FPS that is easy to achieve on your system.

FPS Increase. There is a comprehensive guide [2] and a plugin [3]. The point is to know the bottlenecks of VaM system and the balancing of "heavy" objects number in the scene. Very briefly the main factors affecting performance in order of decreasing their heaviness (very conditionally): hair, shadows, light sources, camera atom enabled, physics. The latter can be the first on this list under some conditions. I would also note that there is a plugin [4] to increase the resolution render, which significantly increases the quality of the picture (at the expense of GPU load, of course).

Time slow down in VaM scenes (there is a slider in the UI). This is an important aspect of this tutorial, as this is the way the VFR increasing achieved. It also has a positive effect on your game FPS by offloading the physics calculation. In order to accurately synchronize the music on the recorded video, we really need 4 digit accuracy to adjust this value. Unfortunately, the VaM time scale slider only displays a rounded to one decimal place value, (while the actual value is unknown), making it impossible to use. To overcome this I created a plugin [6] that allows you to set this value using an input field. This is a modification of the plugin [5] of the esteemed @MacGruber , I just changed the interface a bit and added the time scale input and calculation described further. Also in these plugins there is an option to disable the VaM render when it is in background, which greatly reduces your power consumption (note that for the original plugin this option does not work if animation is freezed in VaM UI settings).

Time flow in VaM. The game has its own time progression, which differs from real time. To compensate for various freezes and lags, time in Unity system is little bit slower (due to microfreezes), even without deliberate slowdown. For my system VaM's time is 1.5 - 3% slower even with stable FPS (learned this from some scripting experiments). Short-term FPS drops associated with opening dialog boxes or affecting scene objects through the user interface are expressed in time freezes. The greater FPS drop the more noticeable time difference is. At the same time, music launched by means of VaM has a real time course!

Encoder settings. This is about real-time video compression capabilities. The more of these settings, the more acceptable quality/size ratio we can get (if, of course, we go deeper into studying these settings). So this is both an advantage and a disadvantage. For Fraps everything is simple - an AVI file is created (this is a disadvantage, by the way) with high image quality and very low compression, and further use of third-party re-encoding software is assumed. The leader in compression settings is OBS. Bandicam is the happy mean - less but quite enough settings to get high video quality to bitrate ratio.

Performance drop. When recording is running, part of your GPU resources are spent on video encoding. This can be important in scenes where your graphics card can barely cope with producing a stable FPS value. Starting recording can "overload" the GPU so that drops will reflect in frame loss on the recorded video. To notice FPS drops you can setup the current FPS indicator during recording (Bandicam, RTSS and Fraps allows you to see this indicator during recording, but it is not recorded on the video).

Frame loss/unsync. If your GPU is unable to produce the target recording frame rate temporarily or permanently, the recorded video will have lost frames. That is, irregularity FPS in CFR mode expressed in duplication of neighboring frames on the video - the new frame is late, and the previous frame is recorded twice (in general, there is a setting to skip double frames when recording, which is actually even worse). This is expressed in twitching of moving image. The more uneven the FPS, the more noticeable is the twitching in the game and on the video. Unfortunately not only the GPU overload is the cause of frame skipping: some SCSs for some reason create frame loss even with stable FPS. For my system, NVIDIA ShadowPlay and OBS produce a large percentage of frame loss, which is noticeable on the result (if you are trained to notice it). Another catastrophe is observed in RTSS: encoder x264vfw simply skips such frames by default, which expressed in short-term video speedups. I should note at once that the losses level, of course, depends on the GPU load (I conducted the NVIDIA ShadowPlay test on another system with NVIDIA RTX3060, the losses there are much less), but it is never zero. Of course, estimation of the number of missed frames is very subjective, - you will think, and you will be almost right: many people play games with unstable or below 60 FPS and don't notice any problems (probably having vision problems later). But there is a way of objective assessment: frame-by-frame viewing of the recorded video will help you to identify identical frames in a row and the next frame with a sharper image change (we are talking about a moving scene, of course). For such a test I used Avidemux [7]. I tested all mentioned SCS in one VaM session in a scene with looped motion at light GPU load and constant FPS. For my system the percentage of frame loss in ShadowPlay and OBS is at least about 5%, while in the same recording conditions Bandicam and Fraps have no loss at all (of course, they will appear if FPS is unstable due to high GPU load).

The following two parameters are really not important for most people, but they are important for my tasks. The purposes and the calculate method will be discussed later.

Key Frame Interval. This is the interval of inserting key frames in the recorded video. In brief: the more frequent (the smaller this value is), the larger the video size, but the more accurate/faster the rewind. Often this number corresponds to 4 or more seconds of video. In most cases, lowering this number only makes sense for fast moving action scenes. There are recording settings that cleverly reconfigure this parameter right during recording (or subsequent transcoding). Bandicam allows you to adjust this by setting an exact value (at least for Nvidia GPUs, post if this is not the case). OBS allows you to set either only an integer number of seconds in the "standard" settings (recalculated to interval), or the number of frames in pieces - in the "special (ffmpeg)" settings. The first option turns out to be useless for my purposes. In RTSS it can be configured with [-i] switch in x264vfw parameters.

Smooth start. All SCSs have a time delay between pressing the record button and the actual appearance of the first frame in the video. It is a hundred millisecons value. This value is maximum for Bandicam, often aggravated by disk space reservation process, plus this time can vary significantly, itself remaining on average about 0.5 sec. The others have much lower latency. ShadowPlay has a (non-disable!?) recording start indicator lasting a couple of seconds, which goes on the recorded video.

Summary from personal experience of use.
Fraps

Advantages: no frame skips, load is low.

Disadvantages: paid (Watermark), very few recording settings, low video compression, further video re-encoding is assumed. It is a very old software that saves video in AVI container, not MP4. Doubt someone find this useful.

NVIDIA ShadowPlay.

Advantages: free.

Disadvantages: not for Radeon, few recording parameter settings, lots of frame skips, can't turn off mouse cursor recording and recording start indicator (post if I'm wrong). Obviously this is the simplest option for Nvidia, but not suitable for Radeon.

And the following are common and up to date.

OBS

Advantages: free, a huge number of settings for video recording parameters, the lowest delay to start recording, a set of possibilities to add video effects.

Disadvantages: complexity of settings (requires more understanding of settings), large number of frame skips. Probably an ideal choice for anyone who has a system with enough performance to get a stable 60 FPS. Unfortunately, not for me.

Riva Tuner Statistic Server - RTSS

This is similar to OBS, but with a different overlay system where you can customize the display of your system load (the direct purpose of this software). The latter makes this software potentially the best. For video compression the authors themselves recommend to use a third software x264vfw (which is based on ffmpeg - like OBS), then there is a huge number of compression settings appears.

Note from my usage experience. This SCS is included in MSI Afterburner package, but can be installed separately as a standalone product. In the standalone version, I failed to capture video (just nothing happens). To be honest, I didn't get anything good in Afterburner either, although I tried much. Capture settings are made both from Afterburner and in RTSS itself, and the settings options are slightly different. It is confusing, because it is not clear which ones are working at the moment. Video is saved only in AVI or MKV (the techniques discussed later allow you to change the container without transcoding easily). The x264vfw settings often just have no effect and the recorded video has a huge number of missing frames (even with GPU load about 70%). I hope someone will share positive experience of using this SCS.

Bandicam

Advantages: no lost frames, easy recording setting, keyframe interval setting.

Disadvantages: paid (watermark), recording often creates a freeze and has the longest delay (about 500 ms).

The mentioned advantages are key for my tasks and that is why I choose this software.

The center idea of this guide - VFR boost. The idea is simple: slow down the time in VaM, lets say, by 2 times, record it in 30 FPS, and speed up the frame rate on the video - also by 2 times. Then we will have 60 VFR with "correct" time progression. To speed up the video during playback, you can use the settings of players such as PotPlayer. You can also convert video using a video editor (discussed below).
Seems simple? Until you state additional conditions: precise time scaling (to match music) and video acceleration without transcoding and changing keyframes.
Here we come to the main idea of this tutorial. My task is recording video of dance movements (strictly cyclic), which can then be edited in a video editor to create combinations of different movements and view angles. This requires accurate frame time binding to the music and preferably no need to transcode the video. The actuality is up to you. The rest of this guide will be devoted to this. Further actions will require the use of additional command line software and installation of plugins in VaM.

Video speed up without transcoding. This can be done with the freeware ffmpeg [8]. It works from the command line, which requires some skill.

I should note right away that I am not an expert on this extremely powerful and complex software, I just found a ready-made answer on SO and verified that it works as needed. The reason I don't use it is because I wrote my own conversion program. I say this in case you want to ask me how to reconfigure something there in ffmpeg - I don't know it.

without re-encode performing in two steps with a temporary file:

Code:

ffmpeg -y -i "input.mp4" -c copy -f h264 "temp.h264"
ffmpeg -r [DFPS] -i "temp.h264" -c copy "output.mp4"

where [DFPS] - your target video frame rate (a float point value without brackets)
I made a .bat file in two versions (see in the last section [10]), the version convert_mp4.bat changes the container to .mp4 and the other one leaves the container unchanged. You only need to specify the ffmpeg path in this file(s) (or add it to the system environment variables).

The following information is for precise music binding methodology only.

Video editing can be done in different ways, depending on the editor's capabilities and your requirements. In case you only need to rearrange or delete parts of the video, but not change the frames themselves, it is possible to do this without transcoding the video. This means that you will not lose video quality, and saving the video is much faster than with transcoding. But there are a number of conditions that must be met in order to do this: 1) the editor must allow you to do this 2) the editing is done with the keyframe placement in mind. This feature is provided, for example, in avidemux [7], if you select the copy mode as a saving mode. Keyframes (I-frames) are self-sufficient frames that do not require neighboring frames for decoding. All other frames require decoded preceding frame (P-frame) or decoded following frames (B-frame). Deleting a keyframe means that all frames following it cannot be decoded (up to the next keyframe). Thus, the condition for editing without transcoding is that the end of the deleted/inserted section must fall on any subsequent keyframe, and the inserted section must start from the keyframe.

The horizontal axis represents the number of frames in the video, blue dots represent keyframes (at 10-frame intervals). The examples of correct placement/deletion area boundary are colored green, incorrect (i.e. requiring insertion of additional keyframes and, consequently, re-encoding) are red.
Once again about the expediency of transcoding evading. The fact of transcoding may reduce video quality or quality to bitrate ratio, but only if you don't want to learn the its settings. On the other hand, the requirement of transcoding evading imposes hudge restrictions on the complexity of motion in the resulting video. In fact, without transcoding you can not compose videos with camera movement and other object's complex movement. Moreover, you can use the tactic of record video with very high quality and low compression (large size), and then transcoding it (possibly using two-pass methods) in order to reduce the size of the video on disk while maintaining quality. The choice is yours.

Let's discuss what numerical characteristics we have. In the simplest case, a music track is built in one tempo. It is usually specified in beats per minute (BPM) and corresponds to a period in seconds. Video is recorded in CFR mode, and its editing is performed by frame boundaries. Any video part duration is always a multiple of the frame period. Another variable that we have is the VaM's time scale factor (CT). With this coefficient, the time on the recorded video is scaled too. Our goal is to make the start time of a music period N on accelerated video exactly coincide with the time of some frame number k.

N*60 / (CT*bpm) = k / VFR where n, k are integers, CT - Time Scale

We cannot precisely control the FPS of the game rather then the VaM's time flow speed. Then we should choose a CT coefficient that will ensure that for a chosen cycle N it coincides with the time of frame k in the resulting video (accelerated), while changing the VFR of the resulting video (resulted video frame rate - RVFR). I call such a variant of the calculation aligned. The alignment period N is a non-zero integer, you can take it as a musical size. The ready-to-use formula for calculating RVFR is written in the plugin [6] and excel-file discussed later. The calculation is done in the downward direction of this value (please note that not all monitors are capable of displaying more than 60 Hz). RVFR tends to the desired VFR (DVFR) with increasing N and at some value can exactly match it (e.g. for a tempo of 128 BPM, Game FPS=30 and DVFR=60, selecting N=8 will make RVFR exactly 60). The negative effect of choosing an irrational value CT (and it will be in most cases) is that the RVFR will be an irrational number (and we would like a standard 60). But we will have to sacrifice this.

One last thing: if we want to combine different movements on the video without transcoding, we need to get the first frame at the same starting phase of cyclic motion. Then it is seems logical to take the interval of keyframes equal to k (from the above explanation). In this case, all keyframes will fall exactly on the same phase of music. But which one? To hit the record key at the right moment is not so simple (even with time slowdown in the game), and it is impossible to do considering the recording start delay variation. That's why the better way is to choose this value as k-1 (or k-2). In this case, each subsequent keyframe will be slightly to the left (earlier) in phase, and if we record many cycles, we will select a suitable keyframe on the recorded video. Let's call this the "k-1 tactics".

Case Study. I show a complete cycle of actions to create a video of simple dance moves to music without transcoding. All further actions are performed with Bandicam as a SCS.
1) Presets (performed once):

a) install a SCS;

b) customize video compression settings and output files storage path, set hotkeys to start/stop video recording, customize FPS indication (preferably);

c) install ffmpeg [8]

d) copy the .bat file(s) to the storage and specify the path to ffmpeg in it

e) install the plugin VideoRecorderHelper [6]

f) (optional) copy excel file from this manual to the storage

g) (optional) install VaM SuperVideo plugin [4]

h) (optional) install avidemux [7]

2) Setting up recording in a VaM scene.

a) Open a scene and adjust the movements tempo as there is no time scale.

b) Add the VideoRecorderHelper plugin [6] to a session or scene or character - it doesn't matter where.

c) In it, set the limit FPS (check the box). The entered value is applied immediately. The same value should be entered in SCS.

d) Set the values (from top to bottom) music tempo (130), desired VFR (75) and, if you want aligned version, the non-zero alignment period (2). The calculation results appears below.

e) Click the apply button to set the calculated time scale (you can also manually enter any value in this field). From this point the VaM's time flow will be slowed down, the GPU load associated with physics should be decreased.

f) (optional) If video will be recorded from the Window Camera Atom, you can apply the plugin [4] on the camera atom to improve render quality. Conveniently, it works only when camera view is enabled. Remember that it heavily increases the load on the GPU. Check that FPS is still stable during the camera view.

g) (optional) In the SCS, set the calculated keyframe interval value minus one (see below).

Explanation for the calculation results (from top to bottom):

a) The period of musical tempo in seconds and the defined align period.

b) Value of keyframe interval in pieces - enter reduced by one value (k-1 tactics) in the SCS. For exact variant of calculation - round it to integer value by yourself.

c) Resulted VFR.

d) The last line in the results is the convert.bat call pattern for the speed conversion, you can copy it to the clipboard right away.

3) Settings done and you can start recording. Hide VaM interface (buttons U, F1). Camera view - M. Start animation and recording (keep in mind the recording start delay).
4) Write a few movement cycles for the "k-1 tactics" (if possible).
5) Stop the recording.
6) Speed up just recorded video without transcoding. To do this, go to Explorer, console or, for example, TotalCommander to run the .bat from the repository. You have already copied the command (actually the RVFR value is only important in it). Substitute the name of the recorded file into the command as the first parameter (in quotes).
7) (optional) Edit the file to find a proper keyframe falling on the starting phase.
Remarks:

1) All SCSs create file names that contain the time the video recording started - this makes them easier to find (simpler organizing).

2) Bandicam creates names with spaces, when converting such a name it is necessary to enclose it in quotation marks (otherwise the command will be perceived incorrectly, that's why there are already quotation marks in the command template).

3) RTSS creates output files in .MKV container, I suggest to use .MP4 for further editing. Then you can use convert_mp4.bat script [10], which within ffmpeg capabilities will change the container to .MP4.

4) The script does not modify the source file.

5) The script removes the sound from the video.

6) This script creates/overwrites without warning a temporary file ~TEMP.h264 in the storage, the size of this file is similar to the input file.

7) The script creates an output file with the new frequency suffix (VFR) in the name.

Video editing without transcoding.
1) Open the accelerated file in Avidemux.
2) When recording in Bandicam, the first frames are always spoiled by incorrect time progression due to recording delay, so I recommend to immediately delete the first part of the video until the next keyframe (Up - ctrl+PgDn - Del).
3) Scrolling through the keyframes (use the up/down arrow on the keyboard) find the initial phase of motion. If recording is started too late and very few cycles were recorded, there may be no proper keyframe on the video. Then record it again.
4) Delete the cycles before it.
5) Select several complete cycles from the rest video, I recommend saving at least 8 motion cycles. Here you can also apply some strategy of saving different movements, because they must be combined somehow on the composite video, and the initial phase of all of must be the same.
6) (optional) Add a music track. Menu Audio - Select Track - Track1-Enable - Add Audio Track.
7) Save the selected part of the video. Copy mode means no transcoding, but are imposed restrictions.

The above actions are demonstated on the video below.

And some bonuses at the end.

You can record and edit a video for one music tempo and then change VFR to the video for a different music tempo. To do this the original's video VFR must be constant (in general it could be variable). You can use the same conversion script [10], specifying as VFR=CVFR*T1/T0, where CVFR - current VFR of the recorded video (this number is right in the file name if you follow these instructions), T1 - new BPM, T0 - old BPM.

In practice, it turns out that a 0.5 BPM difference between the tempo of music and video BPM will be noticeable after a few seconds of video. Now we have learned how to adjust the video recording to a very precisely specified tempo. For perfect synchronization it is also necessary to know the exact tempo of the music. Often a music is builded based on one of the most common tempos, such as 128 BPM. There are many internet sites that help you to determine the tempo of the music from the file you provide or by tapping/clicking. But in my experience, the accuracy of such estimation is not enough, so I use the freeware Audacity [9] to determine the tempo more accurately. To determine the tempo, you need to add a Rhythm track in parallel with your track (Generate - track, issue it while the music track is deselected and the cursor is at the beginning of the track) and visually and by ear determine the coincidence of clicks on both tracks. First you set the tempo at random, compare, then delete the rhythm track, add a new one with a changed tempo. And that's how you match the tempo. In newer versions (3.7 in 2025) by default View - Toolbar - Time Signature Toolbar is enabled. If the checkbox Snap is active, the cursor is snapped to fractions of a beat. If you have guessed the tempo then by placing the cursor in different places you should notice that you are hitting the same fractions of the musical rhythm (this can be observed by ear and on the shape of the audio signal). Otherwise you will hit different places. Unfortunately, changing the tempo value on this toolbar causes the tempo of the original music track to change (there is a discussion on the forum). For final confirmation of tempo detection you need to close all tracks, change the tempo figure on the toolbar, add tracks again (drag-n-drop works) and try to arrange cursor again. Feel free to share your experience of tempo detection with other software. Please be aware of possibly high loud in the video below.

All the calculations presented can be done in the included excel file as well. As a bonus there are extra numbers that help in video editing in there. The cells for the input data are colored in blue:
B2 - BPM music tempo.
B3 - game FPS - FPS value of the recorded video according to the capture software setting (the same value should be in the VaM's FPS limit).
B9 - desired VFR you want on the resulting video (accelerated).
B4 - N - number of musical periods for calculation of keyframe interval.
The output is calculated for two variants: exact (column B) and aligned (column C).
Line 7 - CT - VaM time scale factor you need to apply.
Line 8 - k - keyframe interval value in pieces - enter reduced by one value (k-1) into the SCS.
C9 - resulted VFR - corrected value for the aligned calculation
Lines 14-19 help to calculate the duration of X music intervals for the selected tempo for music (column B), on the raw recorded video (without acceleration) with exact (column C) and aligned (D) calculation.
B20 is the time the misic tact it belongs to is calculated (D21) and its start time (B21) considering the multiplicity in D20.
B22 - allows you to calculate RVFR value for the new tempo (relative to the current tempo in B2).

Sorry it seems I can not post the file here. Please recommend a file sharing service in the discussion, so I will understand that someone needs it.

References:
[1] https://hub.virtamate.com/resources...d-flat-2d-audio-bvh-animation-recorder.11994/
https://hub.virtamate.com/resources/how-to-record-videos-with-poor-performance.17972/
[2] https://hub.virtamate.com/resources/improving-fps-in-vam.445/
[3] https://hub.virtamate.com/resources/givemefps.1367/
[4] SuperVideo from https://hub.virtamate.com/resources/macgruber-essentials.160/
[5] FrameRateControl from https://hub.virtamate.com/resources/macgruber-essentials.160/
[6] Video Recorder Helper https://hub.virtamate.com/resources/videorecorderhelper.55784/
[7] https://avidemux.sourceforge.net/
[8] https://github.com/btbn/ffmpeg-builds/releases
[9] https://www.audacityteam.org/download/
[10] .bat

Code:

@echo off
REM insert your path in quotes, DO NOT add spaces before and after = sign
set ffmpeg_path="ffmpeg"
REM following flags are for silent operation only
set flags=-hide_banner -loglevel warning
REM usage: convert filename target_FPS
REM use quotes in video file name
REM example convert "VaM 2025-01-18 02-20-28-641.mp4" 75.833
%ffmpeg_path% %flags% -y -i %1 -c copy -f h264 "~TEMP.h264"
IF %ERRORLEVEL% NEQ 0 goto error
%ffmpeg_path% %flags% -r %2 -i "~TEMP.h264" -c copy "%~dpn1[%2Hz]%~x1"
exit
:error
pause > nul

Code:

@echo off
REM insert your path in quotes, DO NOT add spaces before and after = sign
set ffmpeg_path="ffmpeg"
REM following flags for are silent operation only
set flags=-hide_banner -loglevel warning
REM usage: convert filename target_FPS
REM use quotes in video file name
REM example convert "VaM 2025-01-18 02-20-28-641.mp4" 75.833
%ffmpeg_path% %flags% -y -i %1 -c copy -f h264 "~TEMP.h264"
IF %ERRORLEVEL% NEQ 0 goto error
%ffmpeg_path% %flags% -r %2 -i "~TEMP.h264" -c copy "%~dpn1[%2Hz]%.mp4"
exit
:error
pause > nul

I hope this guide will help you. Share your recording experience in the discussion.

Guides Video Recording

More resources from Nickon7777

Share this resource

Latest reviews