MCPcopy Create free account
hub / github.com/Breakthrough/PySceneDetect / get_seconds

Method get_seconds

scenedetect/common.py:382–400  ·  view source on GitHub ↗

[DEPRECATED] Get the frame's position in number of seconds. Use the `seconds` property instead. If using to compare a :class:`FrameTimecode` with a frame number, you can do so directly against the object (e.g. ``FrameTimecode(10, 10.0) <= 1.0``). Returns:

(self)

Source from the content-addressed store, hash-verified

380 return float(self._time.value / self._rate)
381
382 def get_seconds(self) -> float:
383 """[DEPRECATED] Get the frame&#x27;s position in number of seconds.
384
385 Use the `seconds` property instead.
386
387 If using to compare a :class:`FrameTimecode` with a frame number,
388 you can do so directly against the object (e.g. ``FrameTimecode(10, 10.0) <= 1.0``).
389
390 Returns:
391 float: The current time/position in seconds.
392
393 :meta private:
394 """
395 warnings.warn(
396 "get_seconds() is deprecated, use the `seconds` property instead.",
397 DeprecationWarning,
398 stacklevel=2,
399 )
400 return self.seconds
401
402 # TODO(https://scenedetect.com/issue/168): We should remove `nearest_frame` if possible, it
403 # assumes constant framerate and causes more problems than it solves. Setting it to False makes

Callers

nothing calls this directly

Calls

no outgoing calls

Tested by

no test coverage detected