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-X Build 183...

Jamie Havill said:
Still getting the black frame issue using this latest build. Tried exporting to all flavours of DNxHD and DPX/TIFF. First few frames render as normal, but then get sporadic black frames. Windows version.
Click to expand...

Can you send us logs with verbose turned on?
What os are you on?
 
yes having real options are very useful in the professional arena.
Maybe RED should have a LITE version for users who don't need real control of there footage?

On a separate note... Transcoding to ProRes taking footage that was shot in 25fps and outputting to 23.98fps doesn't work. So you can't do frame rate conversions on transcoding with RCX.
 
Hey Deanan-
The problem we saw with burn-in not happening in timelapse footage seems to have been resolved in this new build. Man, you guys are busy!
 
Deanan,

Something wrong on the timeline, is difficult to explain but I'll try:

When I reach a time of about 8 or 9 minutes of footage in the timeline, I cannot continue scrolling. The same happens when I change the size of the thumbnails of the clips in there (I mean when moving the slider tool, between the slice and slug).
 
BradWright said:
The problem is that I can't get anywhere near enough saturation with Red Cine X. The green screen is severely washed out with all the settings that I've tried. Apple's Color is the only way I can get the color at a good level of saturation.
Click to expand...

When we've tested with controlled green-screen shots under tungsten lighting, we see an improvement in colorimetry in RC-X with the new CS, compared to the old CS in Color. Green saturation is very similar in both, but with improved red/blue balance in the new CS. However, when comparing between apps with old / new CS it's vital to be able to achieve a correct white balance.

In the old CS, kelvin temperature was pretty close to what you'd measure with, say, a Sekonic C500, but once we started to compare with much more accurate spectroradiometers, we found that 3200k was being reported as 2800k in the old CS. New CS gets colour temperature very much more accurate, and getting the right colour temp on white balance is a very important part of driving the CS code behind the scenes if accurate colorimetry is desired.

Graeme
 
Adrian Hernandez said:
Deanan,

Something wrong on the timeline, is difficult to explain but I'll try:

When I reach a time of about 8 or 9 minutes of footage in the timeline, I cannot continue scrolling. The same happens when I change the size of the thumbnails of the clips in there (I mean when moving the slider tool, between the slice and slug).
Click to expand...

Windows or mac?
 
roryhinds said:
On a separate note... Transcoding to ProRes taking footage that was shot in 25fps and outputting to 23.98fps doesn't work. So you can't do frame rate conversions on transcoding with RCX.
Click to expand...

But you can transcode to 25fps, then change the time-base to 23.98 with Cinema Tools.
 
Jamie Havill said:
I certainly can. I'll forward them to

O/S is Windows 7 Professional x64.
Click to expand...
Jamie, might consider writing email addresses in a way that a bot can't identify them as such? Anyway, not sure but I think a few posts back deanan suggested sending logs to redcinex at red dot (com).

edit: found it. his exact answer was: Can you email the log files to redcinex at red dot com?
 
Last edited:
Adrian Hernandez said:
Deanan,

Something wrong on the timeline, is difficult to explain but I'll try:

When I reach a time of about 8 or 9 minutes of footage in the timeline, I cannot continue scrolling. The same happens when I change the size of the thumbnails of the clips in there (I mean when moving the slider tool, between the slice and slug).
Click to expand...

Deanan, Graeme... ?
 
Do you know when a new QT Codec is coming out.
I had heard one was about to be released the next day... which was about a month ago.
Would be good to get an update
 
roryhinds said:
Do you know when a new QT Codec is coming out.
I had heard one was about to be released the next day... which was about a month ago.
Would be good to get an update
Click to expand...

It's being rewritten for all the new stuff it has to support.
I don't have an ETA but it's high priority.
 
export output location : small bug and temporary fix

export output location : small bug and temporary fix

When batch processing files from RCX bin using export presets I noticed that if you choose "ask for output filename" in the output location while creating your preset it works only for the first export. It asks for the output destination but then somehow the preset is modified and remembers this specific location when you re-use it later on.

I could not find a way in the RCX interface to clear the output location from an export preset but needed to export using same preset to a specific destination every time (DAY_01, DAY_02...) so it was a bit annoying.

until RED has time to fix this small glitch I wrote an applescript to work around it for now, and I'm sharing it here in case someone else ran into the same issue...

When you launch this applescript, it will read your "UserExportPresets.xml" file, then for each preset with a specified output location ask if you want to keep it as set or clean it so you can specify a new one the next time you use that preset...

Mikael
 

Attachments

Jannard said:
Export option to overwrite or to add "_S###" to the file name.
Click to expand...

From the test I did here with overwrite option checked :

When exporting to MXF from a bin, each clip will overwrite the previous one even if it is not the same name...

- populate the bin with a few clips
- export to Avid MXF with overwrite existing checked
- every file will be processed in the batch monitor but at the end only the last clip remains in the output location... same in the ALE, only last rendered clip is listed

Quicktime exports are OK

Also the RED Rocket™ renders were much faster in beta 158 than Beta 183. But the color picker is working again in B183...
 
Mikael Lubtchansky said:
From the test I did here with overwrite option checked :

When exporting to MXF from a bin, each clip will overwrite the previous one even if it is not the same name...

- populate the bin with a few clips
- export to Avid MXF with overwrite existing checked
- every file will be processed in the batch monitor but at the end only the last clip remains in the output location... same in the ALE, only last rendered clip is listed

Quicktime exports are OK

Also the RED Rocket™™ renders were much faster in beta 158 than Beta 183. But the color picker is working again in B183...
Click to expand...

MXF goes through a more complex export path.
We'll take a look and see if there's something missing.
 
Well, it looks like the Mac 183 build doesn't seem to retain all the informations about the individual grades for each clip. I worked 2 days for nothing... I saved the projects quite frequently, checked the firt ones which seem to save the timeline with the first clips and then, two days later, when I open a project with a timeline of 15 minutes of clips, nothing in the timeline, just the bins. Gosh ! It looks like switching for Mac didn't improve a lot...

Did anyone succeed in saving, say, a project with 30 min of clips individually graded ?

Thanks.
 
You must log in or register to reply here.
Back
Top