Welcome to our community

Be a part of something great, join today!

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

RELEASED: REDCINE v20.0.0 (BETA)

PC version is working fine here on Windows 7 RC1 x64.

The new colour science really is wonderful, I have some worst case scenario footage from build 18 and it cleans up very nicely under the new debayering algorithm.

Build 20 footage looks even better!

Well done Red. Now I'm just hanging out for the upgraded Adobe plugin and all will be well on the PC side.... :)

Cheers,

Paul
 
I just want to make sure that those folks having trouble running REDCINE v20.0.0 (BETA) are not actually trying to run Beta ROCKETcine-X (Build 440).

Beta ROCKETcine-X (Build 440) required the Red Rocket card.

REDCINE v20.0.0 (BETA) is a new update of REDCINE, that does not currently support the Red Rocket card.
 
So is the Redcine 112 clip limit no longer there - I vaguely remember that caused trouble for some people in a similar way.
 
Just playing with RedCine v20.0.0 on a shoot today. Build 17 on camera. Camera metadata is color temp=5000K tint=0, but when it comes into RedCine it is displayed as Kelvin=3920, tint=-5.52.

I understand that white balancing now needs to take place in B20 color science apps - how can this be done in RedCine? Will this difference between camera and file metadata just be for pre-build 20 files, or is it the same for build 20 files?

In short, how do we understand / work with white balance these days? Surely RedCine should report the kelvin/tint settings the camera recorded.
 
Naming conventions, rendering 1920x1080 from 4k issues

Naming conventions, rendering 1920x1080 from 4k issues

Mark L. Pederson; are not actually trying to run [B said:
Beta ROCKETcine-X[/B] (Build 440).

Beta ROCKETcine-X (Build 440) required the RED Rocket™™™ card.
.
Click to expand...

I reposted this in the correct forum, I'm talking RED Rocket™ issues here if you can help, thanks.

How do I get ROCKETCINE to name the render the same name as the R3D file?

When I do a render from 4k to 2k it's all fine, if I render from 4k to 1920x1080 I have various problems with the render. I wonder if it's my host computer which I'm told does the ProRes rendering, it's last years 8 core with 8gb ram.

Tomorrow I'll try shooting quadHD and see if that renders to 1920x1080 easier.

Is there a manual somewhere?

Can I add to the batch more then one file at a time?

Thanks, Keith
 
I wonder the REDCINE boot issue happens depending on the video card? I can't install on the Mac Pro with ATI Radeon HD3870. The other Mac Pro with stock ATI cards work fine. Is anyone with 3870 having similar issue?
 
I put the original Radion back and tried it but still not booting. So it wasn't because of the 3870.
 
Okay, I found out why it doesn't boot.

I suspected something to do with the permissions since Steve was mentioning about the disk utitlity/fix permission thingie, but those didn't help in my case. After swapping the video card back to stock card and didn't help neither, then I looked at the permission on the Library folder itself being not writable, I suspected that REDCINE can't create the folder. I remember from numerous times that the REDCINE folder in the Library caused problems and being right there instead of application-support folder, so I change the permission of the Library folder to write/read for my login acount and bang, it worked. I don't remember if this is default, so RED Team should look into how new REDCINE create the preference folder.
 
Miguel "Macgregor" De Olaso said:
Can anyone put examples of what´s changed in the new color science? Because all i see are slightly warmer colors, not a huge different matrix here.
Click to expand...

Same here. The noise in one of my tungsten shots (from build 17) looks identical to previous version of Redcine. Wasn't there an improvement in this area?
 
Kaz said:
Same here. The noise in one of my tungsten shots (from build 17) looks identical to previous version of Redcine. Wasn't there an improvement in this area?
Click to expand...

did you open the old project or open the footage in the new project? Because the manual explain how the new version treats the old project and leave it as old color science when you open it.
 
Kaku Ito said:
Because the manual explain how the new version treats the old project and leave it as old color science when you open it.
Click to expand...

Can someone point me to the manual please?
 
Brent@RED said:
The latest version of REDCINE v20.0.0 (BETA) has been posted on www.red.com/support .

SUMMARY:
* Support for RED ONE build 20 and new color math.
* Updated FORMAT list to include new ANAMORPHIC camera formats.
* Added RECENT PATHS in the Media Browser to allow quickly navigating to common locations.
* Improved QuickTime rendering.
* Support for all DNxHD quality levels.


Thanks, BC
Click to expand...

Red Team,

Why all metadata info related to Wite Balance and Tint is changed (4259, and -7 respectively) at the Shot screen, and 4258 and 6.58 at the Colors screen? I mean, change from the original Metadata (5,600, 0), and discrepancy between the same information within RC on the 2 different mentioned screens?:anti-old:

Any guess, McGregor?

Please advise,
 
Kaku Ito said:
Okay, I found out why it doesn't boot.

I suspected something to do with the permissions since Steve was mentioning about the disk utitlity/fix permission thingie, but those didn't help in my case. After swapping the video card back to stock card and didn't help neither, then I looked at the permission on the Library folder itself being not writable, I suspected that REDCINE can't create the folder. I remember from numerous times that the REDCINE folder in the Library caused problems and being right there instead of application-support folder, so I change the permission of the Library folder to write/read for my login acount and bang, it worked. I don't remember if this is default, so RED Team should look into how new REDCINE create the preference folder.
Click to expand...

Mine crashed all the time as well, and I could not find it in the library folder, so I created one with the name RedCine in the library folder ( with the C instead of c) and now everything works.....
 
Mick, thanks for sharing your info..

I also thought of that, too but I wend for changing the privileges instead.
It seems because of some mishandling for the preference names by REDCINE.
 
You must log in or register to reply here.
Back
Top