Sound effect parameter adjustment method, electronic equipment and readable storage medium

Abstract

The invention discloses a sound effect parameter adjustment method, electronic equipment and a readable storage medium, and relates to the technical field of sound effect control, the method comprises the steps that prototype design information for a target sound effect algorithm is acquired, the prototype design information at least comprises parameter definition information, and the parameter definition information is used for defining adjustable parameters of the target sound effect algorithm; generating a prototype definition file based on the prototype design information; and in response to a parameter adjustment request for the target sound effect algorithm, analyzing the prototype definition file to obtain parameter definition information, and generating a corresponding sound effect parameter adjustment interface based on the parameter definition information, so that a user performs parameter adjustment on the sound effect parameter adjustment interface. According to the method, the development and deployment efficiency of the sound effect parameter adjustment function is improved, and quick response and flexible adaptation of the parameter adjustment process are realized.

Description

Technical Field

[0001] This application relates to the field of sound effect control technology, and in particular to a sound effect parameter adjustment method, electronic device, and readable storage medium. Background Technology

[0002] Audio processing technology is crucial in modern smart audio devices, typically requiring various audio algorithms to enhance and adapt sound effects. These algorithms generally run on embedded platforms on the device side, and parameter adjustments and effect demonstrations are performed through accompanying client applications. The two interact via communication methods such as Bluetooth, Wi-Fi (Wireless Fidelity), or USB (Universal Serial Bus).

[0003] In existing methods of audio effect parameter tuning, whenever an algorithm engineer develops or updates an audio effect algorithm, application developers need to manually write the corresponding debugging interface and interaction logic based on the algorithm's parameters, and solidify the parameter format into the application layer protocol. This process not only involves adapting the interface controls one by one, but also requires ensuring consistency with the parameter receiving and processing logic on the device side, resulting in extended development cycles and a significant increase in multi-terminal collaboration costs.

[0004] Therefore, overcoming the problem of low efficiency in repetitive development and debugging across multiple platforms caused by the reliance on manual adaptation in the audio effect parameter tuning process has become an urgent technical challenge. Summary of the Invention

[0005] The main purpose of this application is to provide a method for audio effect parameter tuning, an electronic device, and a readable storage medium, which aims to solve the technical problem that the traditional audio effect parameter tuning process relies on manual adaptation, resulting in low efficiency of repeated development and debugging across multiple terminals.

[0006] To achieve the above objectives, this application provides a method for adjusting sound effect parameters, the method comprising the following steps: Obtain prototype design information for the target sound effect algorithm, wherein the prototype design information includes at least parameter definition information, and the parameter definition information is used to define the adjustable parameters of the target sound effect algorithm; Generate a prototype definition file based on the prototype design information; In response to a parameter tuning request for the target sound effect algorithm, the prototype definition file is parsed to obtain the parameter definition information, and a corresponding sound effect parameter adjustment interface is generated based on the parameter definition information, so that the user can adjust the parameters in the sound effect parameter adjustment interface.

[0007] In one possible implementation, after the step of generating a prototype definition file based on the prototype design information, the method further includes: Based on the prototype definition file, a corresponding interactive design control is generated in the link design platform, wherein the link design platform is a graphical design platform for configuring the sound effect processing link; After the interactive design control is deployed to the link design area in the link design platform, a parameter tuning request for the target sound effect algorithm is triggered in response to the selection operation of the interactive design control.

[0008] In one possible implementation, after the step of generating the corresponding sound effect parameter adjustment interface, the method further includes: In response to a request to run a sound effect algorithm topology link in the link design region, the corresponding sound effect algorithm is run sequentially according to the definition of the topology link; When the target sound effect algorithm associated with the prototype definition file is run, a corresponding parameter adjustment command is generated based on the target parameter value set by the user on the sound effect parameter adjustment interface; wherein, the parameter sequence of the parameter adjustment command is consistent with the parameter order defined in the prototype definition file; The parameter tuning command is sent to the target audio device so that the target audio device calls the target sound effect algorithm according to the parameter tuning command and applies the target parameter value to perform audio processing, thereby completing the operation of the target sound effect algorithm.

[0009] In one possible implementation, prior to the step of generating the corresponding parameter tuning instructions, the method further includes: The user sets a target parameter value on the sound effect parameter adjustment interface for compliance verification, wherein the compliance verification includes verifying whether the target parameter value conforms to the constraint rules defined for the corresponding adjustable parameter in the prototype definition file; If the verification passes, then the step of generating the corresponding parameter adjustment command based on the target parameter value set by the user on the sound effect parameter adjustment interface is executed; If the verification fails, a verification error message is generated and the generation or sending of the parameter tuning command is prevented.

[0010] In one possible implementation, the step of generating a prototype definition file based on the prototype design information includes: The prototype design information is encapsulated into structured text that conforms to a preset syntax specification to obtain a prototype definition file; The structured text is in XML format.

[0011] In one possible implementation, the step of parsing the prototype definition file and generating the corresponding sound effect parameter adjustment interface includes: The prototype definition file is parsed from XML format into structured data in JSON format, and configuration information is obtained based on the structured data; Based on the configuration information, a corresponding sound effect parameter adjustment interface is generated.

[0012] In one possible implementation, after the step of obtaining prototype design information for the target sound effect algorithm, the method further includes: Verify whether the adjustable parameters in the target sound effect algorithm are consistent with the adjustable parameters contained in the prototype design information; If the verification is successful, then proceed with the step of generating a prototype definition file based on the prototype design information; If the verification fails, a message indicating that the adjustable parameters are not fully configured will be output.

[0013] In one possible implementation, the prototype design information further includes module definition information, port definition information, and parameter mapping display information; The module definition information is used to uniquely identify and classify the target sound effect algorithm; The port definition information is used to define the input and output interfaces of the audio data and control signals of the target sound effect algorithm; The parameter mapping display information is used to define aliases for specified parameter values ​​displayed on the sound effect parameter adjustment interface.

[0014] In addition, to achieve the above objectives, this application also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the audio parameter tuning method as described above.

[0015] In addition, to achieve the above objectives, this application also provides a readable storage medium, which is a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the steps of the audio parameter tuning method described above.

[0016] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the sound effect parameter tuning method described above.

[0017] One or more technical solutions proposed in this application have at least the following technical effects: This application improves upon the inefficiency of repetitive multi-platform development and debugging caused by manual adaptation by introducing an automatic generation and parsing of prototype definition files based on prototype design information. Specifically, prototype design information containing parameter definitions is first obtained, and a prototype definition file is generated accordingly. This file essentially constitutes a structured description of algorithm parameters, replacing the manually written and fixed application layer protocol in traditional development. When a parameter tuning request is received, the parameter definition information can be automatically obtained by parsing the prototype definition file, and the corresponding sound effect parameter adjustment interface can be dynamically generated accordingly. This eliminates the need for application developers to manually write interfaces and adapt interaction logic for each new algorithm or algorithm update. This automated process ensures that the generation of both algorithm parameter definitions and user parameter tuning interfaces is based on the same standardized prototype definition file, achieving consistency in parameter format and logic between the device-side algorithm and the application-side parameter tuning interface, and avoiding protocol inconsistencies or adaptation errors that may be caused by multiple manual interventions. In this way, the audio effect parameter tuning process is transformed into an automated, standardized, data-driven process, no longer relying on cumbersome manual adaptation. This significantly shortens the cycle from development to debuggable deployment of audio effect algorithms, effectively reduces the collaboration complexity and communication costs between algorithm engineers and application developers, improves the development and deployment efficiency of audio effect parameter tuning functions, and ultimately achieves rapid response and flexible adaptation of the parameter tuning process. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating the first embodiment of the audio effect parameter tuning method of this application; Figure 2 This is a schematic diagram of the audio effect algorithm topology link involved in one embodiment of the audio effect parameter tuning method of this application; Figure 3 This is a schematic diagram illustrating the audio effect parameter tuning interface generation process in one embodiment of the audio effect parameter tuning method of this application. Figure 4 This is a schematic diagram of the audio effect parameter tuning process involved in one embodiment of the audio effect parameter tuning method of this application; Figure 5 This is a schematic diagram of the hardware operating environment of the audio effect parameter adjustment method device in the embodiments of this application.

[0021] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0022] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] With the development of AI (Artificial Intelligence), artificial intelligence is becoming increasingly sophisticated, and intelligentization is an inevitable trend, such as intelligent cockpit audio.

[0024] For audio, audio algorithm processing is inevitably involved. This processing typically runs on the device, and a corresponding client application controls and demonstrates sound effects via a communication medium. However, with the growth of audio algorithm modules, the workload for new requirements is increasing daily. Algorithm engineers first develop the algorithm prototype, and subsequently, not only do application engineers need to develop the corresponding UI (User Interface) support for the algorithm, but device embedded engineers also need to develop systems compatible with the algorithm.

[0025] For the reasons mentioned above, in terms of iterative development of audio algorithms, how to quickly iterate and support new modules at the application and software levels will greatly improve development efficiency, reduce the workload of developing new requirements, and make the software more template-based and intelligent to meet the needs of intelligent audio development. This has become an urgent technical problem to be solved.

[0026] Based on this, the main solution of this application is: to obtain prototype design information for the target sound effect algorithm, wherein the prototype design information includes at least parameter definition information, which is used to define the adjustable parameters of the target sound effect algorithm; to generate a prototype definition file based on the prototype design information; and in response to a parameter tuning request for the target sound effect algorithm, to parse the prototype definition file to obtain the parameter definition information, and to generate a corresponding sound effect parameter adjustment interface based on the parameter definition information, so that the user can tune the parameters in the sound effect parameter adjustment interface.

[0027] This application obtains prototype design information containing parameter definitions and generates a prototype definition file accordingly. This file essentially constitutes a structured description of the algorithm parameters, replacing the manually written and fixed application layer protocol used in traditional development. When a parameter tuning request is received, the parameter definition information can be automatically obtained by parsing the prototype definition file, and the corresponding sound effect parameter adjustment interface can be dynamically generated accordingly. This eliminates the need for application developers to manually write interfaces and adapt interaction logic for each new algorithm or algorithm update. This automated process ensures that the generation of both algorithm parameter definitions and user parameter tuning interfaces is based on the same standardized prototype definition file, achieving consistency in parameter format and logic between the device-side algorithm and the application-side parameter tuning interface, and avoiding protocol inconsistencies or adaptation errors that may be caused by multiple manual interventions. In this way, the audio effect parameter tuning process is transformed into an automated, standardized, data-driven process, no longer relying on cumbersome manual adaptation. This significantly shortens the cycle from development to debuggable deployment of audio effect algorithms, effectively reduces the collaboration complexity and communication costs between algorithm engineers and application developers, improves the development and deployment efficiency of audio effect parameter tuning functions, and ultimately achieves rapid response and flexible adaptation of the parameter tuning process.

[0028] It should be noted that the execution subject of the various embodiments of the audio effect parameter tuning method of this application can be a computing service device with data processing, network communication and program running functions, such as a server, tablet computer, personal computer, mobile phone, etc., or an electronic device that can realize the above functions, such as a VR (Virtual Reality) headset. The various embodiments of the audio effect parameter tuning method of this application do not impose specific limitations on this.

[0029] Based on this, this application proposes a sound effect parameter adjustment method according to a first embodiment. In this embodiment, referring to... Figure 1 As shown, the sound effect parameter adjustment method includes the following steps S10~S30: Step S10: Obtain prototype design information for the target sound effect algorithm, wherein the prototype design information includes at least parameter definition information, and the parameter definition information is used to define the adjustable parameters of the target sound effect algorithm; The target sound effect algorithm refers to the sound effect algorithm that needs to be debugged, verified, or its effects demonstrated. This prototype design information can be provided by the algorithm engineer during the algorithm development phase. Specifically, after completing the development of the core algorithm logic, the algorithm engineer can use an integrated prototyping tool or platform to structurally input and set this prototype design information in a specific configuration interface.

[0030] Specifically, the prototype design information is a structured data set containing multiple dimensions, and its components include, but are not limited to, parameter definition information. In a preferred embodiment, a complete prototype design information typically includes parameter definition information, module definition information, port definition information, and parameter mapping display information. These information work together to define the algorithm's functional attributes, identity, interface specifications, and human-computer interaction interface, thereby providing a comprehensive description of the algorithm. Wherein: Parameter definition information is used to define all adjustable parameters of the target sound effect algorithm. For each adjustable parameter, the specific definition method is systematically expanded according to the parameter's structure type (value parameter, group parameter, or array parameter), and is accomplished by configuring a series of parameter attributes. For example, for group or array parameters, a series of attributes such as parameter type attribute, initial array size, array size control expression, and the definition of its internal sub-parameters can be configured to form a machine-understandable composite parameter specification that describes the overall structure and relationship of the parameters. For value parameters, a series of attributes such as data type, value range, adjustment step value, default value, operation permissions, and display precision (for floating-point types) can be configured to form a machine-understandable atomic parameter specification that defines the parameter's numerical behavior and constraints.

[0031] Module definition information is used to uniquely identify and classify target sound effect algorithms. For example, it includes the algorithm's unique ID, version number, algorithm type (such as equalizer, compressor), and functional description text, which facilitates system management and retrieval.

[0032] Port definition information is used to define the input and output interfaces for audio data and control signals of the target audio effect algorithm. It includes, but is not limited to, port direction (input / output), port type (such as audio stream port, control signal port, configuration port), and port identifier.

[0033] Parameter mapping display information is an optional enhancement that defines more user-friendly aliases for specified parameter values ​​(such as enumerated values) displayed on the sound effect parameter adjustment interface (e.g., mapping the internal value "1" to the interface display text "Pop Mode") to improve the user experience.

[0034] Step S20: Generate a prototype definition file based on the prototype design information; After collecting complete prototype design information, this information is converted into a machine-readable format, typically XML, which facilitates software parsing and processing. The prototype definition file organizes the collected prototype design information in a standardized way to facilitate subsequent parsing and application.

[0035] Furthermore, to facilitate file management and integration, the generation process allows algorithm engineers to specify a target storage directory. The generation program will create and write the prototype definition file in this specified directory. This design enhances deployment flexibility, enabling the generated files to be easily incorporated into version control systems, packaged into algorithm libraries, or automatically discovered and loaded from a defined location by subsequent client applications and debugging tools, thus achieving plug-and-play algorithm description and parameter tuning capabilities.

[0036] Step S30: In response to the parameter tuning request for the target sound effect algorithm, the prototype definition file is parsed to obtain the parameter definition information, and a corresponding sound effect parameter adjustment interface is generated based on the parameter definition information so that the user can adjust the parameters in the sound effect parameter adjustment interface.

[0037] Upon responding to a parameter tuning request, the application or debugging tool first parses the prototype definition file to extract the parameter definition information. Then, based on this information, it automatically generates a user interface containing necessary controls such as sliders, knobs, and drop-down menus, allowing users to intuitively adjust each parameter. This interface matches the layout and interaction logic described in the prototype definition file. Finally, users can tune the parameters on the generated audio effect parameter adjustment interface. All adjustments are reflected in the audio processing in real time, allowing users to immediately hear the changes and make further fine-tuning. This method not only improves the convenience and accuracy of parameter tuning but also reduces the workload for developers, as they do not need to manually create and maintain a user interface for each new algorithm.

[0038] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description and will not be repeated hereafter. Based on this, after the step of generating a prototype definition file based on the prototype design information, the method further includes: Step A10: Based on the prototype definition file, generate corresponding interactive design controls in the link design platform, wherein the link design platform is a graphical design platform for configuring the sound effect processing link; The Link Design Platform is a software environment for configuring, connecting, and managing multiple audio processing modules in a graphical drag-and-drop manner to build a complete audio effects processing link.

[0039] This generation process is executed automatically by the platform: the platform parses the prototype definition file, extracts the module definition information (such as algorithm name and type) and port definition information (input and output interfaces), and creates a visual design control (such as an icon or function block) representing the target sound effect algorithm. This control is internally associated with its corresponding prototype definition file and reproduces the audio ports declared by the algorithm, allowing users to connect it with other algorithm controls via virtual connections in the graphical interface.

[0040] Step A20: After the interactive design control is deployed to the link design area in the link design platform, in response to the selection operation of the interactive design control, a parameter tuning request for the target sound effect algorithm is triggered.

[0041] After a user deploys (e.g., drags and drops) an interactive design control to the link design area of ​​the link design platform and completes the necessary signal flow connections, the platform will respond to the user's selection of the control by clicking or other means, automatically triggering a parameter tuning request for the target audio effect algorithm represented by the control. This design allows users to initiate fine-grained parameter tuning of any algorithm node on the link at any time and directly while performing macro-level link design and module assembly, achieving seamless connection and efficient context switching from system-level link construction to module-level parameter adjustment.

[0042] Understandably, this parameter tuning process is usually dynamic, allowing users to hear the effects in real time and further adjust the parameters as needed until a satisfactory sound effect is achieved.

[0043] In one possible implementation, after the step of generating the corresponding sound effect parameter adjustment interface, the method further includes: Step B10: In response to the running request for the audio effect algorithm topology link in the link design area, the corresponding audio effect algorithm is run sequentially according to the definition of the topology link; In response to a user's request to run (or audition) a pre-built audio effect algorithm topology link in the link design area, based on the graphical definition of the link, the corresponding audio effect algorithm modules in the link are instantiated and executed sequentially in the target audio processing engine (such as an embedded device or simulation environment) according to the topology order, forming a real-time audio processing pipeline. Each algorithm module acts as an independent processing unit, applying specific transformations to the flowing audio signal. The modules work in the designed order to jointly achieve the final overall audio effect. This topology link can be flexibly designed according to different audio effect scenarios.

[0044] For example, in one specific embodiment, reference Figure 2The diagram illustrates the audio effect algorithm topology. To meet requirement a, a target audio effect algorithm topology A can be designed, with the following module execution order: gain adjustment module → volume adjustment module → equalizer → multi-band DRC module → sound field expansion module → virtual bass module → limiter → immersive audio effect module → head tracking module → virtual surround module. To meet requirement b, a target audio effect algorithm topology B can be designed, with the following order: gain adjustment module → volume adjustment module → equalizer → multi-band DRC module → sound field expansion module → equalizer → gain adjustment module → virtual surround module. These two (or more) different audio effect algorithm topologies can be applied to the same target audio device, dynamically switching to adapt to diverse audio processing scenarios.

[0045] Step B20: When running the target sound effect algorithm associated with the prototype definition file, a corresponding parameter adjustment command is generated based on the target parameter value set by the user on the sound effect parameter adjustment interface; wherein, the parameter sequence of the parameter adjustment command is consistent with the parameter order defined in the prototype definition file; When the audio processing pipeline reaches the target sound effect algorithm instance associated with the prototype definition file, it captures the target parameter values ​​set by the user on the corresponding sound effect parameter adjustment interface. Then, based on the parameter data structure, type, and order defined in the prototype definition file, these interface values ​​are serialized into a standardized, low-redundancy binary or text parameter tuning instruction. The sequence of parameter values ​​in this instruction matches the parameter definition order in the prototype definition file to ensure that the instruction can be correctly parsed by the device and mapped to the algorithm's internal variables, thus affecting audio processing in the expected way.

[0046] Step B30: Send the parameter tuning instruction to the target audio device so that the target audio device can call the target sound effect algorithm according to the parameter tuning instruction and apply the target parameter value to perform audio processing, thereby completing the operation of the target sound effect algorithm.

[0047] The generated parameter tuning commands are sent to the target audio device (i.e., the embedded hardware platform running the audio effect algorithm chain) via an established communication channel (such as USB, Bluetooth, or Wi-Fi). Upon receiving the commands, the device's protocol stack parses them according to a shared prototype definition specification, extracts the parameter values, and calls the corresponding target audio effect algorithm instance already loaded in memory. The parsed target parameter values ​​are accurately written into the corresponding parameter registers or variables within the algorithm, thereby adjusting its audio processing behavior in real time. After applying the new parameters, the algorithm continues processing the audio stream, completing the run and ensuring that the user's parameter tuning operations immediately produce perceptible changes in audio effects.

[0048] It should be noted that this embodiment constructs an efficient algorithm update and integration ecosystem. After developing the target sound effect algorithm, algorithm engineers can update its compilation library to the firmware algorithm library of the target audio device. The device-side software only needs to replace or load the new algorithm library file, without needing to modify the upper-layer communication protocol or adaptation code for each new algorithm. At the same time, algorithm engineers can use prototyping tools on the client side to define the prototype design information of the new algorithm online and generate its prototype definition file. After the design is completed, restarting the client application will automatically recognize and support the new algorithm for link design and parameter debugging. Therefore, the client application software achieves "zero-code" adaptation, and the device software side only needs minimal algorithm library update work. This greatly reduces the cross-platform development and joint debugging investment required when expanding the new algorithm prototype, significantly reduces project manpower costs, shortens the iteration cycle from algorithm development to function launch, and makes the evolution of the entire sound effect demonstration system more flexible and efficient.

[0049] In one possible implementation, prior to the step of generating the corresponding parameter tuning instructions, the method further includes: Step C10: Perform compliance verification on the target parameter value set by the user on the sound effect parameter adjustment interface, wherein the compliance verification includes verifying whether the target parameter value conforms to the constraint rules defined for the corresponding adjustable parameter in the prototype definition file; A series of compliance checks are performed on the parameter values ​​input by the user through the sound effect parameter adjustment interface. These checks include, but are not limited to, verifying whether the parameter values ​​are within the range specified for the corresponding adjustable parameter in the prototype definition file, whether they meet data type requirements (e.g., integer parameters should not contain decimals), and whether they meet specific step size requirements. The purpose of compliance verification is to ensure that the parameter values ​​provided by the user are within the acceptable range of the algorithm and can produce effective audio processing results.

[0050] Step C20: If the verification passes, then execute the step of generating the corresponding parameter adjustment command based on the target parameter value set by the user on the sound effect parameter adjustment interface; If the compliance check is successful, meaning the user-defined parameter values ​​meet all predefined constraints, subsequent steps will be executed to generate parameter tuning instructions based on these validated parameter values. These instructions will be used to configure the audio effect algorithm to achieve the user's desired audio processing effect.

[0051] In step C30, if the verification fails, a verification error message is generated and the generation or sending of the parameter tuning command is prevented.

[0052] If, during the validation process, user-input parameter values ​​are found to be inconsistent with the constraints defined in the prototype definition file, an error message will be generated. This message will further indicate which parameter values ​​are non-compliant and the reasons for the non-compliance. Simultaneously, the generation or sending of parameter tuning commands will be prevented to avoid applying non-compliant parameter values ​​to the audio device, thereby preventing potential audio processing errors or device damage. Users can adjust the parameter values ​​based on the error message and then re-perform the compliance validation.

[0053] Based on the first and / or second embodiments of this application, in the third embodiment of this application, the content that is the same as or similar to the first and second embodiments described above can be referred to the above description and will not be repeated hereafter. Based on this, the step of generating a prototype definition file based on the prototype design information includes: Step D10: Encapsulate the prototype design information into structured text that conforms to a preset syntax specification to obtain a prototype definition file; wherein the structured text is in XML format.

[0054] The collected prototype design information is organized and packaged according to a predefined syntax specification. This predefined syntax specification typically refers to a standardized file format used to ensure information consistency and readability, facilitating subsequent parsing and processing.

[0055] In this embodiment, the selected preset syntax specification is XML (eXtensible Markup Language) format. XML is a flexible text format used for storing and transmitting data. It allows developers to define their own tags to adapt to different data structures and needs.

[0056] In one possible implementation, refer to Figure 3 As shown, the step of parsing the prototype definition file and generating the corresponding sound effect parameter adjustment interface includes: Step E10: Parse the prototype definition file from XML format into structured data in JSON format, and obtain configuration information based on the structured data; During the parsing process, the hierarchical tag structure of XML is converted into a key-value pair and array structure of JSON, for example, ... <param> Elements and their attributes are converted into JSON objects containing keys such as paramKey, dataType, min, and max. This structured data in JSON format serves as an intermediate representation, offering higher processing efficiency and convenience in client-side runtime environments (such as web browsers or JavaScript engines), and facilitating subsequent logical operations. The configuration information obtained based on this structured data is the set of all necessary parameter definitions extracted to guide interface generation, along with their associated metadata.

[0057] Step E20: Generate a corresponding sound effect parameter adjustment interface based on the configuration information.

[0058] The system iterates through the parameter definition list in the obtained JSON-formatted configuration information. For each parameter definition, based on its `dataType`, `paramAttribute`, and other attributes, it dynamically matches and instantiates the corresponding graphical user interface control component. For example, for a parameter with `dataType` as `int` and a value range of `min` / `max`, it instantiates a numerical slider control and automatically sets its minimum value, maximum value, step value, and default value. For parameters with `paramAttribute` as an array, it generates an expandable / collapseable array panel and recursively generates parameter controls for each element within it. Simultaneously, `paramDisplayName` is used to set the control label, and parameter mapping display information (if present) is used to optimize the display text of the enumerated values. Finally, according to preset layout rules or style templates, all generated controls are assembled and rendered into a complete, interactive sound effect parameter adjustment interface, thus achieving fully automated construction from data definition to a visual interface.

[0059] In one possible implementation, after the step of obtaining prototype design information for the target sound effect algorithm, the method further includes: Step F10: Verify whether the adjustable parameters in the target sound effect algorithm are consistent with the adjustable parameters contained in the prototype design information; By analyzing the interface metadata of the loaded or compiled target sound effect algorithm library (or algorithm module), a list of internal identifiers (or symbols) and their basic types for all actually exposed adjustable parameters of the algorithm can be extracted. Simultaneously, the acquired prototype design information is parsed to extract the logical names (paramKey) of all parameters declared through parameter definition information. Subsequently, these two sets of parameter sets are compared and verified, with the core verification points including: 1) Completeness: Whether all actual adjustable parameters in the algorithm are explicitly defined in the prototype design information without omission; 2) Accuracy: Whether the names of the parameters defined in the prototype design information correctly map to the algorithm's internal parameter identifiers, and whether key attributes (such as basic data types) match. This aims to ensure that the design information completely and accurately covers the algorithm's actual adjustable interface.

[0060] Step F20: If the verification is consistent, then proceed with the step of generating a prototype definition file based on the prototype design information; If the verification results are completely consistent, that is, if the prototype design information has completely and correctly described all the adjustable parameters of the algorithm, then the verification is deemed to have passed, and the subsequent steps of generating the prototype definition file based on the prototype design information are continued.

[0061] If the verification fails in step F30, a message indicating that the adjustable parameters are not fully configured will be output.

[0062] If the verification fails—that is, if parameters not defined in the prototype design information are found in the algorithm, or if parameter names do not match—the file generation process will terminate, and a clear message indicating that adjustable parameters are not fully configured will be output. This message typically specifies the missing or mismatched parameter identifiers to guide algorithm engineers in checking and supplementing the prototype design information. This prevents subsequent interface generation errors or device-side parameter tuning failures due to missing parameter definitions from the outset, ensuring the data foundation quality of the entire automated process.

[0063] For example, in order to help understand the technical concept or principle of the sound effect parameter tuning method combined with the first and second embodiments described above, a specific embodiment is now listed. In this specific embodiment, refer to... Figure 4 As shown, the audio effect parameter tuning process includes: 1) Set project directory: This is mainly used to generate algorithm prototype definition files in the specified project directory.

[0064] 2) Prototype design: Complete the design of algorithm prototype parameters on a specific interface, that is, complete the setting of prototype design information.

[0065] 3) Generate prototype file: After the user clicks to confirm, the UI data on the specific interface is parsed to generate a prototype definition file (xml format) based on the prototype parameters.

[0066] 4) Tool Restart: The tool software (link platform) restarts to display the corresponding visual controls on the link platform, enabling support for newly added algorithms at the application layer.

[0067] 5) Device side: Simply replace the generated version with the new algorithm library. (This reduces the previous work of adapting and ensuring compatibility with new algorithms on the device side.) 6) Audio link design and parameter tuning: AE (Application Engineer) and ALG (Algorithm Engineer) engineers can design and debug audio algorithms and tune sound effects parameters.

[0068] The specific, detailed workflow is as follows: Prototype loading: Loads the XML algorithm prototype definition file in the specified directory when the software starts.

[0069] Generate JSON description file: Parse the prototype definition XML file and generate a JSON file for graphical display and parameter tuning based on the information.

[0070] Load Prototype: Loads the JSON file of the corresponding prototype.

[0071] Link Design: After the application software has loaded the prototype, it can proceed to the sound effect link design. Parameter tuning process: The audio parameters will be encapsulated according to the order defined in the prototype XML and sent to the device side through the communication medium.

[0072] On the device side: by default, the data structure and order defined by the XML prototype are used for data management and interaction with the algorithm side.

[0073] Internal device algorithm: Processes the input sound effect parameters using algorithms.

[0074] It should be noted that the above examples are only used to help understand this embodiment and do not constitute a limitation on the audio effect parameter adjustment process of this embodiment. Any simple modifications based on this technical concept are within the protection scope of this application.

[0075] Furthermore, embodiments of this application also propose an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the method described above.

[0076] refer to Figure 5 The diagram illustrates a structural schematic of an electronic device suitable for implementing embodiments of this application. The electronic devices in the embodiments of this application may also include, but are not limited to, mobile terminals such as mobile phones, VR headsets, laptops, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0077] like Figure 5As shown, the electronic device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the electronic device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. While electronic devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0078] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0079] The electronic device provided in this application, employing the audio parameter tuning method described in the above embodiments, can solve the technical problem that traditional audio parameter tuning processes rely on manual adaptation, leading to low efficiency in repetitive development and debugging across multiple platforms. Compared with the prior art, the beneficial effects of the electronic device provided in this application are the same as those of the audio parameter tuning method provided in the above embodiments, and other technical features of this electronic device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0080] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0081] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0082] In addition, to achieve the above objectives, this application also provides a readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the audio parameter tuning method in the above embodiments.

[0083] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0084] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0085] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by an electronic device, cause the electronic device to perform the process steps of any embodiment of the aforementioned audio parameter tuning method.

[0086] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0087] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0088] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the modules themselves.

[0089] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described audio effect parameter tuning method. This solves the technical problem that traditional audio effect parameter tuning processes rely on manual adaptation, leading to low efficiency in repetitive development and debugging across multiple platforms. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the audio effect parameter tuning method provided in the above embodiments, and will not be elaborated upon here.

[0090] Furthermore, this application also proposes a computer program product, including a computer program that, when executed by a processor, implements the steps of the sound effect parameter tuning method described above.

[0091] The specific implementation method of the computer program product in this application is basically the same as the various embodiments of the above-mentioned sound effect parameter adjustment method, and will not be described again here.

[0092] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0093] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0094] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software sensor. This computer software sensor is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause an electronic device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0095] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for adjusting sound effect parameters, characterized in that, The sound effect parameter tuning method includes the following steps: Obtain prototype design information for the target sound effect algorithm, wherein the prototype design information includes at least parameter definition information, and the parameter definition information is used to define the adjustable parameters of the target sound effect algorithm; Generate a prototype definition file based on the prototype design information; In response to a parameter tuning request for the target sound effect algorithm, the prototype definition file is parsed to obtain the parameter definition information, and a corresponding sound effect parameter adjustment interface is generated based on the parameter definition information, so that the user can adjust the parameters in the sound effect parameter adjustment interface.

2. The sound effect parameter adjustment method as described in claim 1, characterized in that, After the step of generating a prototype definition file based on the prototype design information, the method further includes: Based on the prototype definition file, a corresponding interactive design control is generated in the link design platform, wherein the link design platform is a graphical design platform for configuring the sound effect processing link; After the interactive design control is deployed to the link design area in the link design platform, a parameter tuning request for the target sound effect algorithm is triggered in response to the selection operation of the interactive design control.

3. The sound effect parameter adjustment method as described in claim 2, characterized in that, After the step of generating the corresponding sound effect parameter adjustment interface, the method further includes: In response to a request to run a sound effect algorithm topology link in the link design region, the corresponding sound effect algorithm is run sequentially according to the definition of the topology link; When the target sound effect algorithm associated with the prototype definition file is run, a corresponding parameter adjustment command is generated based on the target parameter value set by the user on the sound effect parameter adjustment interface; wherein, the parameter sequence of the parameter adjustment command is consistent with the parameter order defined in the prototype definition file; The parameter tuning command is sent to the target audio device so that the target audio device calls the target sound effect algorithm according to the parameter tuning command and applies the target parameter value to perform audio processing, thereby completing the operation of the target sound effect algorithm.

4. The sound effect parameter adjustment method as described in claim 3, characterized in that, Before the step of generating the corresponding parameter tuning instructions, the method further includes: The user sets a target parameter value on the sound effect parameter adjustment interface for compliance verification, wherein the compliance verification includes verifying whether the target parameter value conforms to the constraint rules defined for the corresponding adjustable parameter in the prototype definition file; If the verification passes, then the step of generating the corresponding parameter adjustment command based on the target parameter value set by the user on the sound effect parameter adjustment interface is executed; If the verification fails, a verification error message is generated and the generation or sending of the parameter tuning command is prevented.

5. The sound effect parameter adjustment method as described in claim 1, characterized in that, The step of generating a prototype definition file based on the prototype design information includes: The prototype design information is encapsulated into structured text that conforms to a preset syntax specification to obtain a prototype definition file; The structured text is in XML format.

6. The sound effect parameter adjustment method as described in claim 5, characterized in that, The step of parsing the prototype definition file and generating the corresponding sound effect parameter adjustment interface includes: The prototype definition file is parsed from XML format into structured data in JSON format, and configuration information is obtained based on the structured data; Based on the configuration information, a corresponding sound effect parameter adjustment interface is generated.

7. The sound effect parameter adjustment method according to any one of claims 1 to 6, characterized in that, After the step of obtaining prototype design information for the target sound effect algorithm, the method further includes: Verify whether the adjustable parameters in the target sound effect algorithm are consistent with the adjustable parameters contained in the prototype design information; If the verification is successful, then proceed with the step of generating a prototype definition file based on the prototype design information; If the verification fails, a message indicating that the adjustable parameters are not fully configured will be output.

8. The sound effect parameter adjustment method according to any one of claims 1 to 6, characterized in that, The prototype design information also includes module definition information, port definition information, and parameter mapping display information; The module definition information is used to uniquely identify and classify the target sound effect algorithm; The port definition information is used to define the input and output interfaces of the audio data and control signals of the target sound effect algorithm; The parameter mapping display information is used to define aliases for specified parameter values ​​displayed on the sound effect parameter adjustment interface.

9. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the audio parameter tuning method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a device control program, which, when executed by a processor, implements the steps of the audio parameter tuning method as described in any one of claims 1 to 8.

Images