Displaying 2 results from an estimated 2 matches for "expected_time".
Did you mean:
expected_lite
2003 Sep 11
1
"wrong" total time from ov_time_total
...'s there, but the time says different.
So, it's ov_time_total accurate? I'm having some other more serious
problems, as I store events that are time related, and I need to seek to
that specific times.
What I have done to "solve" this problem is get a "time factor"
(expected_time/ov_time_total) and apply it to seek and so on, but I'm not
happy with this, as I would like to know the cause, and not only solve an
effect of the problem.
This problems seems to be more present when saving non 44.1 Khz audio, for
example, 8,820 Hz or so. I haven't tryed with sample rates...
2008 May 03
11
Date comparisons
I occasionally get this error:
1)
''A puzzle once featured, should no longer be nominated'' FAILED
expected: Sun May 04 09:10:26 -0700 2008,
got: Sun May 04 09:10:26 -0700 2008 (using ==)
./spec/models/puzzle_spec.rb:180:
So, the dates looks the same to me. Any ideas for how to debug?
Joe