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.
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.