[ Read my disclosure statement on product reviews here. ]
ClipWrap, from Divergent Media, is legendary amongst video editors for its ability to repackage AVCHD and HDV media into formats that are much friendlier to edit.
However, on June 28, 2016, Divergent Media announced it was officially retiring its popular ClipWrap application; and absorbing its features into the brand-new EditReady application. EditReady includes all of the features and capabilities of ClipWrap – and adds significantly more value for filmmakers – all for the same price.
With the new release, the team at Divergent Media sent me an evaluation copy to use for this review.
The days of shooting, editing and exporting a single video format for a project are long gone. We are awash in competing video codecs and standards. EditReady is designed to take camera native files and convert them into a common format (called a “mezzanine format”) prior to editing, allowing you to standardize on one video format for editing and mastering.
EditReady is a transcoding utility for video files. It will rewrap or transcode any MXF, MTS (AVCHD), M2T (HDV), MP4, or QuickTime (MOV) file and convert it into Apple ProRes, Avid DNxHD/HR, or H.264 output.
It supports popular editing formats – ProRes, DNxHD and rewrapping – and non-linear editors: Final Cut Pro 7, Final Cut Pro X, Avid Media Composer, Adobe Premiere Pro, and Apple iMovie. It also supports applying LUTs (color Look-Up Tables) to your footage prior to conversion.
Key features include: changing clip metadata, including timecode, file renaming, format conversion, batch processing and an easy-to-use interface.
The software ships with a 31-page PDF user manual and a free trial is available.
Developer: Divergent Media
MSRP: $49.95 (Upgrade pricing is available for ClipWrap users)
I’ve been writing about video compression and testing compression speeds for a long time. Video compression is a necessary evil; very few people understand it and even fewer enjoy doing it. However, compression is a necessary and vital part of video production today.
EditReady is designed to convert files prior to editing into a single, high-quality video format. While you can use it at the end of the process to create files for YouTube et al, that is not how it was designed.
This conversion process, called “transcoding,” allows you or an assistant to optimize files without tying up an editing system.
“EditReady accepts files in the QuickTime MOV, MP4 and M4V formats, as well as MXF files from most cameras that record to the MXF format. In addition, it supports files in the AVCHD and HDV formats, which generally use the M2T, MTS and M2TS extensions. In general, if a file plays in QuickTime Player (for MOV/MP4/M4V files) or VLC (for MXF, M2T and MTS files), it’ll play in EditReady.” [EditReady User Manual]
EditReady must be purchased from the Divergent Media website. When first downloaded, it runs in Trial mode, allowing you to compress the first minute of a file. Purchasing the software provides a serial number which is used to unlock the software.
Installation was straight-forward and took me about a minute and a half.
Here’s the opening screen, which can be resized as necessary.
To import files either use File > Open or simply drag the files or folders into the left panel. Here, I’m dragging a folder containing 26 AVCHD/MTS files into EditReady. Note that I’m dragging the entire folder, not just individual clips.
You can display the footage as either a list or thumbnails. (These images courtesy of Joe Centeno and his backyard.) This is the list view.
The default transcode settings are set to ProRes 422, with uncompressed audio.
However, there are eleven preset output options. Remember, EditReady is designed for prepping files prior to editing, not final compression before distribution. For this reason, the presets are optimized for editing.
I really like that the default setting for audio is uncompressed. This is a very smart choice.
Clicking the additional options Edit button allows you to apply a LUT to the footage prior to conversion, retime footage, scale footage, adjust H.264 settings or remove unused audio tracks.
You can learn more about a clip by clicking the triangle icon in the top right corner.
To test the speed of transcoding, I’ll time how long it takes EditReady to convert these 26 clips into ProRes 422 using a 2014 27″ iMac with 32 GB of RAM.
EditReady was finished in exactly three minutes.
Apple Compressor could not open these files, though Final Cut Pro X could.
Importing these files in Adobe Media Encoder generated this error message. Installing the Dolby codec took seconds…
Then this error message appeared. I’ve never seen this before, but I assume this is AME ignoring the metadata associated with each source clip.
Unlike EditReady, which has one transcode setting that applies to all the files, AME has one setting per each clip. This is more flexible, but if all you need to do is prep your files for editing, resetting this setting takes time – especially if you have a lot of clips to transcode. This can be especially irksome if you had the wrong setting applied when the clips were imported.
NOTE: It took me longer to reset all these compression settings and repoint the destination than it did for Edit Ready to transcode these files.
SPECIAL NOTE ON FINAL CUT PRO X AND PREMIERE PRO
Both Final Cut Pro X and Premiere Pro CC can open and edit these files natively. FCP X can also automatically transcode them into ProRes 422 in the background while you are editing. Why should we consider using EditReady?
There are three potential answers:
A NOTE ON LUTS
“Click the “Add LUT” icon to apply a LUT to your file during playback. This allows you to quickly preview any conversions you’d like to apply. Keep in mind that LUTs can be compute-intensive, particularly on 4K files. Slower computers (or computers with slower graphics cards) may have trouble with realtime playback.” [EditReady User Manual]
OTHER COOL STUFF
The converted file name can be altered using a template consisting of the source file name plus any combination of: automatically incremented clip numbers, creation date, image dimensions OR you can add additional values from your file’s metadata to the file naming scheme. For example, a Reel name or even the folder the file is stored in.
This ability to selectively use any of the metadata associated with a clip as part of the file name is a big deal.
You can easily monitor the conversion status of each clip – green is done, blue is in-process. Conversions can be paused or canceled using a menu option, though an on-screen “ALL STOP” button would be helpful for panic situations.
EditReady includes a metadata editor which allows you to change metadata associated with each clip or globally for all clips. A HUGE benefit of this is that you are able to change the starting timecode for a clip before converting it!
Metadata may include camera settings like F-Stop, Iris, and Shutter, as well as items like Location (if your camera has GPS), media serial numbers, or even diagnostic data.
You can flag clips – say as a “Favorite” – then change metadata only for flagged clips, or just convert the flagged clips. This means that you can quickly select which clips to convert without wasting space on clips you’ll never use.
You can open multiple EditReady windows so you can compress files from different sources using different settings all at the same time.
EditReady also supports full-screen mode, though on a 27″ iMac its a bit over-whelming.
EditReady is not a resource hog. The CPUs were busy, but I still had plenty of available CPU power during conversion for other applications to use.
NOTE: The reason the CPU load is so low is that EditReady uses QuickSync hardware acceleration, which is part of the Intel chipset. This section of the chip does not report its usage in Activity Monitor. Because of this EditReady is able to maximize performance, while the general purpose sections of the CPU are still idle for use by other processes.
Edit Ready is very RAM efficient, leaving plenty of overhead for other software.
AN INTERVIEW WITH MIKE WOODWORTH
Mike Woodworth is the CEO and Lead Developer for Divergent Media. As I was writing this review, I sent Mike a few questions to learn more about EditReady. Here is his response.
Larry: We already have a number of video compression utilities, why did you create EditReady?
Mike: We surveyed the market and found the compression tools that existed focus on general purpose transcoding. From the popularity of ClipWrap, we knew there was a market for tools tailor made for workflow specific use cases. More and more cameras are shooting in heavily compressed interframe codecs that are poorly suited for editorial. In addition, its becoming rarer to work on a production with a single camera make or model – we’re seeing multiple camera types, frame sizes and codecs being intercut. We wanted to make a tool for quickly converting a pile of disparate footage into a single clean, organized, well named, edit-ready format. So we set about trying to make a transcoder/ re-wrapper tool for prepping footage for editorial.
Larry: Who do you see as the principle market for the software?
Mike: We target professional and prosumer video creators. People who plan to edit their content, produce dailies, make H.264 layoffs for the web.
Larry: Does this replace ClipWrap?
Mike: Yes, we’ve ported all the camera support from ClipWrap. As an added bonus, a newer foundation which leverages GPU based color science and hardware accelerated encode and decodes gives us a 3x speedup for HDV and AVCHD content. Add in thumbnails, preview, metadata editing, and LUT-based color correction, and we think its an excellent replacement for ClipWrap.
Larry: For people that already own Adobe Media Encoder or Apple Compressor, what do they get with EditReady that they don’t already have?
Mike: The advantage of making such a laser-focused product is how simple we can make the process. The UI is designed to make it super easy to take disparate source media and transcode everything into a single format for editing. This can save users a ton of time and frustration fiddling with settings. In addition, we’ve added other prep-for-edit tasks such as metadata editing and review.
Larry: For people who refuse to read manuals, what secret tip about the software should they know about?
Mike: I think the features people are most surprised by are the things EditReady does for you automatically. Compression software has traditionally barraged users with settings and options they have to properly configure given their source media to achieve a quality output. Because we do all of that automatically based on the metadata we parse within the source media – without user intervention – its common for customers to assume we are somehow more basic than other apps.
In a similar vein, many users are not aware of our camera file parsing. If you drop a folder of camera original clips onto the app, EditReady will automatically join spanned clips into a single seamless movie.
Larry: Is there a quality difference, or just a speed difference, when using EditReady compared to other compression software?
Mike: It depends which apps you are comparing us to. Many of the other transcoding solutions have subpar color science or unlicensed ProRes implementation. We make sure we aren’t altering your image during transcode, and that we choose a code path that preserves the most information and color detail possible for your source and destination formats.
And by choosing the newest foundation to build upon, we are able to achieve this while also being the fastest tool on the market.
Larry: Can EditReady be automated; i.e. droplets or watch folders or batch lists?
Mike: We don’t offer droplets or watch folders out of the box, but we do have command line support for all the functionality. So users can roll their own workflow automations.
Larry: What feature are you most proud/excited about in EditReady?
Mike: Users are always amazed how fast EditReady is. Both the speed of actual file transcodes, and how quickly they can launch the app and setup a batch to transcode. We really pride ourselves on how painless we make the process.
I am impressed with EditReady. While I haven’t tested its speed extensively, it feels very fast. It is ideally suited for organizing the mess of video formats that every editor faces on a daily basis into something manageable for their video editing software.
EditReady is a fast, flexible, simple to use video converter, created by the same folks that created ClipWrap. If you are looking for a tool to help speed your editing, provide greater flexibility with clip naming, change the timecode of a source clip, or simplify media management, you need to take a long look at EditReady.
12 Responses to Product Review: EditReady from Divergent Media
This is probably the one product that I use after nearly every shoot to organize footage especially with multicam shoots. The renaming feature enables me to identify each camera position easily after the shoot instead of asking my camera people to change their naming within their cameras. I then direct each camera’s transcodes into separate folders so when FCPX imports the folders I get automatic keyword collections.
The renaming function is also helpful when you are giving the footage to the client. In FCPX imported footage goes into a hidden folder within the library (not hard to get to) but using EditReady puts the footage wherever you want.
The one option I would like to point out is the “Join Selected Clips” function that is invaluable to people who use cameras that split long files on the card but don’t provide linkage info for the editing programs. With the JVC pro cameras I use, I can end up with an hour of continuous footage in 5 separate files. EditReady gives me the ability to fuse the clips together into one file.
I rarely transcode to ProRes before editing, instead I just re-wrap and if you want to see speed, try that.
As a disclaimer, many years ago I met Mike Woodworth at a trade show and became a beta tester for the wonderful ScopeBox program (I believe I was helpful in figuring out how to talk to JVC cameras and decks despite their poorly programmed FireWire protocol) and later a beta tester for ClipWrap. EditReady is a very, very useful program and I recommend that all editors look into it and at least try it.
You may want to have a look at Kyno from Lesspain Software too – more expensive, but also more capable.
I tested both for “Digital Production” (Munich)
As most of us have been forced to develop a Mac exit strategy, it is a shame divergent ignore the pro PC user. I find Cliptoolz Convert a useful alternative, but would love the control over metadata Editready can give. It may be interesting to also see if Prelude fills in some of this functionality.
p.s. Scopebox for Windows please!
Many of don’t need a Mac exit strategy. The platform and FCPX is better than any PC alternative for us. If you, for probably very good reasons – we don’t all have the same needs, feel that PC is the way to go, good luck and keep us informed.
I second this request! I’ve been using Clipwrap/ EditReady for ages on Mac and sorely miss it since switching to PC. Haven’t found a good alternative yet.
This is a nice piece of software, but this article contains two statements that I want to comment on.
“Both Final Cut Pro X and Premiere Pro CC can open and edit these files natively. FCP X can also automatically transcode them into ProRes 422 in the background while you are editing.”
So can Premiere Pro in the latest version, using the new Ingest feature.
“There is no question that editing ProRes or DNxHD files will provide faster rendering and exporting in your NLE, while allowing greater range in color grading than editing AVCHD or H.264 files natively.”
You’re right about the faster exports and renders – but the footage will NOT allow grater range in color grading after transcoding. Modern software like FCPX and Premiere work in 32-bit color (that’s 32 bits per channel, not 32 total) and a transcode will not do anything to improve the result. This is very different from how FCP7 used to work.
I wrote a blog entry here a few months ago to explain this.
Also, Adobe’s own Karl Soulé explains it very well here. http://blogs.adobe.com/VideoRoad/2010/06/understanding_color_processing.html
Thanks for the article Larry. I use EditReady regularly, however one feature that really is missing that for my workflow is uniquely naming files. This helps for searching for files at the Finder level and in FCP X, and in the case of AVCHD clips – makes sure that every clip name from card to card is unique and not named clip 1, clip 2 etc.
That being said, I think this is a major shortcoming of FCP X and EditReady. FCP X can rename clips but it’s only in the FCP X database and not at the Finder level like FCP 7 could do. EditReady can output nomenclature naming, but you have to do Finder level folder separation and workarounds to have consecutive naming between cards. Keep in mind that I try not to abstract my files into different folders. I keep things simple and name the files uniquely all at the same folder level and let FCP X (or whatever NLE) handle the folder, bin, or keyword organization; especially helpful for relinking (though I know FCP X doesn’t really have that problem due to symlinks).
I wrote to EditReady about this. Otherwise it is very useful. See below what I sent them in May and their reply:
“I’d like to be able add multiple cards to one window for processing; particularly using the auto increment feature. I’d also like to set the increment number.
Currently I have to have a separate window for each card, set the output to separate folders (so the file names in the first folder won’t be overwritten), then use the Mac app called Renamer to go in and rename the files in a new incremental order; folder two continuing from where folder one left off in the file names. Then I repeat this process for addition shoot days and cards.
Being able to add multiple cards to one window would alleviate having to do this.
Reply from EditReady team member:
“You could potentially use other metadata (like a reel name) in the file naming to prevent overwrite. Or you can tell EditReady to say your converted files back to the same folder as the source files, to prevent overwriting. We’re continuing to explore other ways of presenting those types of interfaces.”
Good thoughts, thanks for sharing.
I use a renaming utility (Renamer, Incredible Bee Ltd) to rename clips before transcoding. I agree it would be nice if EditReady could eliminate that step in my workflow.
I just came across this post while searching for info about AVCHD re-wrappers. I really enjoyed the review but the author seems to be combining “transcoding” and “re-wrapping” as one thing and I thought these were two very different actions. Transcoding makes a duplicate of a file while re-wrapping basically takes the original file and changes it to another format. If I have this wrong please let me know. Now having said all that, is EditReady a transcoder or re-wrapper? If both, how do you choose which option you want?
As I understand it, you are sorta right. Mostly.
Transcoding takes the master file and converts it into another video format. Re-wrapping takes the original file and inserts it into a QuickTime format, without changing the original media.
Both operations create separate files, neither transcoding nor re-wrapping alters the original camera master. And, not all files can be re-wrapped.
So, if your format supports re-wrapping, that MAY be a good choice – however, many formats that can be re-wrapped are mathematically hard to edit on slower systems.
My general advice is to transcode, because that way you always know what you are getting. However, as with all media projects, run tests before the deadlines get too tight to see if rewrapping can work for your project. There is NOTHING wrong with rewrapping, except that some codecs that are re-wrappable are harder to edit than others.
“Unlike EditReady, which has one transcode setting that applies to all the files, AME has one setting per each clip. This is more flexible, but if all you need to do is prep your files for editing, resetting this setting takes time – especially if you have a lot of clips to transcode. This can be especially irksome if you had the wrong setting applied when the clips were imported.
NOTE: It took me longer to reset all these compression settings and repoint the destination than it did for Edit Ready to transcode these files.”
Not knowing details about how to accomplish something in a software application can be extremely frustrating. I thought I’d comment on the snippet above for your benefit and the benefit of your readers.
I have been using EditReady now quite a bit and just barely got familiar with the custom preset setting for my H.264 transcodes wich was very helpful. I have also been using Media Encoder a lot and I was overjoyed when I figured out how to solve both the issues you encountered:
1- You can set the output folder before you drag any files into Media Encoder. Just go to Preferences > General, check “Specify output file destination”, click browse and choose your output folder.
2- If you drag just the first of many files into Media Encoder, then set your codec, etc., then drag all the rest of the files and they will have the same settings as the first.
3- If you have all the files in the Media Encoder que already, just select them all (or a subset of them) (Command-A). Now change the folder or encode settings for one of them, and all the highlighted/selected items will change to those settings as well.
This is no harder than changing settings in EditReady. Especially when you save your settings as presets. This is something I have not found yet in EditReady – the ability to save custom presets. So, it takes me longer to change the custom settings in EditReady (and introduces the possibility of making a mistake in the settings I want) than it does to recall a saved preset in Media Encoder, but EditReady encodes faster.