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

ALPHA RELEASE: REDCINE-X and REDline (Build 260)

Brent Carter

REDUSER.NET
Joined
Aug 22, 2007
Messages
4,992
Reaction score
5
Points
0
Location
Irvine CA
Posting for your alpha testing pleasure...

REDCINE-X and REDline for OSX - Build 260:
http://red.cachefly.net/redcinex/REDCINE-X_build_260_mac32.zip
http://red.cachefly.net/redcinex/REDline_build_260_mac32.zip

REDCINE-X and REDline for Windows - Build 260:
http://red.cachefly.net/redcinex/REDCINE-X_build_260_win32.zip
http://red.cachefly.net/redcinex/REDline_build_260_win32.zip

Changes since last BETA release (Build 258):
* Export Timecode in/out point fix.
* Export speed improvement.
* DeBayer dialog now defaults to full instead of 1/16th when creating a new preset.
* 16bit BWF Audio support added.
* Alt clicking in the LGG window will now properly update the video window.
* A manual sync audio tool gui fix.
* Bin/browser columns are now numerically sorted for number columns.

Please see release notes and/or readme files for further details.

ALWAYS READ ALL INSTRUCTIONS CONTAINED IN THE DOWNLOADED INSTALLATION FILES BEFORE PROCEEDING.

WARNING: AS THESE ARE ALPHA BUILDS, THEY ARE RECOMMENDED FOR PREVIEW AND TESTING PURPOSES ONLY. THEY ARE NOT RECOMMENDED FOR USE ON COMMERCIAL PRODUCTIONS.

If you have any questions or feedback, please post in this thread. The software developers will be monitoring...

Thanks, BC
 
At first glance, it seems we're back to RocketCine transcoding speeds with the Red Rocket.

Here's a couple of quick test results.

Clip#1 : 00:50:09 (1207frames), B16, Red 1 Non-MX, 23.98, 4k 16:9
Going from an internal 1.5TB drive to an internal 2TB.

ProRes 422 - 00:54
ProRes 444 - 01:07
MXF 1080 175bit - 00:46
MXF 1080 36bit - 00:45
1080 DPX - 02:54


Clip #2 : 01:02:02 (1489frames) B30, MX Footage, 23.98, 4k 16:9
Going from an external G-Raid via eSata to internal 2TB

ProRes 422 - 01:09
ProRes 444 - 01:23
MXF 175bit - 00:53

Will keep testing tomorrow.

Thanks guys.
 
At first glance, it seems we're back to RocketCine transcoding speeds with the Red Rocket.

Amazing news!!! Thanks for sharing your test results. I'll be testing this build later today.
 
Hey,

I've been getting crashes with an older project file related to the browser window and scrubbing through clips on the viewer. I've send the crash reports and logs to redcinex _at_ red.com

Now testing if cropping still results in black frames when using the quicktime export.

EDIT: Quicktime export with cropping still results in black frames.
 
Last edited:
On a MacBook Pro I've got a bug where I moved the viewing monitor window to a second attached screen at the time, but when I opened it next time (without the second screen attached) I couldn't get the monitoring window back to the (now) single screen, even by resetting the window layout to defaults. Toggling fullscreen gives me the monitor window on the single screen but as soon as it's toggled off again, it disappears once more.

Fix suggestion would be to have the reset function put all windows back to the primary monitor to alleviate a non-attached monitor window saved layout.

Cheers,

Paul
 
Any know issues with the export presets? Having trouble exporting from bin. Will export clip in player (twice in a row). Ever seen this?
Thanks Scott
 
Brent,

Wanted to report a bug last night that we found with RedCine-X Build 258. Tried exporting MXF/AAF DNX HD 90X 720p 23.98.

All was well until we tried bringing in the ALE into media composer only to find it was marked with a header of 1080. We changed to 720 but could not relink our media. After much investigation we figured out that RedCine-X created 1080p DNX 90x media, not 720p as had been selected in the GUI. This might be something worth looking into. Seems like a bug to me.

-JD
 
Speed is way better so far, similar to rocketcine-x. I'll do some more tests as well.
 
Is it just me or does DPX rendering from 4K to 2K seem significantly slower than realtime (2:1)? Was this always the case? Working from a Windows machine with Rocket card.

And thanks again for fixing the Timecode issue! Can I request an added feature to have handles added to clips during the export phase? Reason I ask is I have an edl I imported into clipfinder then exported via .lua to redcinex to render. I guess I could just export the edl and re-import into fcp with the handles instead, but it would be nice for redcinex to have that option as well.
 
What is your storage setup? Rendering to 2K DPX should be pretty close to real-time if you have the storage bandwidth to handle it. Think sustained minimum 250MB/s writes needed to guaranty real-time and if you're trying to read the R3Ds of the same volume, that can really slow you down.
 
Back
Top