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

New REDCINE-X...

Status
Not open for further replies.
Anyone having issues with HD-SDI out. I'm getting a green output only with nothing playing out. Also, the player will not update once I toggle the monitor out button off.

Dave

What setting and output format do you have it set to?
 
Tried all of the YUV422 flavors and different frame rates. The CRT shows sync, however, its just pure green. No refresh on the player window without restarting Redcine-X.
 
What Mac OS was this tested and qualified on? 10.6.4?

Looking forward to diving into this one.
 
Will these features (and things like RedFilm) be integrated into Redline in the near future? And more importantly, into the SDK?

Yes to both.

It's actually in REDline now but not listed in the help yet.
 
Tried all of the YUV422 flavors and different frame rates. The CRT shows sync, however, its just pure green. No refresh on the player window without restarting Redcine-X.

Can you email the logs to redcinex at red.com?
262 works ok?
 
Updated all the drivers but still the win64 version does not run on Windows 7
 
Maybe I'm just being thick but I can't seem to export a QT Wrapper.
Is that feature not working or am I doing something wrong?
It brings up the "choose output folder" (on everything but "timeline all clips"), but nothing happens when I click the "choose" button.

I'm using the 64bit version on Snow Leopard.
I'm a bit new to RedCine-X so I'm not sure if this has been covered with previous versions.

EDIT: - Never mind, checked the log file which says "QT wrappers were not enabled, can't export."
 
Coming along nicely.

Request: when outputting trimmed R3D files from the bin or timeline, save the current grade into the metadata of the trimmed clip, rather than the grade metadata of the original clip. This would allow the following (extremely useful) workflow:

1) Bring EDL into RCX.
2) Grade shot by shot in the timeline.
3) Export shots as trimmed R3D files.
4) Bring trimmed shots into Color, Resolve, etc. with shot looks intact.
5) Conform trimmed shots from EDL.

In other words, you could dial in Red-specific look settings in RC-X, in an interface optimized for working with those parameters, and then have those look settings follow you into your "real" grading environment.

Also... RC-X really needs to traverse entire directory hierarchies when importing clips via the "Import Folder" or EDL importing commands. In real-world workflows, clips are often nested many levels deep, broken out into folders by shooting day, camera, media type, mag, etc. There has been more than one occasion where we've missed a reel of dailies because RC-X's lack of directory traversal requires each mag to be imported separately if the RDM folders are each nested within a containing folder. Which they usually are, because that's how footage management utilities generally organize things.
 
Very nice

Based on Jim's post, methinks Tattoo is just about finished wrapping up...


Now where is my Bomb EVF, SSD Module, etc. etc. etc. LOL!
 
before all.. well done and thanks for this great app..


Coming along nicely.

Request: when outputting trimmed R3D files from the bin or timeline, save the current grade into the metadata of the trimmed clip, rather than the grade metadata of the original clip. This would allow the following (extremely useful) workflow:

1) Bring EDL into RCX.
2) Grade shot by shot in the timeline.
3) Export shots as trimmed R3D files.
4) Bring trimmed shots into Color, Resolve, etc. with shot looks intact.
5) Conform trimmed shots from EDL.

In order words, you could dial in Red-specific look settings in RC-X, in an interface optimized for working with those parameters, and then have those look settings follow you into your "real" grading environment.

Also... RC-X really needs to traverse entire directory hierarchies when importing clips via the "Import Folder" or EDL importing commands. In real-world workflows, clips are often nested many levels deep, broken out into folders by shooting day, camera, media type, mag, etc. There has been more than one occasion where we've missed a reel of dailies because RC-X's lack of directory traversal requires each mag to be imported separately if the RDM folders are each nested within a containing folder. Which they usually are, because that's how footage management utilities generally organize things.


I second this..

we need to have an edl out with the trimmed R3Ds plus their corresponding RMD grades..
one more thing if possible to have the timeline assembled out of the edl file on import not just having them on the bin..
 
Is there a way for existing side by side single stream 3D R3Ds (for example mirror-box) to be used with the enticing new 3D tools in this build?
 
RDM and rewriting are coming later. Traversing and other refinements also.

Good to hear, especially about the rewriting, since embedded look metadata is still supported by more apps than RMD files.

Wow, between Resolve announcing support for Rocket, The Foundry announcing STORM, and all the new goodies in RC-X 320, the last few weeks have been really exciting on the Red workflow front.
 
Status
Not open for further replies.
Back
Top