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 :)

Let's stop referring to "reference files" as "proxies".

I Bloom

Well-known member
Joined
Jan 5, 2007
Messages
2,195
Reaction score
0
Points
0
Location
USA
Website
www.ianbloom.com
I spend a large amount of my day communicating with people about RED workflow. I find that the most confusion comes from the notion that Redcode quicktime reference files are proxies.

We currently user the word "proxy" to mean two very different things. I think it's better to be very specific and only use the word proxie to mean a self contained video file transcoded from the original, whose frames map to the original frames. Thus a stand-in or a proxy.

A quicktime reference file does not work unless the raw R3D file is present in the same directory. So it isn't much of a proxy really, it's more of a window into that file, a pathway that we call a reference.

This may seem like I'm nitpicking over small things, but I notice tons and tons of conversations where there is constant confusion about what we are talking about, especially between veterans and the uninitiated. It's too much energy being wasted for me.

So my suggestion, let's start saying "reference file" when we are talking about the redcode quicktime component files and reserve "proxy" for transcoded ones. Let's add some much needed precision to our evolving terminology.
 
Amen!!!!

I have to clear this up repeatedly as well. Isn't it Red who calls them, repeatedly, the 'proxies'? I think Ted, Rob, Stuart, etc need to sign on as well :-)
 
I just mentioned this a few hours ago? People don't realize that they are Reference files, and want to do silly things with them.
 
YES YES YES YES

lots of folks call offline edit transcodes (self contained QTs) as proxies.

I beg to differ. That does not mean that they are right. Literally, a proxy is a representative. Lim
 
Proxies is a broader term of which reference QTs and transcoded QTs can be subsets of 'proxies'

The flip side is that transcoded QT's can be final quality and not proxies at all. Likewise reference QTs be used for final quality output depending on the application and the output path (ie. through rendering).

I personally always 'try' to say transcoded QTs or proxies and ref QTs or proxies but it's easy to slip up. At the end of the day there is no simple answer because of all the different options.
 
i agree with ian. people also associate quality judgements with specific terminology and phraseology, so giving these files these newer deserved proper names helps clarify what they are and what they can do.

my 2sense
 
Look out,

I think jay is opening up the first RED PANCAKE HOUSE!

:)

David
 
Back
Top