What are the supported video codecs and container formats?
What are the supported video codecs and container formats?
You can check supported codecs immediately by clicking the Codec button in the main oCam window.
The default video codec is Open H.264 + AAC (.MP4).
In addition, MPEG-1, MPEG-2, MPEG-4, XVID, OpenDivX, Microsoft MPEG-4 Part 2, and Microsoft MPEG-4 Part 3 are also supported.
All of these codecs are saved in MP4 or AVI container formats.
oCam records using optimized codecs at installation time, and when these codecs are used, the recorded files can be played on almost all media players without installing additional codecs, unlike many other screen recording programs.
Usually, you may need to install codecs to play a recorded video, but with these codecs, most are supported by default.
This means that you can play oCam-recorded video files directly in Windows Media Player immediately after installing Windows without installing any additional software.
So there is no extra hassle of having to install extra codecs.
Also, MPEG-4, XVID, and OpenDivX are internally encoded with the MPEG-4 codec in oCam, with only the FourCC value changed for XVID and OpenDivX.
Additionally, supported container formats include FLV.
FLV stands for Flash Video and supports live streaming, so you can upload FLV files directly to places like a Zboard forum and preview them immediately on the web.
You can also use an FLV player. FLV is encoded with the MPEG-4 codec in oCam.
For Appleโs QuickTime format, MOV is a QuickTime-only format and uses the MPEG-4 codec.
Also, MPEG-2 Transport Stream has the .TS extension, and MPEG-PS has the .VOB extension; both use MPEG-2 as the codec.
If you choose GIF animation for creating animations, you can make a moving image.
Finally, all audio codecs used during video recording are saved as MP3.
Additionally, external codecs are supported; please refer to a separate post for details on external codecs.
Today's News/Tips
BIOS and CMOS Error Messages and How to Fix Them
โถ BIOS ROM Checksum error
This error appears when there is a problem with the ROM that stores system information.
It occurs when there is an issue while reading the information stored in CMOS. In this case, enter CMOS SETUP and check whether each setting is configured correctly for the current system state.
After completing the settings, select 'SAVE AND EXIT SETUP' to save the changes.
If the system is old, the ROM itself that stores the BIOS information may be damaged. In that case, it is recommended to have it inspected at a motherboard repair shop or service center.
โถ Press [F1] to continue
This message usually appears when the keyboard or mouse is not connected properly.
Please check whether both devices are connected securely to their connectors.
It is also a good idea to check whether the hard disk information is set correctly in CMOS SETUP.
โถ CMOS memory size mismatch
This error occurs when the system cannot properly recognize the memory (RAM).
When new RAM is added, CMOS usually detects it automatically, but in some cases the correct memory size is reflected only after running CMOS SETUP.
Enter CMOS SETUP, check the settings, and then reboot the system.
โถ NO ROM BASIC
This message appears when an error occurs during booting.
It usually occurs when the system cannot boot from drive A. In this case, you need to insert a bootable floppy disk into drive A or change the boot setting to boot from the hard disk drive.
Similar error messages include 'Diskette Boot Failure' and 'Invalid Boot Diskette'.
โถ CMOS display type mismatch
This error occurs when there is a problem with the graphics-related settings in CMOS.
It happens when the graphics type in the 'Video...' item in CMOS SETUP is not set to EGA/VGA.
Since this is the default setting used by most graphics cards, please make sure to check it.
โถ Cache Memory Bad..
This indicates a problem with the cache memory installed on the motherboard.
Cache memory is used to improve system speed, and on some motherboards, this error may appear if the cache memory fails.
In this case, you can replace the cache memory or try setting the cache memory usage option in CMOS SETUP to 'Disable'.
The same symptom may also appear when cache-related settings such as 'Cache Write' are configured incorrectly, so please check those settings as well.