REDCINE-X Professional Build 35 Beta

[Kalulu Ngilo]

Build 35/36 crashes on OpenCL on Hackintosh. But not on CUDA.

 

[Erick von Schulz]

Red Cine-X is my favorite part of the Red workflow. Keep up the incredible work...

 

[Diane Monzon]

Hi Mike P.,

Thank you for the suggestion. I have made note of this for consideration in a future release.

Thanks,
Diane

 

[Alan Peterson]

I've started using 37.1, and it's been great for the most part. The periods of unresponsiveness that I was experiencing in versions 34-36 are gone. It does seem to have a bug where it generates enormous log files, though. I started getting warnings that my startup disk was running out of space, and after some digging, I found that RCX Pro had created a 57GB log file. I deleted it to restore sanity to my computer and I'm not sure how I could have sent it in anyway, so I guess this is just a heads up.

 

[Will Keir]

Are the advanced tools "License" Only now? Alchemy. Unsharp Mask?

 

[Michael Tiemann]

Are the advanced tools "License" Only now? Alchemy. Unsharp Mask?

There are too many RCX-Beta threads. The answer, given in the 38-Beta thread, is that this would be fixed and pushed out as an update this week. The fix has been made and the update pushed. If you fire up RCX-Beta-38 and ask for updates (or get them automatically), you will see that the full functionality has been restored. (Plus some new features.)

 

[Mike P.]

The release build has also been updated/re-licensed.

 

[Bob Gundu]

Hey Diane/Dave, now that you can choose to apply a LUT from within RCXp, would it be possible to give RCXp renders (specifically prores renders) an embedded flag that tells FCPX to use a LUT (specifically pointing to said LUTs location)?

I know that FCPX does this with other cameras that shoot Log files (specifically Arri and Blackmagic cameras... actually I think it does it with their raw & prores files.) So when you drag the file on the timeline, FCPX will automatically apply a default normalizing LUT of your choice (e.g. Rec709), whereas with R3Ds you still need to make an RMD, and even when you do, LUTs applied within RCXp don't carry over to other apps (when, technically speaking, there is nothing preventing it).

For that matter, I don't know why the audio file path doesn't carry over either?

 

[Mike P.]

For that matter, I don't know why the audio file path doesn't carry over either?

You mean for syncing sound within RCXp so when you import the .r3d/rmd in FCPX it's already linked to the dual system audio? That'd actually be pretty damn slick (especially if all the major NLEs took advantage -- basically be crossplatform syncing).

 

[Jason L]

Something that really needs to be added is DPI scaling for screens that run 4k. I can't even read the text unless I get really close to the screen. Or is there an adjustment?

 

[Will Keir]

Thanks guys.

This is a bug then? Wondering if one day, after I get used to using these tools professionally if they will require a license?

There are too many RCX-Beta threads. The answer, given in the 38-Beta thread, is that this would be fixed and pushed out as an update this week. The fix has been made and the update pushed. If you fire up RCX-Beta-38 and ask for updates (or get them automatically), you will see that the full functionality has been restored. (Plus some new features.)