add support for tracks.json #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I encountered an encoding issue when providing a tracklist with Japanese characters. I worked around this by adding support for providing a json file with tracks.
This code automatically detects if a
tracks.jsonoutput file is manually supplied by the user, and if so, takes the title & timestamps from this json object.Right now, the json object should have one attribute,
tracks, which maps to a list of dicts withtitleandstart_time. Maybe it could just be the list itself, thetrackswrapping is not really necessary...Todo: add documentation in the readme.