No really, I’d love to hear about your workflow!

During a recent double over-nighter I found myself thinking about workflows. And the nitty gritty stuff too, like how frequently people version their project files, how they name their assets, and how they arrange their folder structures. I would really love to hear from anyone about the nuts and bolts of how you go about “going about your business” I know this is probably boring stuff to most people, but it can make or break a workplace. Here’s a list of other possible things to talk about.

Do you use any ingest management software? (such as fcp loader or flow by gridiron)
Network setup (do you edit off of a san / internal drives / external drives)
backup plan for old jobs?
do you have any network rendering set up? for what apps?
what do you use as your go-to codec?
do you have any must-have hardware?
how frequently do you version your project files?
(how) do you name your assets?
how do you arrange your folder structures?
Do you have a preferred bin structure in final cut?

Also, what are the worst parts of your current setup? Is there anything that you would like to implement but can’t?

Feel free to post in the comments, email me at r at this domain, or use the comment form in the sidebar. I can’t wait to hear what you have to say!

~ by ross on September 11, 2010.

2 Responses to “No really, I’d love to hear about your workflow!”

  1. I’ll write a large blog post about our workflow here at the Reality TV Production company I work at. I need to write a post production whitepaper anyway for new AEs coming in 🙂

    In short, we use iteration numbers and initials. It’ll be “[show abreviateion] [episode #] [act] [iteration number] [initials]”. Example would be “SQ2 201 Act 4 IT015. That’s the 15th iteration of Scream Queens Season 2 Episode 1. We use iterations because with so many different editors using different systems we enforce them to use one, painfully simple system of every version having a trackable iteration number. Every time you open and edit a sequence, new iteration.

    We had way too many editors labeling project files “CURRENT CUT v5.2” or “current_CURRENT_4/2 4.24”. I’ll be more detailed in my blog post and include our backup regiment and server file structure 🙂

  2. Thanks Nate! I look forward to your post!

Comments are closed.