Camera debugging method and device, computer equipment and storage medium

Abstract

The invention provides a camera debugging method and device, computer equipment and a storage medium, in the application, when a to-be-debugged camera is detected, the to-be-debugged camera is turned on, a preview effect of the to-be-debugged camera is obtained, and if the preview effect does not meet a preset condition, the to-be-debugged camera is debugged. If yes, the register parameters in the initialization configuration file and the corresponding preview effect parameters are modified, the modified initialization configuration file is pushed to the target directory to achieve debugging of the to-be-debugged camera, a driver file does not need to be newly built or modified for the to-be-debugged camera, repeated compiling of the driver file is avoided, and debugging efficiency is improved. And the debugging efficiency of the camera is greatly improved.

Description

Technical Field

[0001] The present application relates to the field of camera technology, and in particular to a camera debugging method, device, computer equipment and storage medium. Background Art

[0002] In some current platforms, during camera debugging, usually one camera corresponds to one driver. Camera manufacturers can provide some configuration parameters related to the sensor, such as register address, register parameters, resolution, etc., and create a new driver file for each camera, and write these configuration parameters of the camera into the driver file. Among them, the format of the driver file needs to be consistent with the driver used by the platform. During the debugging process, it is necessary to frequently compile the driver file and push the library for verification, which is cumbersome and time-consuming, increasing the difficulty of camera debugging. Summary of the invention

[0003] Based on this, it is necessary to provide a camera debugging method, device, computer equipment and storage medium to address the above technical problems, so as to solve the technical problem in the prior art that the camera debugging efficiency is low due to the need to frequently compile driver files.

[0004] In a first aspect, the present application provides a camera debugging method, which is applied to a computer device, wherein a camera initialization configuration file is configured in a target directory of the computer device, and the initialization configuration file includes register parameters of the camera and corresponding preview effect parameters, and the method includes:

[0005] When a camera to be debugged is detected, the camera to be debugged is opened to obtain a preview effect of the camera to be debugged;

[0006] If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged.

[0007] In some embodiments of the present application, before detecting a camera to be debugged, opening the camera to be debugged, and obtaining a preview effect of the camera to be debugged, the method further includes:

[0008] Configure general driver information based on the general driver parameters of the camera;

[0009] The camera to be debugged is detected based on the general driver information and the initialization configuration file.

[0010] In some embodiments of the present application, the detecting the camera to be debugged based on the general driver information and the initialization configuration file includes:

[0011] When the computer device is powered on, a user-defined process is run to read the parameters of the camera from the initialization configuration file;

[0012] If it is detected that the user-defined process does not pass in the parameters of the camera, determining whether the camera to be debugged is detected according to the general driver information;

[0013] Or, if it is detected that the user-defined process passes the parameters of the camera, the driving parameters corresponding to the parameters of the camera in the universal driving information are replaced with the parameters of the camera to obtain updated universal driving information, and it is determined whether the camera to be debugged is detected based on the updated universal driving information.

[0014] In some embodiments of the present application, the method further includes:

[0015] When no camera to be debugged is detected according to the general driver information, and no camera to be debugged is detected according to the updated general driver information, reading the register parameter of the camera from the initialization configuration file as the first target parameter through a custom process;

[0016] The initialization configuration file is modified based on the first target parameter through a system process, and the modified initialization configuration file is pushed to the target directory.

[0017] In some embodiments of the present application, the step of reading the register parameters of the camera from the initialization configuration file as the target parameters through a custom process includes:

[0018] By starting or restarting the user-defined process, the register parameters of the camera are read from the initialization configuration file as target parameters.

[0019] In some embodiments of the present application, before reading the register parameters of the camera from the initialization configuration file as the target parameters through the custom process, the method further includes:

[0020] Creating an executable script based on the initialization configuration file;

[0021] The executable script is added to the startup configuration file of the computer device to obtain the second user process.

[0022] In some embodiments of the present application, if the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to debug the camera to be debugged, including:

[0023] Reading the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through a custom process;

[0024] The initialization configuration file is updated based on the second target parameter through a system process, and the updated initialization configuration file is pushed to the target directory.

[0025] In a second aspect, the present application provides a camera debugging device, which is applied to a computer device, wherein a camera initialization configuration file is configured in a target directory of the computer device, wherein the initialization configuration file includes a register parameter of the camera and a corresponding preview effect parameter, and the camera debugging device includes:

[0026] An acquisition module is used to, when a camera to be debugged is detected, open the camera to be debugged and obtain a preview effect of the camera to be debugged;

[0027] The debugging module is used to modify the register parameters and corresponding preview effect parameters in the initialization configuration file if the preview effect does not meet the preset conditions, and push the modified initialization configuration file to the target directory to realize the debugging of the camera to be debugged.

[0028] In a third aspect, the present application further provides a computer device, the computer device comprising:

[0029] one or more processors;

[0030] A memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the camera debugging method.

[0031] In a fourth aspect, the present application also provides a computer-readable storage medium on which a computer program is stored, and the computer program is loaded by a processor to execute the steps in the camera debugging method.

[0032] In a fifth aspect, the present application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, are used to execute the steps of the camera debugging method described in any one of the first aspects above.

[0033] The above-mentioned camera debugging method, device, computer equipment and storage medium, when detecting a camera to be debugged, open the camera to be debugged and obtain a preview effect of the camera to be debugged. If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged. Since there is no need to create or modify the driver file for the camera to be debugged, repeated compilation of the driver file is avoided, which greatly improves the debugging efficiency of the camera. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0035] Figure 1 It is a flowchart of a camera debugging method in an embodiment of the present application;

[0036] Figure 2 is a flowchart of a camera debugging method in another embodiment of the present application;

[0037] Figure 3 is a flowchart of a camera debugging method in another embodiment of the present application;

[0038] Figure 4 is a flowchart of a camera debugging method in yet another embodiment of the present application;

[0039] Figure 5 It is a structural schematic diagram of a camera debugging device in an embodiment of the present application;

[0040] Figure 6 It is a schematic diagram of the structure of a computer device in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0042] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, "plurality" means two or more, unless otherwise clearly and specifically defined.

[0043] In the description of the present application, the word "for example" is used to mean "used as an example, illustration or explanation". Any embodiment described as "for example" in the present application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is given to enable any technician in the field to implement and use the present invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the present invention can be implemented without using these specific details. In other examples, well-known structures and processes will not be elaborated in detail to avoid obscuring the description of the present invention with unnecessary details. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in the present application.

[0044] In the related art, the driver of the camera sensor only has initialization parameters. If you need to light up this sensor, you need to copy a driver file of a sensor that has already been lit on the same platform, and then modify the parameters related to this sensor in this driver file, such as register parameters, register address, resolution, etc., and then compile the modified driver file, push the library for verification, and debug the camera.

[0045] However, in the above camera debugging method, the same platform and the same interface will debug many sensors of different camera models. Each sensor needs to be configured with a separate driver file and the driver file needs to be compiled and verified, which reduces the camera debugging progress and increases the difficulty of camera debugging.

[0046] In order to solve the above problems, an embodiment of the present application provides a camera debugging method. In this camera debugging method, a computer device can modify the initialization configuration file and push the modified initialization configuration file to the target directory. In this way, the camera can be debugged by updating the initialization configuration file, avoiding repeated compilation of driver files, and improving the debugging efficiency of the camera.

[0047] like Figure 1As shown, it is a flow chart of an embodiment of the camera debugging method in the embodiment of the present application, and the camera debugging method is applied to a computer device, and the target directory of the computer device is configured with an initialization configuration file of the camera, and the initialization configuration file includes the register parameters of the camera and the corresponding preview effect parameters. The camera debugging method may include the following steps 101-102, which are as follows:

[0048] 101. When a camera to be debugged is detected, the camera to be debugged is turned on to obtain a preview effect of the camera to be debugged.

[0049] Among them, the initialization configuration file is a pre-configured initialization file for integrating the register parameters of each camera and the camera preview effect parameters, such as an ini file or an xml file, and the initialization file supports loading by a custom process, that is, the relevant parameters of the camera in the initialization file support reading by a custom process and passing to the kernel after reading. The register parameters include but are not limited to one or more of the following parameters: power-on timing, resolution configuration, initialization register, open flow register, stop flow register, actual number of sensor lanes, x / y register address, linecount register address or frameline register address. The register parameter source of each camera can be provided by the sensor supplier of the camera, or obtained from the sensor specification book, or obtained from the sensor datasheet, or the register parameters of each source are integrated to form the register parameters of the camera, without limitation. The preview effect parameter is a parameter that characterizes the preview screen effect after the camera is turned on, for example, an exposure parameter, wherein the camera register parameter corresponds to the preview effect parameter one by one, and the preview effect parameter can be obtained by professionals through multiple tests on cameras with different register parameters.

[0050] The target directory is used to store the initialization configuration files, such as / vendor / etc / or

[0051] / data / vendor / camera, etc.

[0052] The camera to be debugged is a camera that needs to be debugged and is detected in the camera probe stage when the computer device is turned on. It can be a camera with different interfaces, such as a MIPI interface, a DVP (Digital Video Port) interface, etc.

[0053] As a possible implementation, after detecting the camera to be debugged, the computer device can determine the preview effect of the camera to be debugged by opening the application of the camera to be debugged and according to the real-time graphical interface of the camera application. For example, if there is no real-time graphical interface, it is determined that the preview effect is abnormal, that is, the camera preview fails to be opened. If there is a real-time graphical interface, it is determined that the preview effect is normal, that is, the camera preview is successfully opened. It can be understood that in this embodiment, the preview effect of the camera to be debugged is obtained so that the register parameters of the camera can be dynamically debugged based on the preview effect.

[0054] It is worth noting that the initialization configuration file in this embodiment supports the debugging of the camera after loading by a custom process. Compared with the kernel code driver file which needs to be compiled before the camera debugging can be realized, the initialization configuration file can be used to realize the camera debugging without compilation, which is conducive to improving the efficiency of camera debugging.

[0055] 102. If the preview effect does not meet the preset conditions, the computer device modifies the register parameters and the corresponding preview effect parameters in the initialization configuration file, and pushes the modified initialization configuration file to the target directory to debug the camera to be debugged.

[0056] Among them, the preset condition is a condition used to determine whether the preview effect meets the requirements, which can be pre-set or dynamically input into the computer device by the engineer through the adjustment interface, without limitation. For example, the preset condition is: the preview effect indicates that the camera preview screen is successfully opened. For another example, the preset condition is: the preview effect indicates that the quality of the preview screen meets the requirements under the premise that the camera preview screen is successfully opened.

[0057] As a possible implementation method, when the preview effect does not meet the preset conditions, it indicates that the camera to be debugged has not been successfully debugged, and the computer device can modify the initialization configuration file and push the modified initialization configuration file to the target directory to debug the camera to be debugged. In this embodiment, by modifying the initialization configuration file in the target directory and pushing the configuration file to the target directory, the debugging of the camera to be debugged can be achieved. Since there is no need to create or modify the driver file for the camera to be debugged, repeated compilation of the driver file is avoided, which greatly improves the debugging efficiency of the camera.

[0058] As a possible implementation, when the preview effect does not meet the preset conditions, the computer device can modify the register parameters and corresponding preview effect parameters of the camera in the initialization configuration file. For example, the register parameters of the camera include power-on timing, resolution, register address, register group, switch flow register, 2lane (2 data channels) or 4lane (4 data channels), and the preview effect parameter is an exposure parameter. The register parameters and corresponding preview effect parameters in the initialization configuration file modified by the computer device, that is, the modified power-on timing, resolution, register address, register group, switch flow register, 2lane or 4lane, exposure parameters, can be derived from the datasheet of the sensor of the camera to be debugged, or a mapping relationship table of preview results meeting the preset conditions and corresponding initialization configuration files can be constructed in advance by professionals. According to the preview results meeting the preset conditions in the mapping relationship table, the target modification parameters of the initialization configuration file are determined, the register parameters and corresponding preview effect parameters in the initialization configuration file are modified to the target modification parameters, and the modified initialization configuration file is obtained, and the modified initialization configuration file is pushed to the target directory. For example, the modified initialization configuration file can be pushed to the target directory through the adb command, thereby realizing the debugging of the camera to be debugged.

[0059] In the present embodiment, when a camera to be debugged is detected, the camera to be debugged is opened and a preview effect of the camera to be debugged is obtained. If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize debugging of the camera to be debugged. Since there is no need to create or modify the driver file for the camera to be debugged, repeated compilation of the driver file is avoided, thereby greatly improving the debugging efficiency of the camera.

[0060] In a specific embodiment, Figure 2 As shown, in step 102, if the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged, which may include the following steps 102A to 102B, which are as follows:

[0061] 102A, the computer device reads the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through a custom process.

[0062] The custom process is a user process created in the user space for reading the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file. The system process is a built-in service process of the computer device, which is used to open the camera to be debugged and obtain the preview effect of the camera to be debugged.

[0063] The second target parameter is the register parameter of the camera and the corresponding preview effect parameter read by the computer device from the initialization configuration file.

[0064] 102B, updating the initialization configuration file based on the second target parameter through a system process, and pushing the updated initialization configuration file to the target directory.

[0065] When the preview effect of the camera to be debugged does not meet the preset conditions, the computer device can update the initialization configuration file of the camera to be debugged to debug the preview effect of the camera to be debugged.

[0066] It should be noted that the computer device obtains the preview effect after debugging. If the preview effect after debugging does not meet the preset conditions, the custom process and the system process are killed; and the process returns to the step of reading the camera's register parameters and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through the custom process. After updating the initialization configuration file of the camera to be debugged, the computer device can obtain the preview effect of the camera to be debugged after debugging. In some cases, if the preview effect after debugging meets the preset conditions, the computer device completes the debugging of the camera to be debugged.

[0067] In other cases, if the preview effect after debugging does not meet the preset conditions, the computer device kills the custom process and the system process, returns to step 102A, continues to execute steps 102A-102B, automatically loads the custom process and the system process, updates the initialization configuration file based on the second target parameter, pushes the updated initialization configuration file to the target directory, obtains the preview effect after debugging, and achieves debugging of the camera to be debugged until the preview effect after debugging meets the preset conditions. In this embodiment, when the preview effect after debugging does not meet the preset conditions, there is no need to restart the computer device, and the user-defined process and the system process are automatically reloaded until the preview effect after debugging meets the preset conditions, ensuring that the preview effect of the camera to be debugged meets the conditions, thereby improving the debugging efficiency of the camera.

[0068] In a specific embodiment, Figure 3 As shown, in the case where the camera to be debugged is detected, before the camera to be debugged is turned on and a preview effect of the camera to be debugged is obtained, the following steps 103 to 105 may also be included, which are specifically as follows:

[0069] 103. Configure general driver information based on general driver parameters of the camera.

[0070] Among them, the common driver parameters refer to the configuration parameters shared by the camera's sensor, excluding differentiated driver parameters, such as registers, resolution information, etc.

[0071] 104. When the computer device is powered on, a first user process for reading camera parameters is run.

[0072] The first user process is a computer device startup process created in the user space, and is used to read the camera parameters when the computer device is started. The running results of the first user process include two situations: the camera parameters are read and the camera parameters are not read.

[0073] 105 . Detect the camera to be debugged according to the running result of the first user process and the general driver information.

[0074] As a possible implementation, the camera to be debugged is probed according to the running result of the first user process combined with the general driver information. It can be understood that in this embodiment, the camera to be debugged is probed according to the running result of the first user process and the general driver information, and there is no need to restart the computer device when the camera to be debugged is not detected, which reduces the detection time of the camera and improves the camera detection efficiency.

[0075] In a specific implementation, the step 105 of detecting the camera to be debugged according to the running result of the first user process and the general driver information may include the following steps 105A-105B, which are as follows:

[0076] 105A, if the running result of the first user process is that the first user process does not pass in the camera parameters, determine whether the camera to be debugged is detected according to the general driver information.

[0077] As a possible implementation manner, if the running result of the first user process is that the first user process does not pass in the camera parameters, indicating that the camera parameters are not read, it is determined based on the general driver information whether the camera to be debugged is detected.

[0078] 105B, if the running result of the first user process is that the first user process passes in the camera parameters, the driver parameters corresponding to the camera parameters in the general driver information are replaced with the camera parameters to obtain updated general driver information. The computer device can determine whether the camera to be debugged is detected according to the updated general driver information.

[0079] It can be understood that in this embodiment, the camera to be debugged is detected based on the running result of the first user process and the general driver information, thereby realizing the detection of the camera to be debugged when the computer device is powered on.

[0080] In a specific embodiment, Figure 4 As shown, the method may further include the following steps 106 to 108, which are specifically as follows:

[0081] 106. When the camera to be debugged is not detected according to the general driver information and the camera to be debugged is not detected according to the updated general driver information, the computer device reads the register parameters of the camera from the initialization configuration file as the first target parameters through the second user process.

[0082] The second user process is a user process created in the user space and used to read register parameters of the camera from the initialization configuration file.

[0083] The first target parameter is a register parameter of the camera read by the computer device from the initialization configuration file, and the register parameter of the camera includes a power-on timing and an I2C address.

[0084] 107 . The computer device modifies the initialization configuration file based on the first target parameter through a system process, and pushes the modified initialization configuration file to the target directory.

[0085] As a possible implementation method, the computer device reads the register parameters of the camera from the initialization configuration file as the first target parameters through the second user process, and then, through the system process, modifies the register parameters in the initialization configuration file according to the first target parameters, and pushes the modified initialization configuration file to the target directory through the adb command to obtain the detection results.

[0086] It should be noted that the computer device obtains the detection result. If the detection result is that the camera to be debugged is not detected, the second user process and the system process are killed, and the process returns to the step of reading the register parameter of the camera from the initialization configuration file as the first target parameter through the second user process. After the initialization configuration file of the camera to be debugged is modified, the computer device can obtain the detection result of the camera to be debugged after detection. In some cases, if the detection result is that the camera to be debugged is detected, the computer device completes the detection of the camera to be debugged.

[0087] In other cases, if the detection result is that the camera to be debugged is not detected, the computer device kills the custom process and the system process, returns to step 106, continues to execute steps 106-107, automatically loads the second user process and the system process, modifies the initialization configuration file based on the first target parameter, pushes the modified initialization configuration file to the target directory, obtains the detection result, and detects the camera to be debugged until the detection result is that the camera to be debugged is detected. In this embodiment, if the camera to be debugged is not detected, there is no need to restart the computer device, and the second user process and the system process are automatically reloaded until the camera to be debugged is detected, thereby ensuring the successful detection of the camera to be debugged and improving the efficiency of detecting the camera to be debugged.

[0088] In a specific implementation, the step 106 of reading the register parameter of the camera from the initialization configuration file as the first target parameter by the second user process may include the following step 106A, which is as follows:

[0089] 106A, start or restart the second user process, and read the register parameters of the camera from the initialization configuration file as the first target parameters.

[0090] Specifically, the second user process can be started or restarted to read the register parameters of the camera from the initialization configuration file as the first target parameters, that is, when the computer device is turned on, the register parameters of the camera are first read from the initialization configuration file by starting the second user process as the first target parameters.

[0091] In one example, starting or restarting the second user process reads the register parameters of the camera from the initialization configuration file as the first target parameter. The process is as follows: after opening the initialization configuration file in the target directory, open the initialization configuration file, read the content of the initialization configuration file through the file stream, and read the content corresponding to the register parameter, such as power corresponding to the power-on timing, init_register corresponding to the initialization register, resolution_register corresponding to the resolution register, stream_on / stream_off corresponding to the stream on and off registers, etc.

[0092] In a specific implementation, before reading the register parameters of the camera from the initialization configuration file as the first target parameters by the second user process in step 106A, the following steps 106B to 106C may also be included, as follows:

[0093] 106B, create an executable script based on the initialization configuration file.

[0094] 106C, adding the executable script to the startup configuration file of the computer device to obtain the second user process.

[0095] Among them, the startup configuration file can be an init.rc file, which is used to initialize its system environment when the computer device starts, including: mounting file systems such as / system, / data, etc., creating directories required for system operation, such as / dev, / proc, / sys, etc., setting permissions for files and directories to ensure safe operation of the system, and setting system properties such as sys.boot_completed.

[0096] Specifically, an executable script is created according to the initialization configuration file, and the executable script is added to the startup configuration file of the computer device, thereby generating an automatic startup process, that is, obtaining a second user process, so that the second user process can be automatically started or restarted when the computer device is turned on, ensuring that the parameters of the camera are read from the initialization configuration file.

[0097] It is worth noting that the creation method of the custom user process in this embodiment is the same as the creation method of the second user process.

[0098] In order to better implement the camera debugging method in the embodiment of the present application, based on the camera debugging method, the embodiment of the present application also provides a camera debugging device, which is applied to a computer device, wherein the target directory of the computer device is configured with an initialization configuration file of the camera, and the initialization configuration file includes register parameters of the camera and corresponding preview effect parameters, such as Figure 5 As shown, the camera debugging device 200 includes:

[0099] An acquisition module is used to, when a camera to be debugged is detected, open the camera to be debugged and obtain a preview effect of the camera to be debugged;

[0100] The debugging module is used to modify the initialization configuration file if the preview effect does not meet the preset conditions, and push the modified initialization configuration file to the target directory to realize the debugging of the camera to be debugged.

[0101] In some embodiments of the present application, the camera debugging device 200 further includes:

[0102] A configuration module, used to configure general driver information based on general driver parameters of the camera;

[0103] An operation module, used for running a first user process for reading camera parameters when the computer device is powered on;

[0104] A detection module is used to detect the camera to be debugged according to the running result of the first user process and the general driver information.

[0105] In some embodiments of the present application, the detection module is specifically used to:

[0106] If the running result of the first user process is that the first user process does not pass in the camera parameters, determining whether a camera to be debugged is detected according to the general driver information;

[0107] If the running result of the first user process is that the first user process passes in the camera parameters, the driving parameters corresponding to the camera parameters in the general driving information are replaced with the camera parameters to obtain updated general driving information;

[0108] It is determined whether a camera to be debugged is detected according to the updated universal driver information.

[0109] In some embodiments of the present application, the camera debugging device 200 further includes:

[0110] A reading module, configured to read the register parameters of the camera from the initialization configuration file as the first target parameter through a custom process when the camera to be debugged is not detected according to the general driver information and the camera to be debugged is not detected according to the updated general driver information;

[0111] a modification module, configured to modify the initialization configuration file based on the first target parameter through a system process, push the modified initialization configuration file to the target directory, obtain a detection result, and if the detection result is that the camera to be debugged is not detected, kill the second user process and the system process;

[0112] The loop detection module is used to return to the step of reading the register parameters of the camera from the initialization configuration file as the first target parameter through the second user process until the camera to be debugged is detected.

[0113] In some embodiments of the present application, the reading module is specifically used for:

[0114] The second user process is started or restarted, and the register parameters of the camera are read from the initialization configuration file as the first target parameters.

[0115] In some embodiments of the present application, the camera debugging device 200 further includes:

[0116] A creation module, used to create an executable script based on the initialization configuration file;

[0117] A generation module is used to add the executable script to the startup configuration file of the computer device to obtain the second user process.

[0118] In some embodiments of the present application, the debugging module is specifically used to:

[0119] Reading the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through a custom process;

[0120] updating the initialization configuration file based on the second target parameter through the system process, pushing the updated initialization configuration file to the target directory, obtaining the preview effect after debugging, and killing the custom process and the system process if the preview effect after debugging does not meet the preset condition;

[0121] Return to the step of reading the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through the custom process.

[0122] The embodiment of the present application further provides a computer device, which may be a terminal or a server, and any camera debugging device provided in the embodiment of the present application is integrated in the computer device, and the computer device includes:

[0123] one or more processors;

[0124] Memory; and

[0125] One or more applications, wherein the one or more applications are stored in the memory and are configured so that the processor executes the steps of the camera debugging method described in any of the above camera debugging method embodiments.

[0126] The present application also provides a computer device that integrates any camera debugging device provided in the present application. Figure 6 As shown, it shows a schematic diagram of the structure of the computer device involved in the embodiment of the present application, specifically:

[0127] The computer device may include one or more processing core processors 301, one or more computer readable storage media memories 302, a power supply 303, an input unit 304 and other components. Those skilled in the art will appreciate that Figure 6 The computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0128] The processor 301 is the control center of the computer device. It uses various interfaces and lines to connect various parts of the entire computer device. By running or executing software programs and / or modules stored in the memory 302 and calling data stored in the memory 302, it executes various functions of the computer device and processes data, thereby monitoring the computer device as a whole. Optionally, the processor 301 may include one or more processing cores; preferably, the processor 301 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 301.

[0129] The memory 302 can be used to store software programs and modules. The processor 301 executes various functional applications and data processing by running the software programs and modules stored in the memory 302. The memory 302 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 302 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 302 may also include a memory controller to provide the processor 301 with access to the memory 302.

[0130] The computer device also includes a power supply 303 for supplying power to various components. Preferably, the power supply 303 can be logically connected to the processor 301 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 303 can also include any combination of one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, etc.

[0131] The computer device may further include an input unit 304, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0132] Although not shown, the computer device may further include a display unit, etc., which will not be described in detail herein. Specifically, in this embodiment, the processor 301 in the computer device will load the executable files corresponding to the processes of one or more application programs into the memory 302 according to the following instructions, and the processor 301 will run the application programs stored in the memory 302, thereby realizing various functions, as follows:

[0133] When a camera to be debugged is detected, the camera to be debugged is opened to obtain a preview effect of the camera to be debugged;

[0134] If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged.

[0135] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0136] To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any camera debugging method provided in the embodiment of the present application. For example, the computer program can be loaded by a processor to execute the following steps:

[0137] When a camera to be debugged is detected, the camera to be debugged is opened to obtain a preview effect of the camera to be debugged;

[0138] If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged.

[0139] The embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the communication module reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the communication module executes to implement the steps in any camera debugging method provided in the embodiments of the application.

[0140] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the detailed description of other embodiments above, and will not be repeated here.

[0141] In specific implementation, the above units or structures can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units or structures can refer to the previous method embodiments, which will not be repeated here.

[0142] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0143] The above is a detailed introduction to a camera debugging method, device, computer equipment and storage medium provided in the embodiments of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A camera debugging method, characterized in that: Applied to a computer device, wherein a camera initialization configuration file is configured in a target directory of the computer device, wherein the initialization configuration file includes a camera register parameter and a corresponding preview effect parameter, and the method includes: When a camera to be debugged is detected, the camera to be debugged is opened to obtain a preview effect of the camera to be debugged; If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged.

2. The camera debugging method according to claim 1, characterized in that: In the case of detecting a camera to be debugged, before opening the camera to be debugged and obtaining a preview effect of the camera to be debugged, the method further includes: Configure general driver information based on the general driver parameters of the camera; When the computer device is powered on, a first user process for reading camera parameters is run; The camera to be debugged is detected according to the running result of the first user process and the general driver information.

3. The camera debugging method according to claim 2, characterized in that: The detecting the camera to be debugged according to the running result of the first user process and the general driver information includes: If the running result of the first user process is that the first user process does not pass in the camera parameters, determining whether a camera to be debugged is detected according to the general driver information; Or, if the running result of the first user process is that the first user process passes in the camera parameters, the driving parameters corresponding to the camera parameters in the universal driving information are replaced with the camera parameters to obtain updated universal driving information, and it is determined whether the camera to be debugged is detected based on the updated universal driving information.

4. The camera debugging method according to claim 3, characterized in that: Also includes: When no camera to be debugged is detected according to the general driver information, and no camera to be debugged is detected according to the updated general driver information, reading register parameters of the camera from the initialization configuration file as first target parameters through a second user process; The initialization configuration file is modified based on the first target parameter through a system process, and the modified initialization configuration file is pushed to the target directory.

5. The camera debugging method according to claim 4, characterized in that: The step of reading the register parameter of the camera from the initialization configuration file as the first target parameter through the second user process includes: The second user process is started or restarted, and the register parameters of the camera are read from the initialization configuration file as the first target parameters.

6. The camera debugging method according to claim 4 or 5, characterized in that: Also includes: Creating an executable script based on the initialization configuration file; The executable script is added to the startup configuration file of the computer device to obtain the second user process.

7. The camera debugging method according to claim 6, characterized in that: If the preview effect does not meet the preset conditions, the register parameters and the corresponding preview effect parameters in the initialization configuration file are modified, and the modified initialization configuration file is pushed to the target directory to realize the debugging of the camera to be debugged, including: Reading the register parameters of the camera and the corresponding preview effect parameters from the initialization configuration file as the second target parameters through a custom process; The initialization configuration file is updated based on the second target parameter through a system process, and the updated initialization configuration file is pushed to the target directory.

8. A camera debugging device, characterized in that: Applied to a computer device, wherein a camera initialization configuration file is configured in a target directory of the computer device, wherein the initialization configuration file includes register parameters of the camera and corresponding preview effect parameters, and the camera debugging device includes: An acquisition module is used to, when a camera to be debugged is detected, open the camera to be debugged and obtain a preview effect of the camera to be debugged; The debugging module is used to modify the register parameters and corresponding preview effect parameters in the initialization configuration file if the preview effect does not meet the preset conditions, and push the modified initialization configuration file to the target directory to realize the debugging of the camera to be debugged.

9. A computer device, characterized in that: The computer device comprises: one or more processors; A memory; and one or more applications, wherein one or more of the applications are stored in the memory and configured to be executed by the processor to implement the camera debugging method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the camera debugging method according to any one of claims 1 to 7.

Images