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 Workflow Manual v.1.2

Brandon Kraemer

Well-known member
Joined
Jul 15, 2008
Messages
701
Reaction score
0
Points
0
Age
53
Attached is a zipped PDF file of a work in progress manual I have written for RED Workflow. This version (1.2) deals specifically with Apple FCP based workflow, but future versions will be expanded to include Avid workflow as well. Feedback via this forum is welcomed, if I have missed something or if you have something to add, please let me know by replying to this thread. I developed this document for internal use for myself and my coworkers and I decided to adapt it and share it with the community at large. Corrections and further development of this document are planned for in future versions.

Why this document? Currently there is very little in the way of organized information when it comes to RED post production workflow. Most of the software is still in beta release and the documentation for the available software is widely scattered and somewhat thin on content. It was my intention to bridge this information gap until official documentation catches up with full release software. I hope you enjoy!

Brandon Kraemer
 
God save the order!

Thanks.
 
Cool Brandon. Only thing, you mention that 4K 2:1 is the standard setup and 16:9 should be used for 4K output. Now that a lot of the issues with 4K 16:9 have been worked out and I've been shooting in that format without issue, I think we will see people gravitate towards using the full power of the sensor, even for HD projects. There will still be times when 2:1 is appropriate for sure.

Also, when you discuss transcoding times, you may want to note that this is dependent on system specs, display settings, etc.

Keep it going, these workflow documents are great, especially for editors who are starting to see Red projects show up in their suites.
 
Great Idea!!

future versions will be expanded to include Avid workflow as well.

Brandon Kraemer

With reference to Avid: worktrickle or workdrip are more appropriate terms...:shifty:

I'd be happy to help with my Avid experiences if it would help?


M
 
wow, seriously thanks. very helpful to see how other people are doing it.
 
great doc. thanks.

i just print it out. hopefully this doc will be updated as the red development progresses.
 
Great Idea!!



With reference to Avid: worktrickle or workdrip are more appropriate terms...:shifty:

I'd be happy to help with my Avid experiences if it would help?


M

Absolutely. Any input on the Avid side is helpful. I haven't had the time yet to sit down and take a project through on one of our Avid's, and that is the best way I know how to write a chapter on that workflow, er... trickle.:turned:
 
Cool Brandon. Only thing, you mention that 4K 2:1 is the standard setup and 16:9 should be used for 4K output. Now that a lot of the issues with 4K 16:9 have been worked out and I've been shooting in that format without issue, I think we will see people gravitate towards using the full power of the sensor, even for HD projects. There will still be times when 2:1 is appropriate for sure.

Also, when you discuss transcoding times, you may want to note that this is dependent on system specs, display settings, etc.

Keep it going, these workflow documents are great, especially for editors who are starting to see Red projects show up in their suites.

Working mostly on the post end, I was only going by what I have seen the majority of footage come in at, 2:1. Good to hear that more and more work is being shot with the 16:9 setup!

Thanks for the input.:biggrin:
 
Attached is a zipped PDF file of a work in progress manual I have written for RED Workflow. This version (1.2) deals specifically with Apple FCP based workflow, but future versions will be expanded to include Avid workflow as well. Feedback via this forum is welcomed, if I have missed something or if you have something to add, please let me know by replying to this thread. I developed this document for internal use for myself and my coworkers and I decided to adapt it and share it with the community at large. Corrections and further development of this document are planned for in future versions.

Brandon Kraemer

L&T section is waaaaay out of date. It does work with build 16. Anything less
than 4K will ingest at native size (4K is 1/2 size due to the FCP limit.) Four
channel audio is supported. Ingest point has been corrected. Ingest speed (or
lack thereof is not due to L&T, rather it is due to the debayer process required
for full size high quality transfers. Any process that performs this step will have
speed issues.
 
L&T section is waaaaay out of date. It does work with build 16. Anything less
than 4K will ingest at native size (4K is 1/2 size due to the FCP limit.) Four
channel audio is supported. Ingest point has been corrected. Ingest speed (or
lack thereof is not due to L&T, rather it is due to the debayer process required
for full size high quality transfers. Any process that performs this step will have
speed issues.

Good to know, Ill incorporate this in the next version. I had just checked red.com/support a few days ago and L&T was still not supported past build 15 at that time (according to red.com).

From a speed standpoint, you either take a hit in the front end or after the fact. Which is better seems to depend on the amount of material your working with.
 
Good to know, Ill incorporate this in the next version. I had just checked red.com/support a few days ago and L&T was still not supported past build 15 at that time (according to red.com).

From a speed standpoint, you either take a hit in the front end or after the fact. Which is better seems to depend on the amount of material your working with.

re L&T: yup, v0.0.3 has been there since late July and supports b16

re speed: understood. Just wanted people to understand that the L&T has
nothing to do with speed as it doesn't actually touch the video or audio data.

Thanks a lot,

Craig
 
Hey, Craig...know how RED could 100% guarantee the information in the software manuals is correct?

I know you do... :-)

Kevin
 
Hey, Craig...know how RED could 100% guarantee the information in the software manuals is correct?

I know you do... :-)

Kevin

You mean, write a comprehensive manual themselves?
 
Back
Top