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 feedback..

REDCINE report:

Using Mac Pro 8 core and MacBook Pro 17 " REDCINE works well on MAC OS X Leopard 10.5.1.

On Windwos XP SP2 works REDCINE well on MacBook Pro but not good on MacPro because of display driver's bug. Maybe I should pull out one of ATI Radeon X1900 cards to try out with one card. Anyway Windows XP SP2 is one nightmare system Later will come another report about this bug.

Below here are the System profilers about hardware, graphics/display and memory from the both computers:

Mac Pro

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro2,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 8 MB
Memory: 9 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP21.007F.B06
SMC Version: 1.15f3

ATI Radeon X1900 XT:

Chipset Model: ATY,RadeonX1900
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: ATI (0x1002)
Device ID: 0x7249
Revision ID: 0x0000
ROM Revision: 113-A52027-202
EFI Driver Version: 01.00.202
Displays:
Cinema HD Display:
Display Type: LCD
Resolution: 1920 x 1200
Depth: 32-bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Cinema HD:
Display Type: LCD
Resolution: 2560 x 1600
Depth: 32-bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported

Memory:

DIMM Riser A/DIMM 1:

Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser A/DIMM 2:

Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser A/DIMM 3:

Size: 512 MB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser A/DIMM 4:

Size: 512 MB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser B/DIMM 1:

Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser B/DIMM 2:

Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK

DIMM Riser B/DIMM 3:

Size: Empty
Type: Empty
Speed: Empty
Status: Empty

DIMM Riser B/DIMM 4:

Size: Empty
Type: Empty
Speed: Empty
Status: Empty

------------------------------


MacBook Pro 17" - Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B00
SMC Version: 1.18f2

Memory:

BANK 0/DIMM0:

Size: 2 GB
Type: DDR2 SDRAM
Speed: 667 MHz
Status: OK

BANK 1/DIMM1:

Size: 2 GB
Type: DDR2 SDRAM
Speed: 667 MHz
Status: OK

Graphics/Display - GeForce 8600M GT:

Chipset Model: GeForce 8600M GT
Type: Display
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0407
Revision ID: 0x00a1
ROM Revision: 3172
Displays:
Color LCD:
Display Type: LCD
Resolution: 1920 x 1200
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected
 
Two things we both wished for was dual monitor support. I'm not sure, maybe I just don't know how to enable it but we would have liked it to automatically at start up to recognize your second monitor and be able to use it as a display.

Hey Mike,

Thanks for the feedback... good thoughts and comments! re: dual monitor - I don't believe that is planned.

But - you can easily get a fullscreen single monitor display for playback.

Player -> Shift+Home.

:)

Lucas
------
ASSIMILATE, Inc.
LA, CA, USA
 
Hey while I'm here ...
Can anyone else confirm that if you scale the 2k clip to 4k and then output to any codec with the 4k clip as a part of the export - it borks ?

I can export one or the other scaled up or down, colour correction applied - but not both together in the same timeline (not even sure if thats the right way to describe it in RC) ...

cheers, r
 
Hey while I'm here ...
Can anyone else confirm that if you scale the 2k clip to 4k and then output to any codec with the 4k clip as a part of the export - it borks ?

I can export one or the other scaled up or down, colour correction applied - but not both together in the same timeline (not even sure if thats the right way to describe it in RC) ...

cheers, r

Robbo,

Not to draw too fine a point, but why do you want a 4K Quicktime?

(genuinely curious)

Lucas
------
ASSIMILATE, Inc.
LA, CA, USA

Currently drinking: Golden Draak
Currently playing: Queens of the Stone Age
Currently asleep: Wife and 2 kids.
 
Nah - going out to pro res 1080 causes the problem with both clips in the same tl ... 4k phhhst, wassdat ?

Hey, Lucas - can I thank you for whatever input you've had into RC - really.
 
Nah - going out to pro res 1080 causes the problem with both clips in the same tl ... 4k phhhst, wassdat ?

Hey, Lucas - can I thank you for whatever input you've had into RC - really.

(thanks!!)

Can you look at your logfile and see if there is oddness in the OpenGL section up top that describes your graphics setup?

Lucas
------
ASSIMILATE, Inc.
LA, CA, USA
 
I'll look tomorrow, if you don't mind ... gotta take off for a thing/function.

This app is too much fun.
I said it before and I'm gonna say it again - APPL should have hired you guys to deal with Color's gui - seriously.
cheers,r
 
Hi Lucas - I guess this is the log file you want to check. If it's not just let me know.

(I changed the extension to .doc to upload.)

The export craps out more or less halfway thru' the scaled 2k clip. (ie I scaled it 200% to match the proj setting).
I can tell while watching the export when it borks - the render/export just starts taking off, rendering at a rate of a bit less than real time.

What I end up with is an exported clip that starts to play normally - then at frame 256 stops - and that frame is repeated until the end.

Hope that helps.
 
after update to 10.5.1 is the same single frame in quicktime renders...
no changes. and if I try to export jpeg picture sequence my mac book pro 2.4 crashes...

It seems several people experienced the single frame (first frame) output problem.

Was this ever figured out??
 
Feature Request

Feature Request

I would really like to be able to save specific Format Settings in REDCINE, such as 480p and be able to load those back into the Format as a drop down selection just like 1080p, REDONE 2K, 4K 2:1 etc.
Being able to make this quick selection would be nice. Also, it seems as though the project settings are absolute for all clips in the timeline, so if i have one shot that is REDONE 4K and REDONE 2K settings, I have to adjust the fit width every time i switch from clip to clip rather than REDCINE holding that info on a per clip basis. Maybe I just don't know how to enable that option which could be the case, but I haven't been able to find it yet. Also, how do i loop playback in REDCINE?
 
I would really like to be able to save specific Format Settings in REDCINE, such as 480p and be able to load those back into the Format as a drop down selection just like 1080p, REDONE 2K, 4K 2:1 etc.
Being able to make this quick selection would be nice.

Just edit the ImageFormats.cfg text file

On the Mac its located at:
/Library/Redcine/Settings/ImageFormats.cfg

Open it in TextEdit and add this line:
"SD 480",720,480,1.33,24.000000

Or something close to that...
 
Regarding the shot scaling:
Click the "All" button before selecting a shot framing mode, that will apply the selection to all clips
 
About the loop play:
Press "p" to toggle between playmodes
Use "i" and "o" to mark a range to loop

and "h" brings up the help screen :-)
 
About the loop play:
Press "p" to toggle between playmodes
Use "i" and "o" to mark a range to loop

and "h" brings up the help screen :-)

...and hit "R" to automatically set an In and Out at the beginning/end of the current shot. None of these commands have to happen while playback is stopped, by the way.

For instance, you want to review several shots in a row. Hit "Enter" to Play. Hit "R" to range in. Hit "R" to range out, when done with that shot. When you get to the next shot, hit "R" again, etc.

Lucas
 
My first comment on REDCINE is whatever enhancement it needs, it is really really nice and I am very thanksfull to RED to deliver this pice of software and even more, before getting the camera.

A few things, when I want to "burn in" source TC or stuff like that the x postion max to 1279 while I have a 1080p output.

To enable (for exemple) the range button it has to be light gray (vs black) but (for exemple) the guides, blanking buttons have to be black to be ebabled. Why a difference?

It would be nice to be able to output to avi
also that it shows the frame rate it is playing

Finaly I have some question:
- In the project module, Format setting, which color space to choose? Camera RGB?
- What's the REDLOG, PDLog685 and PDLog985 gamma?
- on all module (project, color, output...) there is a RGB button on the right, what is it for?
- in the shot module there is NR button that can be set on low, med or high, what is it for?

Last thing I took Jim's 2k shot put camera RGB as color space, REDLog as gamma, put the exposure close to 1 and the shadows around 2, and this way on the histograme I had the biggest range. Then I outputed to 2k dpx. Is it the way to go if you decide not to color corect inside REDCINE at all?

ah and in the output module there is a setting called process and you can choose full, standard or draft, is that not to create quick output in low quality (when choosing draft)?

one last thing, I've noticed that on a dualcore computer REDCINE use only one core for playing and outputing, why is it so?

cheers,
antoine.
 
I can only answer a few of these:

the RGB button: just gives you a read out of the RGB values under the cursor position.

It only uses one core during playback and output because the GPU on your video card is actually doing all the hard work.
 
Thanks Mike for the explanation of the RGB button.

About the cpu use, well while the gpu is doing all the hard work, it is not very fast right now, so why not use all the cpus available? If I understand that correctly, using a single core computer or a 32 cores will not do any difference, if the gpu is similar.

Lucas, could you comment on the use of SLI technology with REDCINE.

thanks,
antoine.
 
It uses all cores available for things like decompression of the R3D files. REDLog & PDLog are log outputs if you're going to 10-bit DPX for example. REDLog is our own log curve to cram as much of our 12-bit range into 10-bits. The PDLogs are a print density log curve (what most people dealing with film are used to) with different black & white points.
 
Back
Top