DSP development method, system and device and storage medium

Abstract

The embodiment of the invention discloses a DSP development method, system and device and a storage medium. The DSP development method comprises the steps of determining a development demand of a user based on first input of the user; the development demand comprises a function demand, a module setting demand and / or a parameter setting demand for the DSP component; and based on the development demand, generating and displaying a target DSP component and prompt information, the prompt information comprising a generation result prompt and / or component effect evaluation. According to the method, the requirement is input through the natural language, a user does not need to manually drag the component, the development time and workload are greatly reduced, DSP engineering development is more intuitive and humanized, and the user experience is improved.

Description

Technical Field

[0001] The present invention relates to the field of digital signal processing, and in particular to a DSP development method, system, device and storage medium. Background Art

[0002] The current DSP development process mainly relies on the graphical user interface (GUI), which requires users to build and adjust DSP components by manually dragging and clicking. However, manual operation is not only time-consuming, but also particularly laborious when designing complex systems. In addition, due to the lack of instant feedback and automatic adjustment functions, multiple debugging is often required during the development process, which not only increases the difficulty of users in the DSP development process, but also prolongs the development cycle.

[0003] Therefore, it is desired to provide a DSP development method, system, device and storage medium that can simplify the development process, improve development efficiency, and enhance user experience. Summary of the invention

[0004] One of the embodiments of the present specification provides a DSP development method, the method comprising: determining the user's development requirements based on the user's first input; the development requirements include functional requirements, module setting requirements and / or parameter setting requirements for DSP components; based on the development requirements, generating and displaying target DSP components and prompt information, the prompt information includes generation result prompts and / or component effect evaluations.

[0005] One of the embodiments of the present specification provides a DSP development system, the system comprising: a determination module, configured to determine the user's development requirements based on the user's first input; the development requirements include functional requirements, module setting requirements and / or parameter setting requirements for DSP components; a prompt module, configured to generate and display target DSP components and prompt information based on the development requirements, the prompt information including generation result prompts and / or component effect evaluations.

[0006] One of the embodiments of the present specification provides a DSP development method device, the device includes a processor, and the processor is used to execute the above-mentioned DSP development method.

[0007] One of the embodiments of this specification provides a computer-readable storage medium, wherein the storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the aforementioned DSP development method. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0009] Figure 1 It is a schematic diagram of application scenarios of the DSP development system shown in some embodiments of this specification;

[0010] Figure 2 is an exemplary flow chart of a DSP development method according to some embodiments of this specification;

[0011] Figure 3 is an example diagram of a DSP development method according to some embodiments of this specification;

[0012] Figure 4 is an exemplary schematic diagram of determining component adjustment requirements according to some embodiments of this specification;

[0013] Figure 5 is an exemplary schematic diagram of a habit development model according to some embodiments of the present specification. DETAILED DESCRIPTION

[0014] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0015] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0016] As shown in this specification and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0017] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed precisely in order. Instead, the steps may be processed in reverse order or simultaneously. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0018] Figure 1 1 is a schematic diagram of an application scenario 100 of a DSP development system according to some embodiments of this specification. The DSP development system can achieve DSP development goals in a variety of application scenarios. For example, the application scenarios of the DSP development system include but are not limited to audio processing, speech recognition, communication systems, medical image processing, and other scenarios. The application scenario 100 of the DSP development system involved in the embodiments of this specification will be described in detail below. It should be noted that the following embodiments are only used to explain this application and do not constitute a limitation on this application.

[0019] like Figure 1 As shown, the application scenario 100 of the DSP development system may include a user 110 , a terminal device 120 , a network 130 , a storage device 140 , a processor 150 , and a DSP component 160 .

[0020] User 110 refers to a user who uses the DSP development system. For example, user 110 may be an audio engineer, a speech recognition developer, a communication engineer, a medical imaging technician, a car audio designer, a consumer electronics product developer, or a non-professional who is interested in audio processing or signal optimization, such as an audio enthusiast and a self-media person. User 110 may interact with the DSP development system for data and / or information through network 130 based on terminal device 120. In some embodiments, user 110 may input information related to the development of the DSP to the terminal device, for example, input user feedback on component modification suggestions to the terminal device.

[0021] The terminal device 120 refers to a hardware device used to directly interact with the user 110 and perform operations. For example, the terminal device may include one or any combination of devices with input and / or output functions such as a mobile device 120-1, a tablet computer 120-2, a laptop computer 120-3, a desktop computer 120-4, etc. In some embodiments, the terminal device 150 may include an input device, an output device, etc. The input device may include a keyboard, a touch screen, a mouse, a voice device, etc., or any combination thereof. The output device may include a display, a speaker, a printer, etc., or any combination thereof. In some embodiments, the terminal device 120 may be part of the processor 150. In some embodiments, the terminal device 120 may be integrated with the processor 150.

[0022] In some embodiments, the terminal device 120 may interact with other components in the DSP development system through the network 130. In some embodiments, the terminal device 120 may present the target DSP component and prompt information generated by the processor 150 to the user 110.

[0023] The network 130 may connect various components of the application scenario 100 of the DSP development system and / or connect the application scenario 100 of the DSP development system with external resources.

[0024] In some embodiments, one or more components of the application scenario 100 of the DSP development system (eg, user 110 , terminal device 120 , storage device 140 , processor 150 , and DSP component 160 ) may exchange information and / or data via the network 130 .

[0025] In some embodiments, the network 130 may be any one or more of a wired network or a wireless network. In some embodiments, the network 130 may include one or more network access points. For example, the network 130 may include a wired or wireless network access point (e.g., a base station and / or a network switching point), through which one or more components of the application scenario 100 of the DSP development system may be connected to the network 130 to exchange data and / or information.

[0026] The storage device 140 is used to store data, instructions and / or any other information. The storage device 140 may include one or more storage components, each of which may be an independent device or a part of another device. In some embodiments, the storage device 140 may include a random access memory (RAM), a read-only memory (ROM), a removable memory, etc. or any combination thereof. In some embodiments, the storage device 140 may be connected to the network 130 to communicate with one or more components in the application scenario 100 of the DSP development system. In some embodiments, the storage device 140 may be a part of the processor 150.

[0027] In some embodiments, the storage device 140 may also store data and / or information obtained from the user 110, the terminal device 120, the network 130, the processor 150, and the DSP component 160. For example, the storage device 140 may store historical development data of the user 110, and the like.

[0028] The processor 150 is used to process information and / or data related to the application scenario 100 of the DSP development system. In some embodiments, the processor 150 can process data, information and / or processing results obtained from other devices or system components, and execute program instructions based on these data, information and / or processing results to perform one or more functions described in this specification. As an example only, the processor 150 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), etc., or any combination thereof.

[0029] In some embodiments, the processor 150 is configured to determine the development requirements of the user based on the first input of the user; and generate and display the target DSP component and prompt information based on the development requirements.

[0030] In some embodiments, the processor 150 is further configured to determine, based on a second input from the user, a component adjustment requirement of the user for the target DSP component; and adjust the target DSP component based on the component adjustment requirement.

[0031] In some embodiments, the processor 150 is further configured to determine component adjustment requirements based on component modification suggestions, user feedback, and user development habits.

[0032] In some embodiments, the processor 150 is further configured to determine DSP debugging feedback based on a third input of the user; generate debugging suggestion information based on the DSP debugging feedback, component information and / or operation information of the target DSP component, and send it to the user.

[0033] DSP component 160 refers to a functional unit that is automatically generated or adjusted by the DSP development system according to user requirements. In some embodiments, the DSP component may be composed of one or more modules for implementing a series of related functions. As an example only, the DSP component may include but is not limited to a gain module, a low-pass filter module, etc.

[0034] As used herein, "DSP development" refers to the process of designing and optimizing the processing of audio, video or other signals using digital signal processing technology. In a DSP development system, the system is able to generate or adjust functional units, which may include hardware units and software programs, etc., according to the specific needs of the user. The design and adjustment of DSP components are intended to improve the efficiency and effectiveness of signal processing to achieve specific application goals, such as audio processing, image enhancement or communication signal optimization.

[0035] It should be noted that the application scenarios of the DSP development system are provided for illustrative purposes only and are not intended to limit the scope of this specification. For those of ordinary skill in the art, various modifications or variations can be made based on the description of this specification. For example, the application scenario may also include a database. For another example, the application scenario may be implemented on other devices to achieve similar or different functions. However, the changes and modifications will not deviate from the scope of this specification.

[0036] In some embodiments, the DSP development system may include a determination module and a prompting module.

[0037] In some embodiments, the determination module is configured to determine the development requirements of the user based on the first input of the user. The prompt module is configured to generate and display the target DSP component and prompt information based on the development requirements.

[0038] In some embodiments, some or all modules of the DSP development system may be integrated into the processing device 150 .

[0039] For more information about the relevant functions of each of the above components and / or modules, see Figure 2-Figure 5 and its related description.

[0040] It should be noted that the above description of the DSP development system and its modules is only for the convenience of description and does not limit this specification to the scope of the embodiments. It is understandable that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine the various modules, or form a subsystem to connect with other modules without deviating from this principle. In some embodiments, the determination module and the prompt module can be different modules in a system, or a module can implement the functions of two or more of the above modules. For example, each module can share a storage module, or each module can have its own storage module. In some embodiments, the determination module can also be divided into multiple sub-modules. For example, the determination module can also include an adjustment module. Such variations are all within the scope of protection of this specification.

[0041] Figure 2 is an exemplary flow chart of a DSP development method according to some embodiments of this specification. Figure 2 As shown, the flowchart 200 includes the following steps. In some embodiments, the DSP development method shown in the flowchart 200 may be executed by a processor (eg, the processor 150).

[0042] Step 210 , based on the user's first input 211 , determine the user's development requirement 212 .

[0043] User input refers to the content that the user interacts with the processor for a specific purpose. The user can input in a variety of forms. For example, the input form may include voice, text, pictures, etc. In some embodiments, the user's input is a natural language input. In some embodiments, the user's input may be content related to DSP development. As an example only, the user's input may be "add a bandpass filter with a passband range between 500 Hz and 1 kHz".

[0044] In some embodiments, the user input may include multiple types based on different purposes. For example, the user input may be divided into input based on specific development requirements, input based on component adjustment requirements, input based on problems with running DSP components, input based on the purpose of learning DSP component-related knowledge, input based on the purpose of DSP component optimization consultation, etc.

[0045] For example, the input based on specific development needs can be "design a third-order low-pass filter to remove signal components above 3kHz". The input based on component adjustment needs can be "adjust the sensitivity of the noise suppression module to make it more effective for low-frequency noise". The input based on the problems of the running DSP components can be "the output signal is distorted during operation, please analyze the possible reasons and propose corrections". The input based on the purpose of learning relevant knowledge about DSP components can be "explain the main differences between FIR filters and IIR filters, and give usage scenarios". The input based on the purpose of DSP component optimization consultation can be "I need to reduce the calculation delay of the filter, is there a suitable optimization algorithm or adjustment strategy?".

[0046] In some embodiments, the processor can obtain user input in a variety of ways. For example, the user can enter requirements or questions related to DSP development in a text input box through a keyboard, and the processor can use the received text as the user's input. For another example, the processor can also use speech recognition technology to obtain user input. After the user describes the development requirements through voice, the processor can convert the voice into text as the recognized input.

[0047] The above examples and acquisition methods of user input are for illustrative purposes only and are not intended to limit the scope of the present invention.

[0048] In some embodiments, the processor may also classify the user's input based on other methods, such as classifying the user's input into different types based on different input times. As an example only, the processor may classify the input made by the user in the early stage of developing the DSP as one type of input, and the input made after the DSP component is running as another type of input.

[0049] In some embodiments, the user's input may include but is not limited to a first input, a second input and / or a third input. In some embodiments, the first input may be an input made by the user based on his / her development needs. The second input may be further instructions or information provided by the user after the target DSP component is generated. The third input may be feedback information or data provided by the user to the processor after the target DSP component is running. For details about the second input and the third input, please refer to Figure 3 Description.

[0050] Development requirements refer to the requirements put forward by users to achieve specific technical goals or application functions. For example, development requirements can describe that the DSP component needs to have at least one function such as background noise reduction, echo cancellation, automatic gain control, signal filtering, dynamic compression, audio equalization, sound localization, downsampling, signal demodulation, etc.

[0051] In some embodiments, the development requirements are requirements proposed by the user before the target DSP component is generated. In some embodiments, the development requirements include functional requirements, module setting requirements and / or parameter setting requirements for the DSP component. For more information about the target DSP component, see step 220 and its related description.

[0052] Functional requirements describe the specific functions or services that the DSP component needs to implement. For example, a functional requirement could be "add a DSP module that can implement automatic noise suppression so that the DSP system can automatically reduce background noise when processing audio signals in real time."

[0053] The module setting requirement refers to the requirements for the configuration and layout of specific modules in the DSP development system. For example, the module setting requirement can be "add a low-pass filter module to remove signal components above 1kHz and place it before the gain control module".

[0054] In some embodiments, the component setup requirements may not only cover the connection method of the DSP modules in the DSP development system, but also include specific usage requirements for each module. For example, the component setup requirements may specify that gain module A is used to process frequencies above 1000 Hz, while gain module B is used to process frequencies below 1000 Hz. For more information about the connection method, please refer to the description at step 220.

[0055] Parameter setting requirements refer to the specific parameter configurations that describe each module of the DSP component.

[0056] For example, a parameter setting requirement may be "set the initial gain of the gain control module to 5dB and allow the DSP development system to adjust within the range of ±10dB".

[0057] In some embodiments, the processor may determine the user's development needs in a variety of ways based on the user's first input. In some embodiments, the processor may process the first input through a large language model to determine the user's development needs. The large language model may include but is not limited to GPT, BERT, T5, XLNet, etc.

[0058] Users can input development requirements in natural language through the graphical interface or command line interface of the terminal device.

[0059] In order to adapt the large language model to the specific needs of DSP development, it is necessary to fine-tune the existing large language model to obtain the first large language model. The fine-tuning process can usually include the following steps:

[0060] Collecting corpora in the DSP field: The corpus may include but is not limited to text data related to DSP development, such as technical documents, papers, user guides, etc. The collected corpus in the DSP field is used to train a large language model.

[0061] Preprocess data: clean and annotate the collected corpus and divide it into training set and validation set.

[0062] Model fine-tuning: Fine-tune the existing large language model using the training set to obtain the first large language model, which is able to recognize and understand the terms, concepts, and requirements related to DSP development.

[0063] Model verification and testing: Verify the first language model based on the verification set to ensure that it can accurately understand and process the user's natural language input.

[0064] In some embodiments, after receiving the first input from the user, the first large language model can parse the first input (e.g., context analysis, extraction classification, etc.), convert the first input from the user into a specific development requirement, and the processor can generate a corresponding target DSP component according to the development requirement. For the content of the target DSP component, please refer to step 220 and its related description.

[0065] The embodiments of this specification understand and process the user's natural language input by fine-tuning the large language model, and the processor can directly determine the development requirements of the DSP components. Compared with traditional drag and drop, this process greatly simplifies the interaction between the user and the DSP development system.

[0066] The above method for determining the development needs of a user is for illustrative purposes only and is not intended to limit the scope of the present invention.

[0067] Step 220 , based on the development requirement 212 , generate and display the target DSP component 222 and prompt information 223 .

[0068] The target DSP component refers to a specific DSP module designed and generated by the processor based on the user's development needs. For example, the target DSP component can be a component set that integrates a low-pass filter and a gain control module, which can be used to process input audio signals in real time and output optimized audio. For another example, the target DSP component can also be continuously adjusted and optimized into a new target DSP component until the user's development needs are met.

[0069] Prompt information refers to the feedback related to DSP components provided by the processor to the user during the interaction with the user. Prompt information can help users understand the behavior of the DSP development system or help users decide the next step. For example, the prompt information can be "Connection failed: The output signal type of the modulator does not match the output port." Based on this prompt information, the user can check the consistency of the signal type or add an appropriate converter.

[0070] For example only, see Figure 3 , Figure 3 is an example diagram of a DSP development method according to some embodiments of this specification. Figure 3 As shown, the example diagram 300 shows the process of user interaction with the processor. In some embodiments, the prompt information can be Figure 3 The content “OK, it has been successfully generated for you” in the dialog box 320 shown may also be the content “OK, it has been adjusted” in the dialog box 340 .

[0071] In some embodiments, the prompt information may include generation result prompts and / or component effect evaluations.

[0072] The generation result prompt refers to the feedback information related to the instruction execution process or generation result provided by the processor to the user based on the user's input. For example, the generation result prompt may include whether the instruction execution is successful, the instruction execution time, the parameter information of the DSP component, or any related warnings and notifications.

[0073] Component effect evaluation refers to the feedback given by the processor after the performance or functionality evaluation of the generated DSP component. Component effect evaluation can be used to let users know whether the actual performance of the DSP component meets the development requirements. For example, the component effect evaluation can be an overall effect evaluation of the DSP component "the filtering effect meets the standard, the noise suppression performance is excellent, and the audio signal clarity is improved by 20%"; or "the system response time is slightly higher than expected, and the execution efficiency may need to be optimized."

[0074] In the DSP development system, component effect evaluation helps users understand the actual effect of DSP components on data processing.

[0075] The actual effect may represent the result that the DSP component will output after processing the input signal. In some embodiments, taking the data to be processed as an audio signal as an example, the actual result may include but is not limited to changes in volume, pitch, timbre, etc. For example, based on the component effect evaluation, the user may know that the audio processed by the DSP component may be more muffled.

[0076] In some embodiments, the component effect evaluation can also be an evaluation corresponding to each DSP module in the DSP component. For example, at the low-frequency enhancement filter that has been generated, the component effect evaluation of the processor for the module can be displayed, "The processed audio will become more low and deep, suitable for strengthening the bass part, suitable for electronic music, heavy metal, rock and other music types that need to highlight the low frequency." At the high-frequency reduction filter that has been generated, the component effect evaluation of the processor for the module can be displayed, "The processed audio will reduce the high-frequency part, making the sound softer and less harsh, suitable for lyrical songs, classical music and other music types that require soft timbre." At the reverb effector that has been generated, the component effect evaluation of the processor for the module can be displayed, "Increase the sense of space, make the sound sound like it is reverberating in a large room or hall, suitable for live recordings, instrumental solos, operas and other audio that need to simulate a sense of space."

[0077] The processor can generate component effect evaluation in a variety of ways. In some embodiments, the processor can generate component effect evaluation through a preset table. The preset table contains a description of the effect of common DSP modules and their combinations. After the target DSP component is generated, the processor can call up the actual effect corresponding to the DSP module or DSP component from the preset table and display it to the user in the form of a prompt box or sidebar in the graphical interface of the terminal device.

[0078] In some embodiments, the user can add or modify the component effect evaluation displayed in the graphical interface according to his / her own experience and needs.

[0079] The above method for generating component effect evaluation is only described as an example and is not intended to limit the scope of the present invention.

[0080] The processor can generate the target DSP component based on various methods. For example, the processor can generate the target DSP component based on calling and building.

[0081] Retrieval means that the processor directly obtains an existing DSP component that meets the development requirements from the DSP component database and uses it as the target DSP component.

[0082] The DSP component database contains a large number of different types of DSP components and the development requirements data corresponding to the DSP components. After calling and generating the target DSP component, the user can further adjust the target DSP component through natural language input. For more information about adjusting the target DSP component, see Figure 3 , Figure 4 and its related description.

[0083] Assembly means that the processor combines and sets each independent module according to the user's development requirements for DSP components, and finally generates a target DSP component that meets the development requirements.

[0084] For example, if the user's development requirement is a target DSP component that includes equalization, compression, and reverb functions, the processor will combine the equalizer, compressor, and reverb modules together in turn.

[0085] For another example, the user may provide a combination method, such as first setting module A, and setting the parameter of module A to a; then setting module B, and setting the parameter of module B to b, etc. Then the processor will sequentially combine module A and module B. In some embodiments, the combination order and parameter settings of each independent module in the DSP component can be provided by the user.

[0086] In some embodiments, the order in which the modules are combined may affect the final processing effect. The processor may determine the order in which the modules are combined according to a preset rule or user input. For example, the preset rule may be to first adjust the frequency through an equalizer, then balance the dynamic range through a compressor, and finally add a sense of space through a reverberator.

[0087] In some embodiments, the processor can automatically set appropriate parameters for each module according to specific parameters included in the development requirements (such as gain, frequency range, etc.). For example, if the user's development requirements include a low-frequency gain of 5dB for the equalizer, the processor will automatically set the low-frequency gain parameter to 5dB.

[0088] After generating the target DSP component, the processor may further display the generated target DSP component and prompt information to the user through the terminal device.

[0089] In some embodiments, the processor may also display the generated DSP component detailed information, such as the modules included in the DSP component and the parameters set for different modules.

[0090] In some embodiments, the generated target DSP component can be displayed in a graphical manner on the terminal device. The graphical representation of each module in the DSP component can include but is not limited to the module name, the functional description corresponding to each module, the connection mode between modules, etc.

[0091] The connection mode refers to the path for transmitting and processing signals between modules. For example, the connection mode may include the input and output of each module and the serial or parallel mode between modules. On the graphical interface of the terminal device, the connection mode between modules in the DSP component can be displayed in the form of lines or arrows, indicating the direction of data flow or signal flow.

[0092] The above method of displaying the target DSP component and prompt information is only an example. The processor may also display the generated target DSP component and prompt information to the user in other ways, which is not limited in this specification.

[0093] The embodiment of this specification determines the development requirements based on the user's first input, generates the target DSP component based on the development requirements, and intuitively displays the DSP component and prompt information on the terminal device. The user can immediately view and operate the generated components, which improves the efficiency and convenience of DSP development; through the prompt information, the generation result prompt and component effect evaluation are provided, and the user can immediately understand the expected functions and processing effects of the DSP component. Especially for users without professional background, these prompt information can effectively guide them to make more appropriate choices, making the DSP development process more operational.

[0094] Figure 3 is an example diagram of a DSP development method according to some embodiments of this specification. Figure 3 As shown, the example diagram 300 shows the process of user interaction with the processor. In some embodiments, the DSP development method illustrated in the example diagram 300 can be executed by a processor (eg, the processor 150).

[0095] In some embodiments, the processor may determine the development requirements of the functions that the DSP component described above needs to have based on the first input of the user. Figure 3 As shown, the first input of the user may be the content in the dialog box 310, "Please add a low-pass filter, a gain control module and an equalizer, and set the cutoff frequency to 1000 Hz". Based on the first input, the processor may determine that the user's development requirement is to implement an audio processing link with a cutoff frequency of 1000 Hz, which includes a low-pass filter, a gain control and an equalization function to meet specific audio signal processing requirements.

[0096] In some embodiments, the processor can generate and display target DSP components and prompt information based on development requirements. Figure 3 As shown, the processor can generate and display the target DSP component (not shown in the figure) and the prompt message "OK, it has been successfully generated for you" shown in the dialog box 320 based on the user's first input "Please add a low-pass filter, a gain control module and an equalizer, and set the cutoff frequency to 1000 Hz". For the generation and display method of the target DSP component, please refer to Figure 2 and its description.

[0097] In some embodiments, the processor may determine the user's component adjustment requirement for the target DSP component based on the user's second input; and adjust the target DSP component based on the component adjustment requirement.

[0098] The second input is further instructions or information provided by the user after the target DSP component is generated. In some embodiments, the second input can be used to adjust the current module and parameter settings of the target DSP component.

[0099] For example, Figure 3 As shown, the second input may include the content in the dialog box 330 “Please delete the equalizer and change the cutoff frequency to 2000 Hz”.

[0100] In some embodiments, the second input is obtained in a similar manner to the first input. For details, see Figure 2 The related descriptions will not be repeated here.

[0101] Component adjustment requirements refer to information that can reflect the user's specific intention to adjust the target DSP component. For example, component adjustment requirements may include descriptions of adding or removing DSP modules in the target DSP component, re-layout, or adjusting specific parameters.

[0102] In some embodiments, the processor may parse the second input of the user based on the first language model to determine the component adjustment requirements, including natural language processing, context analysis, or direct instruction parsing. For more description of the first language model, see Figure 2 Description.

[0103] In some embodiments, the processor can determine the component adjustment requirements based on component modification suggestions, user feedback, and user development habits. For more information on determining component adjustment requirements, see Figure 4 and its related description.

[0104] In some embodiments, the processor may make corresponding adjustments to the target DSP component according to the component adjustment requirements output by the first large language model. The adjustment may include module setting adjustment, parameter adjustment, etc. For example, based on the user's second input "increase the gain of the low-frequency enhancement component by 5dB", the processor may set the gain parameter of the low-frequency enhancement module to the desired value according to the component adjustment requirement of increasing the gain of the low-frequency enhancement component by 5dB. For another example, the processor may add a new effect module and delete an old module based on the user's second input, and update the signal chain.

[0105] In some embodiments, the adjusted target DSP component may be displayed graphically on the terminal device.

[0106] The embodiments of this specification determine the component adjustment requirements based on the user's second input, and adjust the target DSP component based on the component adjustment requirements, so that the adjusted target DSP component better meets the user's expectations; the above-mentioned flexible adjustment method allows the user to reconfigure or adjust the component according to specific needs, thereby improving user satisfaction; the processor can automatically parse and execute component adjustment requirements, which can reduce the time and complexity of user manual adjustment and improve operational efficiency.

[0107] In some embodiments, the processor may determine DSP debugging feedback based on a third input from the user; generate debugging suggestion information based on the DSP debugging feedback, component information and / or operation information of the target DSP component, and send the information to the user.

[0108] The third input refers to the feedback information or data provided by the user to the processor after the target DSP component runs.

[0109] In some embodiments, the third input is obtained in a similar manner to the first input. For more information about the third input, see Figure 2 and its related description.

[0110] In some embodiments, the third input may be information related to further improving or optimizing the DSP component provided to the processor by the user based on observation and experience of the operating results of the DSP component.

[0111] For example, after adjusting the DSP component of the processor, the user finds that the adjusted target DSP component has no sound after passing through the low-pass filter. Figure 3 As shown, the third input provided by the user may be the content in dialog box 350 “Why is there no sound after passing through the low-pass filter?”.

[0112] For another example, a user expects the audio to have a stronger sense of three-dimensionality after being processed by a DSP component, but due to his or her limited professional knowledge, he or she does not know how to correctly adjust the DSP component to achieve this effect. In this case, the user can provide a third input, such as "Why is the stereoscopic effect not strong enough?" or "How can I make the audio more stereoscopic?"

[0113] In some embodiments, the processor may generate DSP debugging feedback based on a third input from the user.

[0114] DSP debug feedback refers to information generated by the processor based on the processing of the third input provided by the user. For example, DSP debug feedback may include a user's description of the effect, performance, or possible problems of the configuration of the current DSP component. DSP debug feedback can be used to help the processor further optimize the DSP component after running.

[0115] As an example, after running the audio equalizer, the user may provide a third input: "After adjusting the low-frequency gain, the low-frequency part of the audio becomes fuzzy and the details are unclear." The third input can be processed by the processor to generate DSP debugging feedback. The processor can further generate debugging suggestion information for optimizing the equalizer settings based on the DSP debugging feedback and send it to the user. For more information about debugging suggestion information, please refer to Figure 3 and its related description.

[0116] Component information refers to information related to specific modules contained in the DSP component. Component information can reflect the configuration and structure of the current DSP component. For example, component information can include the name of each module, the connection relationship between modules, and the parameter settings of each module.

[0117] As an example only, the component information may include "Module 1: equalizer, parameters set to low frequency boost 3dB; Module 2: compressor, parameters set to threshold -10dB, compression ratio 4:1; Module 3: reverb processor, parameters set to room size 50%, dry / wet ratio 70:30. Connection relationship: Module 1, Module 2, and Module 3 are connected in series in sequence."

[0118] Operation information refers to log data generated during the operation of the DSP component. For example, the operation information may include operation logs and / or error logs. The operation log records the normal operation of the DSP component, such as the processed audio data, processing time, etc.; the error log records the abnormalities or errors that occur during the operation.

[0119] For example, a run log may include "2024-09-01 14:35:00: The reverb processor started processing audio, parameter setting was X, and processing time was Y seconds." An error log may include "2024-09-01 14:36:00: The reverb processor was overloaded when processing high frequencies, and audio output was interrupted."

[0120] The processor can obtain component information and operation information in a variety of ways. For example, the processor can extract the required component information by parsing the configuration file in the DSP development system or by using methods such as API function calls. For another example, the processor can also integrate logging functions in the DSP development system to automatically record operation information according to preset levels (such as INFO, DEBUG, WARN, ERROR), or capture and record possible exceptions in the code, and save detailed error information for debugging.

[0121] Debugging suggestion information refers to information that can help or guide users to solve problems related to DSP components. In some embodiments, debugging suggestion information may include but is not limited to abnormal cause analysis and debugging modification suggestions for abnormalities. Debugging suggestion information can help users optimize the configuration of DSP components to achieve the desired effect.

[0122] For example, if the reverb processor is overloaded when processing high frequencies, the debugging suggestion information may include "Exception reason: The reverb processor is overloaded because the parameters are set too high when processing the high frequency band. Suggestion: Reduce the high frequency gain parameters of the reverb processor, or increase processor resources to avoid overload."

[0123] In some embodiments, Figure 3 As shown, based on the third input provided by the user, "Why is there no sound after the low-pass filter?", combined with the component information and / or operation information (not shown in the figure) of the target DSP component, the processor can generate debugging suggestion information. For example, the debugging suggestion information can be the content "suggestion to increase gain" in the dialog box 360.

[0124] In some embodiments, the processor may generate debugging suggestion information in a variety of ways. For example, the processor may determine debugging suggestion information through the second largest language model based on DSP debugging feedback, component information of the target DSP component, and operation information.

[0125] In some embodiments, the input of the second largest language model may include DSP debugging feedback, component information of the target DSP component, and operation information.

[0126] For example, the processor may determine, based on the user's third input, that the DSP debugging feedback is "Why is there no sound after the low-pass filter?"; obtain component information of the target DSP component as "the low-pass filter gain is set to -10dB, and the low-pass filter module is correctly connected to other modules in the signal chain"; and obtain operation information as "operating normally".

[0127] In some embodiments, the output of the second largest language model may include debugging suggestion information. For example, the processor outputs debugging suggestion information "suggesting to increase gain" based on processing the above input.

[0128] In some embodiments, the processor may train a second language model based on a large number of first training samples with first labels.

[0129] The first training sample may include sample DSP debugging feedback in sample historical DSP debugging data, component information and / or operation information of a sample target DSP component.

[0130] During the training process, each sample data is annotated with specific labels, which represent the best tuning actions in the corresponding situation. For example, for the DSP tuning feedback of "muddy bass", the label can be "reduce low frequency gain".

[0131] In some embodiments, the processor may obtain the first label corresponding to the first training sample in various ways, such as by manual labeling.

[0132] In some embodiments, the processor can train the second largest language model in a variety of ways. For example, the processor can input multiple first training samples with first labels into the initial second largest language model, construct a loss function through the results of the first labels and the initial second largest language model, and iteratively update the initial second largest language model based on the loss function. When the preset conditions are met, the model training is completed and the trained second largest language model is obtained. Among them, the preset conditions can be that the loss function converges, the number of iterations reaches a threshold, etc.

[0133] The model gradually improves its ability to understand user feedback by continuously learning the input-output relationship in sample data, and learns to extract key details from DSP debugging feedback, component information, and / or operation information. Through repeated training, the second largest language model can identify various common DSP debugging problems and provide users with accurate debugging suggestions based on similar scenarios.

[0134] The embodiments of this specification generate debugging suggestion information based on DSP debugging feedback, component information and / or operation information of the target DSP component through the second language model and send it to the user, which can efficiently process the user's feedback on the DSP component, analyze the structure and operation status of the DSP component, and generate debugging suggestions with practical operation value. In this way, it not only improves the user experience, but also helps non-professional users to achieve better debugging effects.

[0135] In one or more embodiments of the present specification, the target DSP component generated by the processor can be continuously adjusted and optimized into a new target DSP component until the development requirements of the user are met.

[0136] In some embodiments, after the initial target DSP components are generated, the processor may further adjust the initial target DSP components based on the user's component adjustment requirements.

[0137] The processor can determine the component adjustment requirements based on a variety of methods. In some embodiments, the processor can determine the component adjustment requirements based on the component modification suggestions and user feedback through the first language model. For more information about the first language model, see Figure 2 and its description.

[0138] In some embodiments, the input of the first large language model may further include component effect evaluation.

[0139] In some embodiments, the processor may determine the component adjustment requirements through the first language model based on component modification suggestions, user feedback, user development habits, and component effect evaluation.

[0140] For more information on determining component tuning requirements, see Figure 3 and its related description.

[0141] When determining the component adjustment requirements, the processor in the embodiment of this specification further combines the component effect evaluation, so that the component modification suggestions output by the first language model are directly related to the component effect evaluation, and the output natural language will be more in line with the component effect evaluation, which is conducive to user understanding.

[0142] Figure 4 It is an exemplary diagram of determining the adjustment requirement of a component according to some embodiments of the present specification. In some embodiments, the diagram 400 may be executed by a processor (eg, the processor 150).

[0143] In some embodiments, Figure 4 As shown, the prompt information 223 may also include component modification suggestions 420 ; the second input may also include user feedback 430 on the component modification suggestions 420 ; the processor may be further configured to determine component adjustment requirements 450 based on the component modification suggestions 420 , user feedback 430 and user development habits 440 . In some embodiments, the processor may determine component adjustment requirements 450 based on component modification suggestions 420 , user feedback 430 , user development habits 440 , and component effect evaluations 460 .

[0144] Component modification suggestions refer to DSP component improvement or adjustment suggestions made by the processor to the user based on the effect of the generated target DSP component. Component modification suggestions are in the form of natural language that users can directly understand. For example, after adding a noise suppression module, when the processor runs the target DSP component, it detects that the currently set noise threshold value cannot effectively reduce the background noise, so the processor can generate a component modification suggestion "It is recommended to adjust the noise threshold value from -20dB to -30dB to obtain a better suppression effect."

[0145] In some embodiments, the processor may determine the component modification suggestion of the target DSP component based on a variety of ways. For example, the processor may determine the component modification suggestion of the target DSP component based on the second largest language model.

[0146] In some embodiments, the input of the second largest language model may include component information of the target DSP component and an operation log of the target DSP component. The output of the second largest language model may be a component modification suggestion of the target DSP component.

[0147] For more information about the target DSP components, see Figure 2 and its related descriptions; for more information about components and operation logs, see Figure 3 and its related description.

[0148] It should be noted that when generating component modification suggestions for the target DSP component based on the component information of the target DSP component and the operation log of the target DSP component, the second largest language model needs to be retrained separately.

[0149] In some embodiments, the second largest language model can be obtained by training based on a large number of second training samples with second labels. The second training samples for training the second largest language model can be component information of sample target DSP components in historical development data and operation logs of sample target DSP components.

[0150] The second label may be an actual component modification suggestion corresponding to the second training sample in the historical development data. In some embodiments, the second label may be obtained by manually annotating the actual component modification suggestion.

[0151] In some embodiments, the second language model is trained in the same manner as Figure 3 The training process of the second largest language model is similar, except that the training samples and labels are different. For more information, see Figure 3 The relevant description will not be repeated here.

[0152] In some embodiments, the input of the second largest language model may also include component effect evaluation. For more information about component effect evaluation, please refer to Figure 3 and its related description.

[0153] In some embodiments, the second training sample of the second large language model may further include sample component effect evaluations corresponding to component information of the sample target DSP component and operation information of the sample target DSP component.

[0154] In some embodiments, the sample component effect evaluation can be obtained from a pre-set effect evaluation standard. The pre-set effect evaluation standard may be formulated based on industry specifications, user expectations, or specific application scenarios. For example, for an equalizer module, the effect evaluation standard may include gain accuracy, frequency band coverage, and signal smoothness.

[0155] In some embodiments, the sample component effect evaluation can be obtained based on data generated during the generation of historical DSP components that are similar to the component information and operation information of the sample target DSP components. For example, the sample component effect evaluation can be an evaluation generated by the processor after a performance evaluation of the historical DSP components, or it can be the advantages and disadvantages pointed out by the user based on the effects of the historical DSP components in actual use. In some embodiments, the processor can determine the component modification suggestions for the target DSP component based on the component information of the target DSP component, the operation log of the target DSP component, and the component effect evaluation corresponding to the component information and the operation log, through the trained second language model.

[0156] As an example only, if the component effect evaluation is "the current target DSP component does not work well when processing high-frequency signals", the processor can combine the component information of the target DSP component "the sampling rate is 44.1kHz" and the operation information "the component is running normally" to make component modification suggestions to the user. For example, the component modification suggestion may include "you can try to increase the sampling rate to 96kHz or higher to improve the processing effect of high-frequency signals."

[0157] User feedback refers to user feedback on component modification suggestions. For example, user feedback is an expression of approval, such as "yes", "okay", etc. For another example, user feedback can also be an expression of denial, such as "no need", etc. For another example, user feedback can also be a direct new adjustment language instruction, such as "directly delete the equalizer", etc.

[0158] User development habits refer to the usual behaviors exhibited by users when developing DSP components. For example, user development habits can be the user's tendency to use the order of modules during the development process, such as the user prefers to use module A first, then module B, etc. For another example, user development habits can also be the user's preference settings for the configuration parameters of the module, such as the specific parameter values ​​or configuration schemes that the user prefers to adopt when configuring the module parameters. In some embodiments, when users develop different types of target DSP components, different development habits may exist based on different development needs. For example, taking an equalizer as an example, when the user's development needs correspond to vocal enhancement, the user's development habits for the equalizer are: focusing on the mid-frequency band (about 1kHz to 5kHz) for adjustment, and being accustomed to obtaining a cleaner vocal performance by reducing low and high frequencies. For another example, when the user's development needs correspond to bass enhancement, the user's development habits for the equalizer are: tending to increase the low-frequency band (about 20Hz to 200Hz) to enhance the bass part of the music, and being accustomed to slightly weakening or keeping the mid-frequency band and high-frequency band unchanged to ensure that the impact of the low frequency is maximized.

[0159] In some embodiments, user development habits can be represented in the form of a sequence. As an example, for the same development requirement, user development habits can be represented by {(X1, Y1), (X2, Y2), ..., (X i , Y i ),…,(X n , Y n )} characterization. i Indicates the frequency of users using module i under this development requirement. i Indicates the configuration parameters of module i under this development requirement. The processor can use a value between 0 and 1 to represent the usage frequency X i .X i The larger the value, the higher the user's tendency to use module i. i =0.8 corresponds to the configuration parameter Y of module i i It can be "low frequency band (20Hz-200Hz): +6dB; mid-frequency band (200Hz-1kHz): -1dB; high frequency band (1kHz-20kHz): -1dB", which means that the usage frequency of module i is higher, which is 0.8.

[0160] The processor can determine the user's development habits based on a variety of methods. For example, the processor can determine the user's usage priority for each module and each parameter by performing data analysis on multiple historically developed component information based on a storage device. The user's development habits are determined based on the usage priority.

[0161] The usage priority refers to an indicator that can reflect the user's preference for using a module and / or parameter. For example, the usage priority can be represented by a numerical value, and the larger the numerical value, the higher the usage priority.

[0162] The processor can determine the usage priority based on a variety of methods. In some embodiments, the higher the usage frequency of a module / parameter, the higher the priority of the corresponding module and the priority of the parameter.

[0163] For example, for the same development requirement, the processor can analyze historical development data to count the frequency of users' use of different modules in the historical development process, and sort the use frequency from high to low to indicate the use priority, so as to determine the user's development habits for the preferred modules. For another example, the processor can also analyze historical development data to count all the user's configuration schemes for module A parameters in the historical development process, and sort the use frequency from high to low to indicate the use priority, so as to determine the user's development habits for the configuration parameters of module A.

[0164] In some embodiments, when analyzing historical development data, the processor may set a weight for the usage frequency of each module. The closer to the current time, the higher the weight corresponding to the usage frequency of the module in the historical time period. The processor may re-count the usage frequency of different modules by users in the historical development process based on the determined weights, and update the usage priority by sorting the weighted usage frequencies from high to low to determine the user development habits for the preferred modules.

[0165] In some embodiments, the user's development habits can be determined based on historical development data through a development habit model, which can be a machine learning model. For more information about the development habit model, see Figure 5 and its related description.

[0166] The processor of the embodiment of this specification can actively provide component adjustment requirements to the user based on component modification suggestions, user feedback and user development habits. On the one hand, it enables the user to directly obtain optimization suggestions, reducing the time for manual debugging and repeated adjustments. The user can achieve the target configuration in a shorter time, thereby speeding up the development process; on the other hand, it ensures that the component adjustment requirements provided by the DSP development system are more in line with the user's development goals and operating habits, thereby improving the user's usage experience.

[0167] Figure 5 is an exemplary schematic diagram of a habit development model according to some embodiments of the present specification.

[0168] The development habit model refers to a model used to determine the user's development habits. In some embodiments, the development habit model can be a machine learning model. For example, the development habit model can include a neural network (NN) model, etc.

[0169] In some embodiments, Figure 5 As shown, the input of the development habit model 530 may include historical development data 540 , and the output may be user development habits 550 .

[0170] Historical development data refers to historical records and data related to the user's DSP component development process. For example, historical development data may include historical development component information, historical operation information, etc.

[0171] For more information about components and operation, see Figure 3 and its related description.

[0172] In some embodiments, Figure 5 As shown, the development habit model 530 can be obtained by training the initial development habit model 520 based on a large number of third training samples 510 with third labels.

[0173] The third training sample for training the development habit model may be sample historical development data. The third label may be the actual user development habit corresponding to the sample historical development data. The third label may be obtained in a variety of ways. For example, the third label may be obtained by manually annotating the actual user development habit.

[0174] In some embodiments, the processor may train the development habit model through multiple rounds of iterations: in each round of iterations, the processor inputs the training sample into the initial prediction model and obtains the output, then calculates the loss function value based on the model output and the label, and uses the back propagation algorithm (e.g., gradient descent method) to update the parameters to minimize the loss. Iterations are performed until the end condition is met and the model training ends, obtaining a trained development habit model. The end condition may include reaching a specified number of iterations or the loss function converges.

[0175] In some embodiments, the processor may determine component adjustment requirements based on component modification suggestions, user feedback, and user development habits.

[0176] The development habit model in the embodiments of this specification can accurately identify and understand the user's recurring behavior patterns and preferences during the development process by analyzing the user's historical development data. This accuracy ensures that the system can effectively capture the user's personalized needs, thereby providing subsequent development with component adjustment requirements that are more in line with user habits.

[0177] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to this specification. Such modifications, improvements and corrections are suggested in this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0178] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0179] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

[0180] Similarly, it should be noted that in order to simplify the description disclosed in this specification and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the subject matter of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0181] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of this specification are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0182] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification are hereby incorporated by reference in their entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this specification (currently or later attached to this specification) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0183] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. A DSP development method, the method being executed by a processor, characterized in that: The method comprises: Determining the development requirements of the user based on the first input of the user; the development requirements include functional requirements, module setting requirements and / or parameter setting requirements for the DSP component; Based on the development requirements, target DSP components and prompt information are generated and displayed, and the prompt information includes generation result prompts and / or component effect evaluations.

2. The method according to claim 1, characterized in that The method further comprises: Based on the second input of the user, determining the component adjustment requirement of the user for the target DSP component; Based on the component adjustment requirement, the target DSP component is adjusted.

3. The method according to claim 2, characterized in that The prompt information also includes component modification suggestions; The second input also includes user feedback from the user regarding the component modification suggestion; The determining, based on the second input of the user, the component adjustment requirement of the user for the target DSP component comprises: Based on the component modification suggestions, the user feedback and the user development habits, the component adjustment requirements are determined; wherein, The user development habits are based on historical development data and are determined by a development habit model, and the development habit model is a machine learning model.

4. The method according to claim 1, characterized in that: The method further comprises: Determine DSP debugging feedback based on the third input of the user; Based on the DSP debugging feedback, component information and / or operation information of the target DSP component, debugging suggestion information is generated and sent to the user.

5. A DSP development system, the system being executed by a processor, characterized in that: The system comprises: A determination module is configured to determine the development requirements of the user based on the first input of the user; the development requirements include functional requirements, module setting requirements and / or parameter setting requirements for the DSP component; The prompt module is configured to generate and display the target DSP component and prompt information based on the development requirements, wherein the prompt information includes generation result prompts and / or component effect evaluations.

6. The system according to claim 5, characterized in that: The determination module is further configured to: Based on the second input of the user, determining the component adjustment requirement of the user for the target DSP component; Based on the component adjustment requirement, the target DSP component is adjusted.

7. The system according to claim 6, characterized in that The prompt information also includes component modification suggestions; The second input also includes user feedback from the user regarding the component modification suggestion; The determination module is further configured to: Based on the component modification suggestions, the user feedback and the user development habits, the component adjustment requirements are determined; wherein, The user development habits are based on historical development data and are determined by a development habit model, and the development habit model is a machine learning model.

8. The system according to claim 5, characterized in that The determination module is further configured to: Determine DSP debugging feedback based on the third input of the user; Based on the DSP debugging feedback, component information and / or operation information of the target DSP component, debugging suggestion information is generated and sent to the user.

9. A DSP development method device, comprising a processor, characterized in that: The processor is used to execute the DSP development method according to any one of claims 1 to 4.

10. A computer-readable storage medium storing computer instructions, characterized in that: After the computer reads the computer instructions in the storage medium, the computer executes the DSP development method as claimed in any one of claims 1 to 4.

Images