Parameter page confuses --pass=<arg> and --passes=<arg>

[GoogleCodeExporter]

http://www.webmproject.org/tools/encoder-parameters/

One-Pass vs. Two-Pass

-p<arg> is equivalent to --passes=<arg>

the website has 
-p<arg> equivalent to --pass=<arg> 
which is incorrect

Additionally there could be more information about saving the 1st pass 
file/doing the 2 pass encodes with two separate commands.

Original issue reported on code.google.com by frkoe...@google.com on 14 Dec 2010 at 6:07

[GoogleCodeExporter]

Thanks.  Fixed in the next website push.  It's correct in the usage section, 
but incorrect in an example.

WRT an example two-step, two-pass encode using discrete commands, do you have 
suggested syntax that has a real-world ring to it?

Original comment by louquil...@google.com on 15 Dec 2010 at 10:30

• Changed state: Started

[GoogleCodeExporter]

I really don't know if there is any real world usage of splitting up the encode 
on the command line.  Just thought that if we were going to call out using the 
--pass command maybe there should be an example of it.  My usage is confined to 
profiling and only wanting to look at the encode time for pass 1 vs. pass 2, so 
I don't know if it would be relevant.

Original comment by frkoe...@google.com on 16 Dec 2010 at 1:07

[GoogleCodeExporter]

All right.  I'm getting started on a contributors' guide, so maybe that's a 
good place to call out a deliberate two-step encode.  Closing for now.

Original comment by louquil...@google.com on 16 Dec 2010 at 1:58

• Changed state: Done
• Added labels: Priority-Medium
• Removed labels: Priority-Meduim