What's new in 5DtoRGB Batch 1.5.22
Dec 20, 2016
- Updated to work with macOS 10.12 (Sierra)
New in 5DtoRGB Batch 1.5.21 (Dec 7, 2015)
- Updated for Mac OS X 10.11 (El Capitan).
New in 5DtoRGB Batch 1.5.20 (May 29, 2015)
- Fixed issue where audio and video could run out of sync with MTS files
New in 5DtoRGB Batch 1.5.19 (May 20, 2015)
- Updated to work with Mac OS X 10.10 (Yosemite)
New in 5DtoRGB Batch 1.5.18 (Dec 18, 2013)
- Fixed issue that would cause random crashes
New in 5DtoRGB Batch 1.5.17 (Aug 9, 2013)
- Fixed an issue that would cause a crash with certain files without an audio track
New in 5DtoRGB Batch 1.5.16 (Aug 5, 2013)
- Fixed crashing with Panasonic GH3 footage
- Fixed minor color issue affecting Rec. 709 footage
- Rec 709 matrix now correctly autodetected with Panasonic GH3 footage
New in 5DtoRGB Batch 1.5.15 (Jul 9, 2013)
- Audio no longer disabled when the selected frame rate matches the rate of the input file
- Transcoding Canon 5D Mk III (firmware 1.2.1) clips over ~9 minutes works correctly now
- Fixed issue that caused video artifacts when applying gamma correction on some systems
- Fixed issue that prevented accessing an AVCHD directory on Mac OS X 10.7
- Fixed issue that prevented DPX sequences being written properly on some systems
- Fixed issue that would cause artifacts with Canon C100 footage
New in 5DtoRGB Batch 1.5.13 (Feb 15, 2013)
- Fixed issue that caused errors when trying to read from some external hard drives
- Fixed problem that sometimes caused the frame rate to be interpreted incorrectly
New in 5DtoRGB Batch 1.5.12 (Feb 1, 2013)
- Apple AVFoundation now used for ProRes encoding and MOV output
- Fixed problem where matrix selection was disabled when using CineStyle LUT
New in 5DtoRGB Batch 1.5.11 (Oct 3, 2012)
- Fixed issue that would cause a hang when starting a transcode
New in 5DtoRGB Batch 1.5.10 (Aug 28, 2012)
- Fixed issue that would cause transcoding to hang on last few frames with some MTS files
- Fixed incorrect timecode detection with Canon 5D Mark III
- Files with identical file names in batch now incremented instead of being overwritten
- Improved Final Cut Pro XML import feature
- Interlaced detection now turned off when running a batch
- Timecode setting now persists when running a batch
- Better handling of MTS files containing corrupted frames
- Fixed broadcast range being the only luma range choice in command line mode
- Fixed issue where program would crash if batch contained file names with forward slashes
New in 5DtoRGB Batch 1.5.9 (Mar 20, 2012)
- Gamma correction feature resurrected, with ability to specify any gamma value
- m2t and m2ts file extensions now recognized
- File name is now written into the MOV timecode track as the reel name
- Sound output now disabled when changing the frame rate
- Frame counts of MTS files now displayed accurately
- Fixed issue where 24fps timecode was being written with the wrong timebase
- Minor adjustments made to muxer to improve QuickTime compatibility across NLEs
New in 5DtoRGB Batch 1.5.7 (Dec 13, 2011)
- Fixed corruption issue with transcoded files over 4GB
- Fixed issue where movies wouldn't flatten properly
- Fixed issue that caused transcoded MTS files to be short by one frame
- Fixed problem where timecode wasn't being written to files without audio
- Fixed incorrect escape characters in paths after XML import
- Progress indicator now shows transcoding time in minutes/seconds
New in 5DtoRGB Batch 1.5.6 (Nov 29, 2011)
- Muxer has been rewritten from scratch, which fixes audio output problems
- Canon 60D embedded timecode is now supported
- Added the ability to transcode using either full or broadcast luma range
- Moved CineStyle option to the Post-Processing menu
- Removed gamma options (superseded by GLSL shader support)
- Fixed issue where output was black if a display wasn't connected
- Fixed issue where user-specified timecode was not being written in single-file mode
New in 5DtoRGB Batch 1.5.5 (Nov 2, 2011)
- Fixed issue where decoding matrix selection was ignored
- Fixed issue where loading a default.glsl script in command-line mode caused a hang
- Set default frame rate in command-line mode to 23.976
- Fixed directory naming errors when outputting to DPX
- Fixed crashing due to input audio buffer overflow
- Fixed issue preventing writing of user-specified timecode
- Fixed issue that caused QuickTime files to come out darker on Mac OS X 10.7