Hi everyone, I was wondering if there was a way to make the video a smaller footprint. I tied one that was 1080P the size was 1GB. Do I rendered it at 720p and the file size was 600 MB. Is there a better way? Thank you.
In order to help you, one would need to know the Bitrate and Length of your 1 GB video, along with the encoder you used. MediaInfo will tell you all of this and more:
The basic math for determining video file size is:
Bitrate(Mbps) x Time(sec) x .125 = File Size(Mb)
In order to help you, one would need to know the Bitrate and Length of your 1 GB video, along with the encoder you used. MediaInfo will tell you all of this and more:
The basic math for determining video file size is:
Bitrate(Mbps) x Time(sec) x .125 = File Size(Mb)
I deleted it earlier today. I have a 720p one that was smaller:
Bear with me. Why do you feel the need to have a lower bit rate and/or smaller file?
They are for my use and I don't want them too large. If it was going on YouTube, okay. But I want to save drive space without buying a bigger external SSD. I have a 500 GB external SSD right now. Mostly full of GoPro videos.
The 720p file you posted some of the properties for is 8 Mbps. MediaInfo, a free utility, would have provided all of the information needed to make an educated guess.
"Assuming" it uses the AVC (.h264/x264) encoder, you "could" be able to lower the Bitrate, by "maybe" as much as "50%" without affecting the quality "too" much. This obviously would cut the file size in half. Given the full parameters, I could eliminate "most" of the quotation marks in that sentence.
On the other hand, your GoPro videos are taking up many times more space on your hard drive than your edited ones.
The 720p file you posted some of the properties for is 8 Mbps. MediaInfo, a free utility, would have provided "all" of the information needed to make an educated guess.
"Assuming" it uses the AVC (.h264/x264) encoder, you "could" be able to lower the Bitrate, by "maybe" as much as "50%" without affecting the quality "too" much. This obviously would cut the file size in half. Given the full parameters, I could eliminate "most" of the quotation marks in that sentence.
I am going out to take video, will do that later today, thank you.
"The most sensible, long-run approach would be to render to a Constant Rate Factor in Voukoder.
Chances are, if you're shooting with a Go-Pro, the complexity of your video is high. High complexity video requires more bits than low complexity or static video.
The beauty of the Constant Rate Factor strategy, is that the encoder attempts to deliver a visual experience that you decide is best based on your selection of CRF value rather than a target bit rate.
If your shoot video regularly, it's probably time to break out of the 500GB box you mentioned."
said the fellow who buys 3.5 inch hard drives in 16TB sizes and SSDs for physical file delivery in 1TB sizes.
@mark-y Notice the subtle use of "quotes".
I'd suggest getting an external hard drive to achive your files on. I have a few 5TB ones here (small Seagate and WD ones) which are fine for that.
@Ruby888 Hi, 500GB is quite small now a far as drives is concerned, so I'd agree with others that say get a bigger hard drive, recoding your videos to a lower bitrate & therefore prob/poss loosing quality might be something you regret at a later date. Amongst other drives I use for everyday 'stuff' I've got 2 x 12TB hard drives i keep/archive my YT vids on,
"The most sensible, long-run approach would be to render to a Constant Rate Factor in Voukoder.
Chances are, if you're shooting with a Go-Pro, the complexity of your video is high. High complexity video requires more bits than low complexity or static video.
The beauty of the Constant Rate Factor strategy, is that the encoder attempts to deliver a visual experience that you decide is best based on your selection of CRF value rather than a target bit rate.
If your shoot video regularly, it's probably time to break out of the 500GB box you mentioned."
said the fellow who buys 3.5 inch hard drives in 16TB sizes and SSDs for physical file delivery in 1TB sizes.
@mark-y Notice the subtle use of "quotes".
Hi, okay so bitrate is the quality of the video and the more the better, but the file size. I used to game so I guess I would want a high bitrate for that and my GoPro videos. I have video footage of my apple trees with a Sony 4K camcorder, I should not have done that as I just wanted a video for my own use to keep track of the trees every year. So I could cut the bitrate down on that and the resolution to 1080p. So in this template I don't understand the what I should set the rates the arrows point to, any advice?
The values in the original template represents a reasonable compromise for the variability of what the end-user might need based on all the possibilities for what the user might shoot. I've stared at your template and the full copy of it on my machine while I drank a whole cup of coffee and I still wonder if the wind is blowing the leaves on your apple trees and if you use a tripod?
Buy more storage.
Since @john_dennis and I often collaborate on this forum, I hope he won't mind if I provide a bit of context to your question.
You are correct, higher bitrate yields higher quality, but up to a point.
In modern encoding, the single biggest factor in determining average bitrate boils down to one question: "How much detail in motion is there in the viewfinder?"
No motion at all (a slideshow without transitions), requires only minimal bitrate, often as low as 250 Kbps, because the signpost from the current frame to the next one says only, "Do as you did before." A frame needing more bits only occurs once at every transition to a new slide. A comparable situation occurs in a fixed video scene with relatively little motion, such as a talking-head interview.
On the other hand, a scene with lots of fast moving detail and /or rapid panning requires up to 100 times more bits for each consecutive frame, because the math instructions, or motion estimation, is much more complex. The most complex examples of this are ocean waves and ripples, or complex special effects, such as the grainy orange fog in the first Matrix movie. These things literally drive the encoders crazy.
So you can see the thinking that is behind John's question:
. . . and I still wonder if the wind is blowing the leaves on your apple trees and if you use a tripod?
If you will indulge us by uploading a bit of your original apple tree GoPro footage to Drive or Dropbox, one of us can look at it and point out the things you should watch for when determining how low you can safely reduce your Average Bit Rate (the yellow arrow in your picture) without turning the moving leaves to mush (peak bitrate should remain at 20-25Mbps - it won't affect your file size much).
To summarize, the things that will allow your video to survive lower bit rates are:
That all said, a default setting of 10-12Mbps using AVC is an average safe level for 1080p 30p. Thanks for asking the good questions!
Since @john_dennis and I often collaborate on this forum, I hope he won't mind if I provide a bit of context to your question.
You are correct, higher bitrate yields higher quality, but up to a point.
In modern encoding, the single biggest factor in determining average bitrate boils down to one question: "How much detail in motion is there in the viewfinder?"
No motion at all (a slideshow without transitions), requires only minimal bitrate, often as low as 250 Kbps, because the signpost from the current frame to the next one says only, "Do as you did before." A frame needing more bits only occurs once at every transition to a new slide. A comparable situation occurs in a fixed video scene with relatively little motion, such as a talking-head interview.
On the other hand, a scene with lots of fast moving detail and /or rapid panning requires up to 100 times more bits for each consecutive frame, because the math instructions, or motion estimation, is much more complex. The most complex examples of this are ocean waves and ripples, or complex special effects, such as the grainy orange fog in the first Matrix movie. These things literally drive the encoders crazy.
So you can see the thinking that is behind John's question:
. . . and I still wonder if the wind is blowing the leaves on your apple trees and if you use a tripod?
If you will indulge us by uploading a bit of your original apple tree GoPro footage to Drive or Dropbox, one of us can look at it and point out the things you should watch for when determining how low you can safely reduce your Average Bit Rate (the yellow arrow in your picture) without turning the moving leaves to mush (peak bitrate should remain at 20-25Mbps - it won't affect your file size much).
To summarize, the things that will allow your video to survive lower bit rates are:
- Using a tripod
- Not panning your shots
- Filming your trees when the wind is calm
- Smaller frame size. Would 1280x720 work just as well for you? If the answer is Yes, you can lower your average bitrate 33% more without affecting the quality
- Lower your frame rate. If, instead of 30p, you lowered it to 24p (23.976), you can safely reduce your average bitrate by another 20%.
- So, if instead of 1080 p30, you chose 720 p24, an Average Bit Rate of 6-8Mbps should work just as well for you, reducing your file size by 30-50%.
That all said, a default setting of 10-12Mbps using AVC is an average safe level for 1080p 30p. Thanks for asking the good questions!
Wow thank you both for your advice. My tress were filmed on a Sony Camcorder and the original was deleted after creating the finial video in Vegas to conserve drive space. I see no reason keeping it as the job was completed. There was a lot of panning and wind when I filmed the trees back in May.
Then my take is the same as @john_dennis -- use the default bitrates and search Amazon for deals on drives to store your GoPro footage.
Thank you all.