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

Thoughts and Tips...

Status
Not open for further replies.
I have said this before but I'll say it again, shooting features or serious television in 1080P is a big mistake. Since this view will certainly get thrown around the industry, let me explain why.

1. With the certain new standard of 4K delivery for movies AND tv, anything shot on 1080P will be left in the cold for a re-release. Several major companies have 4K displays and projectors nearing release to theaters and to the public. Sony has already converted many theaters to their 4K projectors. Epson has a killer home 4K projector in waiting. Panasonic, Samsung, Christie, Barco, Sharp, Meridian, and others are ready to get their fair share.

2. 1080P is not a quality replacement for film. It has 1/4 the actual measured resolution of film (some less than that). To make the "big screen" it needs sharpening. Often times lots of it. Sharpening is not good for the skin. Real resolution beats sharpening every time... by a lot.

It is my firm belief that hindsight will show the 1st two digital standards, SD and HD, will be considered "mistakes" in the not to distant future. Film will never be considered a mistake. It is the gold standard. It will hold up to 4K releases and you will see many classics re-released in 4K.

Don't count television out of 4K. The delivery mechanism is coming.

I started RED because I did not believe that 1080P was an adequate replacement for film. I love film. When its day is done, we need to honor it with at least as good an image... hopefully better. 1080P is not it.

(Steps down from soapbox)

Jim
 
Last edited:
REDCINE-X BUILD 356

Test Build 356:
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_356_mac32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_356_mac64.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_356_win32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_356_win64.zip

Changes 351 to 356:
REDGamma2 and REDColor2 added to REDline help.
Fixed crashes when loading certain RMD files.
Fixed bug where 3d clip exports weren't respecting in and out points.
Fixed REDline bug where --useRSX 2 would use in and out points from the RMD file.
Fixed ReelID and AltReelID output from REDline.
The mouse wheel will no longer scroll drop downs.
Improved error messages for the "move to trash" operation.
Fixed crashes when loading project files or R3D's from the Finder on Mac.
Fixed bugs with multiple "Save As" dialogs appearing when the Export button is pressed multiple times.
Fixed coloring issue with drop downs in the Export Settings dialog.
64-bit REDline is now functional.
Rubber-band selection in the browser will now scroll the view if necessary.
Improved thumbnails seen when dragging clips in the bin and browser.
Fixed the "too many open files" bug in the bin and browser for 64-bit Mac builds.
Fixed bug where the Shift-Z shortcut was not working.
Added REDCODE and "Record framerate" metadata fields.
Fixed hit region of buttons on Mac.
Framing performance improvements
Fix for Avid 16 char edl's not relinking correctly.
Fix for off by one FCP XML import.
Better slug handling for FCP XML import/export.
Better clip handle support for export FCP XML's.
Handle FCP XML transition items, so no frame dropping occurs on import.
Properly quote paths in REDLine batch scripts.
Video window zoom improvements.
Fixed backwards copy during Top Bottom 3d exports.
Always use filename of left clip for 3d exports.
Added Growl Batch Finished notification.
Export handle size increased to 100.
Can now refresh currently selected look and framing presets.
Fixed 3d offset behavior.
Fixed timeline clip split bug, where a duplicate frame was introduced.

Jim
 
Last edited:
This is NOT official (yet) but should give you a good idea what's happening with REDCODE and SSDs.

Double the times for a 256GB card and halve the times for a 64BG card (pretty obvious I guess)...

Jim

1293435891.jpg
 
While it is not usually our position to offer rewards for our customers stolen property, this one is an exception. EPIC #00006 is truly a historic camera. It is the very 1st EPIC shipped to one of our customers and the way it was taken irritates me no end.

We are now offering $100,000 for the safe return of EPIC #00006 and the rest of the system including the media with Mark's files... and the arrest and conviction of those that broke into Mark's chalet in France. We will ONLY pay this amount if there is an arrest and conviction of the parties as we are not interested to be ransomed by thieves.

If you have any information regarding the theft, the location of Mark's property or any details that might solve this case, please contact anyone at RED and they will make sure I hear about it.

Posting information on REDUSER is NOT a good idea for several reasons, including your own safety. Please do NOT post any information you have obtained. Any post we see on REDUSER regarding information on this case will be deleted.

Jim

Jannard said:
The unthinkable has just happened. Mark's chalet was broken into while they were sleeping and EPIC 0006 was stolen along with cash. Mark is at the Police Station right now in Meribel, France.

The family is safe and no one was hurt.

This is a tight community. We need your help. Keep your eyes and ears open for any news, tips or details about an EPIC floating around. An EPIC is a hard thing to circulate since there is only one in the world.

Please contact anyone at RED if you hear of anything.

Of course Mark is heartbroken. So are we.

Jim
Click to expand...
 
Last edited:
HDRx SAMPLES...

These were taken at the same time as the "barn shot". I'm doing some testing of HDRx in REDCINE-X (early build) and thought I would post as we go along.

These are all UNGRADED. I took a frame of "normal", "under" and then one from the standard HDRx blend tool using NO SLIDER CONTROL (default settings). With the slider, you can have more or less highlight protection... as you wish. These are LOW QUALITY screen grabs from the files stacked up in Photoshop. But you get the idea. I think we used +3 on both of these... can't quite remember, I'm getting old and the metadata wasn't in back then. Opened with REDcolor2 and REDgamma2. No other settings were touched or grading done in either REDCINE-X or Photoshop! Again, this is from the standard HDRx blend tool with no slider control.

Note: Back then we probably cheated a bit with the normal exposure and put it a tad over. Please don't tell anyone.

Jim

1294205688.jpg


1294146737.jpg
 
So what exactly is HDRx™?

HDRx™ is a RED invention that is built into every EPIC and Scarlet camera giving the user an option for extended dynamic range when the situation calls for it… from 2 to 6 stops over native by preset.

How does HDRx™ work?

In a single camera, HDRx™ simultaneously shoots two image tracks of whatever resolution and frame rate you have chosen. The primary track (A-track) is your normal exposure. The secondary track (X-track) is a "highlight protection" exposure that you determine in the menu settings. You select the amount of highlight protection you need in stops… 2,3,4,5, or 6. Each stop represents a stop less exposure in shutter speed. Example… if you select 2 and your primary exposure is 1/48th sec, the X-track will be two stops less exposure at 1/192 sec. The ISO and aperture remain the same for both exposures.

During recording, the two tracks are "motion-conjoined", meaning there is no gap in time between the two separate exposures. If they were two alternating standard exposures, there would be a time gap between the two tracks that would show up as an undesirable motion artifact. Both tracks (A & X) are stored in a single R3D. Since there are two exposures, the camera is recording double the amount of frames. For example, if you are shooting 24fps, the camera is recording 2-24fps tracks, the data equivalent of 48fps.* After combining the two tracks for playback you see only one 24fps motion stream.

Once I record HDRx™... what do I do with it?

The power of HDRx™ is the multiple options you have to use it.

1. Combine the two tracks in post tools like REDCINE-X, Storm or any other application that supports the SDK to create "Magic Motion" (see below). This blending of the two tracks comes with a slider so you can decide in post just how much of each track you want to use. A preview window shows you the result of your selection. You can also view each track individually.

2. You can combine the two tracks using MNMB (More Normal Motion Blur). MNMB is designed to emulate the motion of a traditional camera with full motion blur. This is a tool created by The Foundry (creators of Nuke) that uses a new motion estimation algorithm designed specifically for HDRx™. The shorter exposure (sharper image) is blended to match the motion blur of the normal exposure. Again, the preview window shows the combined result or each track individually.

3. You can use the X-track separately (sharper image) for motion tracking, then combine with the A-track as in #1 or #2 above… or ignore the X-track altogether.

4. You can combine with a variety of additional new tools created by Graeme Nattress for a multitude of creative options.

Exporting to EXR will give you a multi-view EXR with both exposures (like a stereo EXR).

So what is "Magic Motion"?

Shooting 24fps and 180 degree shutter on film or digital is an illusion. It is not really the way we see motion. Ask someone to stand in front of you and swing their arm over their head from one side to the other. If this was shot traditionally at 24fps at 1/48th shutter all you would see is a constant motion blur until the arm stopped. But that isn't what your eyes actually see. You see both motion blur AND sharper references to the arm and hand all along the path. "Magic Motion" is much closer to what the eyes see… the combination of motion blur (A-track) and a sharper reference (X-track)… with the bonus of extraordinary dynamic range not seen in any motion capture camera.

Note: If you ignore the X-track completely, you will have a standard exposure with 13 stops of native dynamic range from the EPIC… just as if you had not turned HDRx™ on. For this reason, we encourage the A-track exposure to be "normal". It gives you the most options, including "turning off" HDRx™ (the X-track). If you are tempted to shoot "over-under", you are then fully committed to HDRx™. While no one will call the police on you if you do this, your options are dramatically reduced.

So what are the downsides to HDRx™?

1. Since you are recording twice as many frames, your maximum frame rate, minimum REDCODE ratio, and maximum record time on your media will be cut in half.

2. Limitations. MNMB is more effective than Magic Motion with very fast moving, bright objects in a dark environment. Can you break HDRx™? Sure. Just like you can pan too quickly with any 24fps camera. All digital cameras have to deal with judder. We got used to film grain to the point where we thought we actually didn't want to give it up. Learn the limitations just like everything else. Then shoot 18 stops of dynamic range and show all your friends what your camera can do.

Jim
 
EPIC dimensions...

Jim

1295322998.png


1295388169.png


1295369482.png
 
Recap.

EPIC and Scarlet are coming.

EPICs and RED ONE MX are being used on:

The Hobbit- 3D EPIC
Spiderman- 3D EPIC
Contagion- RED ONE MX & EPIC
Girl With the Dragon Tattoo- RED ONE MX & EPIC
Clash of the Titans 2- 3D EPIC
Underworld 4- 3D EPIC
Ridley Scott Un-named- 3D EPIC
Jack the Giant Killer- 3D EPIC
Un-named biggie #1 (another huge budget studio movie) announced soon- 3D EPIC
Un-named biggie #2 (another big budget studio movie) announced soon- 3D EPIC
Un-named biggie #3 (another big budget studio movie) announced soon- 3D EPIC

EPIC-Xs ship in reasonable quantities before NAB 2011.
Scarlet 8X and interchangeable soon after.
Deliveries of EPIC-X to all existing customers by summer 2011.

Big surprise at NAB 2011.

Jim's vacation after NAB 2011.

New REDcolorEPIC due February 1st.

REDray Pro ships April 2011.

RED booth at NAB- SL6320

All EPICs built in the USA.

EPICs used by still photographers for major magazine shoots- now.

EPIC-S ships as soon as we take care of EPIC-M and EPIC-X customers.

Development of future RED technology... well on the road.

Happy customers- priceless.

Jim
 
Last edited:
REDCINE-X Build 416

This build has lots of new stuff including color science specific to EPIC. It has remedial HDRx™™ support but DOES NOT have RED Rocket support. It is a BETA build and hasn't fully been tested.

Jim

http://red.cachefly.net/redcinex/test/REDCINE-X_build_416ER_mac64.zip

http://red.cachefly.net/redcinex/test/REDCINE-X_build_416ER_win64.zip

http://red.cachefly.net/redcinex/test/REDCINE-X_build_416ER_win32.zip


Change list 356 -> 416:
• Watermark improvements for offscreen cases
• FCP Xml improved to use unique id's for clip items.
• XML improvements with parsing paths to R3D files.
• Import/Export settings dialogs interaction cleanup.
• Support for HDRx™™ exporting.
• Support for HDRx™™ Viewing in the default 2d mode of the viewer.
• Fixes for exporting complete timelines
• XML added URL encoding to imported/exported paths.
• Added OSX Quicklook plugin for R3D files
• Improved batch list descriptions for wrapper/trim timeline exports.
• Added windows R3D thumbnail plugin
• Added Separate eyes mode to 3d export options.
• Windows menu bar has been improved to be easier to access.
• Added a quicktime export option for using our own file I/O calls instead of quicktime calls.
• Fixed libjpeg.dylib issue with Avid SDK.
• Added shutter speed, timestamp, look settings, absolute and edge time-codes, number of file segments, to the metadata window.
• Auto matching of 3d clips.
• TC generation for left and right eyes for burn in fixed.
• TC generation for left and right eyes for AAF/MXF/ALE fixed.
• Removed Set Finder Icon options - replaced by the Quicklook plugin
• Added select all and select non options to the browser context menu.
• Added Clear all in and out points option to the bin context menu.
• Added auto saving of projects.
• Updated project format to use RMDs to improve auto save time.
• Added prompt to save project before closing app.
• Added better error reporting for Save RMD and Reload from RMD operations.
• DPX Endianess header issue fixed where present.
• Slider clicks on color correction controls fixed.
• Fixed auto save RMDs when current look is changed via "Look Manager"
• Added an option to force terminate batch jobs when they are unresponsive.
• Additional fixes for failed batch jobs that used to hang the batch queue.
• Additional checks added for starting batch jobs to Quicktime and Avid.
• Fixed option click to reset sliders for gains.
• Added extraction and setting of sequence names from EDL.
• Snapshot updated to include an RMD file.
• Fixed a problem where the active eye does not update when dropping a 3d clip in the player.
• Allow any drive to be ejected from within the RCX Gui - Note System drives will simply deny the eject request.
• Fixed Hot Keys with fullscreen mode so space bar will now stop/start playback and escape will exit fullscreen again.
• Added a Spotlight plugin for R3D files.

Jim
 
After talking with our group, and after exhaustive work on supply chain issues... there are 18 parts (out of 18,000) of EPIC-X that come from Japan. More specifically... northern Japan factories. If you are not brain dead and have been watching the news, you will understand that this is bad news.

We are late shipping EPIC for many reason up to now... mostly due to us. We have made changes, had no idea how difficult this project was... yada, yada. Now that we know what we are doing and are ready to rock, including building a complete production line in Irvine... this happens.

Ugh...

While we have a handful of production parts for EPIC-X and will deliver them before NAB as promised, we are now looking at how to make more EPIC-Ms available to EPIC-X customers because there will be a delay in EPIC-X production due to the "Japan-effect".

No one is more disappointed than me... I am spending a fortune in blood pressure medication. Really.

We still feel that we can deliver all EPIC-X orders by summer's end but it will be "back-end" weighted. April and May will be "light".

Life is short. Put yourself in a position doing what you were meant to do. Expect curveballs. They come. Do your best and take the consequences. I guess I am talking to myself...

I promised to be transparent. Mostly that is a good thing. Tonight I am depressed. But always willing to tell you the straight scoop.

Jim
 
REDCINE-X Build 449...

http://red.cachefly.net/redcinex/eval/REDCINE-X_build_449_mac32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_449_mac64.zip

http://red.cachefly.net/redcinex/eval/REDCINE-X_build_449_win32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_449_win64.zip


Firmware:
http://red.cachefly.net/rocket/RED_Rocket_Installer_v1.4.7.zip

Release notes: 416 -> 449:
Scopes added.
Default ISO is 800.
Additional Metadata fields added.
Added additional compression options for EXR.
Added ability to auto cancel export jobs if the output already exists.
HDRx controls for epic. (HDRx viewing is only enabled in "Default 2d" mode. HDRx + 3D viewing is coming.)
Multi-Rocket speed improvement.
Epic source resolutions added to framing controls
RecordFPS added to Redline metadata.
Added Bin/Browser/Export window to the window menu.
In/Out point buttons now highlight respectively if there is an in/out point set on the current clip.
Crop settings are now more intuitive.
Dynamic Cache sizes for better performance on machines with lower amounts of memory.
Framing/Convergence metadata added to burn in options.
3D Rig metadata added to redline printmeta (4) command.
Added updated Avid SDK with a fix for NFS writing.
Added support for auto matching 3d clips using 'D' as the identifier for the primary clip.
Added logging of operating system version and OpenGl version on startup.
Added support for loading of 3D EDL and XML files.
Fixed: DPX header for 16bit dpx to properly represent the ranges used in the dpx files.
Fixed: Undo/Redo for curve control.
Fixed: Use initial clip's in point for timecode on timeline as a single file exports.
Fixed: Playback channels resetting after scrubbing.
Fixed: Audio waveform tool updating when it doesn't need to.
Fixed: Removed M/D buttons from Command History panel.
Fixed: RMD naming issue introduced in 441 and fixed in build 444.
Fixed: Avid INSUFFICIENT_MEDIA error.
Fixed: Crop UI Lock aspect ratio error
Fixed: Crash on browsing.
Fixed: Crash on bad decode.
Fixed: Redline csv missing some commas.
Fixed: SMTPE range with 3d exports.
Fixed: Double click and "Open in Player" in the timeline bin.
Fixed: H-key help window not showing up.
Fixed: Saving of HDRx values to RMD
Fixed: Export timecode issues with in points.
Fixed: Rocket Monitor out: play to end - 1 fixed, play head position fixes, etc
Fixed: UI focus issues with Rocket Setup Dialog.

Jim
 
REDCINE-X Build 452...

Here you go.

http://red.cachefly.net/redcinex/eval/REDCINE-X_build_452_mac64.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_452_mac32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_452_win64.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_452_win32.zip

Rocket Firmware:
http://red.cachefly.net/rocket/RED_Rocket_Installer_v1.4.7.zip

Change list 449->452:
Fixed: Windows not returning after CMD+H on mac.
Fixed: Windows Rocket Video out issues.
Fixed: Windows 7 Export issues.
Fixed: Autosave RMD for browser.
Fixed: An EDL Issue.
Added the new EXR compression options to RedLine.
Added singleRocket option to Redline to limit the number of rockets it will use.
Added forceRocket option to Redline to cause Redline to abort instead of switching to software mode if no RedRockets are available.


Jim
 
Last edited:
Last edited:
REDCINE-X Build 454...

http://red.cachefly.net/redcinex/eval/REDCINE-X_build_454_mac32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_454_mac64.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_454_win32.zip
http://red.cachefly.net/redcinex/eval/REDCINE-X_build_454_win64.zip

Rocket Firmware

http://red.cachefly.net/rocket/RED_Rocket_Installer_v1.4.7.zip



Change list 452 -> 454:
ï Fixed the double spin boxes in the clip settings frame to no longer steal
focus and change values when using the scroll wheel over them to scroll the
entire window.
ï Fixed scroll focus issues on spin boxes and combo boxes fixed.
ï Fixed scopes appearing with a zero height on startup in some cases.
ï Fixed bug where frame number/timecode edit fields on the Viewer couldn't
be edited.
ï Fixed handling of slugs when exporting XML/EDL from the menu.
ï Make sure look and framing settings update properly in certain cases after
pausing in the video player.
ï Turn off/gray-out in the scopes when coming out of monitor out mode.
ï Make video player window active after double clicking on a clip.
ï More robust handling of decode mode changes from the viewer. Fixes random
crash.

Jim
 
REDCINE-X Build 470:

http://red.cachefly.net/redcinex/test/REDCINE-X_build_470_mac64.zip
http://red.cachefly.net/redcinex/test/REDCINE-X_build_470_mac32.zip

http://red.cachefly.net/redcinex/test/REDCINE-X_build_470_win64.zip
http://red.cachefly.net/redcinex/test/REDCINE-X_build_470_win32.zip

Jim

Changes: 454-470
Fixed: rotate and flip framing setting application in the video window for hdr clips when blend is enabled.
Fixed: DRX, Sharpness, and Denoise controls are properly enabled/disabled when rockets are disabled/enabled at runtime
Fixed: HDRx crash when switching between blending and not blending.
Fixed: HDRx in 2d View with 3d clip fixed.
Fixed: misc video player issues issues with frame indexing on the video card.
Fixed: 3d clip crash when one side doesn't return an image.
Fixed: Windows Export crash issue.
Fixed: HDRx Blend enable in viewer crash issue.
Fixed: RMD autosave breaks from using White Balance shortcut key.
Fixed: HDRx blend button disables when you switch between HDRx clips.
Fixed: Slugs appearing as garbage in the viewer.
Colors of some ColorSpace and GammaSpace list items changed.
Additional HDRx info added to Redline output
Eject now works from Video Player
EDL Handling Improvements
ALEs generated from RCX now put the Sync'd External Audio TC into the SoundTC field instead of the source BWF's starting TC.
Quicktime frame rate override feature.
Fix for Viewer 5k Ana from Rocket at 1/8th
Fix for snapshot where fractional frame sizes occurred.
Fix 3d offset range calculation.
Fix frame mismatch in viewer when dropping in a new clip from the bin.
EDL/XML minor improvements.
Fix for properly detecting camera source.
Fixed Debayer setting's dialog not restoring old values if you cancel out.
Fix to show correct clip aspect ratio numerator in clip metadata.
Fix folder history for all export dialog prompts.
Fixed Stereo 3D Meta/Default buttons not showing up in the command stack.
Video Window SAC/SEC meta options now have corresponding tooltips.
Fixed pairing information in RMD's for manual HDR clips.
Fixed absolute and edge timecode calculation in Quicktime exporter.
Fixed undo/redo command descriptions for the curve widget.
Fixed REDLine script checkbox not setting state properly in export format dialog.
Added 3D clip trimming.
Fixed REDLine crashing on exit. More robust error handling if a codec is not found.
Added HDRx Metadata to REDline
 
So we were invited to see some Spiderman footage today at Sony. John Schwartzman was there and we talked a bit before going into the screening room.

"This is the best looking footage I have ever shot... these are the best images I have ever seen!" was his comment. I asked him if this was just his enthusiasm spilling out or if this was actually the case (pretty big statement). He thought for a few moments and said "No, really... this is the best footage I have ever seen from any camera. Ever."

So, with that, we went in. There was a Sony T420 projector (same as we have at RED Studios) in a grading room at Colorworks. We talked to "The Steve" (colorist) about his experience with the EPIC footage and opinion. He confirmed his opinion matched John's and we sat front row with huge expectations.

I have to say that we were all stunned. Shocked. So incredible. Not like RED ONE MX. Not like anything we had seen from another camera. Same resolution and feel of our new EPIC reel, but with actors and a story and Schwartzman's ability to light.

The consensus in the room (to a person) was that this looked like film. Like 65mm film. Better. Without any trace of film's blocky detail in shadows or grain. Jaw dropping.

EPIC is performing as it's name implies it should. We will keep John's comment close to us... to remind us how hard we need to work to never lose this position. We really like it.

Jim
 
EPIC-S is dependent on a few things...

1. EPIC-X finished and shipping most of the orders.

2. The rework of the camera given less electronics and features.

3. Cost saving advantages from a mature assembly process and efficiency of production techniques.

We expect EPIC-S to be in production in Fall of this year. That presupposes no more supply chain surprises.

Jim
 
Just for reference, these are the frame rate specs for EPIC (all shown widescreen except QuadHD and 720P).

5k 2.40 = 120
QuadHD = 120
4k 2.40 = 150
3k 2.40 = 200
2k 2.40 = 300
720P = 360

Jim
 
Status
Not open for further replies.
Back
Top