Animation file management method and system, readable storage medium and computer equipment

Abstract

The invention provides an animation file management method and system, a readable storage medium and computer device.The method comprises the steps that retrieval information is obtained according to a label retrieval request initiated by a user in a target animation item; performing matching retrieval in an animation file resource library of the target animation item according to the retrieval information, and displaying a plurality of corresponding animation file identifiers; in response to a selection instruction of a user for the displayed animation file identifier, obtaining a corresponding animation file according to an entity storage path corresponding to the animation file identifier; and in response to an animation production instruction of a user, carrying out animation production based on the obtained animation file, and generating an animation video corresponding to the target animation item. Therefore, by applying the technical scheme of the invention, the animation production efficiency can be effectively improved.

Description

Technical Field

[0001] This application relates to the field of animation production, and in particular to an animation file management method, system, readable storage medium, and computer device. Background Technology

[0002] In the current field of computer animation (CG) production, the complexity of animation projects is increasing day by day. The digital assets involved, such as models, materials, animation clips, and special effects shots, are not only numerous, but also often need to be reused between different animation projects.

[0003] However, the existing mainstream asset management model usually adopts a "full project preparation" preprocessing strategy: that is, at the start of the animation project, all possible animation files are downloaded or copied from the central storage to the animation project's dedicated local storage space in advance, forming a static and closed set of animation files for the animators to use in creating animation videos.

[0004] This "full localization" management approach has significant drawbacks: First, it leads to severe redundancy and synchronization burden on storage resources; more importantly, because the animation file set is predetermined, its organization is often disconnected from the current creative intent and descriptive context of the animation project. However, animators can only search for the required animation files within this fixed set of animation files, relying on basic animation file attributes or loose global keywords, and cannot accurately locate the required animation files based on the logical dimensions (creative intent and descriptive context) closely related to the current animation project.

[0005] Therefore, animators often find themselves in a dilemma of "difficulty in finding materials and interruption of the creative flow" in their daily creative work, which seriously restricts the overall efficiency and response speed of animation production. Summary of the Invention

[0006] Based on this, the purpose of this application is to provide an animation file management method, system, readable storage medium, and computer device that can effectively improve the overall efficiency and response speed of animation production.

[0007] The objective of this application can be achieved through the following technical solutions: In a first aspect, embodiments of this application provide an animation file management method, comprising the following steps: obtaining retrieval information based on a tag retrieval request initiated by a user within a target animation project, wherein the retrieval information includes at least tag information set by the user for animation files associated with the target animation project; performing a matching retrieval in the animation file resource library of the target animation project based on the retrieval information, displaying a plurality of corresponding animation file identifiers, wherein the animation file identifiers correspond to the animation files, and the animation file resource library of the target animation project stores at least: a first correspondence mapping from the tag information to the animation file identifiers, and a second correspondence mapping from the animation file identifiers to the physical storage paths of the animation files; in response to a user's selection instruction for the displayed animation file identifiers, obtaining the corresponding animation file based on the physical storage path corresponding to the animation file identifier; and in response to a user's animation production instruction, performing animation production based on the obtained animation file to generate an animation video corresponding to the target animation project.

[0008] Secondly, embodiments of this application provide an animation file management system, comprising: a retrieval information acquisition unit, configured to acquire retrieval information based on a tag retrieval request initiated by a user within a target animation project, wherein the retrieval information includes at least tag information set by the user for animation files associated with the target animation project; a matching retrieval unit, configured to perform a matching retrieval in the animation file resource library of the target animation project based on the retrieval information, and display a plurality of corresponding animation file identifiers, wherein the animation file identifiers correspond to the animation files, and the animation file resource library of the target animation project stores at least: a first correspondence mapping from the tag information to the animation file identifiers, and a second correspondence mapping from the animation file identifiers to the entity storage paths of the animation files; an animation file acquisition unit, configured to acquire the corresponding animation file based on the entity storage path corresponding to the animation file identifier in response to a user's selection instruction for the displayed animation file identifiers; and an animation video production unit, configured to perform animation production based on the acquired animation files in response to a user's animation production instruction, generating an animation video corresponding to the target animation project.

[0009] Thirdly, embodiments of this application provide a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the steps in the animation file management method as described in the first aspect.

[0010] Fourthly, embodiments of this application provide a computer device, comprising: a processor and a memory; the memory storing a computer-readable program executable by the processor; and the processor executing the computer-readable program to implement the steps of the animation file management method as described in the first aspect.

[0011] Compared to existing technologies, the method described in this application achieves a paradigm shift in animation file management by introducing an animation file resource library bound to the target animation project and a two-level mapping relationship. Specifically, in the technical solution of this application, firstly, in response to a user's tag search request initiated within an animation project, the tag information set by the user based on the context of the animation project is obtained as search conditions; then, in the animation file resource library of the corresponding animation project, a matching search is performed according to the stored "tag information-animation file identifier" mapping relationship, and the results are displayed; finally, only when the user selects a specific file, the corresponding physical file is obtained according to the "animation file identifier-physical storage path" mapping relationship for animation production. Thus, the method described in this application, by replacing the full preparation in existing technologies with on-demand acquisition of animation files, and by transforming the organization and retrieval dimensions of corresponding animation files from basic attributes and global keywords to semantic tags closely related to the creative intent of the animation project, solves the technical defects of storage redundancy and inefficient retrieval in existing technologies, significantly improving the workflow continuity and overall efficiency of animation production.

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

[0013] Figure 1 A flowchart of an animation file management method provided in this application; Figure 2 A flowchart illustrating the steps of recommending input tag information to the user in the animation file management method provided in this application; Figure 3 Flowchart of the steps in the animation file management method provided in this application for identifying and alerting to the risk of modifying tag information; Figure 4 A structural schematic diagram of an animation file management system provided in this application; Figure 5 A schematic diagram of an electronic device used to implement the animation file management method provided in this application. Detailed Implementation

[0014] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0015] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0016] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0017] Those skilled in the art will understand that the terms "client," "terminal," and "terminal device" as used in this application include both devices that are wireless signal receivers, which are devices that only have wireless signal receiver capabilities without transmission capabilities, and devices that have receiving and transmitting hardware, which have receiving and transmitting hardware capable of bidirectional communication on a bidirectional communication link. Such devices may include: cellular or other communication devices such as personal computers or tablets, which have single-line displays or multi-line displays or cellular or other communication devices without multi-line displays; PCS (Personal Communications Service), which can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant), which may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar, and / or GPS (Global Positioning System) receiver; and conventional laptop and / or handheld computers or other devices that have and / or include radio frequency receivers. As used herein, "client," "terminal," and "terminal device" can be portable, transportable, installed in a means of transportation (air, sea, and / or land), or suitable and / or configured to operate locally and / or in a distributed manner, operating in any other location on Earth and / or in space. "Client," "terminal," and "terminal device" as used herein can also be a communication terminal, an internet access terminal, or a music / video playback terminal, such as a PDA, a MID (Mobile Internet Device), and / or a mobile phone with music / video playback capabilities, or a smart TV, set-top box, etc.

[0018] The hardware referred to by the names "server," "client," and "service node" in this application is essentially a computer device with the equivalent capabilities of a personal computer. It is a hardware device with the necessary components revealed by the von Neumann architecture, such as a central processing unit (including an arithmetic logic unit and a control unit), memory, input devices, and output devices. The computer program is stored in its memory, and the central processing unit loads the program stored in the secondary storage into the main memory to run it, execute the instructions in the program, and interact with the input and output devices to complete specific functions.

[0019] It should be noted that the concept of "server" used in this application can also be extended to the case of server clusters. Based on the network deployment principles understood by those skilled in the art, the servers should be logically divided. Physically, these servers can be independent of each other but accessible through interfaces, or they can be integrated into a single physical computer or a computer cluster. Those skilled in the art should understand this flexibility and should not use it to constrain the implementation of the network deployment method in this application.

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

[0021] Example 1 Please refer to Figure 1 , Figure 1 A flowchart illustrating an animation file management method provided in this application. The method includes the following steps: S10: Obtain search information based on the tag search request initiated by the user within the target animation project; S20: Based on the search information, perform a matching search in the animation file resource library of the target animation project and display several corresponding animation file identifiers; S30: In response to the user's selection instruction for the displayed animation file identifier, obtain the corresponding animation file according to the entity storage path corresponding to the animation file identifier; S40: In response to the user's animation production instruction, perform animation production based on the acquired animation file to generate an animation video corresponding to the target animation project.

[0022] Compared with existing technologies, the technical solution of this application effectively overcomes the technical defects of the traditional "full localization" animation asset management model, such as redundant storage resources, low retrieval efficiency, and interruption of the creation process, by constructing a complete management process based on project-based tag mapping and on-demand acquisition of animation files. Specifically, in the technical solution of this application, firstly, in response to the tag search request initiated by the user within the target animation project, the tag information set by the user for the animation files in the target animation project is used as the search information. This ensures that the search dimensions are closely related to the current creative intent and semantic context of the animation project, solving the technical problem of the disconnect between the animator's search intent and the organization of animation files. Secondly, in the animation file resource library of the target animation project, the matching search is performed based on the pre-stored mapping relationship of "tag information - animation file identifier" and the corresponding results are displayed. This realizes the logical and precise location of animation files, replacing the traditional method of inefficient browsing or global keyword matching in the entire file set. Finally, only after the user selects the animation file identifier corresponding to the required animation file, the physical file corresponding to the animation file is obtained according to the mapping relationship of "animation file identifier - physical storage path" for animation production. This realizes the dynamic on-demand calling of animation files, fundamentally avoiding the duplicate storage and synchronization burden of animation files.

[0023] Therefore, the technical solution of this application transforms the management and acquisition of animation files from a physical copy and static collection organization mode to an on-demand service mode based on semantic tags and logical mapping. This not only significantly saves storage resources for animation files and simplifies the synchronization process of animation files, but also enables animators to quickly and accurately locate the required production materials (animation files) according to the production context of the animation project. This ensures the continuity and efficiency of the animation creation process, thereby improving the overall response speed and collaborative efficiency of animation video production.

[0024] For step S10: Obtain search information based on the tag search request initiated by the user within the target animation project.

[0025] The retrieval information includes at least the tag information set by the user for animation files associated with the target animation project; the target animation project refers to an independent animation video creation task unit, which includes its own production context, resource set, and progress management; the animation files include various digital assets required to constitute the animation video, such as 3D models, texture maps, rigging skeletons, animation clips, or special effects shots; the tag information is semantic descriptive keywords or classification labels set by the user within the target animation project for the corresponding animation files based on their own creative intent or the content of the animation files, in order to facilitate subsequent retrieval and identification.

[0026] In this embodiment, when a user needs to find animation files within a specific animation project, this step captures their search intent based on the creative intent and descriptive context of the animation project, which includes the corresponding tag information of the animation project, providing input for subsequent accurate matching.

[0027] In one embodiment, this application provides a graphical user interface for users to initiate the tag retrieval request. The interface can be integrated into the project management module of animation production software and includes a retrieval box or filter panel for inputting or selecting tag information. When a user inputs or selects a tag and confirms the retrieval, a tag retrieval request is constituted. The tag retrieval request and the tag information it contains are then captured, and structured retrieval information is generated for subsequent processing steps.

[0028] In another embodiment, the animation files are each assigned a corresponding tag in different animation projects; when a user initiates a tag search request within an animation project, the matching search is performed based on the animation file resource library of the current animation project, so that the animation file identifier is displayed based on the tag information set for its corresponding animation file in the current animation project.

[0029] As a specific example of this embodiment, the same animation file (e.g., a tree model named "Tree_Model_A") can be tagged with "vegetation" or "background" in an animation project of the "Forest Scene," while it can be tagged with "decoration" or "greenery" in an animation project of the "City Park." Therefore, when an animator searches for the "background" tag in an animation project of the "Forest Scene," the search is only performed in the animation file resource library of that animation project. Thus, "Tree_Model_A" will be retrieved and its corresponding animation file identifier will be displayed because of the "background" tag information set under that animation project. Conversely, if a user searches for the "background" tag information in an animation project of the "City Park," the animation file will not be displayed because this tag information is not set in the animation file resource library of the "City Park" animation project. This ensures that the search results for animation files strictly conform to the semantic context of the current animation project, avoiding search noise caused by cross-animation project tag definition conflicts.

[0030] In one specific embodiment, to improve retrieval flexibility, the retrieval information may include not only keywords of tag information, but also other limiting conditions specified by the user, such as the combination logic of tag information (e.g., "AND" or "OR"), the predefined category directory to which the tag information belongs, or the combined filtering conditions combined with the basic attributes of animation files (e.g., file type, creation time range). Thus, in some specific implementations, all these conditions can be integrated into the retrieval information for comprehensive matching in subsequent steps.

[0031] In one embodiment, step S10 includes: S101: In response to the first user action performed by the user within the project operation interface corresponding to the target animation project, create and display the animation file search box component.

[0032] The project operation interface is the graphical operating environment corresponding to the target animation project in the animation production software, used to centrally manage and present the resources and functions related to the animation project; the animation file search box component is a dynamically generated graphical user interface element used to receive the search content input by the user; the animation file search box component is configured to: receive the tag information input by the user, and use the tag information as the search information for matching and searching in the animation file resource library.

[0033] In this embodiment, by implementing step S101, users can quickly initiate a search for specific tag information by actively inputting text.

[0034] Alternatively, based on the inventive concept of this application, the specific implementation method for obtaining the retrieval information is not limited to the one described above. Those skilled in the art can use other steps to replace step S101 to obtain the retrieval information, thereby continuing to implement other steps of the technical solution of this application. Therefore, in another embodiment, the steps include: S102: In response to a second user operation performed by the user within the project operation interface corresponding to the target animation project, obtain the corresponding tag information as the retrieval information.

[0035] The project operation interface provides a first tag information set corresponding to the target animation project. The first tag information set refers to a list, panel or other visual set presented in the project operation interface that contains all or part of the tag information created and used in the target animation project. The first tag information set includes at least the tag information set by the user for the animation file associated with the target animation project. The tag information is obtained from the first tag information set through the second user operation (e.g., clicking, checking or dragging).

[0036] In this embodiment, by implementing step S102, users can quickly select the corresponding tag information directly from the existing tag set of the animation project without manual input, thus conveniently initiating a search.

[0037] For step S20: Based on the search information, perform a matching search in the animation file resource library of the target animation project and display several corresponding animation file identifiers.

[0038] The animation file identifier corresponds to the animation file and can be a code, name, or encoding that uniquely identifies a specific animation file in the animation file resource library. The animation file resource library of the target animation project is a logical or physical storage unit that stores all relevant mapping data within the animation project. The animation file resource library of the target animation project stores at least: a first correspondence between the tag information and the animation file identifier, and a second correspondence between the animation file identifier and the physical storage path of the animation file.

[0039] In one embodiment, since the user sets tag information for animation files associated with the target animation project, it is understood that those skilled in the art can obtain the first correspondence based on this.

[0040] The first correspondence enables file location based on tag information; the second correspondence allows for the retrieval of the corresponding physical file after locating the animation file identifier, according to the entity storage path. Thus, this step, based on retrieval information including tag information, uses the first correspondence to search and match within the animation file resource library, ultimately presenting the user with one or more animation file identifiers that meet the criteria, thereby completing the logical-layer retrieval.

[0041] In one embodiment, in the target animation project, the animation file is assigned several different tag information, and there is a preset subordinate relationship between the several different tag information. In some optional specific embodiments, the subordinate relationship defines the hierarchy or classification logic between the tag information. For example, in the biological taxonomy system, "Primates" is a tag information belonging to "Mammalia", and "Hominidae" and "Gibbonidae" are tag information belonging to "Primates".

[0042] In this embodiment, step S20 includes: S201: In response to the tag information in the search information, determine a second set of tag information that has a subordinate relationship with the tag information according to the preset subordinate relationship.

[0043] The second tag information set is a dynamically generated tag information set based on subordinate relationships, used to expand the search scope. The second tag information set includes the tag information in the search information and other tag information belonging to that tag information. For example, when a user enters "Primates" for a search, if the tag information of "Hominidae" and "Gibba" belongs to the "Primates" tag information according to the preset subordinate relationships, then the determined second tag information set will include "Primates", "Hominidae", and "Gibba".

[0044] S202: Based on the first correspondence, in the animation file resource library, match and display the animation file identifier that has a mapping relationship with any tag information in the second tag information set.

[0045] Specifically, by querying the first correspondence, all mapping entries whose key values ​​(tag information) fall into the second tag information set are found, and the animation file identifier corresponding to the entry is obtained and displayed. For example, an animation file may only have the "Hominidae" tag information set, but not the "Primates" tag information. By implementing this step, when a user searches for the "Primates" tag information, since "Hominidae" is included in the second tag information set corresponding to the "Primates" tag information, the animation file identifier of that animation file will also be matched and displayed. Thus, intelligent extended retrieval based on the tag hierarchy structure is realized, enabling users to automatically retrieve all animation files associated with lower-level category tags when using higher-level category tags, improving the coverage and convenience of the retrieval.

[0046] For step S30: In response to the user's selection instruction for the displayed animation file identifier, the corresponding animation file is obtained according to the entity storage path corresponding to the animation file identifier.

[0047] In one embodiment, step S30 is used to convert the logical identifier of the animation file into the physical data corresponding to the animation file; wherein, the selection instruction is a selection command issued by the user through a graphical user interface (such as clicking or double-clicking) to a specific animation file identifier displayed, and the physical storage path refers to the specific address (e.g., local file system path, network share path, or cloud storage object identifier) ​​of the physical data of the animation file stored for locating and accessing it.

[0048] In this step, in response to the selection instruction, the second correspondence is queried in the animation file resource library using the selected animation file identifier as the key to obtain the physical storage path uniquely corresponding to the identifier. Subsequently, based on the obtained physical storage path, the corresponding storage location is accessed, and the physical data of the animation file is read and loaded, thereby completing the file acquisition. Thus, this process transparently and accurately maps the logical selection on the front-end interface to the back-end's call to specific animation file data.

[0049] In one optional embodiment, when a user selects the item labeled "Char_001_Rig" by clicking on the animation file identifier list displayed in the aforementioned steps, this click operation generates a selection instruction for that animation file identifier. In response to this instruction, the animation file resource library is queried, and the entity storage path "\AssetsServer\ProjectX\Characters\Char_001.mb" mapped to "Char_001_Rig" is found in the second mapping relationship. Subsequently, the 3D model file "Char_001.mb" is loaded from the specified location on the network storage server "AssetsServer" according to this path and loaded into the creation environment of the current animation production software for use in subsequent animation production steps.

[0050] For step S40: In response to the user's animation production instruction, animation production is performed based on the acquired animation file to generate an animation video corresponding to the target animation project.

[0051] In one embodiment, step S40 is the final output stage of the animation file management method, which transforms the acquired and loaded animation files into the creation environment into the final animated video result. The animation production instructions are commands issued by the user through the animation production software interface to initiate or confirm a series of animation generation and rendering operations, such as clicking the "Render Sequence" or "Export Video" button. The animation production includes, but is not limited to, a series of creation and processing steps such as keyframe setting, motion trajectory editing, camera movement, lighting and special effects compositing, and final image sequence rendering. The animated video refers to the final generated digital video file containing dynamic audiovisual content.

[0052] In this step, in response to the animation production instruction, based on one or more animation files acquired and loaded in the preceding steps, the corresponding animation production process is executed under the target animation project. In some optional embodiments, this process utilizes the rendering engine or other generation modules of the animation production software to process the physical data such as models, actions, and / or scenes corresponding to the animation files, and finally synthesizes and outputs a complete animation video file. Thus, the generated animation video is logically and spatially associated with the target animation project, serving as the final deliverable or intermediate result of the animation project.

[0053] In one optional embodiment, after the user performs motion binding, scene setup, and camera design on the "Char_001.mb" character model file acquired and loaded in step S30, they click the "Render Entire Sequence" button in the timeline interface of the animation production software. This operation constitutes an animation production instruction. In response to this instruction, the animation production software, based on the current project settings (including the loaded "Char_001.mb" file and its motion data, scene lighting, camera paths, etc.), calls the rendering engine to calculate and generate an image sequence frame by frame. After rendering is complete, the software encodes and combines the image sequence into a single video file, such as "ProjectX_Animation_v01.mp4," and automatically saves it to the preset output directory of the target animation project. Thus, a final animation video that completely corresponds to the "target animation project" is generated.

[0054] In addition, this application also provides some animation file management steps that can be used in the animation file management method to manage the tag information of the animation files, the steps including: S50: In response to a third user operation performed by the user within the project operation interface corresponding to the target animation project, display the tag editing interface of the animation file corresponding to the third user operation.

[0055] The third user operation is an interactive action initiated by the user in the project operation interface for a specific animation file, with the intention of managing its tag information. For example, right-clicking the animation file identifier and selecting "Edit Tag" from the context menu. The tag editing interface is an independent graphical user interface panel or floating window, which is specifically used to display and edit all the tag information that the selected animation file is currently associated with (i.e., has been set).

[0056] S60: In response to the user's triggering operation on the label editing control on the label editing interface, execute the corresponding label management behavior.

[0057] The label editing control is a graphical button, icon, or menu item integrated into the label editing interface to trigger specific label management functions (such as adding, deleting, or modifying).

[0058] In one embodiment, the tag management behavior includes at least one of the following: S601: In response to the operation of adding a control to the label, display the label input area, receive the label information input by the user, and associate the label information with the animation file to update the first correspondence in the animation file resource library.

[0059] In one specific embodiment, when a user clicks the "Add Tag" control, a tag input area that can receive text input is displayed in the tag editing interface. After the user enters new tag information (such as "Main Character") in the tag input area and confirms, the tag information is associated with the current animation file (i.e., set). Subsequently, a new entry is added to the animation file resource library, mapping the tag information to the animation file identifier, thereby completing the update of the first correspondence. Thus, the animation file can be retrieved subsequently using the newly added tag information.

[0060] S602: In response to the operation of the tag deletion control, remove the association between the target tag information displayed in the tag editing interface and the animation file, so as to update the first correspondence in the animation file resource library.

[0061] In one specific embodiment, a user selects one or more target tag information (e.g., "draft version") from the tag list displayed in the tag editing interface and triggers the "delete" control. In response to this operation, the system removes the association between the animation file and these target tag information (i.e., cancels the setting). Subsequently, the corresponding mapping entry is deleted from the animation file resource library, thereby updating the first correspondence. Afterward, the animation file will no longer be retrieved using the deleted tag information.

[0062] S603: In response to the operation of the tag modification control, for the target tag information displayed in the tag editing interface, display the tag modification area, receive the tag information modified by the user, and associate the modified tag information with the animation file to update the first correspondence in the animation file resource library.

[0063] In one specific embodiment, the user selects an existing target tag information (such as "rock texture") in the tag editing interface and triggers the "modify" control. The system pre-fills a tag modification area. The user modifies the text in the tag modification area to the new tag information (such as "granite texture") and confirms. The system then replaces the association between the animation file and the original target tag information with the association with the modified tag information (i.e., updates the settings). At the same time, in the animation file resource library, the corresponding mapping entries are updated: the mapping from the original tag information to the animation file identifier is deleted, and a new mapping from the new tag information to the animation file identifier is established, thereby completing the update of the first correspondence.

[0064] Please refer to Figure 2 , Figure 2 A flowchart illustrating the steps of recommending input tag information to the user in the animation file management method provided in this application.

[0065] In one embodiment, the steps of displaying a label input area and receiving label information input by the user in response to an operation of adding a control to a label include: S6011: At the same time or after displaying the label input area, a preset computer vision algorithm is invoked to extract the visual content features of the animation file.

[0066] The computer vision algorithm is a set of pre-programmed instructions or models used to analyze and understand digital image or video content, such as a convolutional neural network (CNN) model; the visual content features refer to the digital information extracted from the animation file by the computer vision algorithm that can characterize its visual content, such as color histograms, texture features, shape contour features, or high-level semantic feature vectors extracted by deep learning models.

[0067] S6012: Match the visual content features with a preset tag feature library, and generate several recommended tag information based on the obtained matching results.

[0068] The tag feature library is a pre-built database that stores multiple known tag information and their corresponding feature data (such as standard feature vectors). The matching refers to the process of calculating the similarity or correlation between the extracted visual content features and the feature data corresponding to each tag information in the tag feature library. The matching results include, but are not limited to, similarity scores or classification probabilities. The recommended tag information is a list of tag information that is generated based on the matching results (for example, selecting the tag information corresponding to the top N results with the highest similarity) and suggests that users adopt it.

[0069] S6013: Display the information of the several recommended tags in the tag editing interface.

[0070] In one specific embodiment, the generated recommended tag information is presented in the tag editing interface in the form of a list, tag cloud, or button, usually adjacent to the tag input area, for users to view and select.

[0071] S6014: In response to the user's selection of the recommended tag information, the selected recommended tag information is used as the tag information input by the user and associated with the animation file.

[0072] In one embodiment, associating with the animation file means setting the recommendation tag information for the animation file. It is understood that other "associations" in this application embodiment are similar.

[0073] In one specific embodiment, when a user selects one or more recommended tags from the displayed recommendation list through clicking or other operations, this selection operation is captured; subsequently, the selected recommended tags are automatically filled into the tag input area, and the association / setting with the animation file is performed (i.e., updating the first correspondence), which is equivalent to the user manually entering these tag information. Thus, intelligent tag information input is achieved.

[0074] Please refer to Figure 3 , Figure 3 A flowchart illustrating the steps for identifying and alerting users to the risk of modifying tag information in the animation file management method provided in this application.

[0075] In one embodiment, after the steps of displaying a label modification area for the target label information displayed in the label editing interface and receiving the modified label information from the user in response to an operation on the label modification control, the method further includes: S6031: Obtain the first semantic vector corresponding to the target label information and the second semantic vector corresponding to the modified label information.

[0076] The semantic vector is a high-dimensional numerical vector used to mathematically represent the semantics of the tag information; the first semantic vector and the second semantic vector respectively represent the semantics of the tag information before and after modification; in some embodiments, the text of the tag information can be converted into a semantic vector through a word embedding model (such as Word2Vec, BERT).

[0077] S6032: Calculate the semantic similarity between the first semantic vector and the second semantic vector.

[0078] The semantic similarity is a numerical indicator used to quantify the degree of closeness between the two semantic vectors in the semantic space, and can be obtained by calculating cosine similarity, Euclidean distance, etc.

[0079] S6033: When the semantic similarity is higher than a preset risk threshold, query the animation file identifier corresponding to the animation file in the animation file resource library.

[0080] The risk threshold is a preset value used to determine whether modifications to the label information may lead to significant semantic changes.

[0081] In some embodiments, when the semantic similarity is higher than this risk threshold, it indicates that the semantic difference between the tag information before and after the modification is large, which may affect the generated content (such as animated videos) that depends on the semantics of the original tag, thus triggering the subsequent impact analysis step.

[0082] S6034: Based on the animation file identifier obtained from the query, determine the animation video obtained by using the animation file to create the animation in the target animation project.

[0083] In one embodiment, the system records the usage relationship between animation files in the target animation project and the final generated animation video; therefore, this step queries the usage relationship through the animation file identifier to identify all animation videos that reference this animation file.

[0084] S6035: Generate modification impact prompt information corresponding to the target animation project and display it in the tag editing interface.

[0085] The modification impact notification information includes at least the identification information of the animated video.

[0086] In one embodiment, the modification impact notification is a notification message used to inform the user that the modification of the tag information may affect the related animated video. It includes at least the identification information of the identified animated video, such as the video name, number, or storage path, so that the user can locate and verify it.

[0087] In one specific embodiment, the user changes the tag information of the animation file "Animal_A" from "Carnivora" to "Herbivora". At this time, the semantic vectors of "Carnivora" and "Herbivora" are obtained and the similarity is calculated. The result is much higher than the risk threshold. Then, the animation file identifier of "Animal_A" is found in the resource library, and it is determined from the project records that it was used to generate the animation videos "Scene_1_Final.mp4" and "Scene_2_Teaser.mp4". Then, a prompt window pops up in the tag editing interface, showing: "Impact of modification prompt: This tag change may affect the following videos that use this animation file: [Scene_1_Final.mp4], [Scene_2_Teaser.mp4], please confirm." In one embodiment, the animation file management method further includes a step of version control for the animation files. These steps allow users to perform controlled updates to the animation files in a collaborative environment and record their modification history.

[0088] In one specific embodiment, the version modification management steps include: S70: In response to the user's modification mark operation on the animation file, the animation file is placed in the marked modification state.

[0089] The modification mark operation is an action initiated by the user through the corresponding interface, with the intention of exclusively modifying the animation file.

[0090] In one embodiment, when the animation file is in the marked-modification state, only the user who initiated the operation has the permission to upload a new version of the animation file; other users cannot upload new versions during this period, but can read or create animations based on the current version of the animation file. When the animation file is not in the marked-modification state, multiple users are free to upload their own new version files based on the current version.

[0091] S80: In response to a modification completion operation initiated by a user with authority (including the file modifier or a user with specific management authority) on the animation file, cancel the marked modification status.

[0092] S90: During the marked modification state, respond to multiple file submission operations initiated by the user and perform version management on the animation file.

[0093] Specifically, during the entire period of the marked modification state, each file submission operation by the user is recorded as a "submission", but a new version of the animation file is not immediately generated. Meanwhile, during this period, the content of the most recently submitted file is continuously used as the temporary latest content of the animation file, which can be previewed by the user or other authorized users within the project or used as a basis for further work. However, for external records, the corresponding file version number remains unchanged.

[0094] When the marked modification status is canceled through step S80, the system officially creates a new version of the animation file from the last submitted file content and assigns it a new version identifier (e.g., an incrementing version number). Simultaneously, the system associates all submission records from the entire marked modification period with this finally generated new version.

[0095] In one specific implementation, User A initiated a modification marking operation on the animation file "Character_Rig_v2.ma", putting the file into a marked modification state. Afterward, only User A could submit updates to this file. User A submitted three updates to the file within a day (e.g., fixing binding errors, adjusting weights, and adding controllers). During User A's operations, the system interface displayed the file as "Version 2 (3rd commit)," and the temporary latest content seen by project members was the modification of the third commit. The next day, User A (or the project manager) performed a modification completion operation; the system then canceled the marked modification state and officially saved the third commit file as "Character_Rig_v3.ma," and the version history recorded that Version 3 was created by User A and generated from Version 2 after three commits.

[0096] Example 2 Please refer to Figure 4 This application also provides an animation file management system to implement the steps of the animation file management method described in the above embodiments. The animation file management system includes: an information retrieval unit 1001, a matching retrieval unit 1002, an animation file acquisition unit 1003, and an animation video production unit 1004; The retrieval information acquisition unit 1001 is used to acquire retrieval information based on the tag retrieval request initiated by the user in the target animation project, wherein the retrieval information includes at least the tag information set by the user for the animation files associated with the target animation project in the target animation project; The matching retrieval unit 1002 is used to perform matching retrieval in the animation file resource library of the target animation project according to the retrieval information, and display a number of corresponding animation file identifiers. The animation file identifiers correspond to the animation files. The animation file resource library of the target animation project stores at least: a first correspondence relationship from the tag information to the animation file identifiers, and a second correspondence relationship from the animation file identifiers to the entity storage path of the animation files. The animation file acquisition unit 1003 is used to acquire the corresponding animation file according to the entity storage path corresponding to the animation file identifier in response to the user's selection instruction for the displayed animation file identifier; The animation video production unit 1004 is configured to respond to the user's animation production instructions, perform animation production based on the acquired animation file, and generate an animation video corresponding to the target animation project.

[0097] It should be noted that the animation file management system provided in the above embodiments is only illustrated by the division of the above functional modules when implementing the animation file management method. In actual applications, 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.

[0098] Furthermore, the animation file management system provided in the above embodiments and the animation file management 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.

[0099] Example 3 This application provides a computer device, such as Figure 5 As shown, the computer device 21 may include: a processor 210, a memory 211, and a computer program 212 stored in the memory 211 and capable of running on the processor 210, such as an animation file management program; when the processor 210 executes the computer program 212, it implements the steps in Embodiment 1 above.

[0100] The processor 210 may include one or more processing cores. The processor 210 connects to various parts within the computer device 21 using various interfaces and lines. It executes various functions of the computer device 21 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 211, and by accessing data in the memory 211. Optionally, the processor 210 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 210 may integrate one or more of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required to be displayed on the touch screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 210 and may be implemented as a separate chip.

[0101] The memory 211 may include random access memory (RAM) or read-only memory. Optionally, the memory 211 may include a non-transitory computer-readable storage medium. The memory 211 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 211 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch instructions), instructions for implementing the various method embodiments described above, etc.; the data storage area may store data involved in the various method embodiments described above, etc. Optionally, the memory 211 may also be at least one storage device located remotely from the aforementioned processor 210.

[0102] Example 4 This application also provides a computer storage medium that can store multiple instructions. These instructions are applicable to the steps of an animation file management method according to the above embodiments, which are loaded and executed by a processor. For details of the execution process, please refer to the specific description of the above embodiments, which will not be repeated here.

[0103] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0104] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0105] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0106] In the embodiments provided in this application, it should be understood that the disclosed apparatus / terminal devices and methods can be implemented in other ways. For example, the apparatus / terminal device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0107] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0108] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0109] If integrated modules / units are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms.

[0110] 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. A method for managing animation files, characterized in that, Includes the following steps: Based on the tag search request initiated by the user within the target animation project, search information is obtained, wherein the search information includes at least the tag information set by the user for the animation files associated with the target animation project within the target animation project; Based on the search information, a matching search is performed in the animation file resource library of the target animation project, and several corresponding animation file identifiers are displayed. The animation file identifiers correspond to the animation files. The animation file resource library of the target animation project stores at least: a first correspondence mapping from the tag information to the animation file identifiers, and a second correspondence mapping from the animation file identifiers to the entity storage paths of the animation files. In response to the user's selection instruction for the displayed animation file identifier, the corresponding animation file is obtained according to the entity storage path corresponding to the animation file identifier; In response to the user's animation production instructions, the system performs animation production based on the acquired animation files, generating an animated video corresponding to the target animation project.

2. The animation file management method according to claim 1, characterized in that: The animation files are each assigned a corresponding tag in different animation projects. When a user initiates a tag search request within an animation project, the matching search is performed based on the animation file resource library of the current animation project, so that the animation file identifier is displayed based on the tag information set for its corresponding animation file in the current animation project.

3. The animation file management method according to claim 1, characterized in that, The steps to obtain search information based on the tag search request initiated by the user within the target animation project include: In response to a first user operation performed by the user within the project operation interface corresponding to the target animation project, an animation file search box component is created and displayed. The animation file search box component is configured to: receive tag information input by the user and use the tag information as the search information for matching and searching in the animation file resource library. or, In response to a second user operation performed by the user within the project operation interface corresponding to the target animation project, the corresponding tag information is obtained as the retrieval information. The project operation interface provides a first tag information set corresponding to the target animation project. The first tag information set includes at least the tag information set by the user for the animation file associated with the target animation project. The tag information is obtained from the first tag information set through the second user operation.

4. The animation file management method according to claim 1, characterized in that: In the target animation project, the animation file is set with several different tag information, and there is a preset subordinate relationship between the several different tag information; The steps of matching and searching in the animation file resource library of the target animation project based on the search information, and displaying the corresponding animation file identifiers, include: In response to the tag information in the search information, a second set of tag information that has a subordinate relationship with the tag information is determined according to the preset subordinate relationship, wherein the second set of tag information includes the tag information in the search information and other tag information that belongs to the tag information; Based on the first correspondence, in the animation file resource library, the animation file identifier that has a mapping relationship with any tag information in the second tag information set is matched and displayed.

5. The animation file management method according to claim 1, characterized in that, The animation file management method further includes a step of managing the tag information of the animation file, the step including: In response to a third user operation performed by the user within the project operation interface corresponding to the target animation project, a tag editing interface for the animation file corresponding to the third user operation is displayed; In response to a user's triggering operation on the tag editing control in the tag editing interface, the corresponding tag management behavior is executed, wherein the tag management behavior includes at least one of the following: In response to the operation of adding a control to a label, a label input area is displayed, label information input by the user is received, and the label information is associated with the animation file to update the first correspondence in the animation file resource library; In response to the operation of the tag deletion control, the association between the target tag information displayed in the tag editing interface and the animation file is removed, so as to update the first correspondence in the animation file resource library; In response to the operation of the tag modification control, a tag modification area is displayed for the target tag information displayed in the tag editing interface, the modified tag information is received from the user, and the modified tag information is associated with the animation file to update the first correspondence in the animation file resource library.

6. The animation file management method according to claim 5, characterized in that, The steps for displaying the label input area and receiving label information input by the user in response to an operation of adding a control to a label include: Simultaneously or after displaying the label input area, a preset computer vision algorithm is invoked to extract the visual content features of the animation file; The visual content features are matched with a preset tag feature library, and several recommended tag information are generated based on the matching results. The recommended tag information is displayed in the tag editing interface; In response to the user's selection of the recommended tag information, the selected recommended tag information is used as the tag information input by the user and associated with the animation file.

7. The animation file management method according to claim 5, characterized in that, After the steps of responding to an operation on the label editing control, displaying the label editing area for the target label information displayed in the label editing interface, and receiving the modified label information from the user, the method further includes: Obtain the first semantic vector corresponding to the target label information and the second semantic vector corresponding to the modified label information; Calculate the semantic similarity between the first semantic vector and the second semantic vector; When the semantic similarity is higher than a preset risk threshold, the animation file identifier corresponding to the animation file is queried in the animation file resource library. Based on the animation file identifier obtained from the query, the animated video obtained by using the animation file to create the animation is determined in the target animation project; Generate modification impact prompt information corresponding to the target animation project and display it in the tag editing interface; wherein, the modification impact prompt information includes at least the identification information of the animation video.

8. An animation file management system, characterized in that, The animation file management system includes: The information retrieval unit is used to obtain retrieval information based on the tag retrieval request initiated by the user within the target animation project, wherein the retrieval information includes at least the tag information set by the user for the animation files associated with the target animation project in the target animation project; The matching and retrieval unit is used to perform matching and retrieval in the animation file resource library of the target animation project according to the retrieval information, and display a number of corresponding animation file identifiers, wherein the animation file identifiers correspond to the animation files, and the animation file resource library of the target animation project stores at least: a first correspondence relationship from the tag information to the animation file identifiers, and a second correspondence relationship from the animation file identifiers to the entity storage paths of the animation files; An animation file acquisition unit is used to, in response to a user's selection instruction for the displayed animation file identifier, acquire the corresponding animation file according to the entity storage path corresponding to the animation file identifier; An animation video production unit is used to respond to the user's animation production instructions, perform animation production based on the acquired animation file, and generate an animation video corresponding to the target animation project.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the steps of the animation file management method as described in any one of claims 1 to 7.

10. A computer device, characterized in that, include: Processor and memory; The memory stores a computer-readable program that can be executed by the processor; when the processor executes the computer-readable program, it implements the steps of the animation file management method as described in any one of claims 1 to 7.

Images