- Admin
- #61
- Joined
- Dec 27, 2006
- Messages
- 10,644
- Reaction score
- 33
- Points
- 10
May 30th 
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Jeff, you are correct to a certain degree, but it doesn't matter because that's not the reality that most of us are facing. Even in my own workflows I use offline/online approach. It just makes the editing experience with a client in the room much better, especially with a sequence that has twelve tracks, all with effects on them. Also, certain NLEs are just better when exchanging media, keeping proper metadata, etc. And you can't underestimate the years of experience editors have with a toolset. Having them switch over due to a codec is not an easy sell. We can still have R3D glory and proxies. There's no shame in it. Experienced editors have worked this way for decades. Now, if Avid steps it up and builds in awesome GPU support, then you may see the tides change a bit. FCP 7 is what it is. Nothing new going to happen with those workflows.
...But If you really want a compact and cheap recordingmodule, get a Blackmagic Shuttle2.
Guys, "editoral" and "proxy file" aren't synonomous with "finishing" and "master file."
If there are people here, who because they can edit their own projects natively, believe that movies like "The Social Network" and "The Amazing Spiderman" were/should/could be edited using .R3D's, sobeit.
I am not too sure why so much anger is being directed at RED, as if somehow they personally are out to get you. While it would be great to have some sort of module for recording proxy files, I would rather red spend what little resources they have on creating a better sensor instead of tackling an already oversaturated market. I own an Atomos Samuari and it records identical clip names as the red and triggers when the red is triggered. It is simple to use and provides instant proxys for offline editing which can then be easily resync'd to the R3D files because they have the same name. At least for my workflow this works great. There is no such thing as a perfect camera and there never will be. What we do have, however, is an amazing camera that produces fantastic footage and thats what Red needs to continue to focus on. Again this is just my opinion. Cheers
In 2008, I picked the right camera to invest in for sure. Back then there was really no other options for the price - super 35mm sensor and raw recording. The camera was groundbreaking without a doubt. My concern is my investment for the next 4, or lets say 2 years. This discussion is not really about the use of r3d, it's awesome, I get it, I've used it and promoted it from day one of owning my red one.tbh if you invest in Red you're investing in R3D. If you're no onboard for R3D then you probaly picked the wrong camera to invest in. For the times when you might want to push a square peg into a round hole and deliver a 1080p prores or dnxhd file then there are a plethora of options.
In 2008, I picked the right camera to invest in for sure. Back then there was really no other options for the price - super 35mm sensor and raw recording. The camera was groundbreaking without a doubt. My concern is my investment for the next 4, or lets say 2 years. This discussion is not really about the use of r3d, it's awesome, I get it, I've used it and promoted it from day one of owning my red one.
There may be a plethora of options of options (well, a few options anyway) but wouldn't it be nice to just attach a prores module and generate PROXY files for editing or prores files for quick turnaround projects on the camera system that I have invested in and championed for the last 4 years?
Mark Toia is a huge epic fan and yet he was the one the asked for this several years ago. Back in 2010, Jim announced a proxy module http://www.reduser.net/forum/showthread.php?43613-Proxy-Module which shows that red also recognized a need for it.
Once more: nobody is attacking red or your choice of camera, we are having a discussion.
RED is caught between a rock and a bigger rock on this one. If they give in and deliver ProRes/ DNxHD proxy recording, then that means they have caved in to the masses and the whole "good enough" approach. People will do what they do when shooting Alexa. 99% of everything shot on Alexa will be acquired, posted and delivered at 1080p/2K baked RGB. That is what they DON'T WANT. Native R3D support is becoming quite good in most NLE and post software now and the more people embrace it, the greater and more widespread that support will become. RED is about shooting high resolution and RAW. Proxies are an enabler drug for those addicted to the past, IMO.
I haven't needed proxies in any of my work for some time now. I don't own a proxy module and don't dick around with transcodes. The tools are there, people just have to be willing to explore them and learn new ways to use this stuff. 95% of the time, transcoding to ProRes for proxies, dailies, etc.. is a waste of time. And yes, that is my official stance on that. The sad and unfortunate reality is that, even though it's a waste of time, most in the post industry don't understand this and they still want to shoehorn the R3D RAW workflow into their tired old methods from 2005. It's not about making it easy or keeping it simple, this is about complacency within the industry. Proxy workflows are a pain in the ass. It's so much easier and less problematic to just go DTE with the R3D files and stay RAW all the way through the pipeline until you final render. If your workflows and tools don't allow for that, maybe it's time to evaluate new workflows and tools instead of trying to perpetuate the past.
Anyway, I feel like I'm preaching to the choir and I'm about to get stoned, so I'll step down from my soapbox.