Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"ETA" IS NOT ETA #9072

Closed
petfold opened this issue Apr 3, 2016 · 5 comments
Closed

"ETA" IS NOT ETA #9072

petfold opened this issue Apr 3, 2016 · 5 comments

Comments

@petfold
Copy link

@petfold petfold commented Apr 3, 2016

Please follow the guide below

  • You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
  • Put an x into all the boxes [ ] relevant to your issue (like that [x])
  • Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.04.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

  • [x ] I've verified and I assure that I'm running youtube-dl 2016.04.01

Before submitting an issue make sure you have:

  • [ x] At least skimmed through README and most notably FAQ and BUGS sections
  • [x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

  • [ x] Bug report (encountered problems with youtube-dl)
  • Site support request (request for adding support for a new site)
  • Feature request (request for a new functionality)
  • Question
  • Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue


If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:

Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):

$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.04.01
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):


Description of your issue, suggested solution and other information

Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue required an account credentials please provide them or explain how one can obtain them.

WHILE DOWNLOADING, YOUTUBE-DL GIVES FEEDBACK SUCH AS

[download] 35.1% of 576.20MiB at 360.25KiB/s ETA 17:42

IN THIS LINE, THE USE OF "ETA" IS INCORRECT. WHAT YOU WANT TO SAY IS THAT THE DOWNLOAD IS EXPECTED TO FINISH 17 MINUTES FROM NOW. ETA ALWAYS MEANS AN ABSOLUTE TIME (ESTIMATED TIME OF ARRIVAL). INSTEAD OF "ETA" IT SHOULD SAY "remaining time" OR "remaining". IT'S NOT ETA, PLEASE CHANGE THIS, THANKS.

@jaimeMF
Copy link
Collaborator

@jaimeMF jaimeMF commented Apr 3, 2016

Well, it seems that both formats are accepted: http://english.stackexchange.com/a/104893.
And according to https://en.wikipedia.org/wiki/Estimated_time_of_arrival, Bittorrent clients also use it in this way.

I'm far from being an expert on the terminology, could you provide some reference that supports your view?

@davidbailey00
Copy link

@davidbailey00 davidbailey00 commented Apr 10, 2016

IN THIS LINE, THE USE OF "ETA" IS INCORRECT. WHAT YOU WANT TO SAY IS THAT THE DOWNLOAD IS EXPECTED TO FINISH 17 MINUTES FROM NOW. ETA ALWAYS MEANS AN ABSOLUTE TIME (ESTIMATED TIME OF ARRIVAL). INSTEAD OF "ETA" IT SHOULD SAY "remaining time" OR "remaining". IT'S NOT ETA, PLEASE CHANGE THIS, THANKS.

You don't need to shout dude :D

@dstftw
Copy link
Collaborator

@dstftw dstftw commented Apr 10, 2016

Closing since no certain proof provided.

@dstftw dstftw closed this Apr 10, 2016
@petfold
Copy link
Author

@petfold petfold commented Apr 11, 2016

Even if you close my ticket and even if you cite Bittorrent as using it, it is an incorrect usage. The term comes from aviation and I asked pilots who confirm this is only used with absolute time.
Look it is not essential for me that you don't make fools of yourselves. I am just trying to help you. But if you resist, I give up on you and your attitude. I will also submit a bug report to bittorrent, maybe they have more sense. Which bittorrent client did you mean?

The fact fact that I am right is clear from how in some applications both ETA and remaining time is displayed (e.g. Waze). In this case both are referred to correctly. I am really puzzled by why you insist confusing your users by using an incorrect, or at least ambiguous term.

@rg3
Copy link
Collaborator

@rg3 rg3 commented Apr 11, 2016

The term "ETA" has been used by the program almost since I wrote the initial version, for two reasons. I was trying to keep the progress line as short as possible, because it needs to fit in a single terminal line typically below 80 characters for the line to be properly overwritten when using the carriage return method. Second, the term was already being widely used by GNU wget in its output, so it would be familiar to anybody who had used the ubiquitous program. GNU wget uses it to express the remaining time.

Nowadays, on top of that, we can find many GUIs and tools on top of youtube-dl that parse its progress output, and may beed to be rewritten if we change the line.

Nobody is insisting on "confusing [our] users by using an incorrect [...] term". There are contextual, historical and practical reasons to keep it the way it is, and they're more important than the point raised here, however right it may be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.