This action might not be possible to undo. Are you sure you want to continue?
What's New? Version 1.5.2 (Mac OS X) introduces audio output for MTS files. This is good news for Panasonic GH2 users, since previous versions of 5DtoRGB only supported video output with this camera. New OpenGL-based Transcoding Engine As of version 1.5, 5DtoRGB uses a new, OpenGL-based transcoding engine which offloads the transcoding task to your video card (GPU). It is both faster and higher-quality than the previous engine. Please note that the new engine requires OpenGL support from the operating system. Most modern video cards support hardware-accelerated OpenGL, so this shouldn't be a problem for most users. However, out-of-date video card drivers or older video cards may produce color distortions in 5DtoRGB's output and/or cause the program to crash. If you encounter these problems, try updating your video card's driver. Basic Usage 5DtoRGB transcodes files in the AVC/H.264 video format to either uncompressed DPX image sequences or Apple ProRes QuickTime files. To convert a file, do this: 1. Click the "Convert..." button in the main window or select "Open..." from the "File" menu. 2. In the file browser window, select the file you would like to convert and click "OK." 3. Specify an output format, decoding matrix and program options, then click "Convert…" 4. Use the file browser to select a save location for the image sequence or QuickTime file. 5. Once the progress bar reaches 100%, the conversion is complete! NOTE: Clicking "Cancel" will terminate the conversion process. If a DPX conversion is in progress when "Cancel" is clicked, 5DtoRGB will finish writing the current frame to disk before stopping. If a QuickTime conversion is in progress, 5DtoRGB will remove the partially converted QuickTime file. dMatrix Custom Matrix Support If you've designed a custom decoding matrix for use with 5DtoRGB, dmtx files will be automatically loaded if in the same directory as the footage and with the same file name (e.g. MVI_0123.MOV and MVI_0123.dmtx). The matrix will show in the "Decoding Matrix" list as "dMatrix Custom." If you want 5DtoRGB to ignore this custom matrix, choose another from the decoding matrix list.
you would match the matrix that was used to encode the video to YUV (technically YCbCr). Selecting a ProRes format will output a QuickTime file with embedded timecode. You can disable decoding altogether by choosing "Raw YCbCr.976. and Cb and Cr to blue and red. You can also specify a custom decoding matrix by choosing "Import Matrix…" from the "File" menu. Decoding Matrix: Choose the decoding matrix you want to use here.709 is for HD material and BT. Frame Rate Selection: Use this to set your footage play at an arbitrary frame rate.97 fps material to 23. It simply sets the playback rate of the video without changing the frame count. It wouldn't be useful for converting 29. If you select this option. like when shooting at 60 fps for 24 fps output. Canon HDSLRs use the BT. Gamma Flagging: This setting will add a gamma flag to the output QuickTime file without actually affecting the picture data (pixel values) in the footage.601 matrix." This copies luminance to the green channel of the output file.dmtx files). DPX output is often used for visual effects purposes. BT. If you notice that your footage looks either too light or too dark when importing it into a QuickTimeenabled app. You may still need to select a gamma flagging option if some applications are not displaying your custom gamma properly. If you want this custom gamma value applied to the footage. This is useful for "overcranking" effects. or when the highest possible quality is needed. Keep in mind that this does not "convert" footage from one frame rate to another. . ProRes files generated by 5DtoRGB will play back in Final Cut Pro without rendering (no red bar). which may or may not use this setting to affect the way your footage is displayed. Choosing "DPX" will output a DPX image sequence with timecode inserted into the header of each DPX file. Generally speaking. as the luminance data is unprocessed bit-exact output from the H. ProRes output is typically used for compatibility with Apple's Final Cut Pro or Final Cut Pro X. Program Options Output Format: Choose the output format to which you want to transcode.601 is for SD. which is selected by default. this option will increase transcoding time. Selecting this also enables the gamma corrections made in dMatrix if a custom matrix is used. This option can be used to access the raw luminance data out of the input files.264 decoder. You can also use this for "undercranking" effects or any other special purpose. try changing this setting. respectively. for example. Bake Gamma Correction: This setting will "bake" a gamma correction into your footage by modifying the pixel values in the image. select the "Bake Gamma Correction" option in 5DtoRGB (this will override the default gamma correction value). Normally. This may be useful if another application does not recognize the QuickTime gamma flag.dMatrix files can store a gamma correction value as well as matrix values. it is recommended that you do not add a gamma flag to the file as it may cause the footage to look very dark when imported into applications that read the gamma flag. 5DtoRGB accepts matrix files in Rarevision's dMatrix format (. If running a non-GPU accelerated version of 5DtoRGB. This flag can be read by QuickTime-enabled applications.
opengl.vec3(1. 5DtoRGB will only process the video track. The timecode value entered in the timecode entry field will be used instead. With this option. Don't select this when working with Canon HDSLR footage.818)). user-defined shaders execute within main() after gl_FragColor. This will disable matrix decoding. so do not use it if you need timecode (or use Final Cut Pro to add a timecode track later). For more information on GLSL and OpenGL. run a second conversion and choose "Raw YCbCr" from the matrix menu.rgb = pow(gl_FragColor.rgb.Post-Processing: You can use this setting to post-process your footage using a custom GLSL fragment shader. this simple script will perform a gamma correction to the R. If you want to implement your own shader. G and B channels: gl_FragColor.0/. If you need a separate luma matte to use with a DPX sequence." in the "File" menu.. you can use gl_FragColor as your starting point. 5DtoRGB does not currently perform any GLSL syntax validation.264 footage from cameras other than Canon DSLRs. You should validate your GLSL code prior to importing it into 5DtoRGB. Effects like color correction.org. Cb and Cr channels are made full raster using "nearest neighbor" scaling . Disabled: Disables chroma interpolation. The best choice for progressive footage like from the Canon 5D Mk II or 7D. Choose this if a particular clip is causing 5DtoRGB to write a corrupted QuickTime file. This only works with ProRes 4444 output. Chroma Mode: Selects the chroma interpolation method. In 5DtoRGB. check out http://www. GLSL code containing errors may cause the fragment shader to fail. Override Timestamp in THM: Select this if you want to ignore the timestamp in a clip's accompanying THM file and specify your own timecode. This may result in grayscale-only or corrupted video output. Include Luma Matte as Alpha: This copies the unprocessed Y (luminance) data from the input file to the alpha channel of a ProRes 4444 QuickTime file. Fragment programs are written in the GLSL language and can be imported into 5DtoRGB by using the "Import Fragment Shader. This is a powerful feature that allows users to run their own fragment programs on the video card's GPU. but correct results cannot be guaranteed. Disable Muxing: With this option selected. Interlaced: Uses an alternate method better suited to interlaced material. You will also lose timecode support with this option. This option may make it possible to successfully process H. The options are: Default: Uses the highest quality chroma interpolation available. . allowing you to extract the luma matte from the second sequence (luma will be mapped to the green channel). noise and sharpening can be implemented by these programs. For example. Because of this. Only useful for testing and comparison purposes..
Use this option to change it to 00:00:00:00 instead. The following preferences can be set: Don't warn about missing THM files . Command Line / Shell Scripting Support 5DtoRGB supports basic command line operation when running in CLI (command line interface) mode. Preferences are stored on disk in the file ~/5dtorgb.Disables the warning that is displayed when an input file's accompanying THM file in not present. It only needs the THM file to be in the same directory as the MOV file. An integer representing the decoding matrix value 4. Using a terminal.app/Contents/MacOS/5DtoRGB /Clips/MVI_0001. This option will not allow machines without ProRes support to output ProRes QuickTime files (the video will be black on these systems). Note that you must have ProRes codecs installed for ProRes output to work properly. you can pass 5DtoRGB five arguments: 1. you can force 5DtoRGB to allow ProRes output even if no ProRes codecs were detected.conf. An integer representing the desired output format 3.On some systems. In the event that the THM file is unavailable.Preferences The preferences dialog contains options for modifying the behavior of the program. Bypass codec check at startup . A float representing the frame rate value Here's an example: $ /Applications/5DtoRGB. 5DtoRGB uses a default timecode value of 01:00:00:00. Set default timecode hour to 0 – If a THM file containing timecode is not found when importing a clip. you can still specify the start timecode yourself by entering an arbitrary value prior to starting the conversion. unlike the Canon plugin.MOV 2 1 1 23. this check fails even though ProRes codecs are installed.976 . 5DtoRGB does not require the CF card directory structure to be intact. However. Don't automatically load dmtx files – Selecting this will prevent 5DtoRGB from loading dMatrix files automatically when present in the same directory as the input file. An input file path 2. By selecting this. An integer representing the gamma flagging value 5. Timecode Support 5DtoRGB will derive start timecode values from THM files in the same way that Canon's E1 plugin for Final Cut Pro does when using the "Log and Transfer" function.
the faster 5DtoRGB can perform read/write operations.The first argument. this index is zero-based so "0" is the first item in the list. . The last argument is the desired frame rate to use for the transcoded file. "/Clips/MVI_0001. This makes it possible to do multiple conversions simultaneously. ProRes 422 (LT) 5. "2. The second argument. Unlike the output format list. Third-party scripts are available for download that support batch conversions.mov" suffix. The supported output formats are as follows: 1. so numbering starts at 1 (Which would be ProRes 4444).app Each time you enter this command. dmtx files are automatically loaded when present. ProRes 422 4." corresponds to the index of the desired format in the list of output formats. DPX output is not supported in command line mode. ProRes 422 (HQ) 3. A SAN or locally attached disk array is preferable. if you want to output the file as ProRes 422 (HQ). To do so. The output file will be written to the input file's directory with the same name as the input file and a "_1. place 5DtoRGB. ProRes 422 (Proxy) The next two arguments correspond to the list index of the desired decoding matrix and gamma flagging value. This overrides the value specified for the decoding matrix on the command line. This is used to retime shots that have been shot at higher frame rates with "overcranking. There is no option for an output file at this time. a new instance of 5DtoRGB will be launched. Note that when in CLI mode." or slow motion in mind. and type this command in a terminal: $ open -n /Applications/5DtoRGB. since it is the second ProRes option in the list. It is also possible to do batch conversions using a shell script that utilizes 5DtoRGB's command line interface." is a path to an input file. If you would rather specify a matrix even when dmtx files are present. ProRes 4444 2. So.MOV. The faster the storage device. Usage Tips 5DtoRGB will perform at its best when reading from and writing to fast storage media. You can run multiple instances of 5DtoRGB on Mac OS X.app in your /Applications folder. this number would be 2. disable automatic loading of dmtx files in the preferences. respectively.
ffmpeg.8 or later. Apple ProRes codecs must be installed in order to output files in ProRes format.org/licenses/lgpl-2.txt. Notes on LGPL Compliance This software links with software libraries from the FFmpeg project under the terms of the GNU LGPL version 2. Source code for these libraries can be found at http://www. . 5DtoRGB is compiled as a 64 bit Intel-only binary.1.Requirements 5DtoRGB requires Mac OS 10. and the the OpenGL implementation on the system must support the OpenGL extensions used by 5DtoRGB. and will only run on 64 bit Intel processors. An OpenGL-enabled video card or motherboard video chipset is required. Full text of the GNU LGPL 2.1 can be found at http://www.gnu.5.1.org.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.