Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / eoyilmaz/timecode issues and pull requests

#56 - [#55] Fix encoding issue in `setup.py`.

Pull Request - State: closed - Opened by eoyilmaz 3 months ago

#54 - Add type hints, and restrict package to 3.7+

Pull Request - State: closed - Opened by austinwitherspoon 7 months ago

#53 - Type Hints!

Issue - State: closed - Opened by austinwitherspoon 7 months ago - 1 comment

#52 - Add realtime and systemtime getters. Preserve flags with operators.

Pull Request - State: closed - Opened by cubicibo 9 months ago - 1 comment

#51 - Why do frames have to be larger than 0?

Issue - State: closed - Opened by octimot 9 months ago - 6 comments

#50 - Why does thsi library not support arbitrary FPS/Framerate?

Issue - State: closed - Opened by RalfReddings 9 months ago - 4 comments
Labels: feature request

#49 - Read a timecode source

Issue - State: closed - Opened by MilkMGN 11 months ago - 1 comment

#48 - Why does self.frames = int(seconds * self._int_framerate) ?

Issue - State: open - Opened by cheng-chi about 1 year ago - 3 comments

#47 - README.md - py code syntax highliting

Pull Request - State: closed - Opened by Thomasparsley over 1 year ago - 1 comment

#46 - - Fixed a class method call

Pull Request - State: closed - Opened by kchinzei over 1 year ago

#45 - fix class method call

Pull Request - State: closed - Opened by kchinzei over 1 year ago - 1 comment

#44 - Why is the frame_number for tc1 + tc2 = 1 and not 0 in this example?

Issue - State: closed - Opened by quantum909 over 1 year ago - 1 comment

#43 - IndexError

Issue - State: closed - Opened by rgodement over 1 year ago - 2 comments

#42 - Fix pytest and coverage

Pull Request - State: closed - Opened by rafrafek over 1 year ago - 3 comments

#41 - ValueError exception

Issue - State: closed - Opened by struzjos almost 2 years ago - 3 comments

#40 - Unexpected TC change on instantiation.

Issue - State: closed - Opened by pmacdonald-tl about 2 years ago - 1 comment

#39 - Question: Possible to convert from frame to timecode

Issue - State: closed - Opened by rarajabs over 2 years ago - 2 comments
Labels: question

#37 - Any plans to add support for high-frame rate timecode frame rates?

Issue - State: open - Opened by mbechard over 3 years ago - 8 comments

#36 - Float property inaccurate?

Issue - State: closed - Opened by mvanherk over 3 years ago - 1 comment

#35 - Different timecodes occurring for same number of frames.

Issue - State: closed - Opened by aki-sud almost 4 years ago - 1 comment

#34 - Incorrect frame_number for 29.97 NDF

Issue - State: closed - Opened by marcrleonard almost 4 years ago - 2 comments

#33 - Incorrect rollover for 23.98

Issue - State: closed - Opened by ambustion almost 4 years ago - 1 comment

#32 - Initializing with start_seconds does not create the correct Timecode object

Issue - State: closed - Opened by JohnENoonan almost 4 years ago - 3 comments

#31 - Frame validation breaks timecode manipulation

Issue - State: closed - Opened by SimonWilkinson almost 4 years ago - 4 comments

#30 - Buggy Timecode calculation when invoked with `frames`

Issue - State: closed - Opened by rsomani95 almost 4 years ago - 3 comments
Labels: bug

#29 - Timecode calculation

Issue - State: closed - Opened by aki-sud almost 4 years ago - 3 comments

#28 - Comparison operators throw an Error?

Issue - State: closed - Opened by caliban17 about 4 years ago - 10 comments

#27 - Revert "Added option to make the Timecode fractional from creation"

Pull Request - State: closed - Opened by eoyilmaz about 4 years ago

#26 - Discarding '23.98' framerate in @framerate.setter?

Issue - State: closed - Opened by morganwl over 4 years ago - 1 comment
Labels: enhancement, question

#25 - Remove restriction of start_seconds not being zero

Pull Request - State: closed - Opened by jonata over 4 years ago - 1 comment

#24 - Added option to make the Timecode fractional from creation

Pull Request - State: closed - Opened by jonata over 4 years ago - 1 comment

#23 - Fix for issue #13 - 29.97 NDF and 59.94 NDF support

Pull Request - State: closed - Opened by kingb over 4 years ago - 1 comment

#22 - Construction using seconds is not accurate

Issue - State: closed - Opened by julaudo over 4 years ago - 1 comment

#21 - float doesn't use frame_number

Issue - State: closed - Opened by merlink01 over 4 years ago - 1 comment

#20 - Tests are failing

Issue - State: closed - Opened by kenokenobingo over 4 years ago - 1 comment

#19 - Wrong result in addition or subtraction.

Issue - State: closed - Opened by pathakumesh almost 5 years ago - 4 comments

#18 - TC to frameCount

Issue - State: closed - Opened by stesteau about 5 years ago - 2 comments

#17 - Added 23.976 variation of 23.98

Pull Request - State: closed - Opened by apetrynet over 5 years ago

#16 - Fails if a low binary coded decimal is passed to it

Issue - State: closed - Opened by SolenOchHavet over 5 years ago - 1 comment

#15 - Added > and < operator overloading because it does not always work ot…

Pull Request - State: closed - Opened by foleyj2 over 5 years ago - 2 comments

#14 - Incorrect comparison

Issue - State: closed - Opened by foleyj2 over 5 years ago - 1 comment

#13 - 29.97 Non-Drop

Issue - State: closed - Opened by iluvcapra almost 6 years ago - 6 comments

#12 - Added float property (secs)

Pull Request - State: closed - Opened by jonata almost 6 years ago - 1 comment

#11 - Error when used on Windows

Issue - State: closed - Opened by arrancorbett over 6 years ago - 1 comment

#10 - Fix: NameError: global name 'basestring' is not defined (python 3)

Pull Request - State: closed - Opened by yoyonel over 6 years ago

#9 - Added some features and updated README, suggested minor version bump

Pull Request - State: closed - Opened by apetrynet almost 7 years ago - 1 comment

#8 - Added support for Binary Codec Decimal timecode

Pull Request - State: closed - Opened by apetrynet almost 7 years ago - 4 comments

#7 - Suggested Major release update

Pull Request - State: closed - Opened by apetrynet almost 7 years ago - 2 comments

#6 - start_seconds issue

Issue - State: closed - Opened by johnwheeler almost 7 years ago - 2 comments

#5 - Dealing with framerates that has many decimal points

Pull Request - State: closed - Opened by Theodeus almost 7 years ago - 1 comment

#4 - Support specifying an integer timecode as a float

Pull Request - State: closed - Opened by mike1158 almost 7 years ago - 1 comment

#3 - Failed unittest

Issue - State: closed - Opened by greg-ruane over 7 years ago - 2 comments

#2 - Set framerate to 24 when specified as 23.98

Pull Request - State: closed - Opened by thomasheritage about 8 years ago - 1 comment

#1 - New frame rate initialization and frame delimiters

Pull Request - State: closed - Opened by apetrynet over 8 years ago - 5 comments