Multimedia file acceptance methods and systems

Abstract

This disclosure relates to a method and system for accepting multimedia files. The method includes: acquiring a multimedia file to be accepted; sending an acceptance instruction for the multimedia file to multiple acceptance terminals; receiving acceptance results returned by the acceptance terminals; and responding according to the acceptance results. The multimedia file acceptance method and system of this disclosure, with multiple acceptance terminals accepting the multimedia file, can promptly correct multimedia files that do not meet requirements or have defects, effectively shortening the multimedia file development process.

Description

Technical Field

[0001] This disclosure generally relates to the field of computer technology. More specifically, this disclosure relates to methods and systems for accepting multimedia files. Background Technology

[0002] With the development of computer networks, the amount of data displayed to users online is constantly increasing, and the types of visual information provided to users are becoming increasingly diverse, such as pushed articles, videos, and images. Each of these types of information contains a large amount of data. The integration of these various media—videos, sounds, images, text, animations, etc.—into a cohesive whole, capable of achieving certain functions, is commonly referred to as multimedia. A multimedia file represents the various encoded data of the media stored in the computer as a file; it is a collection of binary data.

[0003] To ensure that designed or developed multimedia files meet the requirements specified in contracts or by users, user acceptance testing (UAT) is typically performed. However, in current technology, development teams lack UAT processes, and automated testing lacks visual verification. This makes it impossible to promptly correct multimedia files that do not meet requirements, have flaws, or have poor visual effects, thus prolonging the development process and reducing the user experience.

[0004] Therefore, how to obtain an optimized method and system for accepting multimedia files is a problem that needs to be solved in the existing technology. Summary of the Invention

[0005] In order to at least partially solve the technical problems mentioned in the background art, the present disclosure provides a method and system for accepting multimedia files.

[0006] According to a first aspect of this disclosure, this disclosure provides a method for accepting multimedia files, wherein the method includes: acquiring a multimedia file to be accepted; sending an acceptance instruction for the multimedia file to multiple acceptance terminals; receiving an acceptance result returned by the acceptance terminals; and responding according to the acceptance result.

[0007] Optionally, the acceptance instructions include the multimedia file, the branch to which the multimedia file belongs, and the purpose of the multimedia file; wherein, the branch to which the multimedia file belongs includes sub-branches and main branches.

[0008] Optionally, the acceptance end includes the development end, the testing end, and the user end.

[0009] Optionally, responding based on the acceptance results includes: if one or more of the acceptance terminals return acceptance results indicating that the acceptance failed, then the multimedia file is returned to the development terminal for correction.

[0010] Optionally, responding based on the acceptance results further includes: if all the acceptance results returned by the acceptance terminals indicate that the acceptance has passed, then the multimedia file is sent to the test terminal for visual verification.

[0011] Optionally, the visual verification includes: determining whether there is a corresponding benchmark file for visual verification in the branch to which the multimedia file belongs; if so, comparing the multimedia file with the benchmark file.

[0012] Optionally, the comparison includes comparing the multimedia file with the reference file using a similarity comparison algorithm or a pixel comparison algorithm.

[0013] Optionally, the visual verification further includes: if not, storing the multimedia file as a reference file for visual verification of its branch.

[0014] According to a second aspect of this disclosure, a multimedia file acceptance system is provided, wherein the system includes: an acquisition module configured to acquire a multimedia file to be accepted; a sending module configured to send an acceptance instruction of the multimedia file to multiple acceptance terminals; a receiving module configured to receive an acceptance result returned by the acceptance terminals; and a response module configured to respond according to the acceptance result.

[0015] Optionally, the system includes multiple acceptance terminals, including a development terminal, a testing terminal, and a user terminal; the acceptance instructions include the multimedia file, the branch to which the multimedia file belongs, and the purpose of the multimedia file; wherein, the branch to which the multimedia file belongs includes a sub-branch and a main branch.

[0016] Optionally, the response module is configured to respond based on the acceptance results in the following manner: if one or more of the acceptance terminals return acceptance results indicating that the acceptance has failed, the multimedia file is returned to the development terminal for correction.

[0017] Optionally, the response module is further configured to respond according to the acceptance results in the following manner: if all the acceptance results returned by the acceptance terminals indicate that the acceptance has passed, then the multimedia file is sent to the test terminal for visual verification.

[0018] Optionally, the system further includes a visual verification module, which is set at the test terminal. The visual verification module is used to perform visual verification on the multimedia file in the following manner: determining whether there is a corresponding benchmark file for visual verification in the branch to which the multimedia file belongs; if so, comparing the multimedia file with the benchmark file.

[0019] Optionally, the system further includes a storage module, which is used to store the multimedia file as a reference file for visual verification of its branch when there is no corresponding reference file for visual verification in the branch to which the multimedia file belongs.

[0020] According to a third aspect of this disclosure, an electronic device is provided, wherein the electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method of the first aspect of this disclosure described above.

[0021] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program that, when executed, implements the method of the first aspect of this disclosure.

[0022] The multimedia file acceptance method and system disclosed herein involve multiple acceptance endpoints to inspect multimedia files, enabling timely correction of multimedia files that do not meet requirements or have defects, effectively shortening the multimedia file development process. Furthermore, the multimedia file acceptance method of this disclosure further integrates a visual verification process to verify the visual effects of multimedia files, thereby ensuring the visual quality of multimedia files and improving the user experience. Attached Figure Description

[0023] The above and other objects, features, and advantages of this disclosure will become readily apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings. In the drawings, several embodiments of this disclosure are illustrated by way of example and not limitation, and like or corresponding reference numerals denote like or corresponding parts, wherein:

[0024] Figure 1 This is a flowchart illustrating a method for accepting multimedia files according to an embodiment of the present disclosure;

[0025] Figure 2 This is a schematic block diagram illustrating a multimedia file acceptance system according to an embodiment of the present disclosure. Detailed Implementation

[0026] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0027] The specific embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0028] This disclosure provides a method for accepting multimedia files. (Refer to...) Figure 1 , Figure 1 This is a flowchart illustrating a method for accepting multimedia files according to an embodiment of the present disclosure. Figure 1 As shown, the method includes the following steps S101-S104. Step S101: Obtain the multimedia file to be accepted. Step S102: Send the acceptance instruction of the multimedia file to multiple acceptance terminals. Step S103: Receive the acceptance result returned by the acceptance terminal. Step S104: Respond according to the acceptance result.

[0029] The multimedia file acceptance method and system disclosed herein allow multiple acceptance endpoints to accept multimedia files, thereby enabling timely correction of multimedia files that do not meet requirements or have defects, effectively shortening the multimedia file development process.

[0030] In step S101, the multimedia files to be accepted can be obtained.

[0031] According to embodiments of this disclosure, in order to accept a multimedia file, the multimedia file to be accepted should first be obtained. This multimedia file can be specifically developed and designed by the developer, or it can be included in software or functional modules developed and designed by the developer; the multimedia file can be any of the following: image, video, GIF, audio, etc.; the format of the multimedia file can be common multimedia file formats such as *.bmp, *.gif, *.jpg, *.tif, *.pic, *.avi, *.dat, *.mpg, *.swf, *.flc, *.wav, *.mid, *.mp3, etc., and is not particularly limited herein.

[0032] In step S102, the acceptance instruction for the multimedia file can be sent to multiple acceptance terminals.

[0033] According to embodiments of this disclosure, the acceptance instructions include the multimedia file, the branch to which the multimedia file belongs, and the purpose of the multimedia file; wherein, the branch to which the multimedia file belongs includes a sub-branch and a main branch. The acceptance end includes a development end, a testing end, and a user end.

[0034] Specifically, in the embodiments of this disclosure, multiple acceptance terminals, including development, testing, and user terminals, conduct acceptance of multimedia files. Each of the development, testing, and user terminals can include one or more, with the specific number configured according to actual needs. User terminals can be selected from external target user groups or comprised of internal personnel familiar with the requirements. These multiple acceptance terminals can accept multimedia files based on the same or different acceptance criteria. For example, multiple acceptance terminals can individually accept multimedia files based on aspects such as materials, functionality, layout, special effects, response / feedback patterns, and / or their fit with the requirements. Alternatively, all acceptance terminals can conduct a unified and comprehensive acceptance of the multimedia file. Acceptance instructions can include the multimedia file, its branch, and its purpose, and can be sent to the acceptance terminals in the form of links or QR codes, allowing them to obtain the multimedia file and its related information by clicking the link or scanning the QR code. The branch to which the multimedia file belongs and / or the purpose of the multimedia file can be uploaded by the developer of the multimedia file or obtained based on the nature and path of the multimedia file; no particular limitation is made here. A multimedia file's branch can include sub-branches and a master branch. Sub-branches and the master branch have a direct or indirect hierarchical relationship. The master branch can be the parent branch of a sub-branch or a higher-level branch. The relationship between sub-branches and the master branch is determined by the nature or function of the multimedia file or its associated software / module. The purpose of a multimedia file can be determined based on its nature or function, the branch it belongs to, etc., and can be adjusted or changed based on subsequent acceptance results and / or visual verification results.

[0035] In step S103, the acceptance result returned by the acceptance terminal can be received.

[0036] According to embodiments of this disclosure, multiple acceptance terminals, including the development terminal, testing terminal, and user terminal, perform acceptance of multimedia files. Each acceptance terminal performs acceptance independently and returns the acceptance results.

[0037] Specifically, the acceptance end performs acceptance checks on the multimedia files according to the received acceptance instructions. Each acceptance end performs the acceptance check independently and generates acceptance results. The acceptance results can include acceptance conclusions such as "acceptance passed" and "acceptance failed," and can also include specific acceptance categories and acceptance evaluations. The multimedia file acceptance system receives the acceptance results returned by each acceptance end so that it can respond accordingly in subsequent steps.

[0038] In step S104, a response can be made based on the acceptance result.

[0039] Preferably, responding based on the acceptance results includes: if one or more of the acceptance terminals return acceptance results indicating that the acceptance has failed, then the multimedia file is returned to the development terminal for correction; if all the acceptance terminals return acceptance results indicating that the acceptance has passed, then the multimedia file is sent to the testing terminal for visual verification.

[0040] Specifically, in this embodiment, multiple acceptance terminals, including the development terminal, testing terminal, and user terminal, accept the multimedia file. If any terminal fails the acceptance, the multimedia file is returned to the development terminal for correction. The development terminal receiving and correcting the multimedia file can be one or more of the participating development terminals, or it can be different from the participating development terminals. In practical applications, this can be configured as needed, and no particular limitation is made here. Through this method, any multimedia file that does not meet the requirements or has any defects can be identified through multi-terminal acceptance and then corrected in a timely manner, thereby effectively improving the design efficiency and effect of multimedia files.

[0041] Furthermore, after acceptance testing, the multimedia files are sent to the testing end for visual verification to evaluate whether their visual effects meet the predetermined standards. By adding visual verification to the multimedia file acceptance process, the visual effects of the multimedia files are further controlled, which helps to obtain multimedia files with better visual effects and improves the user experience.

[0042] Preferably, the visual verification includes: determining whether a corresponding benchmark file for visual verification exists in the branch to which the multimedia file belongs; if so, comparing the multimedia file with the benchmark file; if not, storing the multimedia file as the benchmark file for visual verification of its branch. The comparison includes using a similarity comparison algorithm or a pixel comparison algorithm to compare the multimedia file with the benchmark file.

[0043] Specifically, the test server receives the verified multimedia file and performs visual verification. This visual verification primarily involves comparing the multimedia file with a benchmark file using a similarity comparison algorithm or a pixel comparison algorithm. If the comparison results are similar, the multimedia file's visual effect meets the benchmark file's standard, and the visual verification passes. If the comparison results are dissimilar, the multimedia file does not meet the benchmark file's visual effect, and the file is returned to the development server for correction. The structural similarity (SSIM) algorithm is typically used to measure image similarity and can also be used to judge the quality of compressed images. SSIM consists of three parts: brightness comparison, contrast comparison, and structural comparison. SSIM is a number between 0 and 1; the larger the SSIM, the smaller the difference between the two images. The pixel comparison algorithm (PixelMatch) is essentially a minimal, simple, and fastest JavaScript pixel-level image comparison library. It is suitable for raw image data arrays, is fast, and can be used in any environment (node ​​or browser). The test server can be one or more of multiple acceptance servers, and can be, but is not limited to, a test server within the acceptance servers. It can also be a terminal or program specifically used for visual verification of multimedia files; no particular limitation is made here.

[0044] When a branch containing a multimedia file lacks a corresponding benchmark file for visual verification, the required benchmark file can be obtained through any feasible means. For example, a suitable multimedia file can be selected from a relevant database, a suitable benchmark file can be designed by a designer, a suitable benchmark file can be obtained from other branches, or the multimedia file can be directly stored as the benchmark file for visual verification of its branch. The embodiments of this disclosure preferably store the multimedia file as the benchmark file for visual verification of its branch for use in the visual verification of subsequent related multimedia files of that branch. It is understood that before storing the multimedia file as the benchmark file for visual verification of its branch, the visual effect of the multimedia file can be manually verified. After verification, it can be used as the benchmark file for visual verification of its branch to ensure the visual verification effect of that branch.

[0045] Furthermore, if the branch to which the multimedia file belongs is a sub-branch, and the multimedia file serves as the visual verification benchmark file for the sub-branch, then when the sub-branch is merged into the main branch, it is necessary to further determine whether the main branch has a corresponding benchmark file for visual verification. If not, the multimedia file is further transferred to the main branch as the visual verification benchmark file for the main branch, so as to be used for the visual verification of the multimedia file in the main branch.

[0046] The multimedia file acceptance method disclosed herein can effectively improve acceptance efficiency and effectiveness by establishing a detailed acceptance process and clarifying the responsibilities of each acceptance end, enabling collaborative acceptance across multiple acceptance ends and cross-platform acceptance. Furthermore, the integration of automatic visual verification during the multimedia file acceptance process further verifies and corrects the visual effects of the multimedia files, thereby effectively ensuring the visual quality of the multimedia files and enhancing the user experience.

[0047] This disclosure also provides a multimedia file acceptance system. This system is used to perform the above-described combination. Figure 1 The steps in the embodiment of the multimedia file acceptance method described herein.

[0048] Reference Figure 2 , Figure 2 This is a schematic block diagram illustrating a multimedia file acceptance system 100 according to an embodiment of the present disclosure. The system 100 includes an acquisition module 101, a sending module 102, a receiving module 103, and a response module 104. The acquisition module 101 is configured to acquire a multimedia file to be accepted. The sending module 102 is configured to send an acceptance instruction for the multimedia file to multiple acceptance terminals. The receiving module 103 is configured to receive acceptance results returned by the acceptance terminals. The response module 104 is configured to respond based on the acceptance results.

[0049] According to embodiments of this disclosure, the system includes multiple acceptance terminals, including a development terminal, a testing terminal, and a user terminal; the acceptance indication includes the multimedia file, the branch to which the multimedia file belongs, and the purpose of the multimedia file; wherein, the branch to which the multimedia file belongs includes a sub-branch and a main branch.

[0050] According to an embodiment of this disclosure, the response module 104 is configured to respond based on the acceptance result in the following manner: if one or more of the acceptance terminals return an acceptance result indicating that the acceptance has failed, the multimedia file is returned to the development terminal for correction.

[0051] According to an embodiment of this disclosure, the response module 104 is further configured to respond based on the acceptance results in the following manner: if all acceptance results returned by the acceptance terminals indicate that the acceptance has passed, then the multimedia file is sent to the test terminal for visual verification.

[0052] According to an embodiment of this disclosure, the system 100 further includes a visual verification module, which is disposed on the test terminal. The visual verification module is used to perform visual verification on the multimedia file in the following manner: determining whether there is a corresponding benchmark file for visual verification in the branch to which the multimedia file belongs; if so, comparing the multimedia file with the benchmark file.

[0053] According to an embodiment of this disclosure, the system 100 further includes a storage module, which is used to store the multimedia file as a reference file for visual verification of its branch when there is no corresponding reference file for visual verification in the branch to which the multimedia file belongs.

[0054] It is understood that the acceptance end, development end and / or testing end can be the same or different terminals, or different hardware modules or software programs based on the same or different hardware platforms, or the same or similar hardware modules or software programs, without any particular limitation here.

[0055] It is understandable that the above references Figure 2 The multimedia file acceptance system described in the embodiments, wherein the specific methods by which each module performs operations are already incorporated into the system. Figure 1 The embodiments of the multimedia file acceptance method described herein have been described in detail, and will not be elaborated upon here.

[0056] This disclosure also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it performs the following steps: acquiring a multimedia file to be accepted; sending an acceptance instruction for the multimedia file to multiple acceptance terminals; receiving the acceptance result returned by the acceptance terminals; and responding according to the acceptance result.

[0057] It is understood that the steps implemented by the processor when executing the computer program are basically the same as the implementation of each step in the above method. The specific implementation has been described in detail in the embodiments of the multimedia file acceptance method, and will not be elaborated here.

[0058] In another aspect, this disclosure provides a computer-readable storage medium storing a computer program that, when executed, performs the following steps: acquiring a multimedia file to be accepted; sending an acceptance instruction for the multimedia file to multiple acceptance terminals; receiving acceptance results returned by the acceptance terminals; and responding according to the acceptance results.

[0059] It is understood that the steps implemented by the processor when executing the computer program are basically the same as the implementation of each step in the above method. The specific implementation has been described in detail in the embodiments of the multimedia file acceptance method, and will not be elaborated here.

[0060] The embodiments of this disclosure have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this disclosure. The description of the above embodiments is only for the purpose of helping to understand the methods and core ideas of this disclosure. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this disclosure. Therefore, the content of this specification should not be construed as a limitation of this disclosure.

[0061] It should be understood that the terms "first" and "second," etc., in the claims, specification, and drawings of this disclosure are used to distinguish different objects, not to describe a specific order. The terms "comprising" and "including" as used in the specification and claims of this disclosure indicate the presence of the described features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or collections thereof.

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

[0063] The embodiments of this disclosure have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this disclosure. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this disclosure. Furthermore, any changes or modifications made by those skilled in the art based on the ideas of this disclosure, and on the specific implementation methods and application scope of this disclosure, are all within the scope of protection of this disclosure. Therefore, the content of this specification should not be construed as a limitation of this disclosure.

Claims

1. A method for accepting multimedia files, wherein, The method includes: Obtain the multimedia files to be accepted; The acceptance instructions for the multimedia file are sent to multiple acceptance terminals, including the development terminal, the testing terminal, and the user terminal. Receive the acceptance result returned by the acceptance terminal; Responding based on the acceptance results includes: if one or more of the acceptance terminals return acceptance results indicating that the acceptance has failed, then the multimedia file is returned to the development terminal for correction; if all the acceptance terminals return acceptance results indicating that the acceptance has passed, then the multimedia file is sent to the testing terminal for visual verification. The visual verification includes: determining whether there is a corresponding benchmark file for visual verification in the branch to which the multimedia file belongs; if so, comparing the multimedia file with the benchmark file; if not, storing the multimedia file as the benchmark file for visual verification of its branch. If the branch to which the multimedia file belongs is a sub-branch, and the multimedia file serves as the visual verification benchmark file for the sub-branch, then when the sub-branch is merged into the main branch, it is determined whether the main branch has a benchmark file for visual verification. If not, the multimedia file is converted into the visual verification benchmark file for the main branch for use in the visual verification of the multimedia file in the main branch.

2. A multimedia file acceptance system, wherein, The system includes: The acquisition module is configured to acquire multimedia files to be accepted. A sending module is configured to send the acceptance indication of the multimedia file to multiple acceptance terminals; A receiving module, configured to receive the acceptance result returned by the acceptance terminal; The response module is configured to respond based on the acceptance results. The response module responds based on the acceptance results in the following manner: if one or more of the acceptance terminals return acceptance results indicating that the acceptance has failed, the multimedia file is returned to the development terminal for correction; if all the acceptance terminals return acceptance results indicating that the acceptance has passed, the multimedia file is sent to the testing terminal for visual verification. The system also includes a visual verification module, which is set at the test terminal. The visual verification module is used to perform visual verification on the multimedia file in the following manner: determine whether there is a corresponding benchmark file for visual verification in the branch to which the multimedia file belongs; if so, compare the multimedia file with the benchmark file. The system also includes a storage module, which is used to store the multimedia file as a reference file for visual verification of its branch when there is no corresponding reference file for visual verification in the branch to which the multimedia file belongs. If the branch to which the multimedia file belongs is a sub-branch, and the multimedia file serves as the visual verification benchmark file for the sub-branch, then when the sub-branch is merged into the main branch, it is determined whether the main branch has a benchmark file for visual verification. If not, the multimedia file is converted into the visual verification benchmark file for the main branch for use in the visual verification of the multimedia file in the main branch.

3. An electronic device, wherein, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method as described in claim 1.

4. A computer-readable storage medium, wherein, The storage medium stores a computer program, which, when executed, implements the method as described in claim 1.

Images