Allow user to work in context and to setup the environment for any given working-application.
By having users working in context enables scripts to work on the metadata of that context.
For instance, a user working on shot 5 could publish shot 5 with the click of a button. The tool then uses the environment to find the information necessary to set the correct format, put the appropriate assets in the correct place and notify whomever has a need to know about the event.2 votes
For tools to work at their best, rigging needs some standards.*
Document clear conventions along with best practices for use with Pipi. Additionally, provide tools to support these.
*This forms the foundation for any sort of automatic rigging.0 votes
Each of the Graphical User Interfaces that ships with Pipi come with a set of features that will utilise an open-ended system, accessible via Python in any given situation.* (Similar to how any tool in Maya simply runs MEL in the background)
This means that you could write your own tools to replace the ones that ship by default with Pipi, without sacrificing their interoperability with other tools that you might find more useful.
*The same applies to script-based tools.3 votes
Pipi is all about content, so there will be lots of effort going into creating a stable and simple yet rich API to access that content, along with its metadata, from your own custom scripts.3 votes
Allow users to append any data to any entity throughout Pipi.
Some entities, such as shots, have some information that goes with it. Such as a description, frame ranges and which assets go into it.
This data can then be accessed by either the user looking for a brief overview of his newly assigned task, or by automation scripts such as Scene Builders or Instance Managers
Other examples include reference images, audio clips for animation or links to other entities such as the source of a publish or author of a certain version.3 votes
Allow users to pass work between each other along with a mechanism to filter results, based on type, to fit into the larger whole.
A graphical user interface would act as the bridge between a user's potentially finished version and the public space where any other user could continue to work on it.
E.g. A rigger works on a character setup, based on the work of the modeler, and sends his work off to the animator who continues the tradition by sending his finished work of to the artist in the next pipeline step.3 votes
Allow any user to create and edit shots, assets, projects and so on by having them work within their own sandboxed (Private) environment.
Their entities can then be submitted for approval after which their contributions will become Public, if accepted.
The concept can then be extended for workers outside of your organisation, such as freelancers working remotely.2 votes
Suggested by Simon Bunker at cgtalk.com
If I understood you correctly, support an arbitrary amount of branches for script repositories, such as a development and production-branch for testing and stable environments respectively.1 vote
When customising the environment for working software, take into account the user and his/her responsibilities.
E.g. a modeller is given a certain set of in-application menus that boasts features relevant to modeling.1 vote
Long-running and detailed simulation take time and effort. The current tools for handling it are insufficient.
The cache manager would provide a graphical way of visualising caches and allow for blending, cutting and pasting as well as continuing from arbitrary locations from within each cache, for cases where the first 100 frames looked good, but there are 500 frames left.1 vote
A uniform way of passing the result of an animated asset from one artist to the next.
Providing the user with a metadata-enabled graphical user interface to facilitate the export of typically complex data.
Initially looking at Alembic as natively supported output format.1 vote
The one place to explore and find published material.
I expect the Library to be accessed by every user working in production on several occasions throughout the day and will therefore concentrate on making it as fast and minimalist as possible to support that use.
Of course, a graphical user interface will ship with this along with a rich API for custom made tools.0 votes
Allow users to quickly mock up metadata in the markdown conversion-language.0 votes
Allow users to nest combine several channels of metadata into one.
Facilitates a summary-based approach of presenting a large set of metadata.
E.g. To provide a summary of existing metadata within a Character Rig. The summary could consist of a description, various data points such as available animation controls, images and reference videos. The summary itself would also be metadata.0 votes
Each graphical user interface will be designed using the latest technology*, independent of what libraries are shipped by default by the various supported applications.
This is made possible by developing from outside the target applications and communicating with them via a server/client-based relationship.
This also makes it so that software that doesn't inherently support Qt** can still benefit from what Qt has to offer.
*Qt 5 offers flexibility in terms of, for example, Qt Quick and its real-time performance.
**Softimage, Photoshop or After Effects amongst others0 votes
- Don't see your idea?