Newer REDCINE-X posted...

[Peter Moretti]

Correct. Use the latest releases (96 and 1735).

When using a Rocket card, is there a speed difference between using RocketCine-X versus RedCine-X, esp. as it relates to creating Avid MXF's?

Thanks very much.

 

[Jith Paul]

Hi there.

We have just wrapped principal photography on a feature here in Ottawa, Canada, and I'm starting to get a handle on the post process. Our intent is to come up with a workflow that we can employ effectively amongst multiple editors. I'm playing with build 104_PreRelease at the moment and I have a few questions.

I apologize if these have been already raised and answered elsewhere in the forums.

(1) Is there a way to import an exported sequence (XML) built from proxies in FCP into REDCINE-X?

(2) I notice the export palette (is that the right term?) supports Quicktime, DPX, TIFF and Avid MXF. Is there a way to export a timeline into R3D format? That would make it possible to get a full REDCODE representation of a sequence that is portable, to avoid carrying around all of the source REDCODE material, whether it's used in a specific sequence or not.

Thanks very much.

JP.

 

[Simon Blackledge]

(1) Is there a way to import an exported sequence (XML) built from proxies in FCP into REDCINE-X?

>>Nope.
>>(scripting should allow this but not currently)

(2) I notice the export palette (is that the right term?) supports Quicktime, DPX, TIFF and Avid MXF. Is there a way to export a timeline into R3D format? That would make it possible to get a full REDCODE representation of a sequence that is portable, to avoid carrying around all of the source REDCODE material, whether it's used in a specific sequence or not.

>>Nope. You can't edit the native R3D files. Nor transcode back to Redcode >>codec.

Si

Thanks very much.

JP.[/QUOTE]

 

[Luis Otero]

Hi there.

We have just wrapped principal photography on a feature here in Ottawa, Canada, and I'm starting to get a handle on the post process. Our intent is to come up with a workflow that we can employ effectively amongst multiple editors. I'm playing with build 104_PreRelease at the moment and I have a few questions.

I apologize if these have been already raised and answered elsewhere in the forums.

(1) Is there a way to import an exported sequence (XML) built from proxies in FCP into REDCINE-X?

(2) I notice the export palette (is that the right term?) supports Quicktime, DPX, TIFF and Avid MXF. Is there a way to export a timeline into R3D format? That would make it possible to get a full REDCODE representation of a sequence that is portable, to avoid carrying around all of the source REDCODE material, whether it's used in a specific sequence or not.

Thanks very much.

JP.

Hey Jith,

I have asked the XML question directly to Deanan about three times, and even though on the previous software version thread he said is is working on it, he has not responded at all to this inquiry. Maybe you will have a better luck than me. :sarcasm:

I am exactly on the same boat: I need to start a CC of a feature starting next week, and having XML will allow me to do it 100% using Redcine-X.

Nothing but high respect for Deanan and his great work, but a courtesy update on this can help us to re-calibrate the expectations and the working plans. :angelsad2:

Regards,

 

[Jannard]

Hey Jith,

I have asked the XML question directly to Deanan about three times, and even though on the previous software version thread he said is is working on it, he has not responded at all to this inquiry. Maybe you will have a better luck than me. :sarcasm:

I am exactly on the same boat: I need to start a CC of a feature starting next week, and having XML will allow me to do it 100% using Redcine-X.

Nothing but high respect for Deanan and his great work, but a courtesy update on this can help us to re-calibrate the expectations and the working plans. :angelsad2:

Regards,

Deanan has commented on this several times since we announced what it is on RED Day.

Jim

 

[Sid Idris]

Hey Jith,

I have asked the XML question directly to Deanan about three times, and even though on the previous software version thread he said is is working on it, he has not responded at all to this inquiry. Maybe you will have a better luck than me. :sarcasm:

I am exactly on the same boat: I need to start a CC of a feature starting next week, and having XML will allow me to do it 100% using Redcine-X.

Nothing but high respect for Deanan and his great work, but a courtesy update on this can help us to re-calibrate the expectations and the working plans. :angelsad2:

Regards,

I always got the impression that RedCineX was destined for 3rd party plugins that would include things like edl support.

 

[Luis Otero]

I always got the impression that RedCineX was destined for 3rd party plugins that would include things like edl support.

Jim,

The expectation was clearly placed there by Deanan, by directly answering: "Working on the importing functionality for an upcoming build now " on the posting #18 of the following thread: http://reduser.net/forum/showthread.php?t=40855).

So, since then, many people, including me, are very anxious about the progress of his effort on this specific capability due to the great help this could be if implemented as stated.

Regards,

 

[Paul Lee]

Guys, REDCINE-X is awesome but keep in mind it does NOT have secondaries or many of the other features in a true color grading system. I understood some of that capability regarding XML from FCP could be useful for interchange between Post and the DP/Director on set, looking at assemblies and selects and so forth. If you are about to CC a feature film, why in heavens wouldn't you use Color or Scratch or even AE or Pablo? They all have the ability to read R3D's and have much more sophisticated tools.

Perhaps I am missing something?

 

[Luis Otero]

Guys, REDCINE-X is awesome but keep in mind it does NOT have secondaries or many of the other features in a true color grading system. I understood some of that capability regarding XML from FCP could be useful for interchange between Post and the DP/Director on set, looking at assemblies and selects and so forth. If you are about to CC a feature film, why in heavens wouldn't you use Color or Scratch or even AE or Pablo? They all have the ability to read R3D's and have much more sophisticated tools.

Perhaps I am missing something?

Paul,

The answer is simple: there are people on this community that simply do not have the resources, including the ones available from the project being shot, to use one of the great software you mentioned.

Not everyone has the money to do it, but still needs to use tools it in order to have the film out of the door and be shown to an audience. IMHO, that is the reason why we make movies; it is not just a self-gratifying experience, but you want to share it with others, and BTW, make money.

Respectfully,

 

[Paul Lee]

How did you cut the movie? I assume FCP? Color is free in a box of Final Cut, right? It's a very powerful tool. I don't want to admit what we paid for it back when it was Final Touch! It is great software and very accessible to the masses now, like RED and their tools. That's way cool- totally get you on financial limitations and the need for profitability. That's exactly why we're here as well!

 

[Luis Otero]

Sorry to disagree on this, Paul, but Color is not as powerful as Redcine-X for many CC instances at all, specially since it directly work on my ultra-flexible RAW R3D.... Just to mention FLUT™™.

I need to admit that I am in love with it, as well as I need to admit that it has limitations (secondary, etc), but Color lacks support of the new color magic, which is what many of us are so gratefull for re: Redcine-X.

Again, different markets...

 

[Deanan]

Jim,

The expectation was clearly placed there by Deanan, by directly answering: "Working on the importing functionality for an upcoming build now " on the posting #18 of the following thread: http://reduser.net/forum/showthread.php?t=40855).

So, since then, many people, including me, are very anxious about the progress of his effort on this specific capability due to the great help this could be if implemented as stated.

Regards,

Hi Luis,

The scripting/import functionality was shown at the last red day and there was a discussion on Lua in another thread.

Rather than providing a limited interface through XML, we've implemented a much more powerful scripting interface. This means that third parties like Monkey Extract can implement an import mechanism for a variety of editors.

As it evolves it also means that other apps can then communicate directly with REDcineX.

The next build we put out will have this functionality in it.

 

[Paul Lee]

Not sure what that has to do with different markets? Both 'cheap,' both desktop on commodity hardware and operating systems. Different tools for sure- Color's got XML, secondaries, software FXs and geometry (also handles non-R3D material). REDCINE-X looks to be the dawn of a badass tool specific to RED workflow. I see them working TOGETHER as a good marriage right now. Heck they even coexist on the same box and use the same control surface. NICE. Exciting times for sure!

 

[Jason Ing]

Not sure what that has to do with different markets? Both 'cheap,' both desktop on commodity hardware and operating systems. Different tools for sure- Color's got XML, secondaries, software FXs and geometry (also handles non-R3D material). REDCINE-X looks to be the dawn of a badass tool specific to RED workflow. I see them working TOGETHER as a good marriage right now. Heck they even coexist on the same box and use the same control surface. NICE. Exciting times for sure!

hey... if redcine had secondaries... and we already know that graeme has done fx for color... hmmm... :smiley:

 

[Rudi Herbert]

Problems installing Redcine X

Problems installing Redcine X

Guys,

I'm having problems installing Redcine X on a second computer, it's running fine on another one?! I uninstalled the previous version but this one does not seem to come with an installer at all, so all I can do is run it directly from the container folder but not b itself. Any suggestions?

 

[Paul Lee]

hey... if redcine had secondaries... and we already know that graeme has done fx for color... hmmm... :smiley:

Heck yah. We're rockin Nattress filters all over the place already. That was actually one reason we got so geeked on RED. "They have that Nattress guy work for them? Oh, this is gonna be big!"

 

[Luis Otero]

Hi Luis,

The scripting/import functionality was shown at the last red day and there was a discussion on Lua in another thread.

Rather than providing a limited interface through XML, we've implemented a much more powerful scripting interface. This means that third parties like Monkey Extract can implement an import mechanism for a variety of editors.

As it evolves it also means that other apps can then communicate directly with REDcineX.

The next build we put out will have this functionality in it.

Deanan,

Thanks for the update! Sorry that I missed my spot for Red Day, but family calls first... As for the no-direct support for XLM in/out, I am OK with it. Sure, more money to the programmers from our pocket, but heck, Redcine-X is for free!

Can you point me to the other thread that this is discussed. I am sure it is very informative and educational.

Again, thanks for the update!

Regards,

 

[Luis Otero]

Not sure what that has to do with different markets?...

Paul,

My comment re: different markets, is referring to a fact: some productions can have the resources for use of Scratch, the others are exited just to use Colors. I am working more with the second group, so by asking about XML is to be prepared to supply the best I can to the low-budget clients.

Hope this clarifies my comment, and sorry if I was not that clear enough. :seeya:

Cheers,

 

[Eric Haase]

Guys, REDCINE-X is awesome but keep in mind it does NOT have secondaries or many of the other features in a true color grading system. I understood some of that capability regarding XML from FCP could be useful for interchange between Post and the DP/Director on set, looking at assemblies and selects and so forth. If you are about to CC a feature film, why in heavens wouldn't you use Color or Scratch or even AE or Pablo? They all have the ability to read R3D's and have much more sophisticated tools.

Perhaps I am missing something?

Agreed. I need secondaries for a final grade. But Apple's Color looks at the original R3D file when keying secondaries and NOT the image after the RED tab or primary grade. If you've shot uncorrected in tungsten light, it is very difficult to key secondaries (especially skin tones) from R3D files. So it becomes necessary to use some RED tools to make an intermediate like a flat DPX sequence with baked in white balance. No curve, contrast, or anything- just a basic white balance/tint. That way Color can pull a clean secondary. So, I guess some people who have found this might look forward to being able to make these easily with REDCINEX if it has XML support.

 

[Paul Lee]

Paul,

My comment re: different markets, is referring to a fact: some productions can have the resources for use of Scratch, the others are exited just to use Colors. I am working more with the second group, so by asking about XML is to be prepared to supply the best I can to the low-budget clients.

Hope this clarifies my comment, and sorry if I was not that clear enough. :seeya:

Cheers,

Hey there- we are part of your second group and we use Color, and have foregone other solutions for budgetary reasons, exactly as you say. No market for Lustre, Pablo, etc., in our neck of the woods! Scratch looks cool ,but we can't justify it. That, and Color is a very powerful program. RED just updated their 'tab' again a few days ago and while there is no FLUT™™ yet, it's really quite cool. Again, Color is free in a box of FCP and the RED tab is free. XML stuff all works right now. Tight integration with FCP for proxy or prores off-line, R3D online in RED. Pretty cool right now, is what I'm saying!