Calculate estimated size and processing time from Live Preview
Forum rules
*******************************
Please be aware we are now using GitHub for issue tracking and feature requests.
- This section of the forum is now closed to new topics.
*******************************
*******************************
Please be aware we are now using GitHub for issue tracking and feature requests.
- This section of the forum is now closed to new topics.
*******************************
-
- Posts: 22
- Joined: Fri Feb 14, 2014 11:02 pm
Calculate estimated size and processing time from Live Preview
I may be mistaken, but it seems to me that after processing the 15 second Live Preview in the Preview window, that clip should provide enough information to give a rough file size estimate, right? I know estimated output size gets requested but isn't possible because you can't know before encoding, but the live preview does do encoding and thus Handbrake should be able to take that clip size and extrapolate a rough file size. Obviously a perfect estimate can't be known until the end but this would give a nice range gauge rather than having to take a stab in the dark while still using the advantages of RF quality instead of a forced bitrate.
Additionally, the clip should also be able to extrapolate a processing ETA for the clip. These two figures would be really useful for everyday encoding tasks.
Additionally, the clip should also be able to extrapolate a processing ETA for the clip. These two figures would be really useful for everyday encoding tasks.
Re: Calculate estimated size and processing time from Live Preview
Seems likely to get more complaints than thanks, since it will be so wrong so often.
Re: Calculate estimated size and processing time from Live Preview
Wrong. You can't estimate filesizes from short clips. If you happen to encode a sample of a simple scene, the estimate won't even be remotely close to accurate. You need to encode the vast majority of the source video before you can reasonably accurately estimate filesize.I may be mistaken, but it seems to me that after processing the 15 second Live Preview in the Preview window, that clip should provide enough information to give a rough file size estimate, right?
Re: Calculate estimated size and processing time from Live Preview
Most of the action in movies occurs in the last twenty minutes.IOW, one will always know the size when it's done encoding.
Re: Calculate estimated size and processing time from Live Preview
Credits can be encoded way better than a movie itself -> if you choose the wrong scene, the ETA will be way too short and the file size estimate will be way too small.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
I still don't know why people are so against this, it would be nice to have an estimate. The current time estimate varies quite a bit and no one seems to mind.
Re: Calculate estimated size and processing time from Live Preview
You can't extrapolate filesize. It's that simple. What's the point in giving an "estimate" that isn't even remotely anything like what the end result is?
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
Of course you can 'estimate' it. It would actually be interesting to see what the numbers looked like but it seems like no one is interested, oh well.
Re: Calculate estimated size and processing time from Live Preview
How exactly do you think you can estimate it?
You can't just average the filesize against time. That's already proven not to work.
You can't just average the filesize against time. That's already proven not to work.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
This I did not know, do you have a link to the proof?s55 wrote:That's already proven not to work.
Re: Calculate estimated size and processing time from Live Preview
No. it's just math that you can work out yourself. A good action movie is usually enough to blow any estimate given within the first 5 minutes of the movie out the water.
Re: Calculate estimated size and processing time from Live Preview
No. it's just math that you can work out yourself. A good action movie is usually enough to blow any estimate given within the first 5 minutes of the movie out the water.
I implemented this many moons ago to see how it performed and it was widely inaccurate until late on in the movie at which point it becomes a worthless feature.
Drama's Comedys etc tend not to be so bad as they don't typically have all hell breaking loose in the middle to end of the movie.
It also depends a lot of what kind of settings you use. If you optimise to maintain grain you can get some pretty wild results, particularly where the movie is shot in different styles throughout.
I implemented this many moons ago to see how it performed and it was widely inaccurate until late on in the movie at which point it becomes a worthless feature.
Drama's Comedys etc tend not to be so bad as they don't typically have all hell breaking loose in the middle to end of the movie.
It also depends a lot of what kind of settings you use. If you optimise to maintain grain you can get some pretty wild results, particularly where the movie is shot in different styles throughout.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
This is good to know. I like to know that things have been tested rather than just dismissed because of theories.s55 wrote:I implemented this many moons ago to see how it performed and it was widely inaccurate until late on in the movie at which point it becomes a worthless feature.
Thanks.
Re: Calculate estimated size and processing time from Live Preview
A still image in a movie will have a sustainable bitrate of maybe 200Kbps with no variance from the i-frame.
Detail in motion can sustain bitrates well above 20Mbps (20,000 Kbps), even higher if we let them.
Those, and anything in between, can occur anywhere in a movie, and for any duration.
That's a factored ratio of at least 100:1 between high and low encoded bitrates.
It should be excruciatingly obvious why an estimate isn't going to work, without at least a time-consuming scan pass.
Detail in motion can sustain bitrates well above 20Mbps (20,000 Kbps), even higher if we let them.
Those, and anything in between, can occur anywhere in a movie, and for any duration.
That's a factored ratio of at least 100:1 between high and low encoded bitrates.
It should be excruciatingly obvious why an estimate isn't going to work, without at least a time-consuming scan pass.
Indeed. That is if anyone can recall it from that black hole that was called fifth grade.it's just math that you can work out yourself.
I do too. That's why I've tested my numbers, many times.I like to know that things have been tested rather than just dismissed because of theories.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
No need to act like an internet tough guy, it doesn't really impress anyone.musicvid wrote: Indeed. That is if anyone can recall it from that black hole that was called fifth grade.
Awesome, any chance you could post them here?musicvid wrote: I do too. That's why I've tested my numbers, many times.
Re: Calculate estimated size and processing time from Live Preview
1. 50% of my students can't remember how to manipulate simple and compound ratios, as they were taught under the state's public school curriculum. Just the facts, as you prefer.
2. I did. 200 - 20,000 Kbps+ is what is appropriate to this discussion.
I think you already know that the developers test their assumptions, so your questions seemed a bit surprising.
2. I did. 200 - 20,000 Kbps+ is what is appropriate to this discussion.
I think you already know that the developers test their assumptions, so your questions seemed a bit surprising.
Last edited by Deleted User 13735 on Wed Jul 08, 2015 2:03 pm, edited 8 times in total.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
1. That's nice to know, thanksmusicvid wrote:1. I teach math. Just the facts.
2. I did.
2. Can you provide me a link?
Thanks.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
I don't know any of the developers so I have no idea what they do.musicvid wrote:1. 50% of my ACT/SAT students can't remember how to manipulate simple ratios, as they were taught under the state's public school curriculum. Just the facts, as you prefer.
2. I did. 200 - 20,000 Kbps+ is what is appropriate to this discussion.
I think you already know that the developers test their assumptions, so your questions seemed a bit surprising.
I think we are getting our wires crossed a little (and this is probably my fault), I am not interested in a file size estimate based on a preview (which obviously wont work) I am interested in a file size estimate based on current size.
I have threadjacked here so I wont harp on about it but I have yet to see any actual numbers to suggest that it wouldn't work. Maybe I will record some numbers for my next few encodes and post them.
Even a basic math teacher such as yourself should know that anecdotes do not equal data.
Thanks.
Re: Calculate estimated size and processing time from Live Preview
Whoa.
Your suppositions are wrong, and you don't need me to tell you that.
You have the guys who developed, implemented, and subsequently removed the feature you are obsessing over.
Not taking this, so peace out.
Your suppositions are wrong, and you don't need me to tell you that.
You have the guys who developed, implemented, and subsequently removed the feature you are obsessing over.
Not taking this, so peace out.
Last edited by Deleted User 13735 on Sun May 03, 2015 2:04 pm, edited 3 times in total.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
My supposition would like some proof to agree or disagree with it. Agreed I don't need you to tell me anything.musicvid wrote:Whoa.
Your suppositions are wrong, and you don't need me to tell you that.
You have the guys who developed, implemented, and subsequently removed the feature you are obsessing over.
Not taking this, so peace out.
I believe s55 said he had tried this and it didn't work and I have no reason not to believe him.
However even a basic math teacher such as yourself should know that anecdotes do not equal data.
Thanks
Re: Calculate estimated size and processing time from Live Preview
Which is [Censored] for all the same reasons.rollin_eng wrote:I think we are getting our wires crossed a little (and this is probably my fault), I am not interested in a file size estimate based on a preview (which obviously wont work) I am interested in a file size estimate based on current size.
HB is OSS, perhaps you should give it a whirl?rollin_eng wrote:My supposition would like some proof to agree or disagree with it.
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm
Re: Calculate estimated size and processing time from Live Preview
Any data to back this up?mduell wrote: Which is [Censored] for all the same reasons.
I believe I said earlier in the thread that I might if I get the time.mduell wrote: HB is OSS, perhaps you should give it a whirl?
-
- Veteran User
- Posts: 4854
- Joined: Wed May 04, 2011 11:06 pm