- This topic has 12 replies, 6 voices, and was last updated 12 years, 9 months ago by .
-
Posts
-
Hi all,
My name’s Leo, currently working on full CG movie as compositor. The movie consists of about 1600 shots. Each layer of a shot consists of about 8 passes (Ambience, specular, etc).
How do I set the file management system for this project? Is it better to brake down to several projects, based on scenes (maybe around 90 scenes) or acts (about 4 acts), or just keep ’em in one project with specific folders, or desktop (in Toxik)? Or any other ideas?
I am using Autodesk Toxik for compositing and Final Cut for offline editing.
Really appreciate any inputs of file management or workflow system.
Thanks
Hi Leo,
Based on your description, and depending on the # of users that will be using Toxik simultaneously, I would tend to suggest using one Toxik database per scene (that is, 90 Toxik databases in total), and possibly one Toxik project per each shot (this is not as important). This should provide an optimal solution as far as database management is concerned, especially if you expect to have multiple users accessing the Toxik database simultanenously.
You could reduce the # of databases, but unless you have strong reasons to do so, I would favor a more granular database structure. Note that, on a give workstation, all your database can share the same media cache, same database server, same permit server. New databases are created using the “txdbutil” command line tool:
txdbutil createdb .. (with arguments)
I hope this helps. Please let me know if you need more information with this.
Regards,
Charles Martin
Toxik Development Manager
[/i]Dear Charles,
At first, i would like to thank you for the advise.
What is the benefit by splitting the database for each scene?
Is it going to minimize the risk of data-loss or else?Thanks again.
Cheers,
Leo
Hi Leo,
The use of multiple databases is not to prevent possible data loss, but database contention. By contention, I mean having multiple users accessing the same tables simultaneously. Using multiple database, when appropriate, reduces the risk of contention and can generate better performance.
Charles
Hi Charles,
I see want you mean..
I will create new database based on scenes then.Many thanks.
Leo
Hi Leo,
I further discussed this “one Toxik database per scene” strategy with a few colleagues yesterday. Some people suggested that “one Toxik database per act” might be sufficient (that is, 4 databases in total) and could reduce the database management aspect of your setup. It depends on the # of users, complexity of your shots, and whether you want shots in a given scene to be visible in other scenes (in which case, you would be better off with a “one Toxik database per act”).
Charles
Hi Charles,
there are only 5 compositors including me. Our target is 3 shots/day for each compositor. (phew!) :P.
Well, I think 90 databases take a lot time to manage also (eg. change the toxik.ini every time I run Toxik and need to access another DB). So, yes maybe I will try set the DB based on Acts.Thanks!
Leo
Why are you having to change your toxik.ini? Are you doing it to change the db set in the toxik.ini? If thats the case you don’t have to edit the toxik.ini every time you want to switch db’s all you have to do is use the command line and launch toxik with the -d option specifying the database to use.
Hi Charles,
ok, thanks for the tip! 🙂
leohartadi wrote:Hi Charles,ok, thanks for the tip! 🙂
No problem, except that it was not me who provided the tip!
Charles
1600 shots, 5 compositors and 3 shots a day?!
brave souls. i wish you luck (and let me know if you need help!)
😀
//gD
is not 5 compositors anymore… now is 10 compositors… including me 😀
its a honor to become a part of the team 😀is not 5 compositors anymore… now is 10 compositors… including me 😀
its a honor to become a part of the team 😀
- You must be logged in to reply to this topic.