Blend

From GICLWiki
(Difference between revisions)
Jump to: navigation, search
 
(7 intermediate revisions by one user not shown)
Line 22: Line 22:
 
* '''Family Format(s):''' N/A
 
* '''Family Format(s):''' N/A
  
−
'''Description:''' [[Description:: Loading and saving in Blender is very fast and Blender is known to have excellent downward and upward compatibility. Ton Roosendaal demonstrated that in December 2008 by loading a 1.0 blend-file using Blender 2.48a.
+
'''Description:''' Loading and saving in Blender is very fast and Blender is known to have excellent downward and upward compatibility. Ton Roosendaal demonstrated that in December 2008 by loading a 1.0 blend-file using Blender 2.48a.
  
 
Saving complex scenes in Blender is done within seconds. Blender achieves this by saving data in memory to disk without any transformations or translations. Blender only adds file-block-headers to this data. A file-block-header contains clues on how to interpret the data. After the data, all internally Blender structures are stored. These structures will act as blue-prints when Blender loads the file. Blend-files can be different when stored on different hardware platforms or Blender releases. There is no effort taken to make blend-files binary the same. Blender creates the blend-files in this manner since release 1.0. Backward and upwards compatibility is not implemented when saving the file, this is done during loading.
 
Saving complex scenes in Blender is done within seconds. Blender achieves this by saving data in memory to disk without any transformations or translations. Blender only adds file-block-headers to this data. A file-block-header contains clues on how to interpret the data. After the data, all internally Blender structures are stored. These structures will act as blue-prints when Blender loads the file. Blend-files can be different when stored on different hardware platforms or Blender releases. There is no effort taken to make blend-files binary the same. Blender creates the blend-files in this manner since release 1.0. Backward and upwards compatibility is not implemented when saving the file, this is done during loading.
  
−
When Blender loads a blend-file, the DNA-structures are read first. Blender creates a catalog of these DNA-structures. Blender uses this catalog together with the data in the file, the internal Blender structures of the Blender release you're using and a lot of transformation and translation logic to implement the backward and upward compatibility. In the source code of blender there is actually logic which can transform and translate every structure used by a Blender release to the one of the release you're using. The more difference between releases the more logic is executed.]]
+
When Blender loads a blend-file, the DNA-structures are read first. Blender creates a catalog of these DNA-structures. Blender uses this catalog together with the data in the file, the internal Blender structures of the Blender release you're using and a lot of transformation and translation logic to implement the backward and upward compatibility. In the source code of blender there is actually logic which can transform and translate every structure used by a Blender release to the one of the release you're using. The more difference between releases the more logic is executed.
  
−
'''History:''' [[History:: In 1988, Ton Roosendaal co-founded the Dutch animation studio NeoGeo. This studio quickly became the largest 3D animation house in the Netherlands. Within NeoGeo, Ton was responsible for both art direction and internal software development. After a careful deliberation it was decided that the current in-house 3D toolset needed to be rewritten from scratch. In 1995 this rewrite began and was destined to become the 3D software tool we all now know as Blender.
+
'''History:''' In 1988, Ton Roosendaal co-founded the Dutch animation studio NeoGeo. This studio quickly became the largest 3D animation house in the Netherlands. Within NeoGeo, Ton was responsible for both art direction and internal software development. After a careful deliberation it was decided that the current in-house 3D toolset needed to be rewritten from scratch. In 1995 this rewrite began and was destined to become the 3D software tool we all now know as Blender.
  
 
In 1998, Ton founded a new company called Not a Number (NaN), to further market and develop Blender. NaN's business model involved providing commercial products and services  around Blender. In 2000 the company secured growth financing by several investment companies. Target was to create a free creation tool for interactive 3D (on-line) content, and commercial versions of the software for distribution and publishing.
 
In 1998, Ton founded a new company called Not a Number (NaN), to further market and develop Blender. NaN's business model involved providing commercial products and services  around Blender. In 2000 the company secured growth financing by several investment companies. Target was to create a free creation tool for interactive 3D (on-line) content, and commercial versions of the software for distribution and publishing.
Line 43: Line 43:
  
 
Because of the overwhelming success of the first open movie project, Ton Roosendaal, established the "Blender Institute" in summer 2007. This now is the permanent office and studio to more efficiently organize the Blender Foundation goals, but especially to coordinate and facilitate Open Projects related to 3D movies, games or visual effects.
 
Because of the overwhelming success of the first open movie project, Ton Roosendaal, established the "Blender Institute" in summer 2007. This now is the permanent office and studio to more efficiently organize the Blender Foundation goals, but especially to coordinate and facilitate Open Projects related to 3D movies, games or visual effects.
−
In April 2008 the Peach Project, the open movie "Big Buck Bunny", was completed in the Blender Institute. In September 2008 the open game  "YoFrankie!" was released.]]
+
In April 2008 the Peach Project, the open movie "Big Buck Bunny", was completed in the Blender Institute. In September 2008 the open game  "YoFrankie!" was released.
  
−
'''Example(s):''' [[Example::Blender Example]] - Information and example models of the engineering format.
+
'''Example(s):''' [[Example::Blender Example]]
  
−
'''Identifier:''' [[Identifier::http://www.blender.org]] - A URL or other identifier that refers to the engineering format.
+
'''Identifier:''' [[Identifier::http://www.blender.org]]
  
−
'''Documentation:''' [[Documentation::Documentation Template]] - Information in general about the engineering format.
+
'''Documentation:''' Blend has no official documentation.
  
−
'''File Extensions:''' [[File Extension::]] - Extensions of the engineering format, excluding the dot.
+
'''File Extensions:''' [[File Extension::blend]]
  
−
'''Applications:''' - Applications that the engineering format uses.
+
'''Applications:'''
  
−
* '''Native application(s):''' [[Native Application::Engineering Format Application Template]] - Applications which are primarily designed to specifically run this engineering format.
+
* '''Native application(s):''' [[Native Application::Blender]]
  
−
* '''Interoperable applications:''' [[Interoperable Application::Engineering Format Application Template]] - Applications which can read or write files of this format, but are not native applications for the format.
+
* '''Interoperable applications:''' [[Interoperable Application::None]]
  
−
'''Magic numbers:''' [[Magic Numbers::]] - Unique identifying characters at the beginning of files for this engineering format.
+
'''Magic numbers:''' [[Magic Numbers::None]]
  
−
'''Format(s):''' [[Format::]] - The MIME file types.
+
'''Format(s):''' N/A
  
−
'''Rights:''' [[Rights::]] - The name or type of the license for the engineering format. Examples: BSD-style license, Apache License, Proprietary license
+
'''Rights:''' [[Rights::GNU GPL v2]]
  
−
'''Sustainability Factors:''' - Facts about the sustainability of this particular engineering format.
+
'''Sustainability Factors:'''
  
−
* '''Standardization:''' [[Standardization::]] - Information regarding standardization attempts with this format.
+
* '''Standardization:''' [[Standardization::None]]
  
−
* '''Adoption:''' [[Adoption::]] - Information about how this format has been adopted by other organizations.
+
* '''Adoption:''' [[Adoption::None]]
  
−
** '''Licensing and patent claims:''' [[Licensing and patent claims::]] - Any licenses or patent claims that the engineering format makes.
+
** '''Licensing and patent claims:''' [[Licensing and patent claims::None]]
  
−
* '''Self-documentation:''' [[Self-documentation::]] - Any self-documentation capabilities of the format.
+
* '''Self-documentation:''' [[Self-documentation::None]]
  
−
* '''External dependencies:''' [[External dependencies::]] - Anything that the format depends on outside of its control to function.
+
* '''External dependencies:''' [[External dependencies::None]]
  
−
* '''Technical protection considerations:''' [[Technical protection considerations::]] - Any considerations that are necessary when it comes to technical protection.
+
* '''Technical protection considerations:''' [[Technical protection considerations::None]]
  
−
'''Typical use:''' [[Typical use::]] - Keywords that describe the format's typical use. Examples: CAD and CAM
+
'''Typical use:''' [[Typical use::3D Modeling]]
  
−
'''File classification:''' - Specific properties that pertain to this engineering format.
+
'''File classification:'''
−
* '''Type {Binary, Text}:''' [[File Classification Type::]] - The type of file, choices are binary and text.
+
* '''Type {Binary, Text}:''' [[File Classification Type::Binary]]
−
* '''Raster data:''' - Section describes whether or not the engineering format supports raster data.
+
* '''Raster data:'''
−
** '''Raster data 2D:''' - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
+
** '''Raster data 2D:'''
−
*** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::true]]
−
*** '''Description:''' [[File Classification Raster Data 2D - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Raster Data 2D - Description::None]]
−
** '''Raster data 3D:''' - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a 3D model supports 3D raster data.
+
** '''Raster data 3D:'''
−
*** '''Is Supported:''' [[File Classification Raster Data 3D - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Raster Data 3D - Is Supported::true]]
−
*** '''Description:''' [[File Classification Raster Data 3D - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Raster Data 3D - Description::None]]
−
* '''Geometric representation:''' - Section describes whether or not the engineering format supports geometric representations.
+
* '''Geometric representation:'''
−
** '''Implicit representation:''' - Section describes whether or not the engineering format supports implicit representations.
+
** '''Implicit representation:'''
−
*** '''Implicit surfaces:''' - Can the format support implicit surfaces? Example: A format that can contain surfaces that are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 = 0, supports implicit surfaces.
+
*** '''Implicit surfaces:'''
−
**** '''Is Supported:''' [[File Classification Implicit Surfaces - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Implicit Surfaces - Is Supported::true]]
−
**** '''Description:''' [[File Classification Implicit Surfaces - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Implicit Surfaces - Description::None]]
−
*** '''Implicit curves:''' - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.
+
*** '''Implicit curves:'''
−
**** '''Is Supported:''' [[File Classification Implict Curves - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Implict Curves - Is Supported::true]]
−
**** '''Description:''' [[File Classification Implicit Curves - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Implicit Curves - Description::None]]  
−
*** '''Point set:''' - Can the format support point sets? Example: A format that supports surfaces and lines that are generated by points that form triangles supports point sets.
+
*** '''Point set:'''
−
**** '''Is Supported:''' [[File Classification Point Set - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Point Set - Is Supported::true]]
−
**** '''Description:''' [[File Classification Point Set - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Point Set - Description::None]]
−
** '''Mesh:''' - Section describes whether or not the engineering format supports mesh.
+
** '''Mesh:'''
−
*** '''Manifold surface meshes:''' - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
+
*** '''Manifold surface meshes:'''
−
**** '''Is Supported:''' [[File Classification Mainfold Surface Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Mainfold Surface Meshes - Is Supported::true]]
−
**** '''Description:''' [[File Classification Manifold Surface Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Manifold Surface Meshes - Description::None]]
−
*** '''Manifold volume meshes:''' - Can the format support manifold volume meshes? Example: A format that supports volumes that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
+
*** '''Manifold volume meshes:'''
−
**** '''Is Supported:''' [[File Classification Manifold Volume Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Manifold Volume Meshes - Is Supported::true]]
−
**** '''Description:''' [[File Classification Manifold Volume Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Manifold Volume Meshes - Description::None]]
−
*** '''Non-manifold meshes:''' - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
+
*** '''Non-manifold meshes:'''
−
**** '''Is Supported:''' [[File Classification Non-manifold Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Non-manifold Meshes - Is Supported::true]]
−
**** '''Description:''' [[File Classification Non-manifold Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Non-manifold Meshes - Description::Normals cannot be recalculated correctly on non-manifold meshes.]]
−
** '''Parametric representation:''' - Section describes whether or not the engineering format supports parametric representations.
+
** '''Parametric representation:'''
−
*** '''Parametric surfaces:''' - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
+
*** '''Parametric surfaces:'''
−
**** '''Is Supported:''' [[File Classification Parametric Surfaces - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Parametric Surfaces - Is Supported::true]]
−
**** '''Description:''' [[File Classification Parametric Surfaces - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Parametric Surfaces - Description::None]]
−
*** '''Parametric curves:''' - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
+
*** '''Parametric curves:'''
−
**** '''Is Supported:''' [[File Classification Parametric Curves - Is Supported::]] - Is the feature supported in the engineering format?
+
**** '''Is Supported:''' [[File Classification Parametric Curves - Is Supported::true]]
−
**** '''Description:''' [[File Classification Parametric Curves - Description::]] - This field is used to describe the support or lack of support of the feature.
+
**** '''Description:''' [[File Classification Parametric Curves - Description::None]]
−
** '''Contour sets:''' - Can the format support contour sets?
+
** '''Contour sets:'''
−
*** '''Is Supported:''' [[File Classification Contour Sets - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Contour Sets - Is Supported::true]]
−
*** '''Description:''' [[File Classification Contour Sets - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Contour Sets - Description::None]]
−
** '''NURBS:''' - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
+
** '''NURBS:'''
−
*** '''Is Supported:''' [[File Classification NURBS - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification NURBS - Is Supported::true]]
−
*** '''Description:''' [[File Classification NURBS - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification NURBS - Description::None]]
−
* '''Multi-resolution models:''' - Can the format support models with multiple resolutions? Examples: A format that supports a highly detailed and lowly detailed model simultaneously supports multi-resolution models.
+
* '''Multi-resolution models:'''
−
** '''Is Supported:''' [[File Classification Multi-resolution Models - Is Supported::]] - Is the feature supported in the engineering format?
+
** '''Is Supported:''' [[File Classification Multi-resolution Models - Is Supported::false]]
−
** '''Description:''' [[File Classification Multi-resolution Models - Description::]] - This field is used to describe the support or lack of support of the feature.
+
** '''Description:''' [[File Classification Multi-resolution Models - Description::All models must be at the same resolution.]]
−
* '''Dynamics:''' - Section describes whether or not the engineering format supports dynamics.
+
* '''Dynamics:'''
−
** '''Kinematics:''' - Can the format support kinematics? Example: Does the format allow model parts to rotate?
+
** '''Kinematics:'''
−
*** '''Is Supported:''' [[File Classification Kinematics - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Kinematics - Is Supported::true]]
−
*** '''Description:''' [[File Classification Kinematics - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Kinematics - Description::None]]
−
** '''Assembly:''' - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
+
** '''Assembly:'''
−
*** '''Is Supported:''' [[File Classification Assembly - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Assembly - Is Supported::false]]
−
*** '''Description:''' [[File Classification Assembly - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Assembly - Description::Blender is not meant for CAD applications, so this feature is not supported.]]
−
** '''Force(s):''' - Can the format support forces? Example: Does the format support acceleration forces?
+
** '''Force(s):'''
−
*** '''Is Supported:''' [[File Classification Force - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Force - Is Supported::true]]
−
*** '''Description:''' [[File Classification Force - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Force - Description::One example provided on the official site is a wind force.]]
−
* '''Boundary representation''' - Can the format support models with boundary representations?
+
* '''Boundary representation'''
−
** '''Manifold surface boundary representations:''' - Can the format support manifold surface boundary representations? Example: The engineering format STEP
+
** '''Manifold surface boundary representations:'''
−
*** '''Is Supported:''' [[File Classification Manifold Surface Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Manifold Surface Boundary Representation - Is Supported::false]]
−
*** '''Description:''' [[File Classification Manifold Surface Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Manifold Surface Boundary Representation - Description::None]]
−
** '''Manifold volume boundary representations:''' - Can the format support manifold volume boundary representations? Example: The engineering format STEP
+
** '''Manifold volume boundary representations:'''
−
*** '''Is Supported:''' [[File Classification Manifold Volume Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Manifold Volume Boundary Representation - Is Supported::false]]
−
*** '''Description:''' [[File Classification Manifold Volume Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Manifold Volume Boundary Representation - Description::None]]
−
** '''Non-manifold boundary representations:''' - Can the format support non-manifold boundary representations? Example: The engineering format STEP
+
** '''Non-manifold boundary representations:'''
−
*** '''Is Supported:''' [[File Classification Non-manifold Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+
*** '''Is Supported:''' [[File Classification Non-manifold Boundary Representation - Is Supported::false]]
−
*** '''Description:''' [[File Classification Non-manifold Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+
*** '''Description:''' [[File Classification Non-manifold Boundary Representation - Description::None]]
−
* '''Material transparency:''' - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
+
* '''Material transparency:'''
−
** '''Is Supported:''' [[File Classification Material Transparency - Is Supported::]] - Is the feature supported in the engineering format?
+
** '''Is Supported:''' [[File Classification Material Transparency - Is Supported::true]]
−
** '''Description:''' [[File Classification Material Transparency - Description::]] - This field is used to describe the support or lack of support of the feature.
+
** '''Description:''' [[File Classification Material Transparency - Description::An alpha value can be defined which represents the level of transparency.]]
  
 
'''References:'''
 
'''References:'''
−
*J. Bakker, "The Mystery of the Blend: The Blender File-format Explained", March 2009[http://www.atmind.nl/blender/mystery_ot_blend.html]
+
*J. Bakker, "The Mystery of the Blend: The Blender File-format Explained", March 2009 [http://www.atmind.nl/blender/mystery_ot_blend.html]

Latest revision as of 11:30, 11 May 2009

Title(s): Blend - Blender file format

Version ID: 2.48a

Date released: 2008-10-23

Date: 1998-01-01

Creator(s): Stichting Blender Foundation

Contributor(s): Stichting Blender Foundation

Relationships:

  • Previous Version(s): N/A
  • Contains: N/A
  • Syntax Format(s): N/A
  • Family Format(s): N/A

Description: Loading and saving in Blender is very fast and Blender is known to have excellent downward and upward compatibility. Ton Roosendaal demonstrated that in December 2008 by loading a 1.0 blend-file using Blender 2.48a.

Saving complex scenes in Blender is done within seconds. Blender achieves this by saving data in memory to disk without any transformations or translations. Blender only adds file-block-headers to this data. A file-block-header contains clues on how to interpret the data. After the data, all internally Blender structures are stored. These structures will act as blue-prints when Blender loads the file. Blend-files can be different when stored on different hardware platforms or Blender releases. There is no effort taken to make blend-files binary the same. Blender creates the blend-files in this manner since release 1.0. Backward and upwards compatibility is not implemented when saving the file, this is done during loading.

When Blender loads a blend-file, the DNA-structures are read first. Blender creates a catalog of these DNA-structures. Blender uses this catalog together with the data in the file, the internal Blender structures of the Blender release you're using and a lot of transformation and translation logic to implement the backward and upward compatibility. In the source code of blender there is actually logic which can transform and translate every structure used by a Blender release to the one of the release you're using. The more difference between releases the more logic is executed.

History: In 1988, Ton Roosendaal co-founded the Dutch animation studio NeoGeo. This studio quickly became the largest 3D animation house in the Netherlands. Within NeoGeo, Ton was responsible for both art direction and internal software development. After a careful deliberation it was decided that the current in-house 3D toolset needed to be rewritten from scratch. In 1995 this rewrite began and was destined to become the 3D software tool we all now know as Blender.

In 1998, Ton founded a new company called Not a Number (NaN), to further market and develop Blender. NaN's business model involved providing commercial products and services around Blender. In 2000 the company secured growth financing by several investment companies. Target was to create a free creation tool for interactive 3D (on-line) content, and commercial versions of the software for distribution and publishing.

Sadly, due to disappointing sales and the ongoing difficult economic climate, the NaN investors decided to shut down all operations early 2002. The shutdown also included discontinuing the development of Blender. Enthusiastic support from the user community and customers couldn't justify leaving Blender to disappear into oblivion. Since restarting a company with a sufficiently large team of developers wasn't feasible, in May 2002 Ton Roosendaal started the non-profit Blender Foundation.

The Blender Foundation's first goal was to find a way to continue developing and promoting Blender as a community based open source project. In July 2002, Ton managed to get the NaN investors to agree on a unique Blender Foundation plan to attempt to open source Blender. The "Free Blender" campaign sought to raise 100,000 EUR, as a one-time fee so that the NaN investors would agree on open sourcing Blender. To everyone's shock and surprise the campaign reached the 100,000 EUR goal in only seven short weeks. On Sunday Oct 13, 2002, Blender was released to the world under the terms of the GNU General Public License. Blender development continued since that day driven by a team of far flung dedicated volunteers from around the world led by Blender's original creator, Ton Roosendaal.

With Blender originating as an in-house creation tool, the day-to-day feedback and interaction of both developing and using the software was one of its most outstanding features. In first 2.5 years of open source development, it was especially this uniqueness of Blender that has proven to be difficult to organize and maintain. Instead of getting funding to bring together software developers, the Blender Foundation decided to start a project to bring together the most outstanding artists in the Blender community and challenge them to make an exciting 3D animation movie short.

This is how "Project Orange" started in 2005, which resulted in the world's first and widely recognized Open Movie "Elephants Dream". Not only was the entirely created using Open Source tools, the end-result and all of the assets as used in the studio were published under an open license, the Creative Commons Attribute.

Because of the overwhelming success of the first open movie project, Ton Roosendaal, established the "Blender Institute" in summer 2007. This now is the permanent office and studio to more efficiently organize the Blender Foundation goals, but especially to coordinate and facilitate Open Projects related to 3D movies, games or visual effects. In April 2008 the Peach Project, the open movie "Big Buck Bunny", was completed in the Blender Institute. In September 2008 the open game "YoFrankie!" was released.

Example(s): Blender Example

Identifier: http://www.blender.org

Documentation: Blend has no official documentation.

File Extensions: blend

Applications:

  • Interoperable applications: None

Magic numbers: None

Format(s): N/A

Rights: GNU GPL v2

Sustainability Factors:

  • Standardization: None
    • Licensing and patent claims: None
  • Self-documentation: None
  • External dependencies: None
  • Technical protection considerations: None

Typical use: 3D Modeling

File classification:

References:

  • J. Bakker, "The Mystery of the Blend: The Blender File-format Explained", March 2009 [1]
Retrieved from "http://gicl.cs.drexel.edu/wiki-data/index.php?title=Blend&oldid=31142"
Personal tools