Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

REDCINE PRO X 15 release / 16 Beta

Jarred Land

Jarred Land

Fire Chief
Staff member
Joined
Dec 27, 2006
Messages
10,644
Reaction score
33
Points
10
Now live at Red.com

REDCINE-X PRO BUILD 15

CHANGES SINCE LAST BETA RELEASE
  • Added: Ability to specify dynamic sub folder creation based on metadata for exports.
  • Added: Audio compression options have been added to the QuickTime exporter.
  • Added: The two QuickTime exporters have been merged into one.
  • Added: Separate 3D row interleave in viewer/export into left first/right first variants.
  • Added: ACES chromaticities metadata when doing ACES EXR exports.
  • Added: Preferred audio auto match directory.
  • Added: Record frame rate to the list of available burn in metadata.
  • Added: Context menu clear external audio option. Works on a selection of clips.
  • Added: Missing Epic resolutions from export/framing tools and browser clip descriptions.
  • Added: Tangent Element support. Requires Element-Mf + Element-Kb at minimum.
  • Added: Quick QT Wrapper generation from the bin, browser tree, and menu.
  • Added: Ability to specify which screen to use for a second monitor.
  • Fixed: Confirmation is now required before an export, look, or framing preset can be deleted.
  • Fixed: Issue where unscaled exports with posteffects and use restricted SMPTE range turned on would not be clamped to the SMPTE range.
  • Fixed: FCP7 XML timecode incorrect when exporting with handles in some cases.
  • Fixed: Scrub bar rendering issue on Windows.
  • Fixed: Issue with certain invalid fit width .5x crops on Rocket. Software scale fallback.
  • Fixed: Issue where fit width .5x setting would not be restored correctly in the crop tool.
  • Fixed: Issue where abstract type ICC profiles were selectable for TIFF exports.
  • Fixed: Issues with importing and exporting FCP-X XML files containing clips of mixed framerates.
  • Fixed: Issue where exports via REDline in RCX would come out incomplete.
  • Fixed: Better handling of slugs when importing EDL’s.
  • Fixed: Issue where clips in the browser would retain their state until the directory was changed.
  • Fixed: Improved memory efficiency when added large numbers of clips to the render queue.
  • Fixed: Issue with loading project files that have unicode characters within them.
  • Fixed: Play state is correctly restored when switching between fullscreen modes.
  • Fixed: Issue where it would automatically scale to framing guide dimensions in REDline.
  • Fixed: Issue where certain BWF formats would cause static noise only when playing clips.
REDCINE-X PRO BUILD 16 BETA - Only Mac build as the only change is RETINA support and full screen support.

CHANGES SINCE LAST BETA RELEASE
  • Added: Retina display support.
  • Added: Lion Full Screen support.

RCX 16 (Beta): https://www.red.com/downloads/4f56854e6261f95a570006af


RCX 15 (Release): https://www.red.com/downloads/4fad7fd417ef027cd8000eb1
 
I'll put in a formal bug report but came across an interesting one (unrelated to this beta); apparently RCX crashes when you open a file located on a drive mounted read-only... I'll work on repro but this occurred under Windows 7, opening a file located on an OSX journaled volume mounted read-only under Windows.

This isn't *intended* to fail, is it? I mean a reasonable workflow might well have source files mounted read-only (for safety), with r/w on the scratch disk, and the output file device...

Mike
 
Can u add EXR files that will look exactly the same as tiffs & other formats. The existing exr files are for a workflow that I'm not familiar with.
 
Mike 'Fireman' Ross said:
I'll put in a formal bug report but came across an interesting one (unrelated to this beta); apparently RCX crashes when you open a file located on a drive mounted read-only... I'll work on repro but this occurred under Windows 7, opening a file located on an OSX journaled volume mounted read-only under Windows.

This isn't *intended* to fail, is it? I mean a reasonable workflow might well have source files mounted read-only (for safety), with r/w on the scratch disk, and the output file device...

Mike
Click to expand...

Mike,

It's definitely not intended to fail like that. If you could, please enable verbose logging, and recreate the crash and send the logs in to redcinex at red dot com and we'll get the issue sorted out. Also remember to disable verbose logging again once you're done.

Thanks
 
Ramesh Jai said:
I have the full Tangent Element panel. RCX 15 is not working with Element. Or am I missing something? Thanks
Click to expand...

You have to enable external UI devices in the preferences first, then restart RCX. You'll also need to have the Tangent HUB software package installed.
 
Thanks for the Element and Retina support! Gotta try it when I get home.

I don't see it listed, so I'd like to request the ability to not show the Rocket on a x4 slot warning every time RCXP starts. When running the Rocket through Thunderbolt, as many are now, we're well aware of the x4 lane limitation of our Rockets through Thunderbolt.
 
Thanks Mike,

Yeah we are aware of that annoyance :) It just didn't make it into this build. On the next it should be optional.

David
 
Bug?

Bug?

I am running Lion on a Mac Pro with two 20" Apple Cinema Displays. I can no longer get the video to show up full screen on the second monitor. Have tried both v.15 and beta 16. :-(
 
Mike Halper said:
Thanks for the Element and Retina support! Gotta try it when I get home.

I don't see it listed, so I'd like to request the ability to not show the Rocket on a x4 slot warning every time RCXP starts. When running the Rocket through Thunderbolt, as many are now, we're well aware of the x4 lane limitation of our Rockets through Thunderbolt.
Click to expand...

Yeah the warning sucks and will be nuked, but to respond to the later part of your message, surprisingly alot of people don't know the limitation... Thunderbolt was being marketed as faster than anything you would ever need so its an understandable mistake. Next version of thunderbolt will be alot faster.. and then things really start to get interesting :)
 
You must log in or register to reply here.
Back
Top