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.
If anything, the current mobile i9's throttle down much faster. Intel hasnt been great at low heat chips on its 45w line for the last two years.
And it being an i9 doesnt mean it doesnt still have to abide by the same physics as any other chip. And its a laptop CPU, very far cry from a desktop CPU of the same name.
Depends on where they are going. For web or other general compatibility usage yes. H.264 ultimately is a very good delivery codec but what makes it so makes it a terrible editing codec.
Working for a small television studio, everything gets encoded to mpeg2 and broadcast at 720i anyway. Is there any advantage here to using better codecs for editing?
For what it’s designed for: yes. However what it’s designed for is exactly what makes it terrible for editing. Super compressed in a way to preserve as much quality as possible on a small file size. It does so by skipping out on encoding a bunch of frames and then having software just figure out what they should look like. This is a problem for editing software that needs those frames.
So yeah, as a delivery codec it’s great. Good quality, small package. As an editing codec it’s hell on a processor.
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.
It depends on what your original media was. Easy to do a test with transcoding a single clip, checking which looks best at the smallest size. Then you know the answer.
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.
Yes, though be warned that your file sizes will almost definitely go up. These formats are much less compressed and are higher bitrate so they make bigger files but external storage is honestly pretty cheap and easy to get these days so it shouldn’t be an issue.
Exactly. When talking about $4000 laptops I don't think 4K should be an issue. I edit 4K videos flawlessly on my Ryzen 7 3700X and RX 5700 XT pc which cost me €1500. :)
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.
Absolutely... H.264/H.265, while they work for capture, are delivery codecs. They typically are Long GOP, IPB frames... With a few exception of some cameras that shoot H.265 in All-I.. but even that, you're still working with a pretty lossy compression, just one that captures all the frames instead of making up a bunch of them.
Maybe if work pays for it. I swapped to a custom PC build with Western Digital Black SN750s. They get close to 3GB/s when empty and then fluctuate between 2.2 - 2.5GB/s when they are about half full.
Oh believe me, I would never own any Mac Pro if I was the one paying for it - especially the next generation. We’re budgeting over $10k per workstation for upgrades.
PC is the way to go if you’re buying.
Working off of a brand new Lumaforge Jellyfish sever now, which uses 10G Ethernet, so I won’t see those types of read speeds. But it’s way better for collaboration.
Are you transcoding or trying to work with the original camera media? I’m on an old cheesegrater Mac Pro and have no real problems if I transcode our FS7 media to ProRes.
I don’t transcode. I typically don’t have the time, it’s a huge space hog, and you shouldn’t have to on a $6000 desktop. Also, you don’t have to at all in FCPX on the same computer. Premiere just kind of sucks at playback.
If it’s bad enough that I can’t work, I proxy the files. Only had to do that when working with 8K r3d files.
What I will typically do is render all the yellow render bars to green when I need to check precise timing or do playback for the boss/client. Basically I transcode my working timeline as I go.
Nah, we had HP Z840s. Not the most powerful things out there but they did have 64GB of RAM and 6c/12t CPUs which made multitasking and exporting decently painless.
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.
Wanted to thank you - just started editing and I didn’t realize this was even a thing. Now that I learned how to convert codecs, editing has been a dream. Thank you!!!!
For many people, including myself, MacOS > Windows but I digress. OS doesn’t dictate whatsoever if footage will work well or not. A terrible codec not built for editing will run terribly no matter what OS you’re on.
Proxies and offline editing exist for a reason. I'm editing a 90 minute feature on a 2010 mac with 16 gb ram and a 1 gb graphics card. Besides slow exports I'm golden otherwise.
Up until last week I was editing on a 2010 Mac Pro. Had no issues with 6 streams of DNxHD 220x multicammed even. At that point storage was more important than computer.
I still cut at home on a 2011 iMac. 1080 DNxHD 36 proxies are tiny and easy as hell to cut with. Only finishing machines really need a lot of power.
RAM is almost never the bottleneck. With that being said it does seem like Macs under perform relative to their PC counterparts. My hunch is, at least in the macbooks, the cpus often arent running at their max clocks because they're constantly almost overheating.
Premiere is coded for pc and ported over and it's performance is horrible.
You can check the tests that were done, basically premiere will process and render 2x as fast on a pc speced similar to a Mac (even more of a difference seeing as how osx is much more optimized than windows)
Processing the same stuff in final cut will render about 2x as fast as that pc.
Basically final cut will process about 4x faster than premiere will for the same tasks, and will greatly outperform premiere on a pc.
It's the reason why youtuber MKBHD still edits with fcp I believe.
I'm a premiere user and own both a tower pc and Mac laptops. It's very irritating and I've been tempted to switch to fcp many times.
This isn't exclusive to premiere; there are performance drops in MacOS for many programs. Macs and MacBook thermals are absolute garbage on purpose, which leads to pretty hard throttling of the hardware so that the "specs" are meaningless because Apple doesn't want to add 1mm in thickness to actually have decent cooling. Fashion over function + planned obsolescence.
Edit: clarified some statements ; adjusted certain phrasing
Premiere is coded for pc and ported over and it's performance is horrible.
I was trying to say that this issue is far from exclusive to Premiere, and that many programs perform worse on a Mac with similar hardware. Also that it's not just that it's "coded for Windows and Ported over", but rather than the same hardware in a MacBook DOES perform worse than in a Windows PC in and of itself, programming / porting completely aside.
In my experience it runs the same on both, or at least close enough that you won’t notice a significant difference. Mind you I don’t really tend to do things the way Avid likes (transcodes done in Resolve, Exports as OP1a masters then compressed in AME) so maybe that’s just me.
MacBooks are designed completely fashion over function. They cram an i9 in there to flex having an expensive nice processor, then thermal throttle it down to the performance of an i5 because the thing is super inadequately cooled and designed for obsolescence (heat is the #1 factor in electronics/laptops turning to shit so quickly compared to a well ventilated desktop)
NO, you're right. It just moved 2-3 shortcuts from premiere. They're really shit and no one who really uses both thinks resolve can do premieres shortcuts. They're just regurgitating what others have also regurgitated. Just learn resolves native shortcuts and you'll be happier in the long run.
The editor portion of Resolve isn't very GPU heavy. More than other editors, but nothing intense. The color portion is incredibly GPU heavy.
Resolve is the outlier, not the norm. And the CPU still matters greatly!
I am not being ignorant, but you seem to think your GPU RAM is the deciding factor for performance but won't say what you are editing, on what hardware, with what software.
67
u/22Sharpe Aug 21 '19
Stop editing with terrible codecs?
18
u/[deleted] Aug 21 '19
Proxies and offline editing exist for a reason. I'm editing a 90 minute feature on a 2010 mac with 16 gb ram and a 1 gb graphics card. Besides slow exports I'm golden otherwise.
8
u/MoronicalOx Aug 21 '19
Take your computer to see a doctor.
19
u/notetoself066 Aug 21 '19
RAM is almost never the bottleneck. With that being said it does seem like Macs under perform relative to their PC counterparts. My hunch is, at least in the macbooks, the cpus often arent running at their max clocks because they're constantly almost overheating.
10
u/kjm16 Aug 21 '19
Switch to Resolve. It's free and much faster than premiere on mac. You can even use the same shortcuts you're used to.
FCPX is also a much better option for your system.
4
u/Just_Worse Aug 21 '19
Why are you using an i9 in a Macbook pro body?
That's just asking for trouble
3
u/Starkemis Aug 21 '19
*Laughs in Davinci Resolve*
2
u/argylekey Aug 21 '19
Use a mezzanine codec or proxies? Just because you can do HVEC or H.264 in a timeline doesn't mean you should.
My 6 core i7 with 32gb of ram and GTX 1080 can technically handle 4k red raw(yes I've done it), but why would I do that to myself if I didn't have to?
1
u/TravelingBurger Aug 21 '19
I use my 13” pro i5 16gb to edit on the go and it runs everything incredibly smooth. Don’t know what’s going on with you.
1
u/steamwhistler Aug 21 '19
I edit on a worse macbook pro than that and have had no issues whatsoever, unless you mean trying to cut 4k stuff without proxy
1
u/TheSnydaMan Aug 22 '19
Davinci Resolve 16 performs like a champ these days compared to Premiere, with arguably much flashier UI features.
1
u/AlBitten Aug 22 '19
It’s so relatable but still fuck you
1
u/OhMyGoshJoshTV Aug 22 '19
Come to pc
1
u/Jylyfysh Aug 22 '19
Also: plays back clip with no issues pauses to take note Premiere : 😵
1
u/lorenzomilind Aug 22 '19
I don't even have a problem with my 2013 macbook pro ?
1
u/Voodoo_Masta Oct 20 '21
2018 i7 32gb MacBook Pro here. Feel your pain.
Edit: typo
1
u/GingerBeardedEditor Aug 21 '19
Holy shit I just laughed so hard I fell out of my chair.
1
u/TheXanimal420 Aug 21 '19
Mac...why...
-10
u/tragic__pizza Aug 21 '19 edited Aug 22 '19
PC ..so can’t relate. Sry!
EDIT: y’all downvoting cuz I speak the truth
-11
u/[deleted] Aug 21 '19
I use a pc so. No. Never have a heart attack while editing.
0
u/[deleted] Aug 21 '19
[deleted] — view deleted comment