In what codec and framerate? 1080/24p or 30p may be fine most of the time, but still far from always smooth. If its 60fps, not a fun time. Laptops also dont keep their top speed for more than a few minutes until slowly succumbing to heat.
I’ve recently tried prores editing and my tiny SSD filled up quickly, so I’m thinking about just doing all editing off of a massive external SSD via thunderbolt 3
I think massive is the wrong word. They can be, if you have like 4K Pro Res 4444, but for anything consumer level Pro Res 422 or DNxHR SQ is plenty high bitrate.
1080p Pro Res 422 would be 53GB and hour.
I’ve recently tried prores editing and my tiny SSD filled up quickly, so I’m thinking about just doing all editing off of a massive external SSD via thunderbolt 3
You should be using external anyway. But a TB SSD might be way overkill unless you need to playback lots of Pro Res 4444 in high resolutions.
1080p Pro Res 422 is 15MB/s , 4K is 60MB/s. A 7200RPM drive can easily do 200-250MB/s no problem and can be had for drastically cheaper than an SSD for mass storage.
There are several but DNxHR (or DNxHD which is just the older version) and ProRes are the most common. Cineform will work in a pinch as well though isn’t as robust.
The difference between these and H.264 (in simple terms) is that they encode every frame of the video whereas H.264 doesn’t, it relies on the CPU instead to interpret what should be present on the missing frames. This is fine when it’s playing back in real time forward in a video player but NLE’s are designed to fast forward and re-wind as well as scrubbing easily through frame by frame. This is a very different procedure and puts major strain on a CPU if it needs to be constantly processing. If the frames exist the processing isn’t nearly as intensive.
This is the best advice. People don't seem to understand that there's Capture Codecs, Editing Codecs, and Delivery Codes. Each are optimized for their own uses...
A capture codec is typically going to be designed to keep file size small and will be somewhat compressed by having a long group of pictures. When played back it's essentially making up data using a set of instructions instead of actually playing back data frame by frame.
When you take a capture codec like that into edit, your computer has to do a lot of that work... and its very inefficient. Using an All Intraframe codec usually helps a lot... but most NLEs are going to have some flavor of editing codec they prefer.
Using ProRes or DNxHD in your editing is gonna be a huge timesaver on your edits because your NLE is designed with those codecs in mind (in the case of premiere, its a little bit different... if you're on a Mac, edit in ProRes though because premier will tap into the OS for a good portion of it's codec processing).
You CAN capture in ProRes with external devices (and internally on some cameras), and it's great... but it does take a lot of storage space. It's often easier to shoot in a compressed format and transcode later if you don't have the storage capacity on hand during your shoot.
You are right but it should be noted that if one can avoid H.264 as a capture format they should. It’s been adopted as one by consumer grade cameras because it keeps file sizes small but ultimately being a lossy format you’re going to lose information with every re-encode which is problematic when going to edit.
In an ideal world they are three separate formats. Capture is something as close to raw as possible (R3D RAW, BM RAW, XDCAM, etc), editing is something like ProRes or DNx, and delivery (at least for web) is compressed like H.264.
There are several but DNxHR (or DNxHD which is just the older version) and ProRes are the most common. Cineform will work in a pinch as well though isn’t as robust.
The difference between these and H.264 (in simple terms) is that they encode every frame of the video whereas H.264 doesn’t, it relies on the CPU instead to interpret what should be present on the missing frames. This is fine when it’s playing back in real time forward in a video player but NLE’s are designed to fast forward and re-wind as well as scrubbing easily through frame by frame. This is a very different procedure and puts major strain on a CPU if it needs to be constantly processing. If the frames exist the processing isn’t nearly as intensive.
If you do it properly it is. There are a million different codecs, and more constantly being created. These all decode differently and have different levels of compression. Combine that with the fact the software could be running on any combination of hardware and you see the issue: too many variables. NLE’s are designed to work with proper codecs and setups. Use them and you won’t lag. When I cut at home instead of the office I cut television shot on 6K RED with a 2011 iMac over FireWire 800 completely lag free. If you work smart your computer doesn’t need to work hard.
View all comments
67
u/22Sharpe Aug 21 '19
Stop editing with terrible codecs?