DE202010004029U1 - Device for transmitting data for rendering a multi-dimensional animation - Google Patents

Abstract

System for transferring project data of a multidimensional animation from a first computer to a second computer connected via a network, which has at least one rendering device (render farm) whose required information is determined by a set of rules, comprising the following components:
- means for downloading a plug-in (Farminizer Plugin) to the first computer and incorporating into animation software installed on the first computer,
- means for collecting information on the first computer by the plug-in related to the project data and / or the rendering device;
- Means for checking the collected information by means of a set of rules, and if all the rules have been met, the collected information and the project data are transmitted to the second computer; if the rules are not met, a message is output or the project data is adjusted fully automated and / or semi-automatic with interactive guidance, to then collect the collected information and project data to ...

Description

The The invention relates to a device for controlled transmission and rendering data for rendering a multi-dimensional animation, on a server provided by a service provider.

description

It is known and customary project data of a 3D animation to a service provider (render farm) passed to a rendering can be. The term Rendering (Engl. To render) designates the creation a graphic from a sketch or a model. In this implementation takes a modeling natural phenomena like texture, refraction, reflection, shadows etc., allowing the viewer an impression of materiality, the size and shape mediates becomes. This process is increasingly using computer graphics with appropriate Software performed. For this, 3D models are used often pictures for short movies or for created elaborate graphics.

ever the more complex the model and the more images needed, the more computing power is necessary to render each model. This computing power is often purchased from a service provider when needed because of Users often do not have over has the necessary computing power and therefore its final project file from a render farm with a specially equipped data center for a fee can process.

Save for this the user collects his project data within his application, collects the additional secondary data (Textures, maps, etc) and loads the data over a browser interface to the provider high. In the browser the user will find possibilities to start the rendering process, calculate the results and the results Download renderings locally.

Problematic here is that the process described above is time consuming and is flawed. First, the entire preparation of the rendering manually performed by the user, on the other hand, due to the different configuration of local workstation and 3D application of the user as well as configuration The computer of the render farm mostly errors.

It in the basic configuration of a 3D application gives parameters which simply not saving the project file in a file-inherent way become. additional and usual Modifications of the 3D application by the user by means of further Plugins, rendering engines, version numbers, etc. will not work either stored.

Overview of the Invention:

These and further problems described below are caused by the listed in the claim Characteristics solved.

in the Individual is a system for the transfer of project data multidimensional animation (preferably 3D animation) of one first computer to one over a network connected to the second computer, the at least one rendering device having. In the preferred embodiment, it is A render farm consists of a large number of computers that are central be controlled, and the over the internet accessible are. The information needed by the render farm are determined by a set of rules.

The System includes the following components. After a user the web page The provider of the render farm has entered a plug-in (Farminizer Plugin) and on his computer (first computer) in integrate the animation software installed on the computer.

The Plug-in software collects information on the first computer, the related to the project data and / or the rendering device. A review of collected information is based on a set of rules, such as it will be described below. If all the rules have been met, the collected information and the project data will be sent to the Render farm transmitted directly or indirectly, the rules should be not fulfilled a message is issued or an adjustment is made the project data fully automatic and / or semi-automatic with interactive guide carried out, then the collected information and the project data to the second computer to transmit.

After this If this data was obtained from the render farm, it will be done automatically Setting the render device based on the information and project data and rendering.

The particular advantages of the invention are that the lifting of incompatibilities within the 3D application is done. Ie. where an adaptation and automatic modification of the project is possible at all.

The Collect project-specific but not project-file-inherent data fits the render farm additionally to the project.

The process starts within the 3D application which the user does not have to leave for this purpose.

The Software loads down in the background the results of the calculation and saves locally at the location specified in the project file. Of the User learns Accordingly, the automation increased comfort.

Of the entire process for the remote-controlled calculation of a 3D animation on a render farm, upload, download, and drop locally at desired Location is triggered by a single click. The process is comparable to a local rendering on the computer of the user.

by virtue of the complexity These applications result in numerous sources of error, the one calculation impossible make or lead to erroneous results. Furthermore, the amount at needed Files frequently unmanageable These are usually in different places on the user PC often distributed in the local network of the user are.

How the Farminizer software works

Of the User (in sequence A) involves the service provider (in sequence B) Software package consisting of the "Manager" and the "Farminizer" plugins for all 3D applications. The manager acts as the central collection point and administration of all local projects of A and serves to the overview over the current progress of already submitted projects, to install the Farminizer plugins as well as for transfer the projects to the render farm and receiving the computed files.

task The Farminizer plug-ins are safe in the respective 3D application to make sure that the respective, previously created project of A the Basic conditions on the renderfarm are sufficient and error free and completely calculated can be. For this purpose, a series of technical tests are carried out and finally created uniform "packages" and which is imported automatically in the manager and homogeneous can be processed by the render farm. After successful handover the data to the manager will reflect the original state of the data made, so that A no change finds.

Detailed process of the plugin software

at the installation of the plugin will automatically menu entries in the 3D application integrated, whereby the Farminizer analogous to a normal rendering process can be started. Subsequently, various tests are performed, the the project on possible Investigate problems related to rendering on the render farm. These tests are roughly divided into five sections:

General exams

• • Ist die eigene Plugin-Version mit dem Manager kompatibel bzw. aktuell?
• • Sind ausreichende Rechte des angemeldeten Benutzers vorhanden?
• • Sind benötigte Dateizugriffe möglich?
• • Enthält die Szene dynamische Verlinkungen zu anderen Szenen (z. B. XRefs)
• • Enthält die Szene mindestens eine Lichtquelle?
• • Enthält die Szene animierte Texturen?

These include analyzes regarding the user system used and whether there are general requirements for a scene that are required for the calculation:

• • Is the own plugin version compatible with the manager or up to date?
• • Are there sufficient rights of the registered user?
• • Are required file accesses possible?
• • Does the scene contain dynamic links to other scenes (eg Xrefs)?
• • Does the scene contain at least one light source?
• • Does the scene contain animated textures?

The Results of these analyzes are logged and the user (similar an error message) is displayed. It can preferably only continue if o. g. exams successful. It is often up to the person to fix the errors User, of course the plugin software no way owns administrators rights etc. throughout the system.

• • Version und Erweiterungen (z. B. Service-Packs) der 3D-Applikation sowie des verwendeten Renderers
• • Einheiten und Bemassung der 3D-Application
• • Zugrundeliegende Plattform (Windows, Mac, 32bit oder 64bit-Architektur) und Version
• • Einheiten-Kontext (z. B. Dezimalpunkt oder -komma)?
• • Verwendete Kameras

In addition, "meta-information" about the scene is collected, which can be interpreted by the render farm accordingly. These are automatically written to a configuration file without user interaction and transmitted to the manager. The metadata include:

• • Version and extensions (eg service packs) of the 3D application and the renderer used
• • Units and dimensions of the 3D application
• • Underlying platform (Windows, Mac, 32bit or 64bit architecture) and version
• • Unit context (such as decimal point or comma)?
• • Used cameras

Review of the Render Settings

• • Befindet sich die zu rendernde Auflösung außerhalb der gegebenen Grenzen?
• • Welche Gamma Werte der 3D-Application sind gegeben?
• • Welche Frames sollen gerendert werden? Gibt es Abschnitte oder Sprünge?
• • Werden Pre-Render-Scripts ausgeführt?
• • Werden Post-Render-Effekte verwendet?
• • Wurden Framebuffer definiert, welche Einstellungen haben diese und ist mindestens einer für das Rendering aktiviert?
• • Liegen ungültige Kamera-Einstellungen vor (wie z. B. „tiled”)?
• • Ist ein nicht-unterstützter Renderer aktiviert?
• • In welchem Format soll das Ergebnis ausgegeben werden, wie soll es benannt werden und sind diese Angaben gültig bzw. werden diese von der Renderfarm unterstützt?

This includes general checks for render settings that are independent of specific rendering engines:

• • Is the resolution to be rendered outside the given limits?
• • Which gamma values of the 3D application are given?
• • Which frames should be rendered? Are there sections or jumps?
• • Are pre-render scripts executed?
• • Are post-render effects used?
• • Have frame buffers been defined which settings? are these and is at least one enabled for rendering?
• • Are there invalid camera settings (such as "tiled")?
• • Is an unsupported renderer enabled?
• • In what format is the result to be output, how should it be named and are these details valid or are they supported by the render farm?

Also here will be invalid Test results the User displayed, so that this the appropriate parameters in the scene can correct.

One Special case is the exam whether a single image or an animation should be rendered. This is done automatically based on the number of frames set by the user. If this only covers one frame, a user query is generated whether this one frame will be rendered distributed on the render farm should (distributed single frame job). If this is answered with "yes", so further, single-frame specific tests are carried out: the resolution must be 400 × 400 Pixels exceed and also be completely divisible by the factor 10.

Subsequently logged the plugin in the configuration file rendered a single-frame job shall be.

Review of Textures / maps

• • Alle verwendeten Texturen finden
• • Alle sonstigen Abhängigkeiten zu externen Dateien ermitteln, diese umfassen u. a. VRay Dateien, mental ray Dateien, Global Illumination files, photon maps, Irradiance maps, Final Gather maps, Ifl Dateien, Pointcaches, Simulationscaches, Particle Caches, Hair caches etc.
• • Sind alle diese abhängigen Dateien zum Export-Zeitpunkt vorhanden und lesbar? Wenn nein, werden dem Benutzer alle problematischen Datei-Bezüge angezeigt, so dass dieser entweder die Referenz zur Datei in der Szene entfernen oder aber die Datei an entsprechender Stelle zur Verfügung stellen kann. Ein Export ist nur dann möglich wenn alle Bezüge fehlerfrei vorhanden sind.
• • Sind alle Dateinamen konform mit den Anforderungen der Farm? (Dies heißt insbesondere frei von Sonderzeichen und Leerstellen) Wenn dies nicht der Fall ist, werden alle invaliden Dateien automatisch einer eigenen Notation entsprechend umbenannt und neu verlinkt. Die Korrektur ist automatisiert – hier findet also keine Benutzerinteraktion statt.
• • Hat der Anwender bereits eine oder mehrere der verwendeten Dateien mit einem anderen Projekt auf die Renderfarm geladen? Diese Prüfung erfolgt „live” im Plugin: es wird ein Signal zum Manager gesendet, welcher eine Liste der aktuell auf dem FTP-Server der Renderfarm vorhandenen Dateien des Users bereitstellt. Diese wird dann mit den verwendeten Dateien der Szene im Plugin abgeglichen. Sind identische Dateien vorhanden, wird nur der Bezug zu dieser Datei (einem Link entsprechend) vermerkt, nicht jedoch die Datei selbst kopiert. So kann ein Anwender auf der Farm einen „Datei-Pool” vorhalten und bereits vorhandene Dateien müssen nicht erneut hochgeladen werden. Zum Datei-Abgleich wird hierbei das md5-Prüfsummenverfahren angewendet, um eine vollständige Identität sicherzustellen.

A significant part of the plugin is the collection of all external textures and other files, which are dependent on the user project, so that they are present when calculating on the render farm:

• • Find all textures used
• • Identify all other dependencies on external files, including VRay files, mental ray files, Global Illumination files, photon maps, Irradiance maps, Final Gather maps, Ifl files, Point caches, Simulation caches, Particle caches, Hair caches, etc.
• • Are all these dependent files available and readable at the time of export? If not, all problematic file references are displayed to the user so that he can either remove the reference to the file in the scene or make the file available in the appropriate place. An export is only possible if all references are free of errors.
• • Are all file names compliant with farm requirements? (This means, in particular, free of special characters and spaces) If this is not the case, all invalid files are automatically renamed according to their own notation and relinked. The correction is automated - so there is no user interaction.
• • Has the user already loaded one or more of the used files with another project onto the render farm? This check is carried out "live" in the plug-in: a signal is sent to the manager, which provides a list of the user's files currently available on the FTP server of the render farm. This is then compared with the files used in the scene in the plugin. If identical files exist, only the reference to this file (corresponding to a link) is noted, but the file itself is not copied. For example, a farm user can maintain a "file pool" and existing files do not need to be re-uploaded. File matching uses the md5 checksum method to ensure complete identity.

exams specific renderer

each Contains render engine specific settings and parameters, which are separated accordingly have to be analyzed. Supported by the Farminizer Renderer (non-proprietary renderer of 3D application) are currently z. Mental ray, VRay, final render, Maxwell. The exams concern u. a. the version of the renderer, used additions, global illumination Modes, sampling, gamma correction, etc.

exam of dependencies to plugins or custom shaders

• • Sind beim Anwender lokale Erweiterungen installiert, welche nicht auf der Renderfarm vorhanden sind?
• • Verwendet die Szene nicht-proprietäre Plugins oder Shader?
• • Werden Materialien in der Szene verwendet, welche auf nicht-proprietäre Shader zurückgreifen?

Often, 3D applications are extended by the user by using external attachments (such as plug-ins or custom shaders). If these affect the rendering process or the result of the calculation, a correct result is only given if the render farm has the same plugins or the same versions of these. On the render farm server, there is a whitelist for every 3D application and every platform and version, ie a list of all installed extensions. The Farminizer plugin automatically connects to the server and checks for a new version of this whitelist. If this is the case, the local database is updated automatically. Exams include:

• • Does the user have local extensions that are not present on the render farm?
• • Does the scene use non-proprietary plugins or shaders?
• • Are materials used in the scene that use non-proprietary shaders?

If all exams have been successful, the project can be exported directly. is If this is not the case, then the user is presented with a report that provides information about critical situations and creates indications for implausible inputs. Here are quick guides on how to handle the errors. The Farminizer can remain open, the user can make "live" changes to the project and subsequently restart the test as often as required.

Export:

The Export routine packages the user project into a homogeneous, for managers and renderfarm readable structure and automatically sets for the renderfarm necessary Scene or renderer parameters. A project can only be exported be when all exams were passed without errors - thus User errors and incompatible projects are still ahead of the way recognized and can render to the render farm directly on site in the 3D application Getting corrected.

In front the export will all be needed Files automatically into a specific own folder structure locally copied by the user and linked accordingly in the project. So after the export no dependencies of external files outside of the Farminizer-owned directory it avoids that at the time of transfer to the render farm needed Resources are missing. Likewise, previously used absolute Paths of A, which of course on the render farm are not present, removed and accordingly adapted to the conditions on the server.

The Farminizer plugin creates a config file containing meta data to the project contains. Here All project information is logged, such as which Rendering frames are in which 3D application the project is created which rendering engine should be used. Of great importance Here is the list of all external dependencies such as textures or other files including their checksum. So can upload errors and incomplete Projects are detected even before computational effort on the render farm is claimed.

in the Connection is the total package, consisting of the project files, the config file and all external textures and other files written to the manager for further processing. The package itself is encrypted, so no further changes on the exported project. The manager receives one Message and then starts or updates and imports the new project package independently.

The The final task of the Farminizer plugin is to set the initial state restore the user project. This is necessary with it the scene locally on the user PC can render error-free and no farm-specific changes stored persistently. This happens depending on the 3D application either by undoing made changes or by discarding the modified scene and reloading the source file.

Brief Description:

in the The figures are described below. It shows

1 a schematic structure of the invention with a first computer and the render farm;

2 Fig. 12 shows a flow of steps performed by the system.

The 1 shows the basic structure of the system. On a first computer 1 is the plugin 2 Installed. Over the network 3 (Internet) is connected to the render farm 4 ,

The 2 shows the schematic flow of the steps that the system performs. In one step 1 a download of the plugin takes place. Then the plugin is installed 2 , In step 3 the plugin is called by the application. This collects in step 4 Information. The information thus collected will be in step 5 checked by the plugin, compared with the rules and if necessary adapted as far as possible.

If not all rules are met, a note is issued 6 to the user, who can then modify the data to re-run the test.

In step 7 the information and the project data are transmitted by the plug-in via a network to the second computer, which has at least one rendering device (render farm) whose required information is determined by the set of rules. Then, the automatic adjustment of the rendering device is done on the basis of the information and the project data, and finally the rendering in step 8th ,

Claims (21)

System for transferring project data of a multidimensional animation from a first computer to a second computer connected via a network, which has at least one rendering device (render farm) whose required information is determined by a set of rules, comprising the following components: - means for downloading a plug-in (Farminizer plug-in) to the first computer and incorporating into animation software installed on the first computer, - means for collecting information on the first computer through the plug-in that is related to the project data and / or the rendering device; - Means for checking the collected information by means of a set of rules, and if all the rules have been met, the collected information and the project data are transmitted to the second computer; if the rules are not met, a message is output or the project data is adjusted fully automatically and / or semi-automatically performed with interactive guidance to then transmit the information collected and the project data to the second computer; - means for automatically adjusting the rendering device based on the information and the project data and performing the rendering. The system of the preceding claim, wherein the plug-in in 3D applications like Autodesk Maya, Autodesk 3D Studio MAX, Maxon CINEMA 4D, Autodesk Softimage, Newtek Lightwave, Blender Foundation Blender, Luxology Modo, Autodesk Revit, Rhinoceros 3D, Planetside Terragen, Nextlimit Maxwell, Eon Vue, Autodesk Mudbox, Pixologic Z-brush, Smith Micro Poser, Abvent Artlantis is involved. The system according to one or more of the preceding Claims, it included the rules when the plug-in was started Updated timeliness and if there is a newer set of rules, download the new rules. The system of the preceding claim, wherein the rules part of the plug-in, and a new plug-in downloaded will be to update the rules. The system according to one or more of the preceding Claims, wherein means are provided by which a configuration of the rendering system based on the project data and collected information automatically he follows. The system according to one or more of the preceding Claims, where agents are present, due to the incompatibilities between the animation software and the rendering device based on the rules be detected and / or fixed by both the project file before changed the rendering as well as the configuration of the rendering device. The system according to one or more of the preceding Claims, where there are means by which to render the project data through the renderer without further action of the user and preferably with just one touch (one-click) is performed and the results of the rendering automatically on the first computer is filed. The system according to one or more of the preceding Claims, where there are means by which after successful handover the data is the original one State of the data restored, so on the first computer there is no change preferably by undoing of changes made and / or by discarding the modified data and reloading the source data he follows. The system according to one or more of the preceding Claims, there being means by which during installation of the Plugins automatically menu entries in the Animation application will be integrated, bringing the remote rendering can be started in a normal rendering process. The system according to one or more of the preceding Claims, where there are means by which a general check is made, by checking one or more of the following criteria: - are sufficient Access rights of the logged in user on the first computer available, - are needed File accesses available on the computer, - Contains the scene dynamic links to other scenes, - Contains the scene at least one light source - Contains the scene animated textures. The system according to one or more of the preceding Claims, where means are present through which meta information collected about the project data which are interpreted by the Rendersystem accordingly can, being the meta-information is one or more of the following: - Version and / or extensions of the animation software and the used software Renderers and their gamma values - Underlying operating system platform the first computer, - Units, dimensions and their context, - Used Cameras. The system of one or more of the preceding claims, wherein there are means for checking the render settings with one or more of the following criteria: - Is the resolution to be rendered outside of given limits? - Which frames should be rendered - Are there sections or jumps - Are pre-render scripts executed? - Are post-render effects used? - Have framebuffers been defined and / or configured and are at least one enabled for rendering; - If there are invalid camera settings, - If an unsupported renderer is activated, - In which format should the result be output, how should it be named and supported by the render system. The system according to one or more of the preceding Claims, wherein there are means by which to check whether a single image or a Animation should be rendered, this being done automatically the user sets the number of frames. The system of the preceding claim, wherein Means are available by which only one frame User query is generated, which asks the user if this a frame should be rendered on the render system distributed. The system according to one or more of the preceding Claims, there being means by which a check of textures which are in dependence to the project data is done, and if they are not available so they are searched on the first computer. The system according to one or more of the preceding Claims, where funds are available, through the other dependencies to external files to check if these files exist at export time and readable. The system of the preceding claim, wherein Means are present through which the files preferably one or more more of the following files include: VRay files, mental ray files, Global Illumination files, photon maps, Irradiance maps, Final Gather maps, Ifl files, Pointcaches, Simulation caches, Particle Caches, hair caches. The system after one of the two previous ones two claims, where there are means by which the file name and the file contents checked for compatibility, if necessary automatically changes on the file name and / or the link and / or the content. The system according to one of the three preceding claims, wherein Means are available to check if any of the files, by the user in advance in conjunction with others Project data was transferred to the second computer, if so the case is, only a reference is generated, and the data not retransmitted. The system according to one of the three preceding claims, wherein There are funds available to check for dependencies to plugins or custom shaders in the animation software to verify that they are allowed by the rules. Computer for providing project data Animation software, comprising: - A charger, designed and set up to download a plugin (Farminizer plugin) and to incorporate this into the animation software, which on the first Computer is installed, the plug-in is designed and set up to gather information related to the project data and / or the rendering device; - a device, designed and set up, to evaluate the collected information by means of a set of rules, and if all the rules are met become the collected information and the project data for one Shipping prepared, the rules should not be met, so a message is issued or it will be an adaptation the project data fully automatic and / or semi-automatic with interactive guidance performed to then to prepare the collected information and project data for shipment; Transmission device, which transmits the collected project data and the information. Computer, to render the project data of an animation software through a system according to claim 1 and one or more of the subclaims were, comprising: - One Unit for providing a plug-in with a policy; A receiving unit, the project data and the additional receives collected information, created by the plug-in; - a render system that is up the base of the project data and the information collected parameterize, and that the project data is rendered.