i like the idea but how would be the pipeline look like? whats the end product?
a pipeline for advertisement will look different then a archvis pipeline and
a game pipeline will look different then others.
so i think it would make sense to split the pipeline in different parts so you can build up your pipeline for your requirements.
some examples for some parts:
- Project Folders Structure for Multiple Shots (local and Network)
- Asset Management (Naming, Nodes Layout in Network view, Node Color Definition)
- Managing Revisions / Version Control (Subversion, Git, Perforce)
- External Data Driven Process (example: csv File with Mesh Filename, Shader,some Parameters, Render Resolution, Final Filename)
- Pipeline for Architecture
- Pipeline for Games
- Pipeline for Small Company's
- Pipeline for Lightning and Rendering
- Pipeline Integration with other DCC Apps
- Pipeline Integration with shotgun or ftrack or what ever…..
- Pipeline Customizing
…
hope i could give some inputs :-)
EDIT:
Found something useful :-)
http://www.andrew-whitehurst.net/pipeline.html [
andrew-whitehurst.net]