[FAQ]Cause: Failed to avio_open (error=-13)  

[FAQ]Cause: Failed to avio_open (error=-13)

 

This error can occur as a false alarm, if Avast software is running. When the error appears, press Allow App, and the error disappears and oCam will continue working any problem.

 

If the pop-up window asking wheter to allow app does not appear

Click the + ALLOW APP button in Menu -> Settings -> Blocked and Allowed Apps and select oCam to add it.

If oCam is added to the list of allowed apps, you will be able to record without any problem.

 

or, you can turn off Ransomware Shield off instead as follows.

Either way should be fine.



Additional tips

[HOWTO]Setting up oCam - Record - General tab

Click Tools-Options in the oCam menu to display the following settings window. Learn about the Recording-General tab.

 
Include the cursor

- It is checked by default. If checked, the mouse cursor of recorded video is included. If not checked, the mouse cursor of recorded video is not included.

 

 


Hide drag cursor in recording area

-By default, the check is cleared. If checked, the drag cursor in the middle of the recording area disappears.


Frames Per Second (FPS)
- It is set to 30 by default and can be up to 120 FPS. 30 FPS is suitable for recording general screens. It is recommended to record 60 FPS or more for racing games or games that change screens rapidly during game recording.


Among the built-in codecs, MPEG-2 and MPEG-1 codecs are fixed at 30 FPS without being affected by the codec setting.

Keyframe interval
- By default, it is set to 5. If the keyframe interval is 5, keyframes are generated every 5 seconds, if 1, every 1 second, if 2, every 2 seconds, if n, then every second.

Decoder Resolution Compatibility
- Some video players have a problem with blurry playback of video files that are not set to a specific resolution size. (For example, bear player)

By default, the width is set to a multiple of 8, and the vertical is set to a multiple of 4. If the horizontal size of the recording area specified by the user does not fit to the multiple of 8, it is forced to a multiple of 8. The vertical size of the recording area does not fit to the multiple of 4. If not, the vertical size is applied in multiples of four.

For example, if the decoder resolution is set to "multiple of 8 and vertical of 4" and the recording area is 427x241, the horizontal size is 427, but since it is not divided by 8, the horizontal resolution is corrected to divide by 8 Is 424, and the vertical size is not divided by 4, so it is applied to 240 so that the recording area is finally set to 424x240.


Back to top