Copyright (C) 1986-2009 by Daniel H. Hudgins, All Rights Reserved.
No part of "This Web Site" (HTML document), including associated files, may be: distributed, sublicensed, transmitted, copied, archived, mirrored, modified, bundled, embedded, sold, given away, rented, loaned, or shared in any form without express written permission in a formal Vendor agreement contract dated and signed in ink obtained directly from Daniel H. Hudgins by registered postal mail. All agreements for permission to distribute expire after a period no greater than one year from the date of the signing of the agreement by Daniel H. Hudgins. See the current "EULA" for information regarding limited copying and storage for the purpose of "Beta Testing" "This Web Site."
To view or use the current version of this Web page you may need to reload or refresh the display of this page by your browser. Just clicking on the browser's [Reload] or [Refresh] icon may not be enough to insure that all of the page's most current contents have been cached and displayed. Some browsers may have additional commands to help display the page's most current contents such as: holding down the [Shift] key and clicking on the [Reload] icon, holding down the [Control] key and clicking on the [Refresh] icon, holding down the [Control] and [Shift] keys and clicking on the [Refresh] icon, pressing the [Control] and [F5] keys, pressing [Control] and the [R] key, or some other combination of keys or clicks. Check to see which commands your HTML browser uses to load the most current page contents into its cache and then to display them onto the screen.
This Web site is dedicated to the thousands of "users" of my programs, those who have helped test my programs over the last 23 or so years, and especially those who shared their experiences with me.
You must read this notice: This is a licensed Web site (HTML document and associated files). You must read and agree to be legally bound in contract by the Terms of Use and conditions given in the End User License Agreement ("EULA"), Legal Notices, Instructions, Warnings, Disclaimers, and all other text in "SECTION: 0" of "This Web Site" (HTML document and associated files) before reading or using any of the information, software programs, and or files, contained in, linked to, and or associated with, "This Web Site" (HTML document and associated files). Any use or "Beta Testing" of "This Web Site" constitutes your acknowledgment of your full agreement with the current End User License Agreement ("EULA") and your decision to have this current license supersede all prior and contemporaneous agreements and understandings. Information and files in "This Web Site" (HTML document and associated files) have been placed here so that long time users of "The Author's" programs DANCAD3D.COM (tm) , DANCAD87.EXE (tm), DANCINEL.EXE (tm), DANCINES.EXE (tm) , DANCAM.EXE (tm) , or DANPLOT.EXE (tm) could help proofread the text of the documentation files or screens displayed, and also help test data files, example files, and or any software programs that might be made available from time to time, to aid "The Author" in finding mistakes, bugs, and other errors, omissions, defects, mistakes, and faults. Everything in "This Web Site" (HTML document and associated files) is "Beta Test", "Beta Code", Experimental, Preliminary, requires proofreading, or is being evaluated for possible revision, and is NOT warranted to be free of defect. To help "The Author" report any bugs, foul-ups, defects, or mistakes that you find, see "SECTION: 8" for instructions. "This Web Site" (HTML document and associated files) and all other files and programs by Daniel H. Hudgins are made available "AS IS" without warranty of any kind express, expressed, or implied. All offers and specifications are subject to change or discontinuation without notice of any kind. Please look over "SECTION: 8" of "This Web Site" before contacting "The Author."
SECTION: 6.20 is for some informaton about Workflow issues related to Digital Cinema. See also the program files in the current distribution of my programs, the other parts of this HTML documentation, and the current On-Line version of this Web site for information more specifically about my programs. Any comparisons of my programs or methods to some others is only given as a vague generality of my opinion and is not intended as a recommendation or reference to any particular products, always make your own evaluations and comparisons before taking any action.
Workflow for RED ONE (tm) Digital Cinema Camera is used to make a DI (Digital Intermediate, i.e. computer based replacement movie film lab work) for a movie that was shot with an electronic Bayer filter sensor RED ONE (tm) Digital Cinema camera. The general system of unique steps for the RED ONE (tm) Digital Cinema camera workflow is given below. Steps after the sound has been extracted from the R3D files into WAV files, and the frame images have been converted from R3D files into 48bpp TIF frames is much the same as the Workflow for Movie Film Scans.
The unique steps used for RED ONE (tm) Digital Cinema camera workflow are:
Shoot R3D REDCODE (tm) files in a RED ONE (tm) type camera.
Download or Copy the R3D files to your computer's harddrive.
If you have not already run DANCAD87.EXE (tm) and made a project directory folder structure with the Files Utilities Kinema Structure command, that gives you folders to put the TIF frames into, usually the I01 resolution level folder in each shot folder in the project structure, do so.
Run the third party program VIRTUALDUB (tm) with the R3D decode plug-in and extract the audio from the R3D files into WAV files. Use the third party program Magix (tm) or some other audio program to extract portions of the audio for each shot's WAV data such that you trim any un-needed audio samples off the head and tail of the WAV files data so that the WAV files saved for the sync audio for each shot all start with the slate board clap or slate beep tone so that when converted into audio frames in DANCAD87.EXE (tm) the first audio frame, frame zero, for each sync track will be the slate board clap or sync beep tone frame. The image frames will also be edited so that each shots zero frame is the slate board clap or sync beep frame. To extract any audio recorded at the time of shooting from the R3D file you can use the R3D plug in for the third party program VIRTUALDUB.EXE (tm) as mentioned above, or maybe some other programs as you like. To prepare sync audio recorded on external WAV recorders you use the same idea, load the WAV file into an audio editing program like the third party program Magix (tm) and extract the audio for the shot then trim the head and tail to shot length and have the slate board clap or sync beep as the starting samples. You can also check posts on REDUSER (tm) to find other ways to extract audio from R3D files to make WAV files of that audio. The WAV files for each shot will always need to be trimmed so that they start with the slate clap slap or sync beep, or at least start at the same point as the 00000000.TIF image frame for each shot. You can store the WAV for each shot in a track folder in the corresponding shot folder of the project structure.
Run the third party program REDCINE (tm) and load the R3D file into it.
Select the trim portion of REDCINE (tm) and locate the slate clap board slap closed frame or the beep/flash frame as the first frame of the shot (which will be numbered frame zero later when exported from REDCINE (tm)). Then play through the shot and select the last frame you will need's trim point. Then go to the export part of REDCINE (tm) and alter the filename output string to "00#6.E" or whatever works to get 8 digit file name numbers in my Padded filename type, like 00000000.TIF, 00000001.TIF, 00000002.TIF, ... 00065523.TIF and such. Do not use any of the color correction adjustments in REDCINE (tm), but do select the output type to be un-compressed 16bit 48bpp TIF file type. You then need to set the output file folder directory to the correct shot folder in the project folder structure used by my programs so that you can avoid having to copy or move the TIF frames into the project structure later which could take a great deal of time. You should select REDLOG (tm) brightness and color conversion and maximum quality de-mosaic (de-Bayer) full size in most cases. Do not use the color correction adjustments in REDCINE (tm), leave all color controls at their mid-point neutral setting. Once you have REDCINE (tm) setup you can have it start conversion, on a single typical computer it might take hours to convert a few minutes of footage. The full path to a TIF frame in the project folder structure might be like C:/P0001/S0001/I01/00000000.TIF, where P stands for the Project number (each move you work on would have a unique number), S stands for the Shot in the project, in the Edit list you can move the shot pointers around but the data stays in that folder even if you want the shots to play in a different order by way of moving the numbered pointers around, I stands for the Image resolution level, and then comes the padded numbered filename for the TIF frame. You would put each shot into a different Snnnn or Shot folder's I01 folder.
Once you get the TIF frames into the project structure used by my programs you can make the PIX frame for playback and look at your footage, then do the Key frame Grading and look at what the final result with color correction will resemble, then you can save BMP samples with the View option in the Grading command to show the Director and DP etc. to get feedback on your color correction values. The details of those steps are gone into in the Film Scan Workflow page, see the next step for the link to that page.
This and the remainder of the Steps in the workflow are the same as for the Movie Film Scans workflow in SECTION: 6.20.10.0 so click that hyperlink and read the steps there. That is, once you have copied the 16bit 48bpp TIF frame files numbered from zero for the clap frame into the I01 folder for each shot you need in the project file folder structure the steps to edit shots, Grade the key frames, and mix the sound track are more or less the same no matter what the picture frame images were shot with.
Please see the other example workflows in SECTION: 6.2 for more information.
You can find more information about using my programs for Digital Cinema tasks by looking in the sections that have the text from the program and update documentation files corresponding to the documentation files in the ZIP archive files for the program executables from the Download sections. See SECTION: 3.80.0.0 for information about using DANCINEL.EXE (tm) in a DIY film recorder, see SECTION: 3.85.0.0 for information about using DANCINES.EXE (tm) in a DIY film scanner, and see SECTION: 3.3.7.34 for information about using DANCAD3D.EXE (tm) and DANCAD87.EXE v3.7N+(tm) for motion picture post production and DI (Digital Intermediate) to edit, color correct, and sound mix a feature motion picture. See also any later Update files relating to the programs, and look in the Downloads sub-sections for additional utilities and or programs that may be added that relate to Digital Cinema.