The File Appears to Be Encrypted
Sometimes users contact us saying that a lock icon appears on a file or folder and that they are unable to open it. First, we will guide you through a few things to check and possible solutions.
First, regarding the SecretFolder program, this program does not provide a feature that adds a lock icon to file or folder icons. SecretFolder provides a folder-hiding function, but it does not encrypt files or folders or display a lock icon. Therefore, if a lock icon is being shown, it is highly likely that it is not related to the SecretFolder program.
If a lock icon appears on a file and access is restricted, it is important to look into other possible causes. One of the most common causes is BitLocker encryption, which is built into the Windows operating system. BitLocker is a security feature that encrypts files or drives, and it may be enabled according to IT management policies, especially in company or organizational environments. In this case, the file or drive showing the lock icon may be protected by BitLocker, and it may not be accessible without the correct recovery key or password.
To check whether the file is locked because of BitLocker, we recommend first checking whether BitLocker is enabled on the computer you are using. If it is a company-managed computer, the fastest solution is to contact your IT department or system administrator to check whether BitLocker is enabled and to get the recovery key if needed.
If it is a personal computer, please follow the steps below to check whether BitLocker is enabled:
- Check BitLocker settings: Type "Manage BitLocker" in the Windows search box and open the BitLocker settings screen. There, you can check whether the drive is encrypted.
- Check the recovery key: If BitLocker is enabled, you may need a recovery key. This key can usually be obtained from your Microsoft account, a USB drive, or your company IT department.
- Check administrator permissions: Sometimes a lock icon may appear because of file access permission issues. Right-click the file and check your account permissions under "Properties" โ "Security."
If the lock icon is caused by something other than BitLocker, you may also need to check the following:
- Third-party security software: Certain security software or encryption programs may have locked the file. Please check the list of installed software to see whether there is any program related to file encryption.
- File system errors: A problem with the drive's file system may have corrupted the file or restricted access. In this case, running the "chkdsk" command to check the disk may also help.
If you would like more detailed information or need additional guidance on BitLocker recovery, we recommend referring to the BitLocker documentation provided on the official Microsoft website. You can find detailed help at the link below:
Today's News/Tips
FAQ About Variable Frame Rate (VFR) and Constant Frame Rate (CFR)
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.