Recommended
FAQ About Variable Frame Rate (VFR) and Constant Frame Rate (CFR)
Using oCam at work or school? A license is required, and it removes all ads, including this window. See the paid version →
The following is a brief and clear FAQ about the frame rate modes in oCam.
Q. What exactly is Variable Frame Rate?
Variable Frame Rate (VFR) and Constant Frame Rate (CFR) are distinguished by the number of frames in the recorded video file. If the number of frames per second remains the same throughout a certain period of recorded video, it is considered Constant Frame Rate. On the other hand, if the frame count changes even for just one second during recording, it is classified as Variable Frame Rate. For example, if a screen is recorded for 5 seconds and every second is recorded at exactly 30 frames, it is Constant Frame Rate. However, if the video is recorded at 25 frames per second during the 3 to 4 second section of those 5 seconds, while the rest is recorded at 30 frames per second, it is Variable Frame Rate. However, the frame count in the final part of the video (for example, the last 0.5 seconds of a 4.5-second recording) is excluded when determining whether it is Constant or Variable Frame Rate. In other words, if a video was recorded for 4.5 seconds, stayed consistently at 30 frames per second for the first 4 seconds, and only the final 0.5 seconds had fewer than 30 frames, it is still regarded as Constant Frame Rate.
Q. If I record a game at 60 FPS in oCam with Variable Frame Rate mode enabled, and my system is powerful enough that there is no lag at all, will it be recorded as Constant Frame Rate?
If your system performance is good enough that no lag occurs during recording, then even if Variable Frame Rate mode is enabled, the result may still be recorded as Constant Frame Rate. This is because oCam is operating in an environment where it can accurately record all 60 frames per second. In other words, even in Variable Frame Rate mode, if the frame count remains consistent, the result will be the same as Constant Frame Rate. Therefore, if your system can stably maintain 60 FPS, the recorded video will be saved at a fixed 60 frames per second.
Q. I recorded a game in oCam at 60 FPS for 5 seconds, but exactly 30 frames per second were recorded (150 frames total). Is this Variable Frame Rate?
In this case, the recorded video is regarded as 30 FPS Constant Frame Rate. Even if oCam was set to 60 FPS, if only 30 frames per second were actually recorded consistently, the frame count is still constant, so it is classified as Constant Frame Rate. Variable Frame Rate applies only when the frame count changes during recording. Simply failing to reach the configured 60 FPS does not make it Variable Frame Rate. Therefore, in this case, a video file recorded consistently at 30 FPS is created.
Q. I recorded at 60 FPS in Variable Frame Rate mode, and the game was output at 60 FPS, so why does the recorded file show 59.xx FPS?
Even if the game is output at 60 FPS, the actual screen output may not occur at exact intervals of 16.66666666666667 ms (1000 ms ÷ 60). In most cases, the frame intervals are not perfectly uniform because of tiny differences measured in milliseconds. As a result, the recorded video may be displayed as 59.xx FPS. In addition, oCam calculates and displays FPS in 200-millisecond intervals, so even if it appears as 60 FPS on screen, it may actually be recorded as 59.xx FPS. To resolve this issue, change the setting in oCam to Constant Frame Rate mode before recording. Since Constant Frame Rate attempts to maintain the specified FPS, it can minimize these small differences.
Q. If my computer performance is low when recording in Constant Frame Rate mode, will it be recorded as Variable Frame Rate instead?
No. If you set it to Constant Frame Rate mode, it will still be recorded as Constant Frame Rate even if your computer performance is low. However, if system performance is insufficient, for example, when attempting to record at 120 FPS in Constant Frame Rate mode, the video file will still be created at 120 FPS, but the video quality may drop or severe lag may occur. This happens when the system is forced to maintain the specified frame rate and stuttering appears as a result. Therefore, on lower-performance computers, it is recommended to choose an appropriate frame rate or consider settings that reduce system load.
Programs
Another helpful tip
How to Fix Severe Lag When Recording Games in Nox App Player
If you experience severe lag when starting game recording with oCam, you can resolve the issue by changing the settings as described below. In particular, if you are using Nox App Player, follow these steps to reduce lag and achieve smoother recording.
First, launch Nox App Player. After the program starts, click the gear-shaped icon in the upper-right corner of the screen to open the Settings menu. This icon is generally used to access system settings.
When the Settings window opens, select the 'Advanced Settings' tab from the menu on the left. In the Advanced Settings screen, find the 'Graphics Mode' option and change it to 'Speed Mode (DirectX)'. This setting optimizes performance by using system resources more efficiently and is especially effective for reducing lag during game recording. After making the change, click the 'Save Settings' button to apply it.
After saving the settings, you must completely close and restart Nox App Player. Once it restarts, the changed graphics mode will be applied, which can reduce lag and provide smoother performance when recording games with oCam.
This method is useful for resolving performance issues that occur when using Nox App Player together with oCam. If the problem continues after changing the settings, it is recommended to check your system specifications or review other oCam settings, such as frame rate and resolution, for additional optimization.