[Rejected] ETA for entire queue rather than just each job

Archive of historical feature requests.
Please use the GitHub link above to report issues.
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.

*******************************
Post Reply
nexradix
Posts: 25
Joined: Sat Sep 26, 2009 1:55 am

[Rejected] ETA for entire queue rather than just each job

Post by nexradix »

Currently, the queue window shows the ETA for the currently processing job. It would be great if there was also an ETA for all jobs in the queue, so you'd have a general idea when the queue would finish processing.

I realize such an estimate probably wouldn't be super accurate, but it would still be great to have for huge queues.
User avatar
s55
HandBrake Team
Posts: 10357
Joined: Sun Dec 24, 2006 1:05 pm

Re: ETA for entire queue rather than just each job

Post by s55 »

I realize such an estimate probably wouldn't be super accurate
Not feasible. You could literally end up being hours, or even days out. You can't predict how long an encode will take ahead of time making the number completely useless.
It would just lead to hundreds of people complaining that it's completely inaccurate.
nexradix
Posts: 25
Joined: Sat Sep 26, 2009 1:55 am

Re: [Rejected] ETA for entire queue rather than just each jo

Post by nexradix »

Figured as much. How about a "time elapsed" counter for the entire queue instead? That way if you have several reasonably similar files, you could mentally estimate how much longer based on how long it has taken so far and the current position in the queue. Plus, it could be a decent pseudo-benchmarking tool one could use to compare machines -- by running the exact same encode on both systems and comparing how long it took each system to complete the encode.
TedJ
Veteran User
Posts: 5388
Joined: Wed Feb 20, 2008 11:25 pm

Re: [Rejected] ETA for entire queue rather than just each jo

Post by TedJ »

Compare the time stamps and average encode speed in the activity log.

Code: Select all

[16:52:56] work: average encoding speed for job is 17.956703 fps
Post Reply