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

Quicktime reference Movies for Web work

Adam Levins

Well-known member
Joined
Jan 19, 2007
Messages
703
Reaction score
0
Points
0
Website
www.levinspictures.com
When I get my RED I was thinking of selling my EX1 (would help to fund it).

My only concern is that I sometimes do work for the web and am not too keen on the huge files that the RED generates.

I was thinking that on these projects maybe I can just use the quicktime reference files and throw the other stuff in the trash?

Anyone tried this workflow for web projects?
 
reference files require r3d files

reference files require r3d files

sure you can trash your r3d files after you process and save your reference files as quicktimes or whatever but the reference files require the original r3d files for everything. that's why the reference or proxy files are so small, there's really nothing to them.
 
I was thinking that on these projects maybe I can just use the quicktime reference files and throw the other stuff in the trash?

Anyone tried this workflow for web projects?


The proxies simply point to the large raw file so you have to render before you can trash the R3D file. You could drop the small proxies into compressor and render them to QT and go from there.
 
Anyone tried this workflow for web projects?


I do not recall the project perse, but I can tell you that the best YouTube footage I have ever seen came from footage originated on a Red One!:w00t: Maybe someone else here in the forum can point us at the right direction (what is the video called) so you can see it and judge it by yourself.
 
sure you can trash your r3d files after you process and save your reference files as quicktimes or whatever but the reference files require the original r3d files for everything. that's why the reference or proxy files are so small, there's really nothing to them.

Of course... that makes sense. So there is no way of getting around the encoding time with the current work flo.
 
Of course... that makes sense. So there is no way of getting around the encoding time with the current work flo.

I suppose you could attempt to down res and record the live preview to DV and go from there.

Still probably a cleaner signal than most handi cams.
 
Still probably a cleaner signal than most handi cams.

Haven't tried that, but yesterday I did happen to shoot alongside a XL1 and the smallest RED proxy looked better than the XL1 all around. More resolution etc. And I was like "yeah, that's not color corrected or debayered. It's as bad a RED will ever look."

The guy with the Canon had to go change his underwear.

So the 720P out might work fine for web stuff. Something worth testing.
 
How fast do you need to turn the footage around???
The import into Final Cut from the proxies is not too bad. The files that Red generates is 2 gigs per minute. Not small, but in the day and age of $150 500-gig drives, it it really that bothersome?
My biggest problem is the RedCine program being very unstable, with a kludgy interface that I cannot wrap my brain around. But using the proxies in Final Cut for Web destined footage???
No problem. (IMO)
Cheers,
Harry
 
Back
Top