<p>Most likely, the issue is with the codec you're trying to edit.  Temporal compression schemes require a lot of on-the-fly processing to decode.  Players are optimized to do this sequential decode, but by definition, NLE's are non-linear.</p>

<p>All of the talk you see about proxies is really about converting temporally compressed formats into either uncompressed or spatially compressed formats such as proRes, or Avid DNx.</p>

<p>Some modern hardware, combined with the right editing package and operating system, can handle temporally compressed codecs.  Some combinations don't work so well.  In cases where editing is cumbersome, video professionals will transcode to a format which is easier on the hardware.  This is still common practice in 2020 because even as computer processing power increases, so does the efficiency of compression algorithms, the computation necessary to decode them, and therefore latency in editing applications.  </p>

<p>H.265 HEVC, for example, is a relatively new codec, and is supported by a lot of consumer devices for recording.  It's popular because it's very efficient, supports larger resolutions and higher detail than older codecs at the same bitrate.  But this codec is notoriously difficult to decode on the fly, and is a prime candidate for proxy workflow.</p>

<p>See this wikipedia article for information on intraframe vs interframe codecs: <a href="https://en.wikipedia.org/wiki/Intra-frame_coding" rel="nofollow noreferrer">https://en.wikipedia.org/wiki/Intra-frame_coding</a></p>

<p>DaVinci Resolve does have some fairly hefty system requirements, though, and 8GB of ram does not meet the minimum system requirements as described in the <a href="https://www.blackmagicdesign.com/support/readme/00e0eb2c5ab94938a1e7088e17b35725" rel="nofollow noreferrer">release notes</a>.  </p>

CC BY-SA 4.0
2020-03-24T18:51:11.070Z
2020-03-24T19:00:48.540Z
2020-03-24T19:00:48.540Z
Jason Conrad
<p>Research how to use proxies. Proxies are copies of your original footage encoded at lower resolution, lower quality, or just in a less processor-intensive codec. You use them while you're working on your project, and then swap back the high quality files when you do your final export. A bit like offline and online video editing from the days when dinosaurs ruled the earth.</p>

<p>In your case for example, avoiding h.264 will probably speed things up. H.264 does a good job of making really small files at high visual quality, but it's awful for editing. So if you encode in an all-I-frame low-bandwidth codec, e.g. ProRes Proxy, or DNxHR LB the performance should increase markedly.</p>

<p>You can get away with much lower-powered hardware by using proxies, and you don't lose any quality in the process, because you go back to your originals at the end. A good guide, specific to the Resolve workflow, can be found <a href="https://workflow.frame.io/guide/resolve-proxies" rel="nofollow noreferrer">here</a>.</p>

CC BY-SA 4.0
2020-03-25T07:34:29.087Z
2020-03-25T07:34:29.087Z
stib
<p>I wanted to edit a video and encountered some severe lag and preview stuttering.</p>

<p>I started looking around on the internet, but I'm just not getting any definitive and practical information on anything.</p>

<p>You'll read about how you need at least 32 GB of RAM and a 4 figures CPU to edit at all.</p>

<p>And others on forums say they edit HD videos on old machines with 2 GB RAM with no issues. </p>

<p>I'm running Windows on a SSD drive with an Intel i5 quad core (2.8 GHz), 8 GB of RAM, and an NVIDIA 1050Ti 4 GB GPU.</p>

<p>The videos I'm trying to edit are 1920×1080 30 fps (captured with a USB capture card from PS4 and
encoded with Handbrake) they are 1-2 h long (I have many of these videos and I also put them together in a few videos that are like 10 hours long but I don't know if I should use them to edit; I don't know if it makes a difference if a have many small files or one huge one)</p>

<p>I used DaVinci Resolve, Lightworks, VSDC and Shotcut and every time its unusable. On shotcut just playing back a clip and looking through it works kinda ok most of the time but when I cut together some clips and want to see how it looks it starts to lag beyond being usable.</p>

<p>I know that Video editing takes a lot of horsepower, but is it really THAT much? 
I can't imagine that everyone, every student or just your average Joe who's doing their gaming montages and stuff for YouTube in their free time is sitting on a 2000 bucks high-end PC. </p>

<p>I've read about “Proxy files” for editing, but mostly when people are using 4k videos and even if not, creating lower quality versions every time for every video seems so unpractical.</p>

<p>I don't know, I really didn't think Video editing is so inaccessible. </p>

<p>To add to my confusion: </p>

<p>A view months ago I was editing videos with almost the same specs, the only difference, they were captured from switch, on the exact same PC. But at that time I was running Linux. And I used DaVinci Resolve and I don't remember having any issues at all. And I didn't use anything like proxy files or reducing playback quality, etc... 
I think maybe somethings wrong with my windows but with all that conflicting information I just don't know and I hope someone can help me here. </p>

<p>One thing I want to add: these Videos are kind of big. 2h long video with 8 GB, and they have a bitrate of around 9000.</p>

<p>I don't know much about video stuff, I know bitrates influence quality, but that's it, is 9000 much? Or can you reduce it without a huge quality loss?</p>

<p>Thank you very much!</p>

CC BY-SA 4.0
2020-03-24T19:07:31.113Z
9000 kbps is on the high side if you're talking about 1920x1080 h.264, but you could be talking about 4K or h.265, or a combination, or none of the above.  Plus, the level of detail and the amount of motion in the video will affect this number.  This is a discussion in and of itself, and is addressed multiple times elsewhere in this forum.
Jason Conrad
CC BY-SA 4.0
2020-04-02T13:12:58.833Z
Hi @Gin-Tonic - unlike discussion forums, here we need to focus on a specific question, so that specific answers can be posted for it. If you have new questions, use the Ask a Question button again. And if answers help you, you can upvote any that help, and accept the one that solved your issue.
Dr Mayhem
<video><editing><hardware><davinci-resolve><shotcut>
Do i really need a Super-Computer to edit Videos?
Gin-Tonic
# Do i really need a Super-Computer to edit Videos?

(Asked by: username_0 on 2020-03-24)

I wanted to edit a video and encountered some severe lag and preview stuttering.

I started looking around on the internet, but I'm just not getting any definitive and practical information on anything.

You'll read about how you need at least 32 GB of RAM and a 4 figures CPU to edit at all.

And others on forums say they edit HD videos on old machines with 2 GB RAM with no issues.

I'm running Windows on a SSD drive with an Intel i5 quad core (2.8 GHz), 8 GB of RAM, and an NVIDIA 1050Ti 4 GB GPU.

The videos I'm trying to edit are 1920×1080 30 fps (captured with a USB capture card from PS4 and
encoded with Handbrake) they are 1-2 h long (I have many of these videos and I also put them together in a few videos that are like 10 hours long but I don't know if I should use them to edit; I don't know if it makes a difference if a have many small files or one huge one)

I used DaVinci Resolve, Lightworks, VSDC and Shotcut and every time its unusable. On shotcut just playing back a clip and looking through it works kinda ok most of the time but when I cut together some clips and want to see how it looks it starts to lag beyond being usable.

I know that Video editing takes a lot of horsepower, but is it really THAT much?
I can't imagine that everyone, every student or just your average Joe who's doing their gaming montages and stuff for YouTube in their free time is sitting on a 2000 bucks high-end PC.

I've read about “Proxy files” for editing, but mostly when people are using 4k videos and even if not, creating lower quality versions every time for every video seems so unpractical.

I don't know, I really didn't think Video editing is so inaccessible.

To add to my confusion:

A view months ago I was editing videos with almost the same specs, the only difference, they were captured from switch, on the exact same PC. But at that time I was running Linux. And I used DaVinci Resolve and I don't remember having any issues at all. And I didn't use anything like proxy files or reducing playback quality, etc...
I think maybe somethings wrong with my windows but with all that conflicting information I just don't know and I hope someone can help me here.

One thing I want to add: these Videos are kind of big. 2h long video with 8 GB, and they have a bitrate of around 9000.

I don't know much about video stuff, I know bitrates influence quality, but that's it, is 9000 much? Or can you reduce it without a huge quality loss?

Thank you very much!

**Tags:** video, editing, hardware, davinci-resolve, shotcut

> **Comments:**
> **username_1**: 9000 kbps is on the high side if you're talking about 1920x1080 h.264, but you could be talking about 4K or h.265, or a combination, or none of the above.  Plus, the level of detail and the amount of motion in the video will affect this number.  This is a discussion in and of itself, and is addressed multiple times elsewhere in this forum.  
> **username_2**: Hi @username_0 - unlike discussion forums, here we need to focus on a specific question, so that specific answers can be posted for it. If you have new questions, use the Ask a Question button again. And if answers help you, you can upvote any that help, and accept the one that solved your issue.  

---

## 2 answers

### Answer by username_1 on 2020-03-24. Score: 2 | Accepted answer

Most likely, the issue is with the codec you're trying to edit. Temporal compression schemes require a lot of on-the-fly processing to decode. Players are optimized to do this sequential decode, but by definition, NLE's are non-linear.

All of the talk you see about proxies is really about converting temporally compressed formats into either uncompressed or spatially compressed formats such as proRes, or Avid DNx.

Some modern hardware, combined with the right editing package and operating system, can handle temporally compressed codecs. Some combinations don't work so well. In cases where editing is cumbersome, video professionals will transcode to a format which is easier on the hardware. This is still common practice in 2020 because even as computer processing power increases, so does the efficiency of compression algorithms, the computation necessary to decode them, and therefore latency in editing applications.

H.265 HEVC, for example, is a relatively new codec, and is supported by a lot of consumer devices for recording. It's popular because it's very efficient, supports larger resolutions and higher detail than older codecs at the same bitrate. But this codec is notoriously difficult to decode on the fly, and is a prime candidate for proxy workflow.

See this wikipedia article for information on intraframe vs interframe codecs: <https://en.wikipedia.org/wiki/Intra-frame_coding>

DaVinci Resolve does have some fairly hefty system requirements, though, and 8GB of ram does not meet the minimum system requirements as described in the [release notes](https://www.blackmagicdesign.com/support/readme/00e0eb2c5ab94938a1e7088e17b35725).


---

### Answer by username_3 on 2020-03-25. Score: 2

Research how to use proxies. Proxies are copies of your original footage encoded at lower resolution, lower quality, or just in a less processor-intensive codec. You use them while you're working on your project, and then swap back the high quality files when you do your final export. A bit like offline and online video editing from the days when dinosaurs ruled the earth.

In your case for example, avoiding h.264 will probably speed things up. H.264 does a good job of making really small files at high visual quality, but it's awful for editing. So if you encode in an all-I-frame low-bandwidth codec, e.g. ProRes Proxy, or DNxHR LB the performance should increase markedly.

You can get away with much lower-powered hardware by using proxies, and you don't lose any quality in the process, because you go back to your originals at the end. A good guide, specific to the Resolve workflow, can be found [here](https://workflow.frame.io/guide/resolve-proxies).


---

