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

REDCINE-X Build 340...

I don't know if this has ever been requested, but could you super dudes at RED render an R3D out of some SMPTE test and color chip charts that we could use as a baseline in Red cineX to pipe out to a monitor and through the REDRocket? This would help in judging a bunch of different (and subjective) things that seem to be constantly popping up (render quality in pro res for one, color pipeline calibration, working without an external monitor on someone else's machine where you are not used to the monitor - and getting unpredictable results). I'd even pay for the tools - the thing is - we CAN'T make them, only you guys can... otherwise, I wouldn't even mention it!
 
Last edited:
Framing controls

Framing controls

I'm fairly new to this, but I recently used build 326 (Mac64) to export an offline of a feature film.

Just tried to export a few more clips using build 340 (Mac64), and the framing preset controls didn't work at all. Had to go back to the earlier version (thank you, Red for not locking us into an installer that overwrites old versions).

Anybody else encounter this? Perhaps I'm missing an easy fix.

Thanks!

Don Downie
SmallMediaXL.com
 
When ejecting a drive from RedCineX fails, because a clip is in the player, the lower half of the browser window display format changes and becomes almost unreadable..
Thanks, Joe. This will be fixed in the next version.
 
redexport quit unexpectedly! error every time?

redexport quit unexpectedly! error every time?

The good news is that the export continues...??

I've finally dumped rocketcine as my of-line rushes creating tool.

So using this latest redcinex (with Rocket) I am exporting to MXF (dnx36) for a ofline. The problem is that no matter what I do I very quickly get the OS warning 'redexport quit unexpectedly...'

The few mxf's at the beginning of the export seem alright. Can I trust this? Or shall I downgrade the Rocket drivers and go back to the trusty Rocketcine?

thanks for any lucid thoughts!

Michael L
 
I am in the same wagon going into a 4 x 45 minutes conform for uncompressed online.

1. RC-X
2. Clipfinder
3. Rocketcine-x + clipfinder

I want redlogFilm... -:)
I want good re-conforms after render
I want not crashes...

Also planning for two series that go into production shortly.
Same dilemma.

Clipfinder is my bet at the moment...
But very open for suggestions

(BTW, I have been very happy with RC-X 321, but fast turnarounds and larger Batch jobs, Clipfinder offers so much simplicity. and rational screenspace use...)

Clipfinders workflowtools seems superior to anything at the moment. + it works...
 
The good news is that the export continues...??

I've finally dumped rocketcine as my of-line rushes creating tool.

So using this latest redcinex (with Rocket) I am exporting to MXF (dnx36) for a ofline. The problem is that no matter what I do I very quickly get the OS warning 'redexport quit unexpectedly...'

The few mxf's at the beginning of the export seem alright. Can I trust this? Or shall I downgrade the Rocket drivers and go back to the trusty Rocketcine?

thanks for any lucid thoughts!

Michael L


I keep having problems with trying to open a saved project.
I save it, then when i go to open it, RCX opens, then crashes--every time.
Thanks....

Can I get both of you to send log files from these issues to redcinex at red dot com.

Thanks
 
I keep having problems with trying to open a saved project.
I save it, then when i go to open it, RCX opens, then crashes--every time.
Please send a report to redcinex at red dot com. Go to the Help menu, then select "Save Report..." If you can, also send the project file in question as that would be useful for diagnostic purposes.
 
problem with trim R3D on footage with pre-record

problem with trim R3D on footage with pre-record

Just did a trim R3D operation on a bunch of 2K 120 fps footage, some of it with a 10 second pre-record turned on. Everything worked fine on the non-pre-record footage and the pre-record footage was also trimmed properly, however all of those clips ended up being named Pre_01. Shot folders and RMD files were named correctly.
 
EDL FCP

EDL FCP

The EDL from FCP to REDCINEX works fine. After I color correct in REDCINEX how can I go back to the FCP project with the corrected files?
Thanks
Panos
 
The EDL from FCP to REDCINEX works fine. After I color correct in REDCINEX how can I go back to the FCP project with the corrected files?
Thanks
Panos
Hi Panos,
You could export the files as qt prores 4444 (or another format), place them in the same folder of your uncorrected footage ( keep the names) and reconect the files in FCP.
Hope this helps.

Cheers
Thomas.
 
You could export the files as qt prores 4444 (or another format), place them in the same folder of your uncorrected footage ( keep the names) and reconect the files in FCP.

FCP expects files with the same names, start time-codes and durations for re-linking. You could make this work for a short edit with some manual intervention, but it's not really practical for something of any length. It would not work at all if your edit used multiple sub-clips from one original R3D.

FCP does not really do file based conforms, so you need to use an external tool like Clipfinder to modify an FCP XML to point to graded files.
 
Trim is working fine except for a couple of pre-build16 clips which gave errors (first time I've tried on an old clip from 2008). Is this due to an earlier R3D sub-structure that hasn't been accounted for?

Windows 7 x64 build 340.

Cheers,

Paul
 
Fcp edl redcinex fcp

Fcp edl redcinex fcp

Thanks guys, I will try clipfinder.
 
Trim is working fine except for a couple of pre-build16 clips which gave errors (first time I've tried on an old clip from 2008). Is this due to an earlier R3D sub-structure that hasn't been accounted for?

Windows 7 x64 build 340.

Cheers,

Paul

Hi Paul,

Only Red One firmware build 16 and up is currently supported for Trim.

David
 
OK.....Dumb, but i just noticed this.
When running REDROCKET and RCX build 340....if i click on the ROCKET i get the Rocket setup....was unaware of this. So...it looks like the video output setup is set DEFAULT to RGB 8. Is this ALWAYS the case? and should i be changing this for EACH project to be sure i'm getting 12 bit out monitoring? I just caught this today. I thought output was ALWAYS 12bit via HD-SDI....did not realize we had to go in and manually set this up.

My case, i output HD-SDI to an AJA Hi5 and then output via HDMI to my Dreamcolor monitor. I expect to get 10bit, but looks like i have been monitoring in 8bit now for the past two weeks.

Can i get some clarification on this from RED porfavor?

....That said, is it then best to OUTPUT YUV 444 12bit or RGB 12bit. As i understand (my monitor) with the Dreamcolor it only accepts RGB in....so should i just sent RGB out or YUV ? Thanks......
 
The Dreamcolor needs RGB progressive to function properly, and your chain only supports 10 bit, not 12.
 
RedCineX and Wacom Intuos

RedCineX and Wacom Intuos

RedCineX 340 does not like the Wacom Intuos adjusting the Lift Gamma Gain color wheels. One little nudge sends it off maxing out into Matrix opening shot territory.

Happens on both monitors (I say that because I have software (Waves Audio ProTools plugins) that behave like this only if the GUI is open on the second monitor).

All the best,

Jochen
PS: Where can I get the Rocket driver 1.3.3.0? Would *love* to use my new Rocket card in RCX!
 
Back
Top