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

CURRENT TOOLS CAPABLE OF PROCESSING EPIC FOOTAGE?

Chris Parker

REDuser Sponsor
Joined
Jan 30, 2007
Messages
1,932
Reaction score
0
Points
0
Wanted to start a thread where tools that are updated to work with EPIC footage can be announced or posted here. Can those that know post what software build of REDCine-X is currently being used to process EPIC footage? Can a Rocket be used to process EPIC footage? What are the main differences between processing EPIC and processing MX footage?

Are tools like Storm, DaVinci, Baselight, Clipfinder, etc. etc. capable of doing anything with EPIC footage? If not, this could be a good thread to post in when these updates do become available.

Thinking mainly getting it from .r3d into AVID or Final Cut for offline with a look applied. Any thoughts from those currently doing it are greatly appreciated.
 
I'm going to bet that around NAB time the new final cut pro will support 5k epic footage.

And the gamma issues will be resolved.


Great thread start chris!

David
 
I'm going to bet that around NAB time the new final cut pro will support 5k epic footage.

And the gamma issues will be resolved.


Great thread start chris!

David

That would be the day!:thumbup1:
 
Seriously.

There are tools for sure. It would be good if someone like Brook Willard got on this thread.

There has to be something in place as there are a lot of shoots happening with EPIC cameras.

I am going to guess that the current workflow involves a version of rcx and a beta version that works with red rocket.

Beyond this Im going to guess that an EPIC SDK will be released before the EPICs go out en mass, thereby making sure that post is ready for all of the EPIC footage that is about to be unleashed.

RED has it together. I really think they have learned from the R1 release. I expect they will exceed our expectations.

David.
 
Mark P. has been doing some alpha (beta?) testing with Assimilate Scratch for Epic footy. In the early days of the RedOne some of the usual suspects seemed in no hurry to provide native r3d support - I think times have changed since then :001_smile:.

What I am not clear on is the status of the SDK for 3rd parties as relates to Epic footage vs RedOne footage. AFAIK the basic file structure for r3ds is the same. Does the latest color science work for both RedOne and Epic files? If so, then developers have one less hurdle to clear. There are some new formats on Epic that the RedOne does not support, 5K scope/2:1/16:9 for starters - not sure if the SDK needs to offer hooks for those or if the developers can just add them... While I don't know all the details; levels of compression and how they are notated/flagged is being changed and that may require SDK/dev coordination to implement.

Cheers - #19
 
It appears that EPIC will be one of the most revolutionary cameras ever released... motion and still.

We are keen to release SDKs that give everyone access to EPIC technology. And we are encouraging as many 3rd parties as possible to embrace it.

That's all we can do.

Jim
 
It appears that EPIC will be one of the most revolutionary cameras ever released... motion and still.

We are keen to release SDKs that give everyone access to EPIC technology. And we are encouraging as many 3rd parties as possible to embrace it.

That's all we can do.

Jim

I agree, and I greatly appreciate it. Even though they may not be listening now, I don't think 3rd party support will be a problem once more people have Epic in hand.
 
Wanted to start a thread where tools that are updated to work with EPIC footage can be announced or posted here. Can those that know post what software build of REDCine-X is currently being used to process EPIC footage? Can a Rocket be used to process EPIC footage? What are the main differences between processing EPIC and processing MX footage?

Are tools like Storm, DaVinci, Baselight, Clipfinder, etc. etc. capable of doing anything with EPIC footage? If not, this could be a good thread to post in when these updates do become available.

Thinking mainly getting it from .r3d into AVID or Final Cut for offline with a look applied. Any thoughts from those currently doing it are greatly appreciated.

A number of the sw companies are already working with an Epic enabled sdk. We hope to approaching a full release of the Epic SDK as soon as the rocket driver is finalized..
 
A number of the sw companies are already working with an Epic enabled sdk. We hope to approaching a full release of the Epic SDK as soon as the rocket driver is finalized..

That sounds absolutely delicious. :cheers2:

Wondering if I need to pull the trigger on a second Rocket (FYI: running Win7-64Bit w/ Assimilate Scratch as soon as it's Epic support is live) to achieve real time playback from the larger Epic files??? If its still too early in the optimization phase on decoding the Epic data set to know the limits yet, no worries. But if metrics for the decoding rates of single and dual Rocket systems chewing Epic 5K footage is available knowledge, please share :bigear:

Cheers - #19
 
See.

RED is ready. RCX gets better every week. Post is a priority.

Hopefully all of the software companies will come along quickly as when the EPICs hit the streets they will be ready.

The great news is that we will always have RCX, now from RED, so the solutions exist right mow because you can go from that to anything.

David
 
This is great news and absolutely the last hurdle to make this camera the one and only camera to be used in any production above infomercials.
 
One can only be optimistic that with a new release there was increased emphasis on pro and more dialog with the QT team.
 
Yes, but this gamma issue has been going on for so long, and was already supposed to be fixed in Snow Leopard...
So I have a hard time being optimistic on that part... But I would absolutely love to be proven wrong !
 
One can only be optimistic that with a new release there was increased emphasis on pro and more dialog with the QT team.

If Apple is serious about making a "pro" tool that fits into the current world of post production, they will stop forcing every incoming format into FCP to be in a QT container. That's so 10 years ago...

ProRes is a nice codec and it has its place, we're now hearing murmurings of a ProRes RAW codec. All fine and great if Apple wants to keep ProRes within the QT domain. But When I have to take R3D or other formats and stick them into a QT instead of dropping them onto the timeline, that's a problem. It may not take that much time, but it takes time to re-copy. It takes time to fiddle with re-conforming between post tools now that all the other grading/finishing/compositing softwares support R3D and other formats directly.
 
Back
Top