Windows 11 Update Fails at 99%? How to Fix Install Errors 0x800f0993 and 0x800f0989
Watch Out for Fake "Windows Security" Alerts, and Install the Urgent Chrome Update
Find and Save Your Windows BitLocker Recovery Key Before You Need It
Got a Blue Screen? How to Read the Stop Code and What to Try First (Windows 10 and 11)Using oCam at work or school? A license is required, and it removes all ads, including this window. See the paid version →
In some cases, you may need to modify the Windows Registry to fix an oCam setting or issue. Below is a detailed explanation of how to use the Registry Editor to add the required key values.
1. Press Windows key + R on your keyboard to open the Run dialog box.
2. Type `regedit` in the Run dialog box and click the 'OK' button to launch the Registry Editor.
3. When the Registry Editor opens, follow the instructions in the video below to complete the required settings:
4. As instructed in the video, add the following Registry key values:
- CommonFilesDir: `C:\Program Files\Common Files`
- ProgramFilesDir: `C:\Program Files`
5. After adding the Registry key values, close the Registry Editor and restart your computer to apply the changes.
Because editing the Registry directly affects system settings, it is important to back up the Registry before making changes or follow the instructions in the video exactly. The added key values help oCam reference the correct file paths and can be useful for resolving certain installation or launch issues. After completing the steps, run oCam and check whether the problem has been resolved.
When recording with oCam, you may sometimes encounter problems with sound recording. In particular, when a DAW (Digital Audio Workstation, for example FL Studio) program using Asio4all is running, it may take exclusive control of the system audio, making sound playback or recording unavailable in other programs. As a result, normal sound recording in oCam may become difficult. Below is a detailed explanation of how to solve this problem and record smoothly with oCam.
Asio4all is a driver used for low-latency audio processing and is mainly used in DAW programs. However, when Asio4all is enabled, it takes exclusive control of the system audio, so other programs such as oCam may not be able to capture system sound. To solve this problem, you need to change the audio output device in the DAW program to something other than Asio4all.
The following is how to change the settings:
1. Run the DAW program (for example, FL Studio).
2. In the case of FL Studio, click 'Options' in the top menu, then go to 'Audio Settings'.
3. In the 'Audio Settings' window, check the audio output device and change it from Asio4all to 'Primary Sound Driver' or 'DirectSound'.
4. After saving the settings, play audio in the DAW and then try recording with oCam. The system sound should then be recorded normally.
If you must use Asio4all because of latency issues with a MIDI keyboard, it is best to switch the settings flexibly depending on your working environment. For example:
- When producing music or doing MIDI work in the DAW, use Asio4all to maintain a low-latency environment.
- After finishing your work and when you want to record with oCam, change the playback device in the DAW audio settings to 'DirectSound' or 'Primary Sound Driver' to disable Asio4all.
- After changing the setting, restart the DAW, or reboot the computer if necessary, then confirm that the setting has been applied properly before starting recording with oCam.
Using this method, you can resolve the audio exclusivity issue caused by Asio4all and record system sound smoothly in oCam. If you are working in a DAW and recording at the same time, try switching the audio output device according to the situation to maintain the best environment.