Bug in "time" tab (additional options)

[GoogleCodeExporter]

What steps will reproduce the problem?
  1. Enable "Additional Options" in the menu "Options".
  2. Click the "time" tab.
  3. Select a seek to / time to record value and start the conversion.

What is the expected output? What do you see instead?

  The command line arguments "-ss" (seek to) and "-t" (time to record) expect arguments in seconds or in the format "hh:mm:ss[.xxx]". Unfortunately, WinFF seems to add an extra zero to the minute part every time a conversion is started, producing arguments like these (causing ffmpeg to fail):

  -ss 0:00002:00000 -t 0:00000:10

What version of the product are you using? On what operating system?

   WinFF 1.3.2 on Windows XP

Please provide any additional information below.

   I've noticed this problem since version 1.3.0, but it could exist in earlier versions, too, since I always passed the parameters -ss and -t directly to the ffmpeg encoder.

   These options are extremely valuable to test many different encoding parameters and/or presets in a very short time, so I hope that a bugfix on the next release might help newbies to enjoy this functionality of WinFF!

Thanks!

Original issue reported on code.google.com by Ric.CE...@gmail.com on 21 Feb 2011 at 1:12

[GoogleCodeExporter]

I, see.

Original comment by bgg...@gmail.com on 21 Feb 2011 at 7:16

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in svn will come out with next release

Original comment by bgg...@gmail.com on 21 Feb 2011 at 10:46

• Changed state: Fixed