- Banned
- #61
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Let the Red box be a third party project. It'll get done faster. Red should allow other companies into the fold. They already have so much on their plate.
Here goes - THE RED BOX basics (if well received, I'll post the "advanced")
caveat #1 - I am not an engineer - so this may be really off -
caveat #2 - I have had three glasses of red wine
Before we talk about outputs and features, let's talk about the image processing.
Let's say we have one SCALE and PROCESSING engine just for the video signal output - let's call that the "video out engine" or VOE.
Let's say we have another "engine" that also decodes the REDCODE RAW .r3d file and scales it. It always scales to 1920 x 1080 - 16 x 9 aspect. Let's call it the RPE (Redcode Processing Engine)
So, if the .r3d file is NOT 16x9 (it's 2:1 - yeah, I know - like we needed another aspect ratio) you would have a choice (setting in the RED BOX MENU) to FIT TO HIGHT (crops left and right) or FIT TO WIDTH (which puts the entire 2:1 inside the 16x9 frame)
What the RPE is doing is getting the frames of the .r3d file into a progressive 1920 x 1080 frame buffer so the VOE can take over -
The VOE always works from the 1920 x 1080 progressive frame (primary format)- which is one of three frame rates - 23.98fps, 24fps, 25 fps and can down-convert to a SECONDARY FORMAT -
The VOE can add a pull down pull down. So VOE can take the 1920 x 1080 image and:
1) cross convert to 720/59.94
2) output 1080i
3) output SD PAL (letterbox, anamorphic, center-crop)
4) output SD NTSC (letterbox, anamorphic, center-crop)
so, we should have:
525i 29.97
625i 25
720p 50
720p 59.94
720p 60
1080i 25
1080i 29.97
1080i 30
1080sf 23.98
1080sf 24
The VOE can ADD a ASPECT RATIO MASK. 1:85, 2:40 (this mask is added prior to DOWNCONVERT to SD)
FEATURES:
two SDI outs:
single 4:2:2 HD-SDI
dual 4:4:4 HD-SDI
SD - SDI
always, embedded TC and embedded audio - 4 channels - (max available in an .r3d file)
LIVE DOWNS-STREAM KEYER for WATERMARKS and TEXT OVERLAY
LIVE TIMECODE OVERLAY
RS422 deck control
AES/EBU audio out - 4 channels
additional META-DATA embedded via ANSI/SMPTE 291M
INPUTS:
for .r3d files:
eSata
LEMO for REDDRIVE
FW800 for a standard FW drive
CF slots - 4 total w/rollover
VIDEO OUTS: (all active)
Digital:
SD and HD-SDI, SMPTE-259/292/296 (2 outputs)
HDMI
Analog:
Composite/S Video (Y/C): NTSC, NTSCJ, PAL
12 bit D/A, 8x oversampling
SD Component: SMPTE/EBU N10, Betacam 525 line, Betacam 525J, RGB
12 bit D/A, 8x oversampling
HD Component: YPbPr, RGB
12-bit D/A, 2x oversampling
I have ideas on managing color "looks" as well if there is interest in me continuing my Red Box babble -
curious here, why use 3840 x 2160 crop as opposed to a straight over-sample from a 16 x 9 full 4K image?option to produce the 1920x1080 from a 3840x2160 crop of the 4k, rather than a scale. I expect this to be how I will generate my 1080p in software most of the time (whole number scaling) with the option to go back to the 4k for a slight reframe where necessary.
Bring it and I'll bang it. I want a Red Box.
Very good list.
Love the "fit to height" option.
Add 1080 60p to the frame rates for SRW use and other 60p kit becoming available.
Plan for 1080 90p as SRW1 or other Sony kit may do this in the future.
Add remote control of iris, roll/replay and menue. Full ccu control box with nobs not GUI wil get OB boys attention.
One BNC HDSDI output in addition to HDMI with menue/viewfinder overlay.
Mike Brennan
curious here, why use 3840 x 2160 crop as opposed to a straight over-sample from a 16 x 9 full 4K image?
Just because a 50% scale is less likely to produce scaling artefacts, and also because there will be some 'overscan' in the 4k to help with eg stabilization.
Certainly from my testing with Jim's posted 2k clip, scaling to 1920x1080 in Redcine (in the shot pane, not the output one) produces visible scaling artefacts. 93.75% is not an ideal scaling factor, and I would think 50% is better than 46.875%.
I believe the deal is that an even 2:1 scale is MUCH easier to do and a lot less taxing.
The ideal path from a high quality but simple filter point of view is a 2:1 scale from 4K to 2K (4096 x 2304 to 2048 x 1152) then a crop (pan/scan) to either 1920 x 1080 (HD) or 2048 x 1080 (DCI) pixels.
How much more expensive?hence its more expensive in hardware