<p>The above answer by Adam is not really accurate...</p>

<p>There are different bottlenecks to consider. </p>

<p><strong>Bitrate x Time = Size of File.</strong> means <strong>Higher Bitrate requires Faster Hard Drives</strong></p>

<p><strong>Compression / Codec / Ratio of Compression</strong> is either processor intensive, gpu processor intensive, or both (depending on your GPU/editing software). Adobe for example, makes use of NVidia's CUDA cores for faster decompression and encoding of compressed files. </p>

<p>High Bitrate, such as lossless, uncompressed, etc, will require high throughput (Fast Hard Disks, from SSD to SAS RAID/Etc) to handle the data rate of the video file to play in real time. </p>

<p>However, uncompressed video requires less CPU processing power, because the CPU does not have to "uncompress" the file. </p>

<p>If you are editing for example, H.264, highly compressed at a variable bit rate, your bottle neck would be your CPU and GPU (if you are using a system which uses your GPU for video overlay output). </p>

<p><strong>In general:</strong>  If you have a fast RAID HDD setup, editing uncompressed is far smoother, more responsive, quicker to render especially, than working with a compressed codec. EVEN with a slower CPU/GPU - simply because the CPU/GPU does very little work / calculations to decode the file. </p>

<p>If you are working off a single spinning drive, you'll be limited to the 110 MB/s bottleneck (bi directional) so having a faster CPU and GPU would be the way to go with compressed files. </p>

<p>If you have 2 SSD's of equal size, and can SATA port them to your Motherboard, create a RAID 0 and you should get roughly 1 GB/S read speed. I have 4 SSDs in RAID ZERO on an Intel RAID card, and get 4 GB/s - zero lag at all. </p>

CC BY-SA 3.0
2017-02-08T12:51:50.113Z
To clarify, i'm referring to "playing or scrubbing" through footage while i'm editing it. Assuming a constant frame-rate, and constant bit-rate video. In my case i am using MP4 clips.  The harddrive things makes sense, but i have an SSD so not really worried about that aspect of it, nor am i worried about space. thank you for your answer
Joseph M Cutcher III
CC BY-SA 3.0
2017-02-18T09:17:25.697Z
If you are editing MP4 the file is compressed, likely in H.264. So your responsiveness in terms of scrubbing, or using a jog shuttle, would be improved by 1.) CPU, both fastest clock speed and max cores. 2.) GPU that supports MP4 decompression with as high a clockspeed as possible, and if Nvidia based, max CUDA cores.
McFlySoHigh
CC BY-SA 4.0
2019-11-10T16:56:02.167Z
What about software such as "adobe after effect" or "davinci resolve - fusion" , and specially the second, they use high amount of ram, how much impact graphic card bitrate have on them?
Hassan Faghihi
CC BY-SA 4.0
2019-11-10T16:57:48.190Z
How much bitrate is needed or enough
Hassan Faghihi
CC BY-SA 3.0
2017-02-07T15:42:20.747Z
2017-02-07T15:42:20.747Z
McFlySoHigh
<p>Bitrate is the amount of information contained in the video file. now I think the question is a bit vague. I assume you mean which will affect your computer more for editing.</p>

<p>More bitrate will mean a more beefy computer (CPU, GPU and HDD passthrough) to edit so it can handle the files.</p>

<p>Now if you have a high bitrate file and it is struggeling to play due to computer specs you can convert it to a proxy file which is a low bitrate of the file to make it easier to edit and then relink it later to the high bitrate file for final export.</p>

<p>Hope that helps</p>

CC BY-SA 3.0
2017-02-07T09:06:21.187Z
2017-02-07T09:06:21.187Z
Adam Mann Pro
<p>If will a high bitrate video be easier or harder on a video editor than a low bitrate video?</p>

CC BY-SA 3.0
2017-06-04T18:09:53.057Z
Well to answer everyone's question. I meant: While editing video on a timeline, scrubbing through it is slow. My i5 can't seem to handle going from one frame to the next without taking awhile for it to show it on my preview window. I'm wondering if lowering the bitrate, or if lowering the video's recorded resolution will make moving around the timeline on the editor faster.
Joseph M Cutcher III
<video-editor><editing><performance>
Does a higher bitrate impact video EDITING?
Joseph M Cutcher III
# Does a higher bitrate impact video EDITING?

(Asked by: username_0 on 2017-02-06)

If will a high bitrate video be easier or harder on a video editor than a low bitrate video?

**Tags:** video-editor, editing, performance

> **Comments:**
> **username_0**: Well to answer everyone's question. I meant: While editing video on a timeline, scrubbing through it is slow. My i5 can't seem to handle going from one frame to the next without taking awhile for it to show it on my preview window. I'm wondering if lowering the bitrate, or if lowering the video's recorded resolution will make moving around the timeline on the editor faster.  

---

## 2 answers

### Answer by username_1 on 2017-02-07. Score: 1

The above answer by Adam is not really accurate...

There are different bottlenecks to consider.

**Bitrate x Time = Size of File.** means **Higher Bitrate requires Faster Hard Drives**

**Compression / Codec / Ratio of Compression** is either processor intensive, gpu processor intensive, or both (depending on your GPU/editing software). Adobe for example, makes use of NVidia's CUDA cores for faster decompression and encoding of compressed files.

High Bitrate, such as lossless, uncompressed, etc, will require high throughput (Fast Hard Disks, from SSD to SAS RAID/Etc) to handle the data rate of the video file to play in real time.

However, uncompressed video requires less CPU processing power, because the CPU does not have to "uncompress" the file.

If you are editing for example, H.264, highly compressed at a variable bit rate, your bottle neck would be your CPU and GPU (if you are using a system which uses your GPU for video overlay output).

**In general:** If you have a fast RAID HDD setup, editing uncompressed is far smoother, more responsive, quicker to render especially, than working with a compressed codec. EVEN with a slower CPU/GPU - simply because the CPU/GPU does very little work / calculations to decode the file.

If you are working off a single spinning drive, you'll be limited to the 110 MB/s bottleneck (bi directional) so having a faster CPU and GPU would be the way to go with compressed files.

If you have 2 SSD's of equal size, and can SATA port them to your Motherboard, create a RAID 0 and you should get roughly 1 GB/S read speed. I have 4 SSDs in RAID ZERO on an Intel RAID card, and get 4 GB/s - zero lag at all.

> **Comments:**
> **username_0**: To clarify, i'm referring to "playing or scrubbing" through footage while i'm editing it. Assuming a constant frame-rate, and constant bit-rate video. In my case i am using MP4 clips.  The harddrive things makes sense, but i have an SSD so not really worried about that aspect of it, nor am i worried about space. thank you for your answer  
> **username_1**: If you are editing MP4 the file is compressed, likely in H.264. So your responsiveness in terms of scrubbing, or using a jog shuttle, would be improved by 1.) CPU, both fastest clock speed and max cores. 2.) GPU that supports MP4 decompression with as high a clockspeed as possible, and if Nvidia based, max CUDA cores.  
> **username_2**: What about software such as "adobe after effect" or "davinci resolve - fusion" , and specially the second, they use high amount of ram, how much impact graphic card bitrate have on them?  
> **username_2**: How much bitrate is needed or enough  

---

### Answer by username_3 on 2017-02-07. Score: 0

Bitrate is the amount of information contained in the video file. now I think the question is a bit vague. I assume you mean which will affect your computer more for editing.

More bitrate will mean a more beefy computer (CPU, GPU and HDD passthrough) to edit so it can handle the files.

Now if you have a high bitrate file and it is struggeling to play due to computer specs you can convert it to a proxy file which is a low bitrate of the file to make it easier to edit and then relink it later to the high bitrate file for final export.

Hope that helps


---

