-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
miliseconds #17
Comments
I've come back to check on this. If I submitted a pull request would you be interested in this functionality? |
Not really. Adding microseconds would make this incompatible with ISO_8601. |
I'm curious how supporting milliseconds would break compatibility with ISO 8601 durations? From the Wikipedia article linked above:
Thus, 237ms could be expressed in a ISO 8601-compatible format as |
My mistake, you're right. |
I've come come back again to check on this, haha. But I guess neither I nor anyone else has had the time to implement micro / milliseconds. :( |
I don't use ruby either this lib anymore. If someone else wants to implement microseconds and/or take over the project let me know. |
Di you plan on implementing miliseconds? I started using this for an ffmpeg video editing project, and a lot can happen in a second on film. Ffmpeg has a function that tells you where a video fades to black at say at second 3535.3432. I wanted to store and manipulate these as Duration objects, but it's just not fine grained enough. Seem like a useful thing to have.
Any thoughts?
The text was updated successfully, but these errors were encountered: