-
Notifications
You must be signed in to change notification settings - Fork 51
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
Separators in 'Comma-separated timecode values' section #78
Comments
The original intention for this was that you could feed the list of splits to mkvmerge and thus end up with some video clips representing the exact motion events. Since then though, mkvmerge takes a timecode range now, and this output format also isn't very useful for ffmpeg. Could you share a bit more about your use case for this? I'm open to changing the format, or allowing a CLI option to change the timecode output (maybe as an option when |
I don’t have any specific use case in mind, only something roughly like the obsolete |
The
So I would propose using
Thoughts? I'm okay making this a breaking change, since this should likely be the default behaviour, and it should be pretty easy to update any scripts relying on the old behaviour to use |
So instead of turning (without the spaces)
into
turn it into the following?
That’s perfect! |
In the CLI text output, in the section named “Comma-separated timecode values”, is it actually intended behavior that the separators are all commas, both between start and end time of a single event as well as between separate events?
While the comma between start and end times is fine, I guess if the next comma (i.e. every other comma) between two events were replaced with either a semicolon (or a newline), that would simplify processing without any downsides or obvious reasons not to do it.
The text was updated successfully, but these errors were encountered: