What to Do If the "Cause: failed to avio_open(error=-13)" Error Occurs During Recording

Using oCam at work or school? A license is required, and it removes all ads, including this window. See the paid version →

This error may occur because AhnLab V3 or Avast falsely detects oCam as suspicious. Below is a detailed explanation of how to resolve the issue for each antivirus program.


For AhnLab V3, if oCam is being falsely detected, you can resolve the issue by adding the `oCam.exe` file in the oCam installation folder to the scan exclusion list.  

1. Open the AhnLab V3 program.  

2. Go to the Settings menu and find the 'Scan Exclusions' or 'Exclusion Settings' option.  

3. In the 'File/Folder Exclusions' section, click the 'Add' button.  

4. Go to the folder where oCam is installed, for example `C:\Program Files\oCam`, and select the `oCam.exe` file.  

5. Add it to the exclusion list and save the settings.  

6. Run oCam again and check whether recording works normally.


* There may also be a conflict with the anti-ransomware feature.

For example, if drive E is set as a ransomware-protected drive and oCam's save folder is also set to drive E, an error may occur during recording. This happens because the anti-ransomware feature restricts file writing on that drive, preventing oCam from saving the video file.

In this case, keep drive E as a ransomware-protected drive and set oCam's recording save folder to drive C or D instead.

Because drive E is configured as a ransomware-protected drive, file creation and modification are restricted for security purposes, so programs such as oCam are blocked from saving files there. Therefore, the simplest solution is to move the save path to drive C or another unrestricted location.

If you want to continue using drive E, you may also consider temporarily disabling the anti-ransomware setting or adding the oCam executable file (`oCam.exe`) as an exception in the security policy for that drive. 



 

For Avast, if oCam is falsely detected, a pop-up message like the one below may appear. In that case:  

1. In the pop-up, click the 'Allow App' button to register oCam as a trusted program.  

2. This will remove the error and allow oCam to work normally.


If the pop-up does not appear, you can adjust the allow settings manually:  

1. On the Avast main screen, click 'Menu' and then select 'Settings'.  

2. Go to the 'Blocked & Allowed Apps' section.  

3. Click the '+ Allow App' button and add the oCam executable file (`oCam.exe`).  

4. Once oCam has been added to the allowed apps list, save the setting and run oCam again. Recording should then work without any issues.


 


As an alternative, you can also disable part of the protection feature:  

1. Open the 'Protection' menu on the Avast main screen.  

2. Find the 'Ransomware Shield' option and turn it off.  

3. Disabling Ransomware Shield may resolve the error related to oCam.



You can choose and apply whichever method is more convenient. If the problem continues even after changing the antivirus settings, it may also help to contact AhnLab or Avast customer support.

Another helpful tip

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.