Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Houdini (software)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Operators=== Houdini's procedural nature is found in its operators. Digital assets are generally constructed by connecting sequences of operators (or '''OPs'''). This proceduralism has several advantages: it allows users to construct highly detailed geometric or organic objects in comparatively very few steps; it enables and encourages non-linear development; and new operators can be created in terms of existing operators, a flexible alternative to non-procedural scripting often relied on in other packages for customisation. Houdini uses this procedural generation in production of [[texture mapping|textures]], [[shader]]s, [[particle system|particles]], "channel data" (data used to drive animation), [[rendering (computer graphics)|rendering]] and [[compositing]]. Houdini's operator-based structure is divided into several main groups: *OBJs β nodes that pass transform information (Traditionally these contain SOPs.) *SOPs β Surface Operators β for procedural modelling. *POPs β Particle Operators β used to manipulate [[Particle system|particles systems]]. *CHOPs β Channel Operators β for procedural animation and audio manipulation. *COPs β Composite Operators β used to perform compositing on footages. *DOPs β Dynamic Operators β for dynamic simulations for fluids, cloth, rigid body interaction etc. *SHOPs β Shading Operator β for representing a dozen or more different shading types for several different renderers. *ROPs β [[Rendering (computer graphics)|render]] operators β for building networks to represent different render passes and render dependencies. *VOPs β VEX operators β for building nodes of any of the above types using a highly optimized SIMD architecture. *TOPs - Task Operators<ref>{{Cite web|url=https://vimeo.com/322225534|title=Houdini 17.5 Launch Event|date=8 March 2019}}</ref> *LOPs - Lighting Operators - for generating USD describing characters, props, lighting, and rendering. Operators are connected together in networks. Data flows through, manipulated by each operator in turn. This data could represent 3D [[geometry]], [[bitmap]] images, particles, [[dynamics (mechanics)|dynamics]], [[shader]] [[algorithm]]s, [[animation]], [[Sound|audio]], or a combination of these. This [[node graph architecture]] is similar to that employed in node-based [[Compositing software|compositors]] such as [[Shake (software)|Shake]] or [[Nuke (software)|Nuke]]. Complex networks can be grouped into a single [[meta-operator]] node which behaves like a class definition, and can be instantiated in other networks like any compiled node. In this way users can create their own sophisticated tools without the need for programming. In this way Houdini can be regarded as a highly interactive visual programming toolkit which makes programming more accessible to artists. Houdini's set of tools are mostly implemented as operators. This has led to a higher learning curve than other comparable tools. It is one thing to know what all the nodes do β but the key to success with Houdini is understanding how to represent a desired creative outcome as a network of nodes. Successful users are generally familiar with a large repertoire of networks (algorithms) which achieve standard creative outcomes. The overhead involved in acquiring this repertoire of algorithms is offset by the artistic and algorithmic flexibility afforded by access to lower level building blocks with which to configure shot element creation routines. In large productions, the development of a procedural network to solve a specific element creation challenge makes automation trivial. Many studios that use Houdini on large feature effects, and feature animation projects develop libraries of procedures that can be used to automate generation of many of the elements for that film with almost no artist interaction. Also unique to Houdini is the range of [[input/output|I/O]] '''OPs''' available to animators, including [[MIDI]] devices, raw files or [[Transmission Control Protocol|TCP]] connections, audio devices (including built-in [[phoneme]] and [[Pitch (music)|pitch]] detection), [[mouse (computing)|mouse]] [[cursor (computers)|cursor]] position, and so on. Of particular note is Houdini's ability to work with audio, including sound and music synthesis and spatial 3D sound processing tools. These operators exist in the context called "CHOPs" for which Side Effects won a Technical Achievement Academy Award in 2002. VEX (Vector Expression) is one of Houdini's internal languages. It is similar to the [[Renderman Shading Language]]. Using VEX a user can develop custom SOPs, POPs, shaders, etc. The current implementation of VEX utilizes [[SIMD]]-style processing.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)