Autokode! is a very high quality batch file Transcoder and memory card file Offloader for DSLR and regular cameras. Autokode! backs up, corrects and converts camera files to edit friendly formats and automatically embeds Timecode and Reel Name metadata.
In as little as 3 clicks, Autokode! creates properly formatted, cross platform compatible, broadcast quality files, suitable for professional workflows. The output files are arguably higher in quality than the originals.
| File Offload/Transfer and Backup with destination read check
| Trancodes to over 20 useful formats including ProRes and DNxHD
| Automatic ColorMatrix detection and correction
| Automatic Smart Cropping
| Automatic Metadata Embed
| Automatic and Custom Timecode Embed
| Automatic and Custom Reel Name Embed
| Automatic and Custom Clip Title Embed
| Automatic and Custom Output Subfolder Names
| Gamma Setting
| Noise Reduction
| Highlight Recovery
| Timelapse for Image Sequence
| Metadata extraction to Text
| Encode for Delivery Options
Features in Detail:
Memory Card Offloader-
This is the default operating mode. Select just an Input Folder and Output Folder 1 and Autokode! will copy the media files contained within the source directory to the destination directory and then check to make sure that each destination file is readable after being transferred. Autokode! can automatically rename Output Folder subfolders during the process. It won’t overwrite existing same name files unless instructed to do so and Autokode! can also automatically repeat the process to a second destination for backup to an external drive.
(See below for supported file transfer formats.)
Autokode! can Transcode input files to edit friendly formats including ProRes 4444 (excl. alpha) and 8bit or 10bit DNxHD. Uncompressed formats if you work on a high performance machine, Motion JPEG options for easy editing on any machine, RGB formats for compositing work and Image Sequence options for post processing. Autokode! can also output PCM .wav files for processing with a preferred sound editor.
(See below for supported transcoding formats.)
Automatic ColorMatrix Conversion-
The native HD files from most DLSR’s are encoded with SD Matrix coefficients: BT.601. This can result in inaccurate color representation such as orange skin tones. Autokode! is smart enough to know if this is required on a per file basis and automatically corrects BT.601 to the HD standard BT.709 if necessary during transcode for pleasing skin tones and more accurate colors overall.
Above: Before and after examples of ColorMatrix Conversion with mouse rollover. The BT.601 ColorMatrix used by the Canon 5D Mark II is a contributing factor to the orange skin tones in this footage. Mouse over back and forth, you will notice the before image has a yellow/orange veil over its entirety but after processing from BT.601 to BT.709 with Autokode! the image is more neutral and more natural skin tones are allowed to come through. You can then adjust these more accurate colors in your editor.
Automatic Smart Cropping-
The dimensions of native FullHD files from some DLSR’s are in fact 1920×1088. Sometimes the extra 8 pixels are represented as black space along the bottom of the frame. Again, Autokode! is smart enough to know if this is required on a per file basis and automatically crops these files to 1920×1080 during Transcode if necessary.
The supported native DSLR .MOV files are flagged with a Gamma value in Metadata. Some playback software can have trouble interpreting this “Gamma Flag” correctly on some systems resulting in footage that looks grey or “washed out” or too dark because of “crushed blacks” in the shadows. Autokode! can set the original Gamma into the footage eliminating this problem and preventing guess work when viewing. A Custom Gamma value can also be used as an artistic choice for example to improve the detail in shadows or to add contrast.
As clean as DLSR video looks we know that it can still suffer from noise in some situations. Sometimes resulting from less than ideal lighting conditions, sometimes because of harsh environmental conditions such as heat, noise can be distracting in an otherwise acceptable shot. Autokode! has a Noise Reduction function to help to reduce noise for a cleaner image.
Above: The top image is for context, you can see this is the spinning wheel of a mountain bike. Below that are zoomed in before and after examples of the rim and spoke with mouse pointer rollover. Mouse over back and forth, you will notice the before image has some noise and the spoke is quite blurry but the after image is much cleaner and has more definiton.
Shooting on the run or in unpredictable lighting conditions can result in overexposed footage and it can be difficult to deal with. Autokode! can help here by adjusting only the highlight areas of the footage to correct some of that overexposure and bring balance back into an otherwise compromised shot. Highlight Recovery options are Low, Medium, High and Higher.
Above: Before and after examples of Highlight Recovery with mouse pointer rollover. Mouse over back and forth, you will notice the before image has some noise and the sky is overexposed but the after image has almost no noise and highlights are recovered whilst retaining the exisitng exposure level in the shadows.
Timelapse shots can be great for an intro, a segue or even an entire project but by its very nature there is no such thing as shooting a quick Timelapse. It usually involves having to set up a separate camera with a timer, so it requires a little forethought and post processing. If you hadn’t planned on using a Timelapse in your project but it starts to sound good as an afterthought Autokode! can output movie footage as a Timelapse Image Sequence at 1|2|3|5 frames per second.
When working without Timecode there is no way to know when a clip was shot. So when you import all your clips from even just a one day shoot you find yourself clicking back and forth between windows and checking the original files for the file info. Needless to say this is slow and frustrating. Autokode! automatically reads the time of shot from the native DLSR file, calculates and then embeds Timecode into the output file. This is the default behavior, other options are Current Time of Day Timecode at time of processing each file in a batch or a Custom Timecode starting point for processing an individual file. Timecode also helps when exporting EDL’s for editing, compositing and color correction within different software packages.
Autokode! embeds metadata. It automatically includes Reel Name and/or Clip Title metadata taken from the input file name. Optionally the Clip Title can be based on custom user input and the Reel Name can be a custom one based on User Input, Current Time of Day, Date of Shoot or a combination. In keeping with Reel Name naming best practice it accepts only uppercase alphabetical characters, numbers and underscores (_). Embedding Clip Title and Reel Name metadata into your footage allows you to keep track of the camera, time and date of shoot, artist that produced the shot etc. and when combined with Timecode gives you a powerful way to stay organized and focused on your creativity within your editing app. If it exists within the input file Autokode! will also automatically include “Copyright” and “Artist/Photographer” info. Autokode! can extract Metadata fields as a text file. This is not only interesting information but keep these files side by side with your video files they can also be used to conveniently reference who shot what on the day or production or to see which settings were used for each shot without opening an editing app. (See below for supported metadata fields.)
Most All Canon EOS DSLR’s,
Canon 500D|T1i|Kiss X3 (720p mode only)
Canon 550D|T2i|Kiss X4
Canon 1100D|T3|Kiss X50
Canon 600D|T3i|Kiss X5
Canon 650D|T4i|Kiss X6i
Canon 60D|60Da (60D users please read this article)
Canon 5D Mark II
Canon 5D Mark III
Canon 1D Mark IV
Canon EOS-1D X
Support for All-I and IPB input formats is now available. Please let us know your experience.
(Actually tested and confirmed working with files from Canon 1100D|600D|650D|60D|7D|5D Mark II|Canon 5D Mark III)
Compatible with Magic Lantern . Further Magic Lantern support is on the road map.
Most All Nikon DSLR’s,
(Actually tested and confirmed working with files from Nikon 3200|5100|7000|D800|D800E)
GoPro HDHero 1
GoPro HDHero 2
(Actually tested and confirmed working with files from Panasonic DMC-GH2|Fuji X100|GoPro HDHero1|GoPro HDHero2|Sony SLT-A77)
Please let us know if Autokode! works with a camera not listed here.
(640 x 480 (VGA) mode may work but is not supported)
Supported Input Video Formats-
All Above Native Camera Codecs
Supported Input Video Containers-
Supported File Transfer Extensions-
Supported Input Frame Rates-
Supported Output Formats-
Apple ProRes 4444|Apple ProRes 422 HQ|Apple ProRes 422|Apple ProRes 422 LT|Apple ProRes 422 Proxy|Avid DNxHD XHQ 10bit|Avid DNxHD HQ 10bit|Avid DNxHD HQ 8bit|Avid DNxHD STD 8bit|Avid DNxHD Proxy 8bit|Matrox MPEG-2 I-frame HD HQ|Matrox MPEG-2 I-frame HD STD|Matrox MPEG-2 I-frame HD Proxy|MotionJPEG HQ|MotionJPEG STD|MotionJPEG Proxy|QuickTime Animation RLE|Uncompressed ARGB|Uncompressed BGRA|Uncompressed RGBA|Uncompressed RGB24|Uncompressed YUV 10bit|Uncompressed YUV 8bit|Image Sequence DPX|Image Sequence TIFF|Image Sequence PNG|Audio PCM|Metadata TXT
Supported Output Containers-
Supported Metadata Embed Fields-
Clip Title|Reel Name|Copyright|Artist/Photographer
Supported Metadata Extraction Fields-
(Available Metadata fields are dependent on type of camera.)
Windows 7 32bit|64bit
(Should work with Windows XP or newer. Please let us know your experience.)
Faster the better
No special GPU required
Q. Why is there no Avid DNxHD Proxy output from 720p input files?
A. There is no specification for 720p Proxy files in the Avid DNxHD Whitepaper so 720p input files will not be processed when selecting “Avid DNxHD Proxy” output.
Q. Why are some output file dimensions 1920×1088 when selecting “No Change – Strip old & Embed new Metadata”?
A. The native dimensions of 1080p .MOV files from some Canon DSLR cameras are in fact 1920×1088 or “1088p”. The metadata embedded in these native files tells playback software to display the 1920×1088 file at 1920×1080. When we clean out the old metadata and embed the new metadata, we remove this metadata and we get a true representation of the file at its native dimensions. This only applies to the “No Change – Strip old & Embed new Metadata” option, the other output options all use the Smart Cropping algorithm during transcode to automatically correct the 1920×1088 input file to 1920×1080 output whilst leaving 720p files untouched so you always get a perfectly formatted file at the correct size.
* (Note that the example images above have NOT been intentionally exaggerated. There may be some unintentional exaggeration due to conversion for web and browser rendering but the before and after shots were converted to .PNG images for the web under exactly the same conditions, settings and with the same compression ratio. The only difference between the before and after image workflow is that the after images have had the specified process applied during transcode with Autokode! prior to conversion.)
Autokode! uses open source software components the source code of which can be found here.