Method and system for making external dynamic picture file

Abstract

The invention provides an outgoing dynamic picture file making method and system, and the method comprises the steps: a task issuing end creates an outgoing task file, and transmits the outgoing task file to a transit server in response to a task issuing instruction; the transit server responds to the received outgoing task file and generates task notification information based on the task receiving end identification information; the task receiving end obtains the task notification information corresponding to the task receiving end from the transit server, and obtains an outgoing task file corresponding to the task notification information from the transit server; the task receiving end sends the manufactured outgoing task file to the transit server; the transit server generates corresponding submitted file pushing information, and sends the submitted file pushing information and the manufactured outgoing task file to the task issuing end; and after the task issuing end carries out identity verification, receiving the manufactured outgoing task file. Therefore, the manufacturing efficiency of the external dynamic picture file can be effectively improved.

Description

Technical Field

[0001] This application relates to the field of animation production, and in particular to a method and system for creating external animation files. Background Technology

[0002] With the booming development of industries such as animation, games, and digital visual effects, the scale and complexity of projects are increasing daily, leading to a surge in demand for production resources. Against this backdrop, outsourcing some animation production tasks (such as model making, rigging, animation, lighting, and rendering) to external teams or freelancers has become standard practice and a core production method within the industry.

[0003] Currently, the process of outsourcing animation files typically relies on a combination of various general-purpose tools. The task publisher (the party issuing the project) usually sends the task requirements, reference files, and original animation assets to the task recipient (the party receiving the project) via email, instant messaging tools, or public cloud storage links. After completing the production locally, the party receiving the project then sends the finished file back to the publisher through similar channels.

[0004] However, this decentralized process, which relies heavily on manual labor and non-dedicated tools, has many inherent flaws, severely impacting production efficiency and project security. First, the management and collaboration of animation files are inefficient: the sending and receiving status of related task files is difficult to track effectively, making it difficult for the client to monitor the overall progress of multiple outsourced tasks in real time, easily leading to project delays. Furthermore, file versions are easily confused during multiple transmissions, requiring frequent communication and confirmation, resulting in high collaboration costs. Second, there are risks to data security and integrity: transmitting core animation assets through public network channels carries the risk of leakage. More importantly, when the client receives the returned finished files, they lack the corresponding technical means to verify whether the file corresponds to their assigned task and whether it has been tampered with during transmission or production, posing security and quality risks.

[0005] Therefore, in the field of animation production, the technical defects in existing technologies have severely slowed down the production cycle of externally distributed animation files, affecting the production efficiency of externally distributed animation files. Summary of the Invention

[0006] Based on this, the purpose of this application is to provide a method and system for creating external animation files, which can effectively shorten the production cycle of external animation files and improve the production efficiency of external animation files.

[0007] The objective of this application can be achieved through the following technical solutions: A method for creating an outgoing animation file includes the following steps: a task publishing end creates an outgoing task file, wherein the outgoing task file includes task metadata, and the task metadata includes task receiver identification information; the task publishing end, in response to a task publishing command, sends the outgoing task file to a relay server; the relay server, in response to the received outgoing task file, generates task notification information based on the task receiver identification information; the task receiver accesses the relay server according to a preset polling period and obtains task notification information corresponding to itself from the relay server; the task receiver, in response to a task retrieval command, retrieves task notification information from the relay server. The server retrieves the outgoing task file corresponding to the task notification information; the task receiving end, in response to the task submission instruction, sends the completed outgoing task file to the relay server; the relay server, in response to the received completed outgoing task file, generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end; the task publishing end, in response to the received submission file push information, authenticates the completed outgoing task file, and receives the completed outgoing task file after successful authentication.

[0008] An external animation file creation system is disclosed, comprising a task publishing terminal, a relay server, and a task receiving terminal. The task publishing terminal is used to create external task files, and in response to a task publishing instruction, send the external task files to the relay server. It also in response to received submission file push information, authenticates the completed external task files, and receives the completed external task files after successful authentication. The external task files include task metadata, which includes task receiving terminal identification information. The relay server, in response to the received external task files, generates task notification information based on the task receiving terminal identification information. The task receiving end, in response to the received completed outgoing task file, generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end; wherein, the submission file push information includes the authentication information of the completed outgoing task file; the task receiving end is configured to access the relay server according to a preset polling cycle, obtain task notification information corresponding to itself from the relay server, and in response to a task acquisition instruction, obtain the outgoing task file corresponding to the task notification information from the relay server, and in response to a task submission instruction, send the completed outgoing task file to the relay server.

[0009] Compared to existing technologies, the method described in this application establishes a standardized workflow for producing outsourced animation files through the collaborative operation of the task publisher, relay server, and task receiver. Furthermore, the technical solution of this application creates outsourced task files containing task metadata, with the relay server handling task notifications and file transfers, and the task publisher ultimately verifying the returned files, achieving closed-loop management of animation production tasks from initiation to completion. Therefore, the method described in this application effectively overcomes the problems of chaotic file management, opaque progress, inconsistent versions, and difficulty in verifying the authenticity of file sources caused by the use of non-dedicated platforms such as email or instant messaging tools in traditional outsourcing methods. By integrating scattered collaborative steps into an orderly system workflow, it significantly improves the collaborative efficiency, management standardization, and security of the file transmission process in outsourced animation file production, thereby effectively shortening the production cycle of outsourced animation files and increasing their production efficiency.

[0010] To better understand and implement this application, the following detailed description is provided in conjunction with the accompanying drawings. Attached Figure Description

[0011] Figure 1 A flowchart of a method for creating external animation files provided in this application; Figure 2 A flowchart illustrating the steps of creating an outgoing task file in the method for creating outgoing animation files provided in this application; Figure 3 A flowchart illustrating the steps of creating an outgoing task file in the second method of creating outgoing animation files provided in this application; Figure 4 A flowchart illustrating the steps for obtaining the outgoing task file in the method for creating outgoing animation files provided in this application; Figure 5 A flowchart illustrating the steps involved in the method for creating outsourced animation files provided for this application to review whether the completed outsourced task files meet the artistic style requirements; Figure 6 An interactive diagram of an external animation file creation system provided in this application. Detailed Implementation

[0012] This application provides a method and system for creating external animation files. To make the purpose, technical solution, and effects of this application clearer and more explicit, the following detailed description is provided with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining this application and are not intended to limit this application.

[0013] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0014] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0015] The invention will be further explained below with reference to the accompanying drawings and the description of the embodiments.

[0016] Example 1 Please refer to Figure 1 , Figure 1 A flowchart illustrating a method for creating externally distributed animation files provided in this application. The method includes the following steps: S10: The task publishing end creates an external task file; S20: The task publishing terminal responds to the task publishing instruction and sends the outgoing task file to the relay server; S30: In response to the received outgoing task file, the relay server generates task notification information based on the task receiver identification information; S40: The task receiving end accesses the relay server according to the preset polling cycle and obtains the task notification information corresponding to itself from the relay server; S50: In response to the task acquisition instruction, the task receiving end acquires the outgoing task file corresponding to the task notification information from the relay server; S60: In response to the task submission instruction, the task receiving end sends the completed outgoing task file to the relay server; S70: In response to the received completed outgoing task file, the relay server generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end. S80: The task publishing terminal responds to the received submission file push information by authenticating the completed external task file and receiving the completed external task file after successful authentication.

[0017] For step S10: The task publishing end creates an external task file.

[0018] The outgoing task file includes task metadata, which includes task receiver identification information. In this embodiment, based on the inventive concept of this application, those skilled in the art will understand that the task publishing terminal mentioned in this application refers to a computer system or terminal device used by the animation project leader (contractor) to create and distribute animation production tasks; the created outgoing task file is a structured data packet used to encapsulate the entire animation production task information, which at least contains task metadata, but in some other embodiments, it is understood that it may also include other content (such as the digital signature of the task publishing terminal); the task metadata is a set of information describing task attributes, one of its core fields being the task receiver identification information, but in some other embodiments, it is understood that it may also include other content (such as animation file format requirements); the task receiver identification information is used to uniquely identify the external production party (contractor) that receives and completes this outgoing task, i.e., the task receiver.

[0019] In one embodiment, the outgoing task file further includes a task data package, which includes a plurality of animation files to be produced, animation asset files associated with the animation files to be produced, and associated animation files associated with the animation files to be produced.

[0020] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the steps of creating an outgoing task file in the method for creating outgoing animation files provided in this application. In this embodiment, step S10 includes: S101: The task publishing terminal responds to the file selection command and enters the file association display interface of the corresponding animation file to be produced.

[0021] In one embodiment, the file selection instruction is triggered by the user through the graphical user interface of the task publishing terminal, such as by double-clicking the file icon or dragging a specified file from the file list to the task creation area; the file association display interface is an independent window or panel that dynamically loads and displays a list of files stored in one or more preset paths.

[0022] In one optional specific embodiment, based on the inventive concept of this application, in order to achieve intelligent association recommendation, the file association display interface, when loaded, first parses the metadata tags (such as AssetID, ShotNumber) of the animation file to be produced, and reads association rules from a pre-configured JSON rule file accordingly. For example, the rule can specify that when a file contains the CharacterName tag, all texture files (.tga or .png) and skeleton binding files (.rig) that match the character name in the resource library will be automatically highlighted in the interface. At the same time, relevant sample files (.mp4) will be matched and recommended according to the prefix of ShotNumber. This series of operations is automatically completed by the embedded rule engine during interface initialization, thereby intelligently filtering out highly relevant files for external task publishers and improving task creation efficiency.

[0023] The file association display interface shows several animation files and animation asset files stored in a preset path.

[0024] S102: The task publishing terminal responds to the file selection instruction and obtains the corresponding animation file and animation asset file in the file association display interface.

[0025] In one embodiment, the file selection instruction is triggered by the user clicking a checkbox in the interface; the task publishing terminal records the absolute paths of the animation file and animation asset file corresponding to the file selected by the user in the associated display interface.

[0026] In one optional specific embodiment, based on the inventive concept of this application, to ensure the smooth flow of subsequent processes, after obtaining the paths of the corresponding animation files and animation asset files, the task publishing terminal will automatically execute a pre-verification process. This process includes attempting to open each selected file in exclusive mode to check whether it is occupied by other processes, and verifying whether the version information in the header of specific format files (such as Maya's .ma files) is compatible with the preset version list. At the same time, it performs existence and accessibility tests on all file paths (especially network paths). If the check results show corresponding errors, an error warning list is generated and updated in real time in the sidebar of the UI interface to remind the user to resolve the errors.

[0027] S103: In response to the file association command, the task publishing terminal outputs the animation file to be produced, the corresponding animation file in the obtained file association display interface, and the animation asset file as the task data package of the outgoing task file.

[0028] In one embodiment, the file association instruction is triggered by the user clicking the "Confirm and Package" button, wherein the task publishing end packages the animation files and animation asset files corresponding to the file association display interface selected by the user into a ZIP format compressed package.

[0029] In one optional specific embodiment, based on the inventive concept of this application, in order to ensure the security and integrity of file transmission, the task publishing end will use the SHA-256 algorithm to calculate the hash value of the animation file to be produced and all related files when packaging, and generate a JSON format manifest file (manifest.json) that records the path, size and hash value of each file in detail. Then, the entire data packet (including user files and manifest) is encrypted using the AES-256 algorithm and a one-time key automatically generated by the system. The final output is an encrypted compressed file with the extension .pkg. The one-time key is encrypted and stored in the task metadata for the task receiving end to decrypt.

[0030] Alternatively, based on the inventive concept of this application, those skilled in the art can employ other steps to replace steps S101 to S103 in creating the outbound task file, thereby continuing to implement other steps of the technical solution of this application. Therefore, please refer to Figure 3 , Figure 3 The flowchart of the second step in creating an outgoing task file in the method for creating outgoing animation files provided in this application, in another embodiment, includes the following steps: S101a: The task publishing terminal obtains a preset animation resource association directory table.

[0031] In one embodiment, the animation resource association directory table can be a data structure stored in a database or configuration file.

[0032] The preset animation resource association directory table includes at least several animation resource association directories, and each animation resource association directory stores several animation files and animation asset files.

[0033] In one optional specific embodiment, the preset animation resource association directory table is a configuration file stored in JSON or XML format. The configuration file stores multiple animation resource association directories. Each entry in the animation resource association directory contains one or more of the following fields: a unique directory ID (e.g., char_hero_model), a directory description (e.g., "main character model resource"), the root path corresponding to the directory (e.g., \\server\assets\character\hero), and a resource type tag (e.g., Model, Texture, Rig).

[0034] In one embodiment, the preset animation resource association directory table is loaded into memory during initialization to provide an index basis for subsequent resource matching.

[0035] S102a: The task publishing terminal responds to the file selection instruction, obtains the corresponding animation file to be produced, and displays the animation resource association directory in the animation resource association directory table.

[0036] In one embodiment, after the file selection instruction is triggered, the corresponding UI interface displays the selected animation file to be produced on one side, and displays all the associated directories of animation resources in a list format on the other side.

[0037] In one optional specific embodiment, after obtaining the animation file to be produced, the task publishing end can extract its file name keywords (such as separating them with underscores and removing the version number) and its metadata attributes (such as asset_type). Then, it performs a preliminary match with the directory ID and resource type tag of the directory associated with the animation resource, and prioritizes highlighting the top few directories with the highest matching degree in the UI interface, while displaying irrelevant directories in grayscale, thereby realizing intelligent directory recommendation and guiding users to make a quick selection.

[0038] S103a: In response to the directory selection command, the task publishing terminal matches the animation file to be produced with the animation resource associated directory according to the preset associated resource matching rules. If the match is successful, the animation file and animation asset file stored in the corresponding animation resource associated directory are obtained.

[0039] In one optional specific embodiment, the preset associated resource matching rules are a set of configurable logical judgments. For example, when a user selects a directory named char_hero, the following rules are executed: First, check whether the filename of the animation file to be created (such as sc01_hero_anim_v01.ma) contains the keyword "hero" in the directory ID char_hero; second, check whether the required_asset field in the metadata of the animation file to be created lists any resources. If so, check whether these resources exist in the char_hero directory; finally, traverse all files with extensions .mb, .ma, .tga, and .png in the char_hero directory, and match those files whose filenames begin with char_hero using regular expressions. Only after the first two checks pass or after further confirmation by the administrator will all successfully matched files in the animation resource associated directory be associated.

[0040] S104a: In response to the file association command, the task publishing terminal outputs the animation file to be produced, the animation files stored in the corresponding animation resource association directory, and the animation asset files as the task data package of the outgoing task file.

[0041] In one optional specific embodiment, after responding to the file association instruction, the task publishing end first generates a file list for the animation file to be produced and all associated files obtained from the matching directory. The file list records the original absolute path, relative path in the data packet, size, and calculated MD5 checksum of each file. Subsequently, according to the relative path structure in the file list, the same directory tree is created in the temporary folder, and the files are copied to the corresponding location. Finally, the entire directory tree is packaged using a ZIP algorithm with compression ratio, and the generated ZIP package is digitally signed to ensure that the data packet is not tampered with during transmission. Finally, this signed ZIP package is output as the task data packet.

[0042] In one embodiment, it can be understood that in steps S101-S104 and steps S101a-S104a, one or more types of animation files and animation asset files can be displayed / stored / selected, and the specific settings can be made by those skilled in the art according to the actual situation.

[0043] For step S20: The task publishing terminal responds to the task publishing instruction and sends the outgoing task file to the relay server.

[0044] In one embodiment, the task publishing instruction is triggered by the user clicking the "Publish" button on the operation interface of the task publishing terminal; after receiving the task publishing instruction, the task publishing terminal uploads the packaged outgoing task file to the preset API interface of the relay server via HTTP / HTTPS protocol.

[0045] In one embodiment, the relay server refers to any intermediate computing node in a distributed system that is responsible for receiving, temporarily storing, routing, and forwarding data; while in the technical solution of this application, those skilled in the art will understand that the relay server is a central server located between the task publishing end and the task receiving end, dedicated to the management of outgoing animation tasks.

[0046] In one optional specific embodiment, based on the inventive concept of this application, to ensure the integrity and security of outbound task publishing, the task publishing end may choose to execute the following process after responding to the publishing instruction: First, package and digitally sign the outbound task file (containing task metadata and task data packet) to be sent, and sign the SHA-256 hash value of the data packet using the private key of the task publishing end; then, attempt to establish a TLS connection with the relay server, and through an authenticated RESTful API endpoint (e.g., https: / / <server-address>The task publisher initiates an upload request via ` / api / v1 / task / submit`. The request body consists of multiple forms containing the task file itself and a generated digital signature. After successfully receiving the file, the relay server returns a JSON response containing a unique task ID (e.g., `task_20231027_abc123`) and a receiving timestamp. Upon receiving this response, the task publisher updates its local task status to "published" and displays a successful publication message to the user on the UI. If there is a network error or the server returns an error, the task publisher will automatically resend the task according to a preset retry strategy (e.g., exponential backoff algorithm) and alert the user after multiple failures.

[0047] For step S30: In response to the received outgoing task file, the relay server generates task notification information based on the task receiver identification information.

[0048] The task notification information is a structured data object (such as JSON or XML format) created by the relay server after successfully receiving and preliminarily verifying the outgoing task file.

[0049] In one embodiment, the task notification information includes at least the following core fields: a globally unique task ID (associated with an identifier in the task metadata), a basic description of the task, the associated task receiver identifier information, the timestamp of task creation, the initial value of the task status (such as "pending receipt"), and the storage path or access token of the outgoing task file on the relay server.

[0050] In one embodiment, after receiving an outgoing task file, the relay server parses the task receiver identification information (such as the user ID of the recipient) in its task metadata, and then creates a new task record in the task management database inside the relay server. This record contains the basic content of the aforementioned task notification information.

[0051] In one optional specific embodiment, to ensure the reliability and traceability of task notifications, the relay server may perform the following operations when generating task notification information: First, the relay server scans the received outgoing task files for viruses and performs format verification. After confirming that the files are safe, it moves them to a secure, access-controlled persistent storage area (such as the distributed file system HDFS or a cloud storage bucket) and generates a time-sensitive file access signature URL. Next, the relay server creates a task notification information object, which contains not only basic task information but also the file storage path, access URL, file hash checksum, and task priority identifier. Then, the relay server serializes this task notification information (e.g., converts it to a JSON string), persistently stores it in a new record in the task database, and publishes it to a highly available message queue (such as Apache). In a specific topic of Kafka or RabbitMQ, the topic is named or routed with the task receiver identification information, thereby enabling accurate and asynchronous notification of outgoing tasks and providing load balancing and capability decoupling for multiple possible task receiver instances; finally, the relay server updates the corresponding task status to "ready to receive" and records a complete operation log.

[0052] For step S40: The task receiving end accesses the relay server according to the preset polling period and obtains the task notification information corresponding to itself from the relay server.

[0053] The polling period is a rhythm control parameter for the task receiving end to actively query tasks. In one embodiment, the polling period refers to the time interval setting for the client to periodically send query requests to the server. In this embodiment, the preset polling period specifically refers to a preset strategy configured for the task receiving end to periodically check whether there are any pending tasks related to itself on the relay server.

[0054] In one embodiment, after the task receiver starts, it begins a background timer that sends data to a specific API endpoint (such as https: / / ) of the relay server at preset fixed time intervals (e.g., every minute). <server-address>Send an HTTP GET request to / api / v1 / task / poll, wherein the header or parameters of the HTTP GET request carry task receiver identification information representing its own identity.

[0055] For step S50: In response to the task acquisition instruction, the task receiving end retrieves the outgoing task file corresponding to the task notification information from the relay server.

[0056] Please refer to Figure 4 , Figure 4 A flowchart illustrating the steps involved in obtaining the external task file in the method for creating external animation files provided in this application.

[0057] In one embodiment, step S50 includes: S501: The task receiving end sends a confirmation request for the task notification information to the relay server.

[0058] S502: In response to the confirmation request, the relay server marks the status of the task notification information as read and returns the download address of the outgoing task file corresponding to the task notification information to the task receiving end.

[0059] S503: The task receiving end downloads the outgoing task file corresponding to the task notification information from the relay server based on the download address.

[0060] In one embodiment, based on the inventive concept of this application, after the animator obtains the outgoing task file at the task receiving end (i.e., after step S50), the animator can perform animation production on the outgoing task file on the task receiving end, thereby obtaining the completed outgoing task file.

[0061] For step S60: In response to the task submission instruction, the task receiving end sends the completed outgoing task file to the relay server.

[0062] The task receiving end includes the creator end and the review end.

[0063] In one embodiment, the creator end is a client computing device or software environment used by the task recipient (the party receiving the project) to actually create animation content (such as model making, rigging, animation, lighting rendering, etc.). Its core function is to receive outgoing task files, execute production instructions, and generate corresponding completed outgoing task files. The review end is a client computing device or software environment internal to the task recipient or designated by the task recipient, used to conduct quality review of the outgoing task files completed by the creator end. Its core function is to ensure quality from both artistic and technical standards perspectives.

[0064] In one embodiment, step S60 includes: S601: In response to the completion instruction, the creator sends the completed outgoing task file to the reviewer.

[0065] Specifically, after completing local animation production on the creator's end, the animator can trigger a "submit for review" operation through the corresponding user interface to generate the production completion instruction and transmit the completed outgoing task file to the corresponding review end.

[0066] S602: The reviewing end performs an art review on the completed outgoing task file.

[0067] S603: After the art review is approved, the reviewing end marks the completed outgoing task file with a review completion mark and sends it to the relay server.

[0068] The review completion identifier includes at least the identity information of the reviewing end.

[0069] In this embodiment, the addition of the review completion mark clarifies the responsible party for the review, effectively preventing substandard animation files caused by production oversights from entering the reflow process, reducing potential rework and communication costs, and thus improving the collaborative efficiency of external animation file production and the quality and reliability of the final output animation files from a system perspective.

[0070] In an optional embodiment, the task metadata further includes art style requirement information; the art style requirement information is normative data set by the task publishing end.

[0071] In this embodiment, step S602 includes: S6021: The review terminal obtains the art style requirement information and, based on a preset art style matching threshold, determines whether the completed outgoing task file conforms to the art style requirement information.

[0072] The preset art style matching threshold has a corresponding mapping relationship with the art style requirement information. In one embodiment, those skilled in the art will understand that the art style matching threshold is a preset quantitative parameter for determining whether the completed outgoing task file meets the art style requirement information.

[0073] In one optional embodiment, the art style requirement information includes standard color styles and standard material samples corresponding to the outgoing task file; the preset art style matching threshold includes at least one of the following: color tolerance range, motion smoothness coefficient, and material deviation degree; please refer to Figure 5 , Figure 5 The flowchart of the steps for reviewing whether the completed outgoing animation file meets the artistic style requirements in the method for creating outgoing animation files provided in this application is shown in this embodiment. Step S6021 includes: S6021a: The review end parses the completed outgoing task file and extracts the corresponding screen color feature sequence, character action vector sequence and surface material visual features.

[0074] In one embodiment, the reviewer uses computer vision technology to analyze the completed outgoing task files.

[0075] In an optional specific embodiment, based on the inventive concept of this application, when the completed outgoing task file is a video, the review end uses the OpenCV library to extract the HSV color histogram of each frame in the video sequence as the color feature sequence of the picture, uses the optical flow method to calculate the motion trajectory of the key points of the character to form the character action vector sequence, and uses a pre-trained convolutional neural network (such as VGG or ResNet) to extract the high-dimensional feature vector of the material region as the surface material visual feature.

[0076] In one optional embodiment, the feature extraction process further includes data preprocessing steps, such as extracting keyframes from video files and normalizing material images, to ensure the accuracy and consistency of feature extraction.

[0077] S6021b: The review end compares the extracted color feature sequence of the image with the standard color style, and determines whether the corresponding deviation value is within the color tolerance range.

[0078] The color tolerance range is used to specify the maximum extent to which the colors in the completed outgoing task file are allowed to deviate from the standard colors specified in the task requirement information.

[0079] In one embodiment, the reviewer can convert the extracted image color feature sequence (HSV color histogram) into the CIELAB color space and calculate the corresponding LAB value. Specifically, the video sequence is sampled at a rate of 1 frame per second, and the LAB value of the dominant color gamut of each sampled frame is calculated; at the same time, the standard color style is stored in the form of an array of LAB values, such as the standard color of the main character's clothing being [L:54, a:36, b:-28], and the color tolerance range is set to ΔE≤5.0; the reviewer calculates the ΔE value between the dominant color and the standard color of each frame, using the formula ΔE=√((L1-L2)²+(a1-a2)²+(b1-b2)²).

[0080] In one optional specific embodiment, based on the inventive concept of this application, those skilled in the art can set the passing conditions as follows: the average value of ΔE in consecutive frames is ≤3.0, and the extreme value of ΔE in a single frame is ≤6.0; and set dynamic tolerance for special scenes (such as lighting effects), allowing the tolerance range to be temporarily expanded to ΔE≤8.0.

[0081] In one embodiment, the task requirement specifies that the protagonist's clothes are "standard red" (Lab value: L=50, a=80, b=60). If the set color tolerance range is ΔE≤5, the Lab value of the color of the clothes in the completed outgoing task file is detected. As long as the calculated color difference ΔE is within 5, the color is considered acceptable. If ΔE exceeds 5, the color deviation is considered to be excessive and the review is not approved.

[0082] S6021c: The review end calculates the rate of change between corresponding action frames based on the character action vector sequence, and determines whether the stability of the rate of change satisfies the action smoothness coefficient.

[0083] The motion smoothness coefficient is a mathematical index used to quantitatively evaluate whether the movement of a character or object between consecutive animation frames is smooth, without stuttering or abnormal jumps.

[0084] In this embodiment, if the acceleration of the character's arm changes uniformly from rest to swinging, the variance is small, and the corresponding motion smoothness coefficient is high (indicating smoothness); if there are undue pauses or sudden accelerations during the movement, the acceleration variance will increase sharply, and the corresponding motion smoothness coefficient will be low.

[0085] In one embodiment, the reviewer can calculate motion features based on the character motion vector sequence extracted by optical flow at a frame rate of 30fps. Specifically, the instantaneous acceleration is first obtained by differentiating the displacement vector of the same key point between adjacent frames, with the formula a(t)=(v(t)-v(t-1)) / Δt; the motion smoothness coefficient is defined as the variance threshold σ²≤0.1 of the acceleration sequence.

[0086] In one optional specific embodiment, based on the inventive concept of this application, those skilled in the art can use a sliding window detection method, with 10 frames as a window, to calculate the corresponding acceleration variance. When the acceleration variance is detected to exceed the threshold for three consecutive windows, the motion segment is determined to be unsmooth; for special motion types (such as rapid turns), the coefficient can be temporarily adjusted to σ²≤0.15.

[0087] S6021d: The review end will calculate the matching degree between the extracted surface material visual features and the features of the standard material sample, and determine whether the corresponding matching degree meets the requirements of the material deviation degree.

[0088] The material deviation is an indicator used to measure the difference between the visual attributes (such as texture, gloss, and roughness) of the rendered material (such as metal, skin, and cloth) and the preset standard material.

[0089] In one embodiment, if the outsourced task specifies that the armor is "frosted metal", the texture features (such as contrast and uniformity) and optical features (such as the shape and intensity distribution of the highlight area) of the armor area in the completed outsourced task file will be extracted and compared with the "frosted metal" features in the standard material sample. The corresponding matching score will be calculated. If it is lower than a preset threshold (i.e., the material deviation is too large), it will be determined that the material performance is unqualified and may be too similar to "glossy metal" or "plastic".

[0090] S6022: If the completed outgoing task file meets the art style matching threshold, then the completed outgoing task file is determined to meet the art style requirements and passes the art review of the completed outgoing task file.

[0091] Specifically, if in step S6021, the judgment results of the completed outgoing task file in terms of screen color feature sequence, character action vector sequence and surface material visual features all meet their respective corresponding art style matching thresholds, then the file is determined to have passed the art review.

[0092] S6023: If the completed outgoing task file does not meet the art style matching threshold, the outgoing task file is returned to the creator and the corresponding modification information is sent.

[0093] Specifically, if the judgment result of any aspect in step S6021 does not meet its corresponding art style matching threshold, the review end will return the completed outgoing task file to the creator end.

[0094] The modified information includes at least the art style matching threshold that the outsourced task file does not conform to.

[0095] In one embodiment, the modification information may be "The color difference of the main character's clothes is greater than 5, the color deviation exceeds the standard, and the review is not approved."

[0096] For step S70: In response to the received completed outgoing task file, the relay server generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end.

[0097] In one embodiment, after receiving the completed outgoing task file from the task receiving end, the relay server first performs a virus scan and format verification on it. After confirming that there are no errors, it generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end through a preset message channel.

[0098] For step S80: In response to the received submission file push information, the task publishing terminal verifies the completed external task file and receives the completed external task file after successful verification.

[0099] In one embodiment, step S80 includes: S801: The task publishing terminal obtains the first outgoing task identifier corresponding to the outgoing task file that has been completed from the submitted file push information.

[0100] S802: The task publishing terminal matches the first outgoing task identifier with the second outgoing task identifier of the outgoing task file stored in itself and sent to the relay server. If the matching result is consistent, the authentication is deemed successful, and the task publishing terminal receives and stores the completed outgoing task file.

[0101] In this embodiment, each time the task publishing end sends an outbound task file to the relay server, it stores a second outbound task identifier corresponding to the outbound task file locally. Therefore, after the task publishing end obtains the first outbound task identifier corresponding to the completed outbound task file from the received submission file push information, it matches the first outbound task identifier with the second outbound task identifier stored locally. If the matching result is consistent, the task publishing end receives and stores the completed outbound task file.

[0102] In addition, this application also provides some steps for creating outgoing animation files that can be used in the outgoing animation file creation method described in this application, for obtaining historical statistical information of the outgoing task files of the corresponding task receiving end for work efficiency evaluation, the steps including: S901: In response to the production information query command, the task publishing terminal sends a production information query request to the relay server.

[0103] The production information query request includes at least the task receiving end identification information.

[0104] S902: In response to the production information query request, the relay server obtains the historical statistical information of the corresponding outgoing task file based on the task receiver identification information.

[0105] The historical statistical information includes at least one of the following: the historical completion rate of the outgoing task files of the corresponding task receiving end, the historical completion time of the outgoing task files of the corresponding task receiving end, and the historical number of outgoing task files completed by the corresponding task receiving end.

[0106] S903: The relay server sends the historical statistical information of the outgoing task file to the task publishing terminal.

[0107] S904: The task publishing terminal receives and displays the historical statistical information of the outgoing task files.

[0108] Example 2 Please refer to Figure 6 This application also provides an external animation file creation system to implement the steps of the external animation file creation method described in the above embodiments. The external animation file creation system includes: a task publishing terminal, a relay server, and a task receiving terminal.

[0109] The task publishing terminal is used to create an outgoing task file, and in response to a task publishing instruction, send the outgoing task file to a relay server, and in response to the received submission file push information, authenticate the completed outgoing task file, and receive the completed outgoing task file after successful authentication; wherein, the outgoing task file includes task metadata, and the task metadata includes task receiver identification information. The relay server is configured to, in response to a received outgoing task file, generate task notification information based on the task receiver identification information, and in response to a received completed outgoing task file, generate corresponding submission file push information, and send the submission file push information and the completed outgoing task file to the task publisher; wherein, the submission file push information includes the authentication information of the completed outgoing task file. The task receiving end is configured to access the relay server according to a preset polling cycle, obtain task notification information corresponding to itself from the relay server, and in response to a task acquisition instruction, obtain an outgoing task file corresponding to the task notification information from the relay server, and in response to a task submission instruction, send the completed outgoing task file to the relay server.

[0110] It should be noted that the above embodiment of the external animation file production system is only illustrated by the division of the above functional modules when implementing an external animation file production method. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0111] Furthermore, the external animation file creation system provided in the above embodiments and the external animation file creation method in Embodiment 1 are based on the same concept. The implementation process is detailed in the method embodiment, namely Embodiment 1, and will not be repeated here.

[0112] The embodiments described above are merely examples of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and this application also intends to include these modifications and variations.

Claims

1. An external animation file production method characterized by comprising: Includes the following steps: The task publishing end creates an external task file, wherein the external task file includes task metadata, and the task metadata includes task receiver identification information; The task publishing terminal responds to the task publishing command by sending the outgoing task file to the relay server; In response to the received outgoing task file, the relay server generates task notification information based on the task receiver identification information. The task receiving end accesses the relay server according to a preset polling cycle and obtains the task notification information corresponding to itself from the relay server; In response to the task acquisition instruction, the task receiving end retrieves the outgoing task file corresponding to the task notification information from the relay server; In response to the task submission command, the task receiving end sends the completed outgoing task file to the relay server. In response to the received completed outgoing task file, the relay server generates corresponding submission file push information and sends the submission file push information and the completed outgoing task file to the task publishing end. In response to the received submission file push information, the task publishing terminal verifies the completed external task file and receives the completed external task file after successful verification.

2. The external animation file production method according to claim 1, characterized by, The outgoing task file also includes a task data package, which includes several animation files to be produced, animation asset files associated with the animation files to be produced, and associated animation files associated with the animation files to be produced.

3. The method for creating external animation files according to claim 2, characterized in that, The steps for creating an external task file on the task publishing platform include: In response to the file selection command, the task publishing terminal enters the file association display interface of the corresponding animation file to be produced. The file association display interface displays several animation files and animation asset files stored in a preset path. The task publishing terminal responds to the file selection instruction and obtains the corresponding animation file and animation asset file from the file association display interface; In response to the file association command, the task publishing terminal outputs the animation file to be produced, the corresponding animation file in the file association display interface, and the animation asset file as the task data package of the outgoing task file. or, The steps for creating an external task file on the task publishing end also include: The task publishing terminal obtains a preset animation resource association directory table, wherein the preset animation resource association directory table includes at least a number of animation resource association directories, and the animation resource association directories store a number of animation files and animation asset files. The task publishing terminal responds to the file selection instruction, obtains the corresponding animation file to be produced, and displays the animation resource association directory in the animation resource association directory table; The task publishing terminal responds to the directory selection instruction and matches the animation file to be produced with the animation resource associated directory according to the preset associated resource matching rules. If the match is successful, the animation file and animation asset file stored in the corresponding animation resource associated directory are obtained. In response to the file association command, the task publishing terminal outputs the animation file to be produced, the animation files stored in the corresponding animation resource association directory, and the animation asset files as the task data package of the outgoing task file.

4. The external animation file production method according to claim 1, characterized by, The steps by which the task receiving end, in response to a task retrieval command, retrieves the outgoing task file corresponding to the task notification information from the relay server include: The task receiving end sends a confirmation request for the task notification information to the relay server. In response to the confirmation request, the relay server marks the status of the task notification information as read and returns the download address of the outgoing task file corresponding to the task notification information to the task receiving end. The task receiving end downloads the outgoing task file corresponding to the task notification information from the relay server based on the download address.

5. The external animation file production method according to claim 1, characterized by, The task receiving end includes the creator end and the review end; The step of the task receiving end sending the completed outgoing task file to the relay server in response to the task submission command includes: In response to the completion instruction, the creator sends the completed external task file to the reviewer. The reviewer performs an art review on the completed outgoing task files; Once the art review is approved, the reviewing end marks the completed outgoing task file with a review completion identifier and sends it to the relay server. The review completion identifier includes at least the identity information of the reviewing end.

6. The method for producing outsourced animation according to claim 5, characterized in that, The task metadata also includes information on artistic style requirements; The steps for the reviewer to conduct an art review of the completed outgoing task files include: The review end obtains the art style requirement information and, based on a preset art style matching threshold, determines whether the completed outgoing task file conforms to the art style requirement information. If the completed outgoing task file meets the art style matching threshold, then the completed outgoing task file is determined to meet the art style requirements and passes the art review of the completed outgoing task file. If the completed outgoing task file does not meet the art style matching threshold, the outgoing task file is returned to the creator and corresponding modification information is sent. The modification information includes at least the art style matching threshold that the outgoing task file does not meet.

7. The method for producing outsourced animation according to claim 6, characterized in that, The art style requirements include standard color styles and standard material samples corresponding to the outgoing task file; the preset art style matching threshold includes at least one of the following: color tolerance range, motion smoothness coefficient, and material deviation. The step of obtaining the art style requirement information and determining whether the completed outgoing task file conforms to the art style requirement information based on a preset art style matching threshold includes: The review end parses the completed outgoing task file and extracts the corresponding image color feature sequence, character action vector sequence and surface material visual features; The review end compares the extracted color feature sequence of the image with the standard color style and determines whether the corresponding deviation value is within the color tolerance range. The reviewer calculates the rate of change between corresponding action frames based on the character's action vector sequence, and determines whether the stability of the rate of change satisfies the action smoothness coefficient. The review end will calculate the matching degree between the extracted visual features of the surface material and the features of the standard material sample, and determine whether the corresponding matching degree meets the requirements of the material deviation degree.

8. The method for creating external animation files according to claim 1, characterized in that, The steps of the task publishing terminal responding to the received submission file push information by authenticating the completed outgoing task file and receiving the completed outgoing task file after successful authentication include: The task publishing terminal obtains the first outgoing task identifier corresponding to the completed outgoing task file from the submitted file push information; The task publishing terminal matches the first outgoing task identifier with the second outgoing task identifier of the outgoing task file stored in its own storage and sent to the relay server. If the matching result is consistent, the authentication is deemed successful, and the task publishing terminal receives and stores the completed outgoing task file.

9. The method for creating external animation files according to claim 1, characterized in that, The method for creating external animation files also includes: In response to the production information query command, the task publishing end sends a production information query request to the relay server, wherein the production information query request includes at least the task receiving end identification information; In response to the production information query request, the relay server obtains the historical statistical information of the corresponding outgoing task file based on the task receiving end identification information. The historical statistical information includes at least one of the following: the historical completion rate of the outgoing task file of the corresponding task receiving end, the historical completion time of the outgoing task file of the corresponding task receiving end, and the historical number of outgoing task files completed by the corresponding task receiving end. The relay server sends the historical statistical information of the outgoing task files to the task publishing terminal; The task publishing terminal receives and displays historical statistical information of the outgoing task files.

10. A system for creating external animation files, characterized in that, The external animation file creation system includes a task publishing terminal, a relay server, and a task receiving terminal; The task publishing terminal is used to create an outgoing task file, and in response to a task publishing instruction, send the outgoing task file to a relay server, and in response to the received submission file push information, authenticate the completed outgoing task file, and receive the completed outgoing task file after successful authentication; wherein, the outgoing task file includes task metadata, and the task metadata includes task receiver identification information. The relay server is configured to, in response to a received outgoing task file, generate task notification information based on the task receiver identification information, and in response to a received completed outgoing task file, generate corresponding submission file push information, and send the submission file push information and the completed outgoing task file to the task publisher; wherein, the submission file push information includes the authentication information of the completed outgoing task file. The task receiving end is configured to access the relay server according to a preset polling cycle, obtain task notification information corresponding to itself from the relay server, and in response to a task acquisition instruction, obtain an outgoing task file corresponding to the task notification information from the relay server, and in response to a task submission instruction, send the completed outgoing task file to the relay server.

Images