A cloud rendering method, device and system

Abstract

The application discloses a cloud rendering method, device and system, and belongs to the field of rendering; when a user needs to render a scene file, the user sends a file path through a current account, a cloud rendering system acquires the scene file according to the file path and loads the scene file to a cloud node; in this process, the user only needs to submit the file path, and does not need to submit the scene file; the cloud rendering system directly acquires the scene file according to the file path, and directly stores a rendering result file to a shared file position after rendering; the user does not need to upload the scene file and download the rendering result file, time and labor are saved; and as long as the file path of the scene file is given to multiple users, other users can render the scene file; and the other users only need to use the file path when rendering, so the other users do not need to be provided with the scene file, the rendering speed is accelerated, the other users are prevented from acquiring the scene file, and confidentiality is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of rendering, in particular, to a cloud rendering method, device and system. BACKGROUND

[0002] Cloud rendering is a rendering service provided by a service provider, which provides multiple nodes with the same configuration for users to perform rendering, so that multiple users can perform rendering at the same time.

[0003] When the existing cloud rendering system is used, the user needs to upload the CG scene file to the cloud and submit rendering, and also needs to download it from the cloud to the local after rendering is completed, which is time-consuming and laborious. Especially for large scene rendering, when the scene file has a high degree of secrecy, if only one user performs rendering, it will take a long time. SUMMARY

[0004] In order to overcome the shortcomings of the prior art, the present application provides a cloud rendering method, device and system to solve the problems that the user needs to upload the scene file when the existing cloud rendering is performed, and needs to download it from the cloud after rendering is completed, which is time-consuming and laborious, and when large scene rendering and the scene file has a high degree of secrecy, if only one user performs rendering, it will take a long time.

[0005] The technical scheme adopted by the present application to solve its technical problems is:

[0006] In a first aspect, a cloud rendering method is provided, comprising the following steps:

[0007] Receiving file information sent by a current account, the file information including a file path;

[0008] Loading a scene file obtained from the file path to a cloud node, the cloud node providing a function of rendering the scene file for the user;

[0009] Obtaining a rendering result file rendered in the cloud node, and storing the rendering result file to a shared file location.

[0010] Further, before loading the scene file obtained from the file path to the cloud node, it includes:

[0011] Obtaining the type of the file path, the type of the file path including a network path, a mapping path and a local path;

[0012] If the type of the file path is a network path or a mapping path, detecting a preset storage location of all accounts, the preset storage location storing a preset file path with the permission to obtain the scene file, the all accounts being located in the same local area network;

[0013] If there is any preset file path stored in the preset storage location of any account that is the same as the file path, it is determined that the scene file can be obtained according to the file path, and the scene file obtained from the file path is loaded to the cloud node.

[0014] Further, if none of the preset file paths stored in the preset storage location of any account is the same as the file path, and the scene file cannot be obtained by accessing the file path, a failure message is sent to the current account.

[0015] Further, if the type of the file path is a local path;

[0016] Detecting the preset storage location of the current account;

[0017] If there is any preset file path in the preset storage location of the current account that is the same as the file path, the scene file in the file path is loaded to the cloud node.

[0018] Further, it also includes:

[0019] If any preset file path in the preset storage location of the current account is the same as the file path, and the scene file cannot be obtained by accessing the file path, a failure message is sent to the current account.

[0020] Further, before receiving the file information sent by the current account, it also includes:

[0021] Receiving the custom parameter information input by the user through the current account, the parameter information including rendering parameter information, rendering software version, rendering node information, rendering frame range, priority of rendering scheduling machine, maximum number of machines for rendering the scene, rendering result output file address, CG software plug-in, CG software camera, CG software node and rendering mode;

[0022] Detecting whether the parameter information is complete or correct;

[0023] If the parameter information is complete and correct, when receiving the file information detection command input by the user through the current account, the file information detection command including pre-submitted file information, it is determined whether there is a risk of rendering failure according to the pre-submitted file information.

[0024] Further, the determination of whether there is a risk of rendering failure according to the pre-submitted file information includes:

[0025] Obtaining the file path in the pre-submitted file information;

[0026] If the type of the file path is a network path, it is detected whether the file path exists in the preset storage location of the current account;

[0027] If the file path exists in the preset storage location of the current account, it is determined that there is no risk of rendering failure; if the file path does not exist in the preset storage location of the current account, it is determined that there is a risk of rendering failure.

[0028] Further, if the type of the file path is a local path, it is detected whether the target scene file path is a mapping path;

[0029] If yes, it is detected whether the file path exists in the preset storage location of the current account;

[0030] If the file path exists in the preset storage location of the current account, it is determined that there is no risk of rendering failure; if the file path does not exist in the preset storage location of the current account, it is determined that there is a risk of rendering failure.

[0031] In a second aspect, a cloud rendering device is provided, comprising:

[0032] a file information receiving module configured to receive file information sent by a current account, the file information comprising a file path;

[0033] a scene file loading module configured to load a scene file obtained from the file path to a cloud node, the cloud node providing a function of rendering the scene file for the user;

[0034] a rendering result storage module configured to obtain a rendering result file rendered in the cloud node, and store the rendering result file to a shared file location.

[0035] In a third aspect, a cloud rendering system is provided, comprising:

[0036] a processor;

[0037] a memory configured to store instructions executable by the processor;

[0038] the processor is configured to execute any of the methods provided in the first aspect.

[0039] Beneficial effects:

[0040] The application provides a cloud rendering method, device and system, when a user needs to render a scene file, the user sends file information through a current account, since the file information includes a file path, after receiving the file path, a cloud rendering system acquires the scene file according to the file path and loads the scene file to a cloud node, so that the user can render the scene file in the cloud rendering system; in this process, the user only needs to submit the file path, and the cloud rendering system directly acquires the scene file according to the file path, and stores a rendering result file directly to a shared file position after rendering, without the user uploading the scene file and downloading the rendering result file, saving time and effort; and as long as the file path of the scene file is given to multiple users, the other users can render the scene file, and the other users only need to use the file path when rendering, so the other users do not need to be provided with the scene file, the rendering rate is accelerated, and the confidentiality is improved. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only constitute some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0042] Figure 1 It is a cloud rendering method flowchart provided by an embodiment of the present application;

[0043] Figure 2 It is a specific cloud rendering method flowchart provided by an embodiment of the present application;

[0044] Figure 3 It is a cloud rendering device structure diagram provided by an embodiment of the present application;

[0045] Figure 4 It is a scene file address information detection flowchart in a cloud rendering system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical scheme and advantages of the present application more clear, the technical scheme of the present application will be described in detail below with reference to the drawings and embodiments. Obviously, the described embodiments only constitute some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of the present application.

[0047] The first embodiment, refer to Figure 1The embodiment of the present application provides a cloud rendering method, comprising the following steps:

[0048] S11: receiving file information sent by a current account, wherein the file information comprises a file path;

[0049] S12: loading a scene file obtained from the file path to a cloud node, wherein the cloud node provides a function of rendering the scene file for a user;

[0050] S13: obtaining a rendering result file rendered in the cloud node, and storing the rendering result file to a shared file position.

[0051] The cloud rendering method provided by the embodiment of the present application, when a user needs to render a scene file, sends file information through a current account, since the file information comprises a file path, after receiving the file path, the cloud rendering system obtains the scene file according to the file path and loads the scene file to a cloud node, so that the user can render the scene file in the cloud rendering system; in this process, the user only needs to submit the file path, and the cloud rendering system directly obtains the scene file according to the file path, and stores the rendering result file after rendering to a shared file position, without the user uploading the scene file and downloading the rendering result file, which saves time and effort; and as long as the file path of the scene file is given to multiple users, the other users can render the scene file, and the other users only need to use the file path when rendering, so the other users do not need to be provided with the scene file, the rendering rate is accelerated, and the confidentiality is improved.

[0052] In a second embodiment, the present application provides a specific cloud rendering method, as shown in the following steps: Figure 2

[0053] receiving custom parameter information sent by a user through a current account, wherein the parameter information comprises rendering parameter information, a rendering software version, rendering node information, a rendering frame range, a priority of a rendering scheduling machine, a maximum number of machines for rendering the scene, a rendering result output file address, a CG software plug-in, a CG software camera, a CG software node and a rendering mode; the user can select corresponding parameters and CG software according to his / her ability and preference, thereby greatly improving the operability of the user.

[0054] detecting whether the parameter information is complete or correct; for example, whether the scene file parameter information exists, whether a camera name is set, whether a rendering output result address scene is set, whether the scene file is saved, whether the parameter setting information is supported by the CG software, and the like; the completeness and correctness of the parameter setting are necessary guarantees for later rendering, and therefore it is necessary to automatically detect whether the parameter is complete and correct.

[0055] ​If the parameter information is complete and correct, when a file information detection command input by a user through a current account is received, the file information detection command includes pre-submitted file information, and whether there is a rendering failure risk is determined according to the pre-submitted file information. Specifically, a file path in the pre-submitted file information is obtained; if the type of the file path is a network path, whether the file path exists in a preset storage location of the current account is detected; if the file path exists in the preset storage location of the current account, it is determined that there is no rendering failure risk; if the file path does not exist in the preset storage location of the current account, it is determined that there is a rendering failure risk. If the type of the file path is a local path, whether the target scene file path is a mapping path is detected; if yes, whether the file path exists in the preset storage location of the current account is detected; if the file path exists in the preset storage location of the current account, it is determined that there is no rendering failure risk; if the file path does not exist in the preset storage location of the current account, it is determined that there is a rendering failure risk. If the file path is different, the matters to be detected are also different. Through file information detection, the user can be fully reminded of the existing risks before clicking to submit (i.e., submitting the pre-submitted file information), so that the user can clearly determine whether to continue to submit, which can effectively avoid the situation that the user analyzes and finds problems by himself after rendering failure, improve the rendering efficiency, and reduce the degree of user operation complexity.

[0056] If the file information detection has no problem, the user can send file information through the current account. When the file information sent by the user through the current account is received, the scene file is obtained according to the file path in the file information and is loaded to the cloud node; specifically, the type of the file path is obtained, the type of the file path includes a network path, a mapping path and a local path; if the type of the file path is a network path or a mapping path, the preset storage locations (specifically, input storage) of all accounts are detected, the preset storage locations store preset file paths with the permission to obtain the scene file, and all accounts are located in the same local area network; if the preset file path stored in the preset storage location of any account is the same as the file path, it is determined that the scene file can be obtained according to the file path, and the scene file obtained from the file path is loaded to the cloud node. If the type of the file path is a local path; the preset storage location of the current account is detected; if any preset file path in the preset storage location of the current account is the same as the file path, the scene file in the file path is loaded to the cloud node.

[0057] When the scene file cannot be acquired, a failure message is sent to the user. Specifically, when the type of the file path is a network path or a mapping path, if none of the preset file paths stored in the preset storage locations of any account is the same as the file path, and the scene file cannot be acquired from the access file path, a failure message is sent to the current account. If none of the preset file paths stored in the preset storage locations of any account is the same as the file path, the user can only go to the location indicated by the file path to acquire the scene file. If the location indicated by the file path is an open location (i.e., a location without access permission), the scene file can be acquired. If the location indicated by the file path is not an open location, the scene file cannot be acquired. Or when the type of the target scene file path is a local scene file path, if the preset file path of the current account is the same as the file path, and the scene file cannot be acquired from the access file path, a failure message is sent to the current account. When the scene file cannot be acquired, the cloud rendering system cannot load the scene file to the cloud node, and the user cannot perform rendering in the cloud rendering system.

[0058] The rendering result file rendered in the cloud node is acquired, and the rendering result file is stored to a shared file location. If there is no shared file location, the rendering result file cannot be output, and therefore the shared file location must exist. The shared file location is an output address set in advance in a preset location (in practice, an output storage).

[0059] In this way, for the same scene file, the account of the CG producer can acquire the scene file through the local path when rendering. Other users with permission can also acquire the mapping path or the network path of the same scene file, and then the cloud rendering system acquires the scene file through the mapping path and the network path, and simultaneously performs rendering on the same scene file as the CG producer. In this way, the rendering speed of the scene file can be greatly improved, and it is ensured that only users with permission can perform rendering on the scene file. Finally, the rendering result file is output to a specified output address, and as long as the corresponding permission is set, it is ensured that only users with permission can see the rendering result.

[0060] In the specific cloud rendering method provided by the embodiment of the present invention, when a user needs to render a scene file, the user sends file information through the current account. Since the file information includes a file path, after receiving the file path, the cloud rendering system obtains the scene file according to the file path and loads it to the cloud node, so that the user can render the scene file in the cloud rendering system; in this process, the user only needs to submit the file path, without submitting the scene file. The cloud rendering system directly obtains the scene file according to the file path, and stores the rendering result file directly to the shared file location after rendering. The user does not need to upload the scene file and download the rendering result file by himself, which saves time and effort; and as long as the file path of the scene file is given to multiple users, other users can render the scene file, and other users only need to use the file path when rendering, so there is no need to provide the scene file to other users, which speeds up the rendering rate while avoiding other users from obtaining the scene file, thereby improving confidentiality.

[0061] In a third embodiment, the present invention provides a cloud rendering device, such as Figure 3 Shown, including:

[0062] The file information receiving module 31 is used to receive file information sent by the current account, where the file information includes a file path.

[0063] The scene file loading module 32 is used to load the scene file obtained from the file path to the cloud node, which provides users with the function of rendering the scene file. Specifically, the scene file loading module 32 obtains the file path type, which includes network path, mapped path, and local path. If the file path type is a network path or mapped path, the module checks the preset storage locations of all accounts, which store preset file paths with permission to obtain scene files. All accounts are located on the same local area network. If the preset file path stored in any account's preset storage location is the same as the file path, the module determines that the scene file can be obtained based on the file path and loads the scene file obtained from the file path to the cloud node. If the preset file path stored in any account's preset storage location is not the same as the file path, and the scene file cannot be obtained by accessing the file path, a failure message is sent to the current account. If the file path type is a local path, the module checks the preset storage location of the current account. If any preset file path in the current account's preset storage location is the same as the file path, the module loads the scene file in the file path to the cloud node. If any preset file path in the preset storage location of the current account is the same as the file path, and the scene file cannot be obtained by accessing the file path, a failure message is sent to the current account.

[0064] The rendering result storage module 33 is used to obtain the rendering result file completed by the cloud node and store the rendering result file in a shared file location.

[0065] It should be noted that, before receiving the scene file submission instruction sent by the user through the current account, it also includes:

[0066] The file information receiving module 31 receives the user's input parameter information through the current account, and the parameter information includes rendering parameter information, rendering software version, rendering node information, rendering frame range, rendering scheduling machine priority, maximum number of machines for rendering the scene, rendering result output file address, CG software plug-in, CG software camera, CG software node and rendering mode; detecting whether the parameter information is complete or correct; if the parameter information is complete and correct, when receiving the file information detection command input by the user through the current account, the file information detection command includes pre-submitted file information, and it is judged whether there is a rendering failure risk according to the pre-submitted file information. According to the pre-submitted file information to determine whether there is a rendering failure risk, including: obtaining the file path in the pre-submitted file information; if the type of the file path is a network path, then detecting whether the file path exists in the preset storage location of the current account; if the file path exists in the preset storage location of the current account, it is judged that there is no rendering failure risk; if the file path does not exist in the preset storage location of the current account, it is judged that there is a rendering failure risk. If the type of the file path is a local path, then detecting whether the target scene file path is a mapping path; if yes, then detecting whether the file path exists in the preset storage location of the current account; if the file path exists in the preset storage location of the current account, it is judged that there is no rendering failure risk; if the file path does not exist in the preset storage location of the current account, it is judged that there is a rendering failure risk.

[0067] The cloud rendering device provided by the embodiment of the present application receives file information sent by a current account through a file information receiving module, the file information including a file path; a scene file loading module loads a scene file obtained from the file path to a cloud node, the cloud node providing a function of rendering the scene file for a user; and a rendering result storage module obtains a rendering result file rendered in the cloud node and stores the rendering result file to a shared file location. The cloud rendering device provided by the embodiment of the present application, when a user needs to render a scene file, sends file information through a current account, since the file information includes a file path, after receiving the file path, the cloud rendering system obtains the scene file according to the file path and loads the scene file to the cloud node, so as to facilitate the user to render the scene file in the cloud rendering system; in this process, the user only needs to submit the file path, without submitting the scene file, the cloud rendering system directly obtains the scene file according to the file path, and stores the rendering result file directly to the shared file location after rendering, without the user uploading the scene file and downloading the rendering result file, saving time and effort; and as long as the file path of the scene file is given to multiple users, the other users can render the scene file, and the other users only need to use the file path when rendering, thus without providing the scene file to the other users, accelerating the rendering rate while avoiding the other users to obtain the scene file, improving the confidentiality.

[0068] In a fourth embodiment, the present application provides a cloud rendering system, comprising:

[0069] a processor;

[0070] a memory for storing processor-executable instructions;

[0071] the processor is configured to execute the cloud rendering method provided in the first embodiment or the second embodiment.

[0072] In order to more clearly illustrate the scheme of the embodiment of the present application, the present application provides a specific operation step:

[0073] open the required rendering CG scene file, click submit rendering, the system automatically detects and determines whether the cloud rendering management system has been logged in, if not, a login interface is displayed, and the cloud rendering management system IP address, account password and other information under the intranet need to be input for login, if logged in, a pop-up window is directly entered into the submit rendering interface;

[0074] After successfully entering the submission rendering interface, the rendering parameter information, rendering software version, rendering node information, rendering frame range, rendering scheduling machine priority, maximum number of machines for rendering the scene, rendering output result file address, etc. can be customized. Different CG software specific plugins, cameras, nodes, etc. can also be set according to different CG software. The rendering method can be selected: one machine multiple frames, block rendering, distributed rendering, etc. After setting, the scene detection analysis can be clicked to submit;

[0075] After submitting the analysis and detection, the system first detects whether the current scene parameter information is complete or correct. For example, whether the scene file parameter information exists, whether the camera name is set, whether the scene file exists, whether the rendering output result address is set in the scene, whether the scene file has been saved, whether the parameter setting information is supported by the CG software, etc. If the scene parameter information detection returns an error, the rendering cannot be submitted. If it returns a warning or no error, the scene file address information detection is performed, and different warning information is returned according to the scene file address information. In order to inform the user early that the current internal plugin submission rendering may fail; for example Figure 4 As shown, it includes:

[0076] When the scene file address (scene file, material file, etc.) is a network path, that is, there is no local path, it is determined whether all network paths of the current scene exist in the current user input storage permission. If yes, no error is returned and the submission is successful. If not, a warning is returned: the network path does not exist in the current user input storage, which may cause rendering failure.

[0077] When the scene file address (scene file, material file, etc.) exists in a local path, it is determined whether the local path is a mapped path. If not, a warning is returned: the current path is a local path, and the submission may fail. If it is a mapped path, it is determined whether the current mapped path exists in the current user input storage permission. If yes, no error is returned and the submission is successful. If not, a warning is returned: the mapped network does not exist in the current user input storage, which may cause rendering failure.

[0078] After the analysis and detection are completed, the analysis result is returned. If there is an error, the submission cannot be performed. If there is a warning or no error, the submission can be ignored. After submission, only the scene file path and the scene file path type are sent to the cloud rendering management system. The cloud rendering management system then automatically generates a rendering job in the rendering list, and the rendering job waits for system queuing and scheduling of rendering machines for rendering.

[0079] As the rendering job has been queued on the rendering machine, the system automatically detects the existing storage information (input storage, output storage shared account information) of the cloud rendering management system according to the submitted rendering job information, and if the rendering machine successfully shares and mounts the rendering job asset file path and the rendering output result path, the rendering can be performed; if the shared storage information cannot be detected or the mounting fails, the rendering fails.

[0080] A: The scene file network path does not exist in the current account input storage, or the scene file mapping path does not exist in the current account input storage, the system detects all input storages such as personal storage or other storage, and if all the input storages do not exist, the shared mounting can fail, and if the mounting is successful, the rendering can be performed;

[0081] B: The scene file local path, then automatically detect whether the scene file exists in the input storage path associated with the current submission account, if not, return failure, if exists, mount the file in the input storage path associated with the current submission account for rendering;

[0082] After the job submitted by the intranet plug-in is successfully executed and rendered, the rendering result file is automatically put into the output file address specified by the scene file, and the user can directly access the output file address path to obtain the rendering output result file. The rendering scene file and the rendering result file are in the intranet, so as long as all users are in the same intranet and the operation and maintenance personnel authorize shared access permission to all users, the rendering scene file and the rendering result file can be accessed by sharing.

[0083] The rendering system provided by the embodiment of the application does not need to upload the scene file to the cloud and then submit the rendering, only needs to submit the scene file path, can set the shared access storage permission and the input storage in the intranet, and let the users with the permission jointly complete the production and rendering of the scene file, and the rendering result file does not need to be downloaded from the cloud to the local, all the scene files and the rendering result files are in the intranet, do not need to be uploaded and downloaded and can be directly shared and accessed, and the rendering result file can be jointly viewed. The method can use various CG software, is not limited to software versions and plug-in versions, does not need high bandwidth requirement of the production machine, can satisfy the CG production team or the individual without difference and delay, and realizes real-time synchronous production, rendering and result viewing, and the file transmission waiting is not needed and the direct shared access is realized. The scheme can make up the defect of transmission waiting of the rendering submission in the external network, and avoid the risk of asset file leakage in the external network.

[0084] It can be understood that the same or similar parts in the above embodiments can be mutually referred to, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0085] It should be noted that the terms "first", "second" and the like in the description of the application do not denote any particular importance, but are merely used to distinguish one element from another. In addition, in the description of the application, the meaning of "a plurality of" is at least two, unless otherwise specified.

[0086] Any process or method descriptions or descriptions of the flow diagrams in this application can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for implementing specific logic functions or steps in the process, and the various embodiments of the application include additional implementations in which the order of the steps has been changed, additional steps have been added, or some steps have been omitted, and the like, as will be appreciated by those skilled in the art. The scope of the application encompasses these and any other implementations.

[0087] It should be understood that various parts of the present application can be implemented in hardware, software, firmware or a combination thereof. In the above embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and as in another embodiment, it can be implemented by any one or a combination of the following technologies known in the art: discrete logic circuit with logic gate circuit for implementing logic functions on data signals, application specific integrated circuit with suitable combination logic gate circuit, programmable gate array (PGA), field programmable gate array (FPGA) and the like.

[0088] Those skilled in the art of the present technology can understand that all or part of the steps carried out by the above-mentioned embodiments can be completed by programs instructing relevant hardware, and the programs can be stored in a computer readable storage medium, which includes one or a combination of steps of the method embodiments when executed.

[0089] In addition, each functional unit in each embodiment of the present application can be integrated into one processing module, or each unit can be physically present separately, or two or more units can be integrated into one module. The above integrated module can be realized in the form of hardware or in the form of software functional module. The integrated module, if realized in the form of software functional module and sold or used as an independent product, can also be stored in a computer readable storage medium.

[0090] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0091] In the description of the specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are contained in at least one embodiment or example of the present application. In the specification, the illustrative description of the above terms does not necessarily mean the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0092] Although the embodiments of the present application have been shown and described above, it is understood that the above-described embodiments are exemplary, and cannot be construed as limiting the present application, and those skilled in the art can make changes, modifications, replacements and variations to the above-described embodiments within the scope of the present application.

Claims

1. A cloud rendering method, characterized in that, The method comprises the following steps: receiving file information sent by a current account, the file information comprising a file path; acquiring the type of the file path, the type of the file path comprising a network path, a mapped path and a local path; if the type of the file path is a network path or a mapped path, detecting preset storage locations of all accounts, the preset storage locations storing preset file paths with the permission of acquiring scene files, the all accounts being located in the same local area network; if the preset file path stored in the preset storage location of any account is the same as the file path, judging that the scene file can be acquired according to the file path, and loading the scene file acquired from the file path to a cloud node, the cloud node providing the function of rendering the scene file for a user; acquiring a rendering result file rendered in the cloud node, and storing the rendering result file to a shared file location.

2. The method of claim 1, wherein: if the preset file path stored in the preset storage location of any account is not the same as the file path, and the scene file cannot be acquired by accessing the file path, sending a failure message to the current account.

3. The method of claim 1, wherein: if the type of the file path is a local path; detecting the preset storage location of the current account; if any preset file path in the preset storage location of the current account is the same as the file path, loading the scene file in the file path to the cloud node.

4. The method of claim 3, wherein, Further comprising: if any preset file path in the preset storage location of the current account is the same as the file path, and the scene file cannot be acquired by accessing the file path, sending a failure message to the current account.

5. The method of claim 1, wherein: Before receiving the file information sent by the current account, further comprising: receiving parameter information input by a user through the current account, the parameter information comprising rendering parameter information, a rendering software version, rendering node information, a rendering frame range, a priority of a rendering scheduling machine, a maximum number of machines for rendering the scene, a rendering result output file address, a CG software plug-in, a CG software camera, a CG software node and a rendering mode; detecting whether the parameter information is complete or correct; if the parameter information is complete and correct, when receiving a file information detection command input by the user through the current account, the file information detection command comprising pre-submitted file information, judging whether there is a rendering failure risk according to the pre-submitted file information.

6. The method of claim 5, wherein: The judging whether there is a rendering failure risk according to the pre-submitted file information comprises: acquiring the file path in the pre-submitted file information; if the type of the file path is a network path, detecting whether the file path exists in the preset storage location of the current account; if the file path exists in the preset storage location of the current account, judging that there is no rendering failure risk, and if the file path does not exist in the preset storage location of the current account, judging that there is a rendering failure risk.

7. The method according to claim 6, wherein: if the type of the file path is a local path, detecting whether the target scene file path is a mapped path; if yes, detecting whether the file path exists in the preset storage location of the current account; If the file path exists in the preset storage location of the current account, it is determined that there is no risk of rendering failure; If the file path does not exist in the preset storage location of the current account, it is determined that there is a risk of rendering failure.

8. A cloud rendering device, comprising: The method comprises the steps of: receiving file information sent by a current account, wherein the file information comprises a file path; loading a scene file according to the file path, wherein the file path comprises a network path, a mapping path and a local path; if the file path is the network path or the mapping path, detecting preset storage locations of all accounts, wherein the preset storage locations store preset file paths with the permission of obtaining the scene file, and the all accounts are located in the same local area network; if the preset file path stored in the preset storage location of any account is the same as the file path, it is determined that the scene file can be obtained according to the file path, and the scene file obtained from the file path is loaded to a cloud node, wherein the cloud node provides a function of rendering the scene file for a user; storing a rendering result file obtained by rendering the scene file in the cloud node to a shared file location.

9. A cloud rendering system, comprising: The method comprises the steps of: a processor; a memory for storing instructions executable by the processor; the processor is configured to execute the method of any one of claims 1-7.

Images