hi, thanks for your responses. actually after thinking again about it i came to the decision to choose workflow1 with terminalmode.
the problem is, more needed changes for our pipeline occured and i actually started to write a new pipeline from scratch with different folder/file-structure, proxys and much more flexibility in mind. I did a lot of rewrites of my own stuff because i was not sure, what would be the best place to save configdata for projects, like colorspaces for reads and writes and some other project specific stuff. I already started a approach with a sqlite database, but then realised, if something breaks it it will make the whole company stop working. My current approach is using a config file for each project with pythons configparser-module, so all projects are independent. How are you actually saving configurations for different projects? the config stuff is actually working, i just need a great solution to cut delievered footage and create the proxies and create the basic filestructure. Till now we did this with nuke, but it s not the best solution for cutting purposes. So i thought about HIERO but i still need to check it out, although this should be a good solution for this purpose. In what step and with what tools are you creating your filestructure for new projects to start? These are all new questions and thoughts... maybe i should start a new topic ...
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
