Audiobook recording collaborative management methods, devices, equipment and products
By establishing a two-way communication link between the recording end and the cloud platform, and using a tree structure to display dialogue data and perform consistency analysis, the problem of data disconnect between the cloud and the recording end in audiobook recording is solved. This enables automated management of recording progress and data integrity, thereby improving recording efficiency.
Patent Information
- Application Number
- CN202611312938.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-27
- Publication Date
- 2026-11-17
AI Technical Summary
In the current audiobook recording process, cloud data is disconnected from the recording end, there is a lack of a global shortcut key focus awareness mechanism, the recording operation lacks timing compensation methods, and audio files need to be manually exported and uploaded, resulting in low reliability and efficiency.
By establishing a two-way communication link between the recording end and the cloud platform, using a tree structure to display dialogue data, automatically obtaining audio file paths and performing consistency analysis, the system enables offline uploading and intelligent management of audio files, eliminates mechanical noise, and ensures data integrity.
It realizes a real-time recording workflow for injecting dialogue data, automates the management of recording progress, improves recording efficiency, ensures data integrity and reliability, and avoids tedious steps of repeated transmission and manual operation.
Smart Images

Figure CN123115064A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of digital audio processing technology, and in particular to a method, apparatus, device, and product for collaborative management of audiobook recording. Background Technology
[0002] Current audiobook recording typically involves voice actors recording line by line in a digital audio workstation (DAW, such as Adobe Audition) with the help of an external script. During recording, actors need to frequently switch between a browser or document and the DAW to view the script and manually perform recording operations. The status management of the script segments relies on manual memory or external spreadsheets. When recording starts and stops, the mechanical noise generated by keyboard typing is often captured by the microphone and mixed into the beginning and end of the audio. After recording is completed, the audio files need to be manually exported, named, and archived, and then uploaded to the cloud platform one by one through a webpage or client. In addition, due to the lack of a global shortcut key focus awareness mechanism, shortcut keys may become invalid or be accidentally triggered when switching between different application windows, affecting the recording rhythm.
[0003] However, the aforementioned existing technologies have significant shortcomings. First, there is a data gap between the host software and the cloud platform, making it impossible to inject cloud-based dialogue data into the DAW workflow in real time and synchronize the recording status in reverse. Second, the recording operation lacks compensation methods for timing deviations between keyboard presses / releases and audio transmission start / stop, making it difficult to effectively eliminate mechanical noise. Third, the temporary documents frequently generated within the DAW during the recording process require manual operation by the user for saving, sound effect processing, and closing, lacking intelligent pipeline management. Finally, there is a lack of reliable local persistence, deduplication verification, and concurrent retry mechanisms after audio file upload failures, seriously affecting the integrity of data transmission and work efficiency.
[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention
[0005] The main purpose of this application is to provide a collaborative management method, device, equipment, and product for audiobook recording, which aims to solve the technical problem of insufficient reliability in existing audiobook recordings due to the disconnect between cloud data and the recording end and the need to manually export and upload audio files.
[0006] To achieve the above objectives, this application proposes an audiobook recording collaborative management method, which is applied at the recording end and includes: According to the preset communication protocol, the audiobook dialogue data is obtained from the cloud platform, and the audiobook dialogue data is displayed in a tree structure according to the login information of the recording terminal. Receive user selection instructions for the tree structure, and display dialogue text and character metadata according to the selection instructions; Obtain the audio file path according to the user's recording instructions, and add the audio file path to the offline upload queue; A consistency analysis is performed between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. If the analysis result is inconsistent, the audio file path is uploaded to the cloud, and the recording status of the audiobook dialogue data is updated.
[0007] In one embodiment, the recording terminal includes recording software, and the step of obtaining the audio file path according to the user's recording instructions includes: In response to a recording command sent by the user, the recording software is determined to be the active window through focus detection, and recording is performed through the software script engine of the recording software; If a stop or submit command is received during the recording process of the software script engine, the recording is stopped, and the timing compensation offset is calculated based on the operation duration of the command. The compensation audio range is determined based on the timing compensation offset, and the compensation audio range is repaired using the effects processor of the recording software to obtain the repaired audio. The repaired audio is then processed with sound effects. After the sound effects processing is completed, the target file corresponding to the repaired audio is converted to the target format and the target file is saved to a local folder to obtain the audio file path.
[0008] In one embodiment, the step of determining the recording software as the active window through focus detection includes: Obtain the process name of the foreground window of the recording terminal, and compare the process name with the software name of the recording software; If the process name is the same as the software name, then obtain the real-time interface status of the recording software; When the real-time interface is in the recording interface state, obtain the script engine state of the recording software; If the script engine is in a ready state, then the recording software is determined to be an active window.
[0009] In one embodiment, the step of calculating the timing compensation offset based on the instruction operation duration includes: Record the first timestamp corresponding to the recording instruction, and record the second timestamp of the stop instruction or submit instruction; The instruction operation duration is calculated based on the difference between the first timestamp and the second timestamp; The operation time of the instruction is compared with the manual deviation value to obtain the comparison result, and the initial offset is determined based on the comparison result. Determine whether the initial offset exceeds the repair upper limit. If it exceeds the limit, then the repair upper limit value is determined to be the timing compensation offset; If the initial offset is not exceeded, then the initial offset is determined to be the timing compensation offset.
[0010] In one embodiment, the step of performing sound effects processing on the repaired audio includes: Obtain the sound effect processing chain corresponding to the login information; The repaired audio is processed using the aforementioned audio processing chain; Monitor the processing status of the sound effect processing chain. When the sound effect processing is completed, save the sound effect processing result and close the temporary file corresponding to the sound effect processing chain.
[0011] In one embodiment, the step of adding the audio file path to the offline upload queue includes: The queue data corresponding to the audio file path is encrypted to obtain encrypted data, and the encrypted data is stored in a local queue file; The local queue file is scanned by a timer to obtain queue items whose task status is "waiting". The waiting queue items are uploaded according to the preset number of parallel uploads; After successful upload, update the task status to "completed". If the upload fails, the task status will be updated to "failed".
[0012] In one embodiment, the step of performing consistency analysis on the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform includes: The cloud fingerprint value corresponding to the audiobook dialogue data is obtained through the query interface provided by the cloud platform. The local file corresponding to the audio file path is streamed to obtain audio data blocks; The audio data block is hashed to obtain a local file fingerprint value. Consistency analysis is then performed using the local file fingerprint value and the cloud fingerprint value to obtain the consistency analysis result.
[0013] Furthermore, to achieve the above objectives, this application also proposes an audiobook recording collaborative management device, which is applied at the recording end and includes: The display module is used to obtain audiobook dialogue data from the cloud platform according to a preset communication protocol, and display the audiobook dialogue data in a tree structure according to the login information of the recording terminal. The selection module is used to receive the user's selection instruction for the tree structure and display the dialogue text and character metadata according to the selection instruction. The recording module is used to obtain the audio file path according to the user's recording instructions and add the audio file path to the offline upload queue; The analysis module is used to perform consistency analysis between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. When the analysis result is inconsistent, the audio file path is uploaded to the cloud and the recording status of the audiobook dialogue data is updated.
[0014] In addition, to achieve the above objectives, this application also proposes an audiobook recording collaborative management device, the device comprising: 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 audiobook recording collaborative management method as described above.
[0015] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the audiobook recording collaborative management method described above.
[0016] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the audiobook recording collaborative management method described above.
[0017] One or more technical solutions proposed in this application have at least the following technical effects: This application proposes an audiobook recording collaborative management method, apparatus, device, and product. It acquires audiobook dialogue data from a cloud platform according to a preset communication protocol and displays the audiobook dialogue data in a tree structure based on the login information of the recording terminal. It receives user selection instructions for the tree structure and displays the dialogue text and character metadata based on the selection instructions. It acquires the audio file path according to the user's recording instructions and adds the audio file path to an offline upload queue. It performs consistency analysis between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. If the analysis result is inconsistent, it uploads the audio file path to the cloud and updates the recording status of the audiobook dialogue data. Therefore, by retrieving audiobook dialogue data from the cloud platform according to a preset communication protocol and displaying it in a tree structure, the problem of disconnect between cloud data and the recording end in existing technologies is solved. This allows dialogue data to be directly injected into the recording workflow. Subsequently, the audio file path is automatically obtained according to the recording instructions and added to the offline upload queue, replacing the tedious operations of manually exporting, naming, archiving, and uploading one by one. Finally, by performing consistency analysis on the fingerprint values of local files and cloud fingerprint values, the upload is only performed when the analysis results are inconsistent, avoiding duplicate transmissions and ensuring data integrity. This achieves automated management of the recording progress, solves the problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording and the need for manual export and upload of audio files, and improves the efficiency of collaborative management of audiobook recording. 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 an embodiment of the collaborative management method for audiobook recording provided in this application. Figure 2 This is a flowchart illustrating Embodiment 2 of the collaborative management method for audiobook recording in this application. Figure 3 A simplified flowchart illustrating the collaborative management method for audiobook recording provided in Embodiment 2 of this application; Figure 4 This is a schematic diagram of the module structure of the audiobook recording collaborative management device according to an embodiment of this application; Figure 5This is a schematic diagram of the device structure of the hardware operating environment involved in the audiobook recording collaborative management method in this application embodiment.
[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] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.
[0023] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.
[0024] The main solution of this application embodiment is as follows: In response to a recording command sent by the user, the recording software is determined to be an active window through focus detection, and recording is performed through the software script engine of the recording software; if a stop command or submit command is received during the recording process of the software script engine, the recording is stopped, and a timing compensation offset is calculated based on the command operation duration; a compensation audio range is determined based on the timing compensation offset, and the compensation audio range is repaired through the effects processor of the recording software to obtain repaired audio; sound effects processing is performed on the repaired audio; after the sound effects processing is completed, the target file corresponding to the repaired audio is converted to a target format, and the target file is saved to a local folder to obtain the audio file path. The process name of the foreground window of the recording terminal is obtained, and the process name is compared with the software name of the recording software; if the process name and the software name are consistent, the real-time interface state of the recording software is obtained; when the real-time interface state is the recording interface, the script engine state of the recording software is obtained; if the script engine state is ready, the recording software is determined to be an active window. Record the first timestamp corresponding to the recording instruction, and record the second timestamp of the stop instruction or submit instruction; calculate the instruction operation duration based on the difference between the first and second timestamps; compare the instruction operation duration with the manual deviation value to obtain a comparison result, and determine the initial offset based on the comparison result; determine whether the initial offset exceeds the repair upper limit value; if it exceeds, determine the repair upper limit value as the timing compensation offset; if it does not exceed, determine the initial offset as the timing compensation offset. Obtain the audio effect processing chain corresponding to the login information; perform audio effect processing on the repaired audio through the audio effect processing chain; monitor the processing status of the audio effect processing chain, and when the audio effect processing is completed, save the audio effect processing result and close the temporary file corresponding to the audio effect processing chain. The queue data corresponding to the audio file path is encrypted to obtain encrypted data, and the encrypted data is stored in a local queue file. A timer scans the local queue file to obtain queue items with a waiting task status. The waiting queue items are uploaded according to a preset parallel upload count. Upon successful upload, the task status is updated to "completed"; upon failed upload, the task status is updated to "failed". The cloud fingerprint value corresponding to the audiobook dialogue data is obtained through the query interface provided by the cloud platform. The local file corresponding to the audio file path is streamed to obtain audio data blocks. A hash calculation is performed on the audio data blocks to obtain a local file fingerprint value. Consistency analysis is performed using the local file fingerprint value and the cloud fingerprint value to obtain the consistency analysis result.This invention solves the problems of insufficient reliability in existing audiobook recording, such as the disconnect between cloud data and the recording end, and the need for manual export and upload of audio files. It achieves collaborative management of audiobook recording, improving management efficiency. Based on this invention, addressing the real-world issues of data gaps between host software and cloud platforms, preventing real-time injection of cloud-based dialogue data into the DAW workflow and reverse synchronization of recording status, and the lack of compensation mechanisms for timing discrepancies between keyboard presses / releases and audio transmission start / stop, leading to ineffective elimination of mechanical noise and low efficiency, this invention designs a collaborative management method for audiobook recording. The effectiveness of this method is verified during collaborative management of audiobook recording, and the efficiency of collaborative management of audiobook recording is significantly improved.
[0025] In this embodiment, for ease of description, the following description will focus on the audiobook recording collaborative management device as the implementing entity.
[0026] Due to the limitations of existing audiobook recording collaborative management methods, recording efficiency needs improvement. One issue is data disconnect: the lack of data communication between the host software and the cloud platform prevents real-time injection of cloud-based dialogue data into the recording workflow and reverse synchronization of the recording status. This necessitates frequent window switching to view dialogue during recording, reducing efficiency. Another issue is the lack of timing compensation: the recording process lacks compensation for timing discrepancies between keyboard presses and audio transmission start / stop, making it difficult to effectively eliminate keyboard mechanical noise, requiring manual post-production repair and significantly reducing efficiency. Furthermore, there's the issue of manual operation: the frequent generation of temporary documents within the DAW during recording requires manual user intervention for saving, sound effect processing, and closing, lacking intelligent pipeline management, which also impacts recording efficiency. Therefore, current recording methods also face challenges in upload reliability: the lack of reliable local persistence, deduplication verification, and concurrent retry mechanisms after audio file upload failures severely affects data transmission integrity and work efficiency.
[0027] This application provides a solution that retrieves audiobook dialogue data from a cloud platform according to a preset communication protocol and displays it in a tree structure. This solves the problem of disconnect between cloud data and the recording end in existing technologies, allowing dialogue data to be directly injected into the recording workflow. Subsequently, the audio file path is automatically obtained according to the recording instructions and added to the offline upload queue, replacing the tedious operations of manually exporting, naming, archiving, and uploading one by one. Finally, by performing consistency analysis on the fingerprint values of local files and cloud fingerprint values, the upload is only performed when the analysis results are inconsistent, avoiding duplicate transmissions and ensuring data integrity. This achieves automated management of the recording progress, solves the problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording and the need for manual export and upload of audio files, and improves the efficiency of collaborative management of audiobook recording.
[0028] Based on this, the embodiments of this application provide a collaborative management method for audiobook recording, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the collaborative management method for audiobook recording in this application.
[0029] In this embodiment, the audiobook recording collaborative management method is applied to the recording end, and the audiobook recording collaborative management method includes steps S01~S04: Step S01: Obtain audiobook dialogue data from the cloud platform according to the preset communication protocol, and display the audiobook dialogue data in a tree structure according to the login information of the recording terminal; Before describing the solution in this embodiment, it should be clear that there is a data gap between the host software and the cloud platform, making it impossible to inject cloud-based dialogue data into the DAW workflow in real time and synchronize the recording status in reverse. Secondly, the recording operation lacks compensation methods for timing deviations between keyboard presses / releases and audio transmission start / stop, making it difficult to effectively eliminate mechanical noise. Furthermore, the temporary documents frequently generated within the DAW during the recording process require manual operation by the user for saving, sound effect processing, and closing, lacking intelligent pipeline management. Finally, there is a lack of reliable local persistence, deduplication verification, and concurrent retry mechanisms after audio file upload failures, which seriously affects the integrity of data transmission and work efficiency.
[0030] Therefore, in order to solve the above problems, this embodiment establishes a two-way communication link between the recording end and the cloud audiobook production platform based on the preset REST communication protocol. It completes identity verification and permission matching based on the exclusive login information of the recording end user, and accurately retrieves the original dialogue data of all audiobook projects within the current logged-in user's permission range.
[0031] The massive amount of dialogue data was structurally decomposed and hierarchically reconstructed. It was classified, integrated, and visualized according to a three-level tree structure of "book - chapter - dialogue paragraph". Each line of dialogue was synchronously associated with metadata such as character name, gender, voice description, dialogue text, recording status, emotional tone, and performance action prompts.
[0032] The interface provides a three-level linked navigation view of book list, chapter list, and dialogue list. It supports filtering by recording status, by character, by chapter number and title, and by book title and notes. It also supports sorting by progress indicators such as number of incomplete paragraphs, total number of paragraphs, and effective duration.
[0033] The system uses a polling mechanism every minute to retrieve cloud feedback requests and error corrections, which are then presented as notification dots and message lists. Users can click on a message to jump directly to the corresponding dialogue.
[0034] Whenever a single line of dialogue is recorded locally or the status changes, the system automatically synchronizes the status to the cloud platform via an HTTP request, ensuring that the cloud data is consistent with the local progress. This completely breaks down the data barrier between the cloud dialogue data and the local recording end. In this embodiment, the system can not only receive HTTP requests but also support HTTPS encrypted security requests. Based on the transport layer security protocol, it encrypts the transmission of various interactive data such as status synchronization, message notifications, and audio uploads, preventing data from being stolen, tampered with, or leaked during transmission over the public network. This is suitable for audiobook production projects with high data security requirements. It can automatically adapt to HTTP or HTTPS communication modes according to the cloud platform's interface configuration and the actual network environment. While ensuring real-time data exchange between the cloud and local systems, it also takes into account the security level requirements of different deployment scenarios, further improving the reliability and security of data transmission during collaborative recording.
[0035] Step S02: Receive the user's selection instruction for the tree structure, and display the dialogue text and character metadata according to the selection instruction; Then, the system monitors the user's clicks and shortcut key selections related to the tree-like dialogue structure in real time, accurately captures the user's selection commands, and completes command parsing.
[0036] Based on the parsed location information, the system quickly retrieves and displays the complete text of the target dialogue. Simultaneously, a pop-up window on the recording interface displays all the character metadata corresponding to the dialogue, including core information such as character gender, voice description, performance tone, action prompts, and reasons for backsound. At the same time, the system updates and displays the current recording progress and status tags of the dialogue in real time, providing complete data support for users to accurately record and standardize the performance of dialogue.
[0037] Step S03: Obtain the audio file path according to the user's recording instructions, and add the audio file path to the offline upload queue; It continuously monitors user-triggered recording start, pause, and submit commands on the recording end, and works with the Adobe Audition host software's script engine to complete automated recording tasks, eliminating the need for users to manually manipulate audio files or adjust recording parameters throughout the process.
[0038] After a single dialogue recording is completed, the system automatically identifies the storage path of the locally saved audio file, accurately captures the valid audio file path information, and simultaneously encapsulates the recording task corresponding to the audio path into standardized queue data. This data is then added to the local offline upload waiting queue in an orderly manner, completing the initial archiving and upload preparation work for the recording task.
[0039] Step S04: Perform a consistency analysis on the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. If the analysis result is inconsistent, upload the audio file path to the cloud and update the recording status of the audiobook dialogue data.
[0040] Based on the data query interface opened by the cloud platform, the fingerprint verification data of the cloud audio file corresponding to the currently recorded lines is accurately retrieved. At the same time, the target audio file that has been saved locally is read in a streaming block, and a unique fingerprint value of the local audio file is generated by calculating block by block based on the hash algorithm.
[0041] By comparing two sets of fingerprint values, one local and one cloud, data consistency verification is completed, accurately determining whether there are any abnormalities such as content modification, missing information, or damage in the local audio file.
[0042] If the two sets of fingerprint values are inconsistent, the local audio is determined to be the latest valid recording file, and the cloud upload process is automatically triggered. After the upload is completed, the recording status of the corresponding lines in the cloud is updated synchronously and marked as recorded, pending review, or completed.
[0043] If the fingerprint values match, it is determined that the audio content has not been updated, and the duplicate upload operation is skipped directly, thus achieving data deduplication and efficient synchronization.
[0044] This system retrieves audiobook dialogue data from the cloud platform according to a preset communication protocol and displays it in a tree structure, solving the problem of data disconnect between the cloud and the recording end in existing technologies. This allows the dialogue data to be directly injected into the recording workflow. Subsequently, the audio file path is automatically obtained according to the recording instructions and added to the offline upload queue, replacing the tedious operations of manually exporting, naming, archiving, and uploading one by one. Finally, by performing consistency analysis on the fingerprint values of local files and cloud files, the upload is only performed when the analysis results are inconsistent, avoiding duplicate transmissions and ensuring data integrity, thus achieving automated management of the recording progress.
[0045] Specifically, the recording terminal mentioned above includes recording software, and step S03, the step of obtaining the audio file path according to the user's recording instructions, includes: Step S031: In response to the recording command sent by the user, the recording software is determined to be an active window through focus detection, and recording is performed through the software script engine of the recording software; Step S032: If a stop command or a submit command is received during the recording process of the software script engine, the recording is stopped, and the timing compensation offset is calculated based on the command operation duration. Step S033: Determine the compensation audio range based on the timing compensation offset, and repair the compensation audio range using the effects processor of the recording software to obtain the repaired audio; Step S034: Perform sound effect processing on the repaired audio; Step S035: After the sound effect processing is completed, the target file corresponding to the repaired audio is converted to the target format and the target file is saved to a local folder to obtain the audio file path.
[0046] In this embodiment, the entire audio recording and file generation process relies on the dual runtime architecture of the Adobe Audition CEP plugin. It combines the system monitoring capabilities of the Node.js runtime with the host software control capabilities of the ExtendScript runtime to complete the entire automated operation, completely replacing manual recording operations.
[0047] It monitors user-triggered recording commands in real time, activates a cross-platform window focus detection mechanism, accurately identifies the currently active foreground window, and only starts the formal recording job when it is confirmed that the Adobe Audition host software is the active foreground window, the software recording interface is loaded normally, and the internal script engine is ready and available, thus preventing background recording errors and invalid recording issues.
[0048] Before the recording job starts, the system first executes the intelligent document activation logic, which searches for and activates the corresponding document in the already opened documents according to the target audio file name. If it does not exist, it automatically opens the local audio file, realizing the separation and management of multiple documents for original audio and temporary recorded audio throughout the process.
[0049] The recording start and stop phase encapsulates underlying commands such as recording and stopping transmission, and synchronously executes selection area clearing and playback head reset operations to ensure that each recording starts from the correct playback head position. The entire recording job is autonomously driven by the host software's built-in script engine, which accurately controls the timing of audio recording start and stop, and completely captures the user's voice-over.
[0050] When the system detects that the user has triggered a recording stop or content submission operation, the audio recording process is immediately terminated. The system simultaneously records the duration of all instruction operations during the entire recording process. Combined with preset deviation parameters and repair thresholds, the system intelligently calculates the precise timing compensation offset.
[0051] Based on the calculated offset, the abnormal section at the end of the audio caused by keyboard typing noise is accurately located. The host software's automatic repair effect is then invoked to repair the tail sound of the abnormal section, eliminating clicks and pops, and ensuring the purity of the dry audio.
[0052] After noise repair is complete, an asynchronous save pipeline driven by the AuDocument.BUSY event is initiated, executing state transitions sequentially through a Promise chaining mechanism. The save pipeline defines four states: copyToNew (copy audio to a new document), handleFavorite (apply dry audio processing to favorites), saveDoc (format as MP3 and persist), and backToRecord (switch back to placeholder audio). Each state is encapsulated as an independent Promise, and chained calls using .then() ensure that operations are executed in order. When the BUSY event is triggered and the document ID matches, the state machine automatically jumps to the next operation.
[0053] The pipeline in this embodiment supports both foreground and background modes. In background mode, the dry audio processing is performed in the background, and the user can continue to view and locate the next line of dialogue. The system manages the lifecycle of the background asynchronous operation through a Map object with the document ID as the key. After processing is completed, the system automatically saves and closes the temporary document. In foreground mode, all operations are executed synchronously, and the user waits for the processing to complete.
[0054] The audio processing uses a user-preset Audition custom favorites audio chain, which covers standardized processing procedures such as noise reduction, compression, noise elimination (such as removing saliva) and equalization.
[0055] Once all processing is complete, the system automatically converts the audio file to MP3 format and writes metadata information, neatly saves it to a dedicated local storage folder, generates a traceable standard audio file storage path, and then automatically closes the temporary document, switches back to the placeholder audio, and deletes the processed content, completing the entire process of recording, repairing, processing, and archiving a single segment of dialogue audio.
[0056] If the user enables continuous recording mode, after submitting the current sentence, the system will automatically jump to the next unrecorded line, waiting for the user to trigger the next recording.
[0057] More specifically, step S031 above, the step of determining the recording software as the active window through focus detection, includes: Step S0311: Obtain the process name of the foreground window of the recording terminal, and compare the process name with the software name of the recording software. Step S0312: If the process name is the same as the software name, then obtain the real-time interface status of the recording software. Step S0313: When the real-time interface is in the recording interface state, obtain the script engine state of the recording software. Step S0314: If the script engine is in a ready state, then the recording software is determined to be an active window.
[0058] To eliminate the problem of accidental or invalid triggering of global shortcut keys at the source, the system is equipped with a cross-platform window focus precision detection mechanism to ensure the effectiveness and stability of the recording operation throughout the process.
[0059] On the Windows platform, a pre-compiled native executable is called to obtain the process name of the foreground window through the system API and compare it with the Adobe Audition process name list. On the macOS platform, the foreground application name is obtained by executing an AppleScript and the comparison is completed. The detection result is used as a precondition for handling shortcut key events in the form of an asynchronous Promise.
[0060] After a global shortcut key event is triggered, the actual operation is executed only after passing through three levels of condition filtering: The first level is focus filtering, which determines whether the host software is the currently active window; if not, the event is discarded directly. The second level is status filtering, which determines whether the user is in the recording interface and has not opened the settings pop-up. If the conditions are not met, the event is discarded. The third level is engine readiness filtering, which uses a script to query whether the host software commands are available and confirm that the internal engine is ready.
[0061] Adobe Audition is only considered a valid and active recording window when all three conditions are met: window process matching, interface state compliance, and script engine readiness. Only then will the system recognize and execute the recording shortcut key commands triggered under these conditions. All shortcut key operations in other non-compliant scenarios are automatically intercepted and discarded, effectively avoiding recording disorder issues during window switching.
[0062] This embodiment also has the ability to automatically recover from shortcut key failure: First, maintain a counting threshold, with a default threshold of 200 times. The counter increments each time a non-pressed key event is detected. If the counter exceeds the threshold, the global keyboard listener is deemed invalid, and the rebuild process is automatically triggered, unregistering the old listener and re-instantiating and registering the callback.
[0063] The system synchronously monitors application activation events of the host software, automatically updating the internal focus status flag when a window switches from inactive to active. Furthermore, the system supports user-defined shortcut key combinations, is compatible with modifier keys such as Ctrl and Shift, provides a visual configuration interface, and performs uniqueness checks on each group of shortcut keys and general shortcut keys to prevent key conflicts. Recorded shortcut keys also support key press duration measurement to complement the keyboard sound compensation mechanism.
[0064] Further, step S032 above, the step of calculating the timing compensation offset based on the instruction operation duration, includes: Step S0321: Record the first timestamp corresponding to the recording instruction, and record the second timestamp of the stop instruction or submit instruction; Step S0322: Calculate the instruction operation duration based on the difference between the first timestamp and the second timestamp; Step S0323: Compare the instruction operation time with the manual deviation value to obtain the comparison result, and determine the initial offset based on the comparison result; Step S0324: Determine whether the initial offset exceeds the repair upper limit value; Step S0325: If the value exceeds the limit, then the repair upper limit value is determined to be the timing compensation offset. Step S0326: If the initial offset is not exceeded, then the initial offset is determined to be the timing compensation offset.
[0065] This embodiment employs a timing compensation algorithm that uses real-time key press duration monitoring and dynamic threshold constraints. It supports three compensation schemes: no compensation, automatic mode, and manual mode, accurately eliminating timing deviations between keyboard operations and audio recording.
[0066] The moment a user triggers the recording stop or submit operation, the system immediately captures and records the current high-precision timestamp as the operation end timestamp. Combined with the start timestamp recorded when recording started, the system accurately calculates the duration of the shortcut key press by using the difference between the two. This duration truly reflects the physical interval from the keycap being pressed to its complete release, corresponding to the main time window of the keyboard impact sound.
[0067] In automatic mode, the system compares the measured key operation duration with the user-preset manual deviation value, taking the smaller value as the initial timing offset compensation amount, balancing the accuracy of the measured values with the user's customized adaptation needs. Simultaneously, the system has a built-in fixed automatic repair upper limit parameter, with a default value of 1000 milliseconds, to perform compliance checks on the initial offset amount, including: If the initial offset value exceeds the repair limit, in order to avoid over-repair leading to loss of original audio quality, the system will automatically use the repair limit as the final timing compensation offset.
[0068] If the initial offset does not exceed the threshold range, the initial offset is used directly as the final compensation parameter. In manual mode, the user-preset fixed deviation value is used directly for compensation; in no-compensation mode, the tail note repair step is skipped.
[0069] After the compensation and repair are completed, the system will automatically back off by a very small distance, which is 0.001 times the duration corresponding to the sampling rate, to avoid audio gaps between adjacent recording segments and ensure the continuity of audio during continuous recording.
[0070] Furthermore, step S034 above, the step of performing sound effect processing on the repaired audio, includes: Step S0341: Obtain the sound effect processing chain corresponding to the login information; Step S0342: Perform sound effect processing on the repaired audio through the sound effect processing chain; Step S0343: Monitor the processing status of the sound effect processing chain. When the sound effect processing is completed, save the sound effect processing result and close the temporary file corresponding to the sound effect processing chain.
[0071] Based on Adobe Audition's customizable favorites mechanism, a personalized audio processing chain is configured for different logged-in users. Users can preset audio processing combinations according to their dubbing style and production standards. The core includes three basic processing operations: noise reduction, compression, and equalization. In addition, personalized settings can be made, such as removing saliva. Specifically, the corresponding audio processing chain can be loaded when the user logs in, supporting single or multiple processes to meet the dry audio standardization processing needs of different scenarios.
[0072] After the audio file recording and repair are completed, the system automatically retrieves the audio effect processing chain parameters of the favorites bound to the currently logged-in account and calls the host software's effects processor to perform one-click standardization processing on the target audio file.
[0073] The processing is driven by the AuDocument.BUSY event. The system registers a BUSY event listener. When the document performs time-consuming operations such as sound effect processing, the isBusy property is flipped. The event carries the corresponding document ID. When the event is triggered and the document ID matches, the system automatically determines that the sound effect processing is complete and seamlessly advances to the next format conversion operation through the Promise chain.
[0074] The system monitors the operation status and progress of the audio processing chain in real time throughout the entire process, dynamically tracks the execution of each audio processing operation, and automatically closes the temporary audio files and cache files corresponding to the audio processing after all audio optimization processes are completed and the audio processing is completely finished. This releases the device's running memory and storage resources, avoids redundant files from accumulating and occupying space, and affects subsequent recording operations, while ensuring the cleanliness and standardization of the audio file processing workflow.
[0075] This embodiment, through the above-described scheme, specifically acquires audiobook dialogue data from a cloud platform according to a preset communication protocol, and displays the audiobook dialogue data in a tree structure based on the login information of the recording terminal; receives user selection instructions for the tree structure, and displays the dialogue text and character metadata according to the selection instructions; acquires the audio file path according to the user's recording instructions, and adds the audio file path to an offline upload queue; performs consistency analysis on the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform, and uploads the audio file path to the cloud when the analysis result is inconsistent, and updates the recording status of the audiobook dialogue data. Therefore, by retrieving audiobook dialogue data from the cloud platform according to a preset communication protocol and displaying it in a tree structure, the problem of disconnect between cloud data and the recording end in existing technologies is solved. This allows dialogue data to be directly injected into the recording workflow. Subsequently, the audio file path is automatically obtained according to the recording instructions and added to the offline upload queue, replacing the tedious operations of manually exporting, naming, archiving, and uploading one by one. Finally, by performing consistency analysis on the fingerprint values of local files and cloud fingerprint values, the upload is only performed when the analysis results are inconsistent, avoiding duplicate transmissions and ensuring data integrity. This achieves automated management of the recording progress, solves the problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording and the need for manual export and upload of audio files, and improves the efficiency of collaborative management of audiobook recording.
[0076] 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 the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 In step S03, the step of adding the audio file path to the offline upload queue, the audiobook recording collaborative management method further includes steps S0301~S0305: Step S0301: Encrypt the queue data corresponding to the audio file path to obtain encrypted data, and store the encrypted data in a local queue file; Step S0302: Scan the local queue file using the timer scheduler to obtain queue items with a task status of waiting; Step S0303: Upload the waiting queue items according to the preset number of parallel uploads; Step S0304: After successful upload, update the task status to "completed". Step S0305: After the upload fails, update the task status to "failed".
[0077] To address issues such as audio upload failures, task loss, and duplicate uploads caused by network fluctuations, device restarts, and software shutdowns, the system has built an offline upload queue system with features including encrypted persistence, concurrency control, intelligent retries, and automatic cleanup.
[0078] The upload queue is stored in the user data directory as a JSON array, encrypted using the AES-128-CBC algorithm. The key and initialization vector are hardcoded at the application layer, and the key name is hashed using SHA-256 and used as the storage key name.
[0079] Each queue item contains fields for Task ID, Book / Chapter / Dialogue ID, Local Audio File Path, Dialogue Text Summary, Task Status, Number of Retry Count, Error Log, and Creation and Update Time.
[0080] The queue task has five status lifecycle levels. Status code 0 is in preparation, which means that the audio is still stored in the host software and is not yet ready. Status code 1 is waiting, which means that the audio is ready and waiting to be uploaded. Status code 2 is uploading, which means that the upload operation is being performed. Status code 3 is failure, which means that the upload failed and the error log is left. Status code 4 is completed, which means that the upload was successful.
[0081] Once the audio file is saved locally and a valid file path is generated, the system immediately creates an upload task and marks it as in preparation. All queue data is encrypted and persistently stored in the local queue file to prevent task data leakage and loss.
[0082] The node-cron function executes the queue processing function once every 1 second, and the async-mutex mutex lock protects the critical execution area to prevent multiple timer instances from processing the queue at the same time and causing concurrent conflicts.
[0083] During scheduling, queue items in the waiting state are filtered out. A maximum of a preset number of tasks are processed in parallel each time, with a default concurrency of 4. Slot management is implemented through a custom concurrency handling function, and a collection of executing Promises is maintained. The task completion is detected and the slot is released through Promise.race().
[0084] Once a task is successfully uploaded, the system immediately updates the task status to "completed" and synchronizes the archived task logs. If the upload fails due to network issues or server malfunctions, the task is automatically marked as failed, detailed error logs are recorded, and an intelligent retry mechanism is triggered. By default, two automatic retries are supported. After all retries are exhausted, automatic operation terminates, and failed tasks are retained for manual handling by the user. The system provides a queue management interface that displays the name, status, and operation buttons for all tasks, supporting retrying individual tasks and restarting all tasks.
[0085] Meanwhile, the system has an automatic cleanup capability, which can automatically identify and clean up completed and failed tasks that are older than 7 days, streamline queue storage space, and ensure the long-term efficient and stable operation of the upload queue.
[0086] Specifically, step S04 above, which involves performing a consistency analysis between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform, includes: Step S041: Obtain the cloud fingerprint value corresponding to the audiobook dialogue data through the query interface provided by the cloud platform; Step S042: Stream the local file corresponding to the audio file path to obtain audio data blocks; Step S043: Perform hash calculation on the audio data block to obtain the local file fingerprint value, and perform consistency analysis using the local file fingerprint value and the cloud fingerprint value to obtain the consistency analysis result.
[0087] The system uses the MD5 streaming hash verification mechanism to complete the consistency comparison of local and cloud audio files, accurately achieving upload deduplication and data verification.
[0088] Before the audio file is uploaded, the system actively calls the query interface provided by the cloud platform to accurately match the historical audio resources in the cloud corresponding to the currently recorded lines, and retrieves the MD5 fingerprint value of the corresponding audio file stored in the cloud as the benchmark verification data.
[0089] For local audio files to be uploaded, the traditional method of reading the entire file at once is abandoned. Instead, a streaming, block-based reading approach is used to load audio data segment by segment, generating continuous audio data blocks. Combined with an encrypted hash engine, streaming computation is performed. Data flows through the hash engine in blocks, maintaining a constant memory footprint regardless of file size, effectively solving the memory overflow problem caused by reading large audio files. After segment-by-segment computation and integration of all streaming audio data blocks, a unique MD5 fingerprint value for the local audio file is finally generated.
[0090] The locally generated fingerprint value is compared with the baseline fingerprint value retrieved from the cloud to accurately determine whether the local audio has been modified, re-recorded, or had its parameters adjusted.
[0091] If the MD5 hashes match, it means that the current audio content is the same as the cloud version, and there is no need to upload it again. The task is marked as completed directly. If the MD5 hashes do not match or there is no corresponding record in the cloud, the audio file upload operation is performed in multipart / form-data format to prevent problems such as duplicate uploads, invalid uploads, and erroneous overwriting from the root, and to ensure the consistency, uniqueness and integrity of audio data between the cloud and local systems.
[0092] This embodiment, through the above scheme, specifically encrypts the queue data corresponding to the audio file path to obtain encrypted data, and stores the encrypted data in a local queue file; a timer scheduler scans the local queue file to obtain queue items with a task status of "waiting"; uploads the waiting queue items according to a preset number of parallel uploads; after a successful upload, the task status is updated to "completed"; after a failed upload, the task status is updated to "failed". Therefore, by retrieving audiobook dialogue data from the cloud platform according to a preset communication protocol and displaying it in a tree structure, the problem of disconnect between cloud data and the recording end in existing technologies is solved. This allows dialogue data to be directly injected into the recording workflow. Subsequently, the audio file path is automatically obtained according to the recording instructions and added to the offline upload queue, replacing the tedious operations of manually exporting, naming, archiving, and uploading one by one. Finally, by performing consistency analysis on the fingerprint values of local files and cloud fingerprint values, the upload is only performed when the analysis results are inconsistent, avoiding duplicate transmissions and ensuring data integrity. This achieves automated management of the recording progress, solves the problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording and the need for manual export and upload of audio files, and improves the efficiency of collaborative management of audiobook recording.
[0093] For example, to help understand the implementation process of the audiobook recording collaborative management method obtained by combining this embodiment with the above embodiment one, please refer to... Figure 3 , Figure 3 A simplified flowchart of an audiobook recording collaborative management method is provided, specifically: A complete audiobook recording collaborative management system is built based on the CEP plugin dual-runtime architecture. The overall deployment architecture is divided into three layers: cloud service layer, front-end panel layer, and host interaction layer. The cloud service layer provides services such as dialogue data, audio storage, user authentication, and message notification through a RESTful API server. The front-end panel layer carries the interactive interface built with HTML / CSS / JS based on the CEF rendering engine. It obtains system capabilities such as file system, network communication, encryption, and process management through the Node.js runtime. The host interaction layer calls the host software DOM API through the ExtendScript engine. The panel layer and the script engine layer exchange instructions asynchronously through a cross-runtime communication interface, and event callbacks are passed in reverse through the event bus.
[0094] The system fully covers the entire chain of operations, including cloud data interaction, local intelligent recording, audio optimization processing, offline queue uploading, and data verification and synchronization. After the voice actor starts the host software, the CEP plugin panel is automatically loaded. The QR code login interface is displayed when the user uses it for the first time. The user scans the code to complete the identity verification and account login.
[0095] After successful login, the panel loads the list of audiobook projects assigned to the user, displaying progress indicators such as the number of unfinished paragraphs, the total number of paragraphs, and the effective duration for each book. Users can locate the target book through status filter tags or the search box and click to enter the recording interface.
[0096] After entering the recording interface, the left side displays the chapter list, and the middle area displays the dialogue list of the current chapter. Each line of dialogue is presented in the form of a character tag, dialogue text, and status mark. Users can locate the line to be recorded by clicking or using directional shortcuts. After selection, the information bar on the right automatically updates metadata such as character voice description, performance tips, and feedback instructions.
[0097] After the user presses the record shortcut key, the system first performs a triple check of window focus, interface status, and engine status. After confirming that the recording environment is compliant, it starts automatic recording and measures the key press duration for subsequent keyboard sound compensation.
[0098] After the user finishes reading aloud, pressing the shortcut key again triggers a stop. The system automatically stops recording, calculates the compensation offset based on the key press duration, selects the section at the end of the audio affected by keyboard sounds, calls the automatic repair effect processor, and fine-tunes the playback head position to maintain audio continuity.
[0099] Then, the asynchronous save pipeline is started, which sequentially completes the audio copying and creation, the MP3 format export of the favorites sound effects, and the local persistent saving. In background mode, users can simultaneously browse the next line of dialogue. After processing is completed, the temporary document is automatically closed and the placeholder audio is switched back.
[0100] After the audio is saved, an upload task is automatically created and added to the offline upload queue. The timer scans the queue every second, filters ready tasks, calculates the local audio MD5 value and compares it with the cloud value. If the content has changed, it is uploaded to the cloud server in form format.
[0101] Once uploaded successfully, the background status will be synchronized to "Completed". In continuous recording mode, it will automatically jump to the next unrecorded line, and the progress bar on the panel will update the completion percentage of the current chapter in real time.
[0102] When the cloud platform sends a feedback request, the system receives the notification through periodic polling. A red dot appears on the notification icon at the top of the panel. After the user clicks to view the message list, they can directly jump to the corresponding lines. The status is marked as needing feedback and the reason for feedback is attached. The user can then re-record according to the normal process.
[0103] The entire process requires no switching of software windows, no manual archiving and uploading, and no manual data verification, completely solving the industry pain points of traditional recording processes such as fragmentation, noise interference, cumbersome operation, data error, and low collaboration efficiency, and realizing the industrialization, standardization, and collaborative operation of the entire audiobook recording process.
[0104] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the audiobook recording collaborative management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.
[0105] This application also provides an audiobook recording collaborative management device; please refer to... Figure 4 The audiobook recording collaborative management device is applied to the recording end, and the audiobook recording collaborative management device includes: The display module 10 is used to obtain audiobook dialogue data from the cloud platform according to a preset communication protocol, and to display the audiobook dialogue data in a tree structure according to the login information of the recording terminal. Selection module 20 is used to receive the user's selection instruction for the tree structure and display the dialogue text and character metadata according to the selection instruction; Recording module 30 is used to obtain the audio file path according to the user's recording instructions and add the audio file path to the offline upload queue; The analysis module 40 is used to perform consistency analysis on the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. When the analysis result is inconsistent, the audio file path is uploaded to the cloud and the recording status of the audiobook dialogue data is updated.
[0106] The audiobook recording collaborative management device provided in this application, employing the audiobook recording collaborative management method in the above embodiments, can solve the technical problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording, and the need for manual export and uploading of audio files. Compared with the prior art, the beneficial effects of the audiobook recording collaborative management device provided in this application are the same as those of the audiobook recording collaborative management method provided in the above embodiments, and other technical features in the audiobook recording collaborative management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.
[0107] This application provides an audiobook recording collaborative management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the audiobook recording collaborative management method in the first embodiment described above.
[0108] The following is for reference. Figure 5 This document illustrates a structural schematic diagram of an audiobook recording collaborative management device suitable for implementing embodiments of this application. The audiobook recording collaborative management device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 5 The audiobook recording collaborative management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0109] like Figure 5As shown, the audiobook recording collaborative management 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 the read-only memory 1002 or a program loaded from the storage device 1003 into the random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the audiobook recording collaborative management device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touch screen, 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 the audiobook recording collaboration management device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows audiobook recording collaboration management devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.
[0110] 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 read-only memory 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.
[0111] The audiobook recording collaborative management device provided in this application, employing the audiobook recording collaborative management method in the above embodiments, can solve the technical problem of insufficient reliability assurance caused by the disconnect between cloud data and the recording end in existing audiobook recording, and the need for manual export and uploading of audio files. Compared with the prior art, the beneficial effects of the audiobook recording collaborative management device provided in this application are the same as those of the audiobook recording collaborative management method provided in the above embodiments, and other technical features in this audiobook recording collaborative management device are the same as those disclosed in the previous embodiment method, and will not be repeated here.
[0112] 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.
[0113] 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.
[0114] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the audiobook recording collaborative management method in the above embodiments.
[0115] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having 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 fiber, 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 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.
[0116] The aforementioned computer-readable storage medium may be included in the audiobook recording collaborative management device; or it may exist independently and not be assembled into the audiobook recording collaborative management device.
[0117] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the audiobook recording collaborative management device, the audiobook recording collaborative management device: acquires audiobook dialogue data from a cloud platform according to a preset communication protocol, and displays the audiobook dialogue data in a tree structure according to the login information of the recording terminal; receives user selection instructions for the tree structure, and displays the dialogue text and character metadata according to the selection instructions; acquires the audio file path according to the user's recording instructions, and adds the audio file path to an offline upload queue; performs consistency analysis on the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform, and uploads the audio file path to the cloud when the analysis result is inconsistent, and updates the recording status of the audiobook dialogue data.
[0118] 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).
[0119] 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.
[0120] 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 unit itself.
[0121] 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 audiobook recording collaborative management method. This solves the technical problem in existing audiobook recording systems where cloud data is disconnected from the recording end, and audio files need to be manually exported and uploaded, leading to insufficient reliability. 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 audiobook recording collaborative management method provided in the above embodiments, and will not be repeated here.
[0122] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the audiobook recording collaborative management method described above.
[0123] The computer program product provided in this application can solve the technical problem of insufficient reliability in existing audiobook recordings due to the disconnect between cloud data and the recording end, and the need for manual export and uploading of audio files. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the audiobook recording collaborative management method provided in the above embodiments, and will not be repeated here.
[0124] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.
Claims
1. An audio book recording co-management method, characterized by, The audiobook recording collaborative management method is applied to the recording end, and the audiobook recording collaborative management method includes: According to the preset communication protocol, the audiobook dialogue data is obtained from the cloud platform, and the audiobook dialogue data is displayed in a tree structure according to the login information of the recording terminal. Receive user selection instructions for the tree structure, and display dialogue text and character metadata according to the selection instructions; Obtain the audio file path according to the user's recording instructions, and add the audio file path to the offline upload queue; A consistency analysis is performed between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. If the analysis result is inconsistent, the audio file path is uploaded to the cloud, and the recording status of the audiobook dialogue data is updated.
2. The audiobook recording collaborative management method as described in claim 1, characterized in that, The recording terminal includes recording software, and the step of obtaining the audio file path according to the user's recording instructions includes: In response to a recording command sent by the user, the recording software is determined to be an active window through focus detection, and recording is performed through the software script engine of the recording software; If a stop or submit command is received during the recording process of the software script engine, the recording is stopped, and the timing compensation offset is calculated based on the operation duration of the command. The compensation audio range is determined based on the timing compensation offset, and the compensation audio range is repaired by the effects processor of the recording software to obtain the repaired audio. The repaired audio is then processed with sound effects. After the sound effects processing is completed, the target file corresponding to the repaired audio is converted to the target format and the target file is saved to a local folder to obtain the audio file path.
3. The audiobook recording collaborative management method as described in claim 2, characterized in that, The step of determining the recording software as an active window through focus detection includes: Obtain the process name of the foreground window of the recording terminal, and compare the process name with the software name of the recording software; If the process name is the same as the software name, then obtain the real-time interface status of the recording software; When the real-time interface is in the recording interface state, obtain the script engine state of the recording software; If the script engine is in a ready state, then the recording software is determined to be an active window.
4. The audiobook recording collaborative management method as described in claim 2, characterized in that, The step of calculating the timing compensation offset based on the instruction operation duration includes: Record the first timestamp corresponding to the recording instruction, and record the second timestamp of the stop instruction or submit instruction; The instruction operation duration is calculated based on the difference between the first timestamp and the second timestamp; The operation time of the instruction is compared with the manual deviation value to obtain the comparison result, and the initial offset is determined based on the comparison result. Determine whether the initial offset exceeds the repair upper limit. If it exceeds the limit, then the repair upper limit value is determined to be the timing compensation offset; If the initial offset is not exceeded, then the initial offset is determined to be the timing compensation offset.
5. The audiobook recording collaborative management method as described in claim 2, characterized in that, The step of performing sound effect processing on the repaired audio includes: Obtain the sound effect processing chain corresponding to the login information; The repaired audio is processed using the aforementioned audio processing chain; Monitor the processing status of the sound effect processing chain. When the sound effect processing is completed, save the sound effect processing result and close the temporary file corresponding to the sound effect processing chain.
6. The audiobook recording collaborative management method as described in claim 1, characterized in that, The step of adding the audio file path to the offline upload queue includes: The queue data corresponding to the audio file path is encrypted to obtain encrypted data, and the encrypted data is stored in a local queue file; The local queue file is scanned by a timer to obtain queue items whose task status is "waiting". The waiting queue items are uploaded according to the preset number of parallel uploads; After successful upload, update the task status to "completed". If the upload fails, the task status will be updated to "failed".
7. The audiobook recording collaborative management method as described in claim 1, characterized in that, The step of performing consistency analysis between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform includes: The cloud fingerprint value corresponding to the audiobook dialogue data is obtained through the query interface provided by the cloud platform. The local file corresponding to the audio file path is streamed to obtain audio data blocks; The audio data block is hashed to obtain a local file fingerprint value. Consistency analysis is then performed using the local file fingerprint value and the cloud fingerprint value to obtain the consistency analysis result.
8. An audiobook recording collaborative management device, characterized in that, The audiobook recording collaborative management device is applied to the recording end, and the audiobook recording collaborative management device includes: The display module is used to obtain audiobook dialogue data from the cloud platform according to a preset communication protocol, and display the audiobook dialogue data in a tree structure according to the login information of the recording terminal. The selection module is used to receive the user's selection instruction for the tree structure and display the dialogue text and character metadata according to the selection instruction. The recording module is used to obtain the audio file path according to the user's recording instructions and add the audio file path to the offline upload queue; The analysis module is used to perform consistency analysis between the local file fingerprint value of the recording terminal and the cloud fingerprint value of the cloud platform. When the analysis result is inconsistent, the audio file path is uploaded to the cloud and the recording status of the audiobook dialogue data is updated.
9. An audiobook recording collaborative management device, characterized in that, The device 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 audiobook recording collaborative management method as described in any one of claims 1 to 7.
10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the audiobook recording collaborative management method as described in any one of claims 1 to 7.
