Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

RED One / FCP / Redcine / Color / Resolve workflow questions (LONG)

Luke Holwerda

Well-known member
Joined
Mar 9, 2010
Messages
47
Reaction score
0
Points
6
Website
www.blackchalkproductions.com
Hi. I'm shooting my first feature at the moment. I've shot 2 music videos on RED and done a few other short films on other cameras... so I'm not a complete noob, but I have some semi-basic RED questions I'd like to ask. I think the best way for me to keep everything straight is to just number my questions, then under each one, sort of give a little back story. We’ll see how this works…

Just to give some quick info on us and our current situation… I come from the digital photography world. I have a pretty firm grasp on the physical tech side of the camera world. But I’m self-taught, so terminology might be lost on me sometimes. I’m very into figuring things out for myself…. Up to a point… clearly. But I read a lot online about exports and ‘delivery’… and I want to get everything right on this movie. I don’t want to get to the end and go “Crap, we did this all the wrong way.” What we turn out isn’t going to be perfect, I accept that, but I don’t want to have any compromises on the back end, if I can help it. That said… we are still an indie film. Our lead actor is also our producer. My brother and I are still day-job working schleps. My brother bought the RED way back when they first hit. Since then, we’ve only shot this movie and 2 music videos on it. We’re working on Mac’s, so at least were not in the stone age of computing. But at this point, we’re over budget, and were basically working with the software we have available. Which currently is Final Cut studio "3"... All the RED software... and the Davini Resolve demo. I'm on a late-2008 Macbook pro with 4gb memory, brother is on a 2009 MacPro with 12gb. Anyways… this is all just to tell you what we have, and basically, we can’t really afford to buy anything more than what we have… so I need to find the best way to work with what we’ve got. We both have a copy of all the footage on an E-SATA backup drive, and we'll be trading duties on editing. Or more likely in the end, he'll edit, and I'll color.

Ok! Moving on. Let’s just dive right in.

1 – Editing. What’s the best attack route? (File type-wise)

We've been doing dailies and little edits along the way, but we have conflicting methods. When editing officially begins, I want to have the best plan laid out from the start. Currently, with our dailies, it’s just down and dirty… cut something together… sort of thing. But like I said, when we start passing the files around, and I attempt to color something, I see the flaws.

In my head, I think getting a rough edit together using the ¼ proxies is best. Then once we’ve at least selected all the possible clips we might want in a particular scene, I can pull them all into RedCine and give them a baseline “color correction” job… so we’re not gasping as we watch the edits. However, even at this point, I worry about transcoding and effectively “degrading” the image quality by pushing it down to 1080 or 2k. (I worry that passing things in and out of FCP somehow starts to chip away at the image quality) What are the thoughts on that? Transcoding early, and continuing to work on the image. Also, what are the thoughts on the initial phase... as in, which proxy to work with?

2 – Image quality. When to transcode, and what size?

What I would LIKE to do… what sounds best in my head… is to edit the movie all the way through, with “color corrected” footage. Then at the end, be able to make a decision, scene by scene, on how things should look… then go back to the R3D files, re-color correct, transcode to the proper size, then send to the grading software for the final touches. But here are my issues/questions with that…

What SHOULD the final size be? And what QUALITY output? I hear 2k thrown around a lot for theater showings. Since our film is an ULB SAG project, we have to show it in the theater at least once. Not that I think our film is Star Wars or anything… but since it was shot on RED, and has the possibility to look very nice, I’d like to give us the best POSSIBLE product. So I don’t know exactly what that equates to on the export side of things. I was hoping you could elaborate on this a bit. (Codecs, bitrates, dimensions)

3 – Apple Color. Good enough??

Keeping with the previous question’s theme… is Color a “good enough” program to work with? Honestly, I DO feel a bit limited by it sometimes. It feels cumbersome when compared to the RAW editors I’ve worked with on the still image side. I worry, for no real founded reason, that when I render things in Color for the final project, that they will somehow not be as good as possible. For example, there aren’t as many controls when it comes to rendering in Color as there are in FCP or RCX. Should I worry? I know Color can work off the R3D files, which I think is great actually. But SHOULD I be doing that? Or should I work only with files transcoded from RDX? There are no debayer settings in Color, and that bothers me.

I’ve been looking at DaVinci’s Resolve, and I think it looks amazing! But again, I’m running a fairly old Mac, and I don’t really have the cash to spend on another program. Plus, just to run the demo, I have to update my OS! This is my situation currently!! What is the serious consesus here? I know I CAN do it in Color, but is this just a terrible idea? Should I just abandon Color now, and at least start working in the Resolve demo?? (I would assume I could start with the demo, then buy it later and my files should still work??)

4 – Sound? When to start syncing audio?

Ok. Sound. I sort of hate dealing with sound. For this film, as our first serious endeavor, we had to start from scratch. We did the best we could on our budget. We’re using a very nice Sennheiser shotgun boom mic (I forget the model number, but this was expensive, bought at the same time as the RED), we have 3 Sennheiser EW-112 G2 (or maybe G3) lav mics, all into a Tascam DR-680 field recorder. Sound is going to be inconsistent, we all know that. So we’ve accepted the fact that there will be a lot of ADR. Plus, our soundman was just a friend of ours that we taught to use the machine. (I’m sure you’re cringing by this point J) So some of our sound will suck serious ass. But, regardless, we have to work with what we have, then fix what we can. But when is a good point to start syncing individual audio tracks with the video?

Initially, I thought we’d edit the film, then deal with sound. Because I knew between my brother and I, there was every possibility that we’d change things along the way. But now I sort of feel like we should be working on sound scene by scene. However… again with things I don’t fully understand… I want to use Logic to edit our sound. I know it’s another fully integrated Apple product, so I’m happy with that. But do I need to set everything up in FCP, then “send to” Logic, just like video clips to Color?? This is one area I’m pretty lost on.

5 – The final export.

Ok. I probably have more questions that will crop up, but this is something I think about a lot.

Currently, our files are arranged by scene number on a 12TB backup drive. Movie folder > Scene # folder > RED video folders + Audio folders

I plan to edit BASICALLY scene by scene in FCP. So, effectively, we’ll have a FCP project file for roughly every scene number. (Except those that flow very naturally together) So am I correct in thinking that at “the end of all things”, I will be copying and pasting the individual timelines into a “master” timeline? Or should we just keep one giant project file going?

Again… I’m really curious about the best way to actually export things from FCP. Settings-wise. Even for a 90 minute film, the file would be enormous, wouldn’t it? For some reason I can’t wrap my head around this step. I read Blu-ray reviews and I pick up things like “back ground banding” and “transfers” and “AVC encodes”… and I’m lost. Reviewers seem to attack the distributors of the film for the transfer style chosen… I’d like to have an informed decision when it comes to this. J

Ok. There is probably more I could ask… but this will probably take a long time to answer as it is! I thank you in advance. And if something seems very basic or silly, feel free to laugh… but at least give me a shove in the right direction.

-Luke
 
Thanks for the quick reply! It was an illuminating read. Am I understanding correctly, that you transcoded ALL your files at the start... and edited with those? THEN, relinked using Redcine X? I like this idea... I guess my problem is that we didn't do this on a daily basis, so we'll have to do this one scene at a time. But I like what you said about not relying on Color to handle the native raw 4k files. That's a good point.

Can I just edit with the 1/4 proxies, send to Redcine X, reconnect to the raw files, and go that way?

Also... since Resolve can apparently work with the XMLs and the native raw files, AND grade the footage... this sounds idea. But, if I don't have the hardware to run it... I'm liking this idea so far.
 
Just a few things I would suggest:

1) Have one FCP project and multiple sequences. From the bottom up, you could edit scenes, then drop your scene sequences into Reel sequences and then your reel sequences into your full feature timeline. Typically, reels are anywhere from 10-15 minute chunks of your film.

2) You're going to need to synch your audio by hand or by using Pluraleyes. If using Pluraleyes, make sure you disable the camera's scratch track before you start the synch or you'll spend a ton of time doing this later.

3) Don't fuss with mixing down the audio or doing any coloring until you have locked picture on the edit. Take detailed notes along the way so you can implement fixes during the onlining of your film.
 
Final Cut 3 and Redcine will be fine/great.

You'll save yourself a lot of pain by transcoding to ProRes and editing 'offline' from that, with the intention of re-linking to the r3ds at the end. Oliver used ProResHQ 1080 but I think you'd be pleasantly surprised at how adequate ProResLT 720 24p would be for an offline, and it's a quarter of the file size, meaning it's soooooo much easier to manage, especially with the equipment you've got. We actually use it for masters destined for the web. Oh, and please try to borrow another drive for backing up the r3ds! Drives fail. It happens. Best of luck.
 
Am I understanding correctly, that you transcoded ALL your files at the start... and edited with those? THEN, relinked using Redcine X?

Yes. The workflow was:

1. Redcine-X : transcode R3D to ProRes for offline editing
2. FCP : sync, merge, edit , lock cut
3. Send XML from FCP to Redcine-X by reels (R3D files conformed in Redcine-X timeline)
4. Adjust all shots as "primary grading pass" in Redcine-X
5. Render out timeline in Redcine-X as single piece of ProRes media
6. Import these rendered files into FCP and then notch all cuts
7. Send notched reels from FCP 7 to Color
8. Grade in Color - render - back to FCP for completion

Normally I should have been able to send an XML to Redcine-X and then another XML from Redcine-X to Color and work natively with R3D in Color. This didn't work because the XML from Redcine-X kept crashing color. This "2-step" approach was actually faster than working natively with R3D files in Color without any compromise in quality. Adjusting raw settings in Redcine-X and then further grading in Color is essentially no different than adjusting raw settings in the Color RED tab and then applying further correction on top of that within Color.

Can I just edit with the 1/4 proxies, send to Redcine X, reconnect to the raw files, and go that way?

I don't advocate doing anything natively with the RED files or the "proxies" in an NLE. These are actually linked QT ref files and you are asking for a world of hurt using these on something as complex as a film.

Also... since Resolve can apparently work with the XMLs and the native raw files, AND grade the footage... this sounds idea. But, if I don't have the hardware to run it... I'm liking this idea so far.

The same hardware that can run FCP and Color is fine for Resolve. There is no magic to it and no exotic hardware required. You can run Resolve on a 17" MacBook Pro. Yes, Resolve will read the FCP 7 XML and link to the R3D files. Are you comfortable doing color grading with either Color or Resolve? Do you have proper monitoring?

- Oliver
 
I’m really curious about the best way to actually export things from FCP. Settings-wise. Even for a 90 minute film, the file would be enormous, wouldn’t it? For some reason I can’t wrap my head around this step. I read Blu-ray reviews and I pick up things like “back ground banding” and “transfers” and “AVC encodes”… and I’m lost. Reviewers seem to attack the distributors of the film for the transfer style chosen… I’d like to have an informed decision when it comes to this.


Don't over-think this. A 90 min. export in ProResHQ (1920x1080@23.98) is about 110GB. Even if it's ProRes4444, it won't be horrendous. You can send your exported file to Compressor and use the Blu-Ray preset and you'll get a very good looking disc for presentation and festival purposes. You'll need a BR burner (like one from LaCie), but otherwise you have the tools.

- Oliver
 
Hi. I'm shooting my first feature at the moment. I've shot 2 music videos on RED and done a few other short films on other cameras... so I'm not a complete noob, but I have some semi-basic RED questions I'd like to ask.
Most of your post questions could be answered by taking the Reducation Post class. Lots to be learned there.

One thing I'd advise you to do right now: do a lot of tests and make sure your workflow is practical. I'm not convinced Apple Color is as good an option as DaVinci Resolve, right off the bat. Even the free version of Resolve has more far features than Color, in my experience. But there is a steep learning curve to both.

I would also worry more about the final destination of the project than anything else. Where is this going to? If it's direct to DVD (or Blu-ray), then a 1080 workflow might be more practical and affordable, especially with older Macs.

Then once we’ve at least selected all the possible clips we might want in a particular scene, I can pull them all into RedCine and give them a baseline “color correction” job…
How is your monitor calibrated? Unless you can believe what you're seeing on the monitor and have reliable scopes, all bets are off. You may be literally painting yourself into a corner.

Sound is going to be inconsistent, we all know that. So we’ve accepted the fact that there will be a lot of ADR. Plus, our soundman was just a friend of ours that we taught to use the machine.
That's very sad. If you had gotten a decent sound person for the shoot to begin with, you could probably save thousands of dollars unnecessarily spent on ADR. The other issue is, the actor's performance will never be the same as it is on location. The cheapest fix for this is: immediately after the scene is done, have the actors stand off to the side, get the mike close, and have them say all the lines again just as wild tracks. This will give your sound editor the chance of getting better quality without having to resort to ADR. But a lot depends on how bad the locations are. Sometimes, ADR is unavoidable, if the locations are hostile for sound. (Airports, highways, beaches, noisy cars, wind, rain, etc.)

I want to use Logic to edit our sound. I know it’s another fully integrated Apple product, so I’m happy with that. But do I need to set everything up in FCP, then “send to” Logic, just like video clips to Color?? This is one area I’m pretty lost on.
Pro Tools is by far the most widely-accepted editing and mixing program for film & TV. To me, this is a far better choice than Logic. Once the film is fully edited and locked, break it down to 20-minute reels and export each one as an OMF. Bring those into Pro Tools, and have a sound editor work on each one as required. Dialog, music, and effects are often handled separately, since each has different issues. When the mix is finished, export the finished tracks and lock them back to each reel in the FCP timeline. You can later create a sequence that will play out the entire 90-minute project as one QuickTime file, typically ProRes 4:2:2 HQ or ProRes4444. Many home video companies and film festivals will accept an HDCam or HDCam-SR videotape for delivery, and lots of post houses can take your QuickTime file and transfer them to tape. Some distributors will allow (or even prefer) file delivery, but they have very, very specific requirements on file types, sizes, compression rates, aspect ratio, formatting, and track assignments.

This is not a simple area. This is why post supervisors are an integral part of the process.
 
Thanks for all the responses! I was out of town with no computer this weekend... so I'm gonna fire back at you now...

I'm getting a better grasp on what is the best way to attack this. I still have a few nagging questions tho...

Proxies - What is the big drawback? The only thing I can GUESS, is that the XML files don't recognize the proxy file names... or that the filename doesn't allow for relinking to the raw files in whatever program that XML file is opened in. Is that correct? And if so... the issue is that we'd have to relink every clip one at a time. That still sounds like less time than transcoding every file at the start.

Transcoding - In the "final transcode"... my brain says to do it once, at the end. Meaning... the "best" option, to me, is to edit in FCP, then XML to Resolve... color correct and grade off the raw files, all in one program, then debayer and transcode down to the prores files... and just be done. BUT... I don't think we have the hardware to run Resolve that way... so we'll be forced to transcode in Redcine, then grade off the Prores files rather than the raw. Am I being too picky here?

So basically... talk me out of using the proxies at all... and tell me that the prores files will be good enough to grade off of. (Then render... then send to FCP... then render again! It's all this rendering that bothers me.)
 
Oh... and a few one-on-one replies...

Oliver - Thanks for all the responses! I'm reading a lot of your blog posts now! Great work!

5. Render out timeline in Redcine-X as single piece of ProRes media

Why are you rending as a single piece, if you have to just clip it in FCP? What is the benefit I'm not seeing here?

The same hardware that can run FCP and Color is fine for Resolve. There is no magic to it and no exotic hardware required. You can run Resolve on a 17" MacBook Pro. Yes, Resolve will read the FCP 7 XML and link to the R3D files.

I couldn't get Resolve to play anywhere NEAR normal speed when working from the R3D files. Is there a way to work in Resolve with the proxies? (That was sort of a joke for you) But maybe I'm missing a step in Resolve. It seems very cumbersome... resource heavy. But I imagine it would work MUCH better with the prores files... and much "cleaner" than Color. Thoughts?

Doug - Thanks for the audio tips. I'll wait till the end.

James - I hear you on the prores files... it's just that it will require so much extra time to transcode everything. My brother and I don't work like the most well oiled commercial team... so we tend to have a ton of takes. I still need a solid reason not to use the Proxies. Oh, and we do have the film backed up in 3 places. Different locations too. :) But good call!

Marc - Again, thanks for taking the time to respond. A few answers and questions for you too...

I would also worry more about the final destination of the project than anything else. Where is this going to? If it's direct to DVD (or Blu-ray), then a 1080 workflow might be more practical and affordable, especially with older Macs.

Festivals and eventually Blu-ray/DVD... and web later on. For festival screenings sake... should we be rending/transcoding everything to 2k AND 1080 to be safe?? Is there any image degradation if I work with 2k until the very end and export to 1080 from FCP??

How is your monitor calibrated? Unless you can believe what you're seeing on the monitor and have reliable scopes, all bets are off. You may be literally painting yourself into a corner.

I know what you're saying. I do. But I can only do what I can do, with what I have. Luckily, I at least have the new 27" Apple monitor. I'm not against doing tests for color's sake and watching it in 20 different devices to see how far off I am. I have some background with photos and video... so I'm not at least a complete beginner. I feel confident enough.

That's very sad. If you had gotten a decent sound person for the shoot to begin with, you could probably save thousands of dollars unnecessarily spent on ADR. The other issue is, the actor's performance will never be the same as it is on location.

I agree... but like I said... all we could do was what we could do. We got a lot of good sound... some days it was just impossible.

The cheapest fix for this is: immediately after the scene is done, have the actors stand off to the side, get the mike close, and have them say all the lines again just as wild tracks.

We did at least have the forethought to do this on some of the really terrible days. Good call tho!
 
Luke, at this point I'd look beyond Color for sure. I was hoping to squeeze every last ounce of grading out of it before moving on but it just kept coming up short for me recently. I moved over to Resolve with a minimum hardware config at the moment and all I can say is wow. What a difference. Workflow is easier, quality is better.

Go the transcode route. Proxies used to be a workable solution but most have moved on from them now. Transcode to a lightweight codec for editorial and conform/grade in Resolve with R3Ds. Or edit natively in Premiere CS 5.5 and conform/grade in Resolve. Just graded a feature this way that was edited natively in Premiere. Pretty smooth sailing. By the way, it was really the first thing I had graded in Resolve. Had just a couple of days to get up to speed. Still a lot to learn/master but you can get running quickly with it.

There are a lot of valid workflows. You need to find one that suits you and your facility. Work within the limits of your hardware and you will be fine. Follow the blogs of the post gurus like Michael Cioni and Mike Most. Wealth of information.

Good luck!
 
Steve - Thanks for the reply...

I guess one thing I might have left out is that my brother and I both have a backup of all the footage... so transcoding everything will be very time consuming, even if it's one scene at a time, maybe more so... because then I have to drive to his house and transfer the footage to his drive. (or vice versa) So if I can get by with just editing in FCP with the proxies, that sounds best to me. And from what you said, it sounds possible.

I moved over to Resolve with a minimum hardware config at the moment and all I can say is wow. What a difference. Workflow is easier, quality is better.

What is your hardware set up?? Maybe I just need to learn more about Resolve. I just feel way more than sluggish. Any specific tips you can give me, or a blog/resource you can point me to?

What was the feature you worked in Resolve on? I'd like to see how it turned out.

Thanks!
 
Try a small sequence with the proxies and then take that through your finishing pipeline to make sure it all works for you. By that, I mean make sure the proxies play smoothly on your system while editing, then make sure everything conforms properly in the latter stages. Doing this initial test will save you some headaches.

The hardware I did the grade on was a 2008 Mac Pro with GT120 and GTX285 cards from MacVidCards and a Decklink SDI Card (yep, the $295 version). The footage was stored on a RAID connected to an ATTO R380 SAS card. I'm keeping an eye on the Mac Pro front to see what Apple does, but I plan on having a system that can support all of the Nvidia cards and my RED Rocket.

The project I graded was a feature called Exhumed shot on Red One M sensor by Ken Willinger and it's a black and white movie. It's aimed at film festivals and Blu Ray release. I'm sure Netflix eventually. I'll post more info when it becomes available.

Some technical notes, I was not able to grade in realtime. Hardware limitation. With an expansion chassis, I could get the RR involved and probably be getting close to realtime. Render time without Red Rocket at full quality was 17 hours for a 1.5 hour movie. Actually not too bad.
 
Why are you rending as a single piece, if you have to just clip it in FCP? What is the benefit I'm not seeing here?

I rendered each reel as a complete conformed timeline. But this is only a first step to get basic raw settings correct and shots matched. Since I had to go back to Color for the "subjective grade", I needed to go through FCP for the Send To function. Remember, the RCX XML was crashing Color. Plus, ultimately I would need to be back in FCP anyway to marry with my audio mix from Pro Tools and to create the various deliverables. "Notching" each cut in the timeline ("blade" or "add edit") gives Color defined clips for correction. This is essentially the same process as if you went through a DaVinci 2K doing a tape-to-tape color correction pass. It's also a manual version of what DaVinci Resolve does with Automatic Scene Detection.

Regarding the option of Color versus DaVinci... This was not my system. The client already owned FCS (with Color) and a KONA card. Could hardly justify spending $2K to replace it with DaVinci Resolve and a Decklink card.

- Oliver
 
I rendered each reel as a complete conformed timeline. But this is only a first step to get basic raw settings correct and shots matched. Since I had to go back to Color for the "subjective grade", I needed to go through FCP for the Send To function. Remember, the RCX XML was crashing Color. Plus, ultimately I would need to be back in FCP anyway to marry with my audio mix from Pro Tools and to create the various deliverables. "Notching" each cut in the timeline ("blade" or "add edit") gives Color defined clips for correction. This is essentially the same process as if you went through a DaVinci 2K doing a tape-to-tape color correction pass. It's also a manual version of what DaVinci Resolve does with Automatic Scene Detection.

Regarding the option of Color versus DaVinci... This was not my system. The client already owned FCS (with Color) and a KONA card. Could hardly justify spending $2K to replace it with DaVinci Resolve and a Decklink card.

- Oliver
Perfect example of the various ways one can do something. Valid workflow that got the job done. And for many workflows, Color and a Kona card can still go a long way too. I had to move away from it because I needed faster render times, Epic support, etc. But others may not have those same needs and could get good results from a setup they already have.
 
I know what you're saying. I do. But I can only do what I can do, with what I have. Luckily, I at least have the new 27" Apple monitor. I'm not against doing tests for color's sake and watching it in 20 different devices to see how far off I am.
That is a very, very bad idea. The Apple Cinema Displays are not accurate for judging color, especially for a home video or theatrical release. You need to buy or rent or borrow a "real" monitor (even a Panasonic plasma), and hire a pro to come in and set it up properly for Rec709 color space, assuming you're going to have a home video delivery. Anything else could have tragic results. I'm sure there's an ISF-certified alignment person in your area who could do this for you for a few hundred dollars.

I agree... but like I said... all we could do was what we could do. We got a lot of good sound... some days it was just impossible.
Hiring good people can make all the difference in the world. It's a funny thing: many non-technical people don't necessarily know what good audio sounds like. But everybody knows what bad sound is like.
 
Anything else could have tragic results.

How would you define "tragic"? Something like skin tones are a little more orange than they should be, and the distributor throws the movie away and shouts "You'll never work in this town again!"?

It's a funny thing: many non-technical people don't necessarily know what good audio sounds like. But everybody knows what bad sound is like.

I hear that! (See... we were talking about sound and then I did a pun. Yeah.)

Here's the bottom line. As I said in the original post... we don't have money to hire a bunch of people to finish the movie for us. If we did, we'd have hired people to help us film the movie too. We're just making our start with this film. It's indie. It's self produced. And we were lucky enough to get our hands on a Red. And we need to do the best we can with what we've got. I agree with you... if I hired a bunch of professional industry people... we'd be able to churn this movie right out and be done. But it's not going to happen. So I'm just looking for a few answers and a shove in the right direction. Anything you can offer to the end, I will appreciate.
 
How would you define "tragic"? Something like skin tones are a little more orange than they should be, and the distributor throws the movie away and shouts "You'll never work in this town again!"?
It could be worse. The distributor could look at the results and say, "this fails our quality control and cannot be aired. Do it all over again or the deal's off." I have personally had panicked clients come in with failed QC reports, because they either tried to take a shortcut or do the work themselves, and we wound up redoing all or part of the project for them. In some cases, the fixes were simple, like minor tweaks of the audio levels and smoothing out the mix; in other cases, the fixes took days and days, when the color was all over the place, and we had to essentially reconform and redo their color-correction from scratch. I worked on another major studio project where we were told we had 30 days to get everything done. Two weeks in, the producers told us: "whoops! We just re-read the contract, and if it's not all done by Monday, we'll get sued!" So we worked 4 20-hour days in a row and got two weeks of work done in 4 days. Post is not easy.

It's kind of like building your own house. You can draw up your own plans (instead of hiring an architect), you can put up the frame and hammer the nails (instead of hiring a carpenter), you can mix and pour your own concrete (instead of hiring a foundation expert), but there's always the risk that the city inspector could come in at the end and say, "nope -- this is not up to code and you didn't get the permits. Tear it down and start over." I've seen it happen. Sometimes, movies are even harder to make than buildings.

I agree with you... if I hired a bunch of professional industry people... we'd be able to churn this movie right out and be done. But it's not going to happen. So I'm just looking for a few answers and a shove in the right direction. Anything you can offer to the end, I will appreciate.
There are always ways to get things done affordably, if you're inventive, lucky, and treat people well. I know of $100,000 features shot in LA that had a surprising number of pros working on it, because they cared, they had a few days free, and they worked out a reasonable deal with the producers.

Having said that, there is a dollar figure below which a movie can't be made. If you can do it all yourself and own the right equipment, cool. But be aware that audiences and distributors will judge your film and compare it to everything else they see -- and that includes $100 million blockbusters, $3 million indies, and $50,000 student films. You may start off thinking that, but if a $50,000 film requires $50,000' worth of fixes to repair all the problems, you'll be in trouble.

Michael Cioni has some great advice in his Reducation post seminars, and I think one of the best ones is: figure out your workflow and post before you shoot. Make tests. Make more tests. Ask around. Figure out the final destination for your film so you can work backwards and figure out how to get there. Don't reinvent the wheel -- people have done this before. Don't assume you already know the best way. Ask the experts. Figure out a reasonable budget for each step (editing, conform, VFX, temp mix, color-correction, final mix, titles, and deliverables). And remember, sometimes, hiring good people early on will save you money, especially in post.
 
Back
Top