Skip to content
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

[bug] timestamp formatting ignored now for output? #33

Closed
Gorrrg opened this issue Dec 27, 2017 · 2 comments
Closed

[bug] timestamp formatting ignored now for output? #33

Gorrrg opened this issue Dec 27, 2017 · 2 comments

Comments

@Gorrrg
Copy link
Contributor

Gorrrg commented Dec 27, 2017

It looks as if the date/time formatting is broken. This here...

"output": { "format": "{channel[name]} - {created_at} - {_id} - {title}.txt", "timestamp": { "absolute": "%Y%m%d" } }
produces a OSError: [Errno 22] Invalid argument: error because the string looks like 2017-12-27T13:30:00Z despite the formatting.

@PetterKraabol
Copy link
Owner

Hi, use custom variables for timestamps, rather than {created_at}. In this case it would be {timestamp[absolute]}.

It doesn't make much sense to specify it to be absolute, but it makes timestamp formatting consistent for output and comments.

@Gorrrg
Copy link
Contributor Author

Gorrrg commented Dec 28, 2017

Ok I used that and added the timestamp absolute formatting. But it seems to be failing for SRT.

        "srt": {
            "duration": 2000,
            "comments": {
                "format": "{commenter[display_name]}: {message[body]}"
            },
            "output": {
                "format": "{channel[name]} - {timestamp[absolute]} - {_id} - {title}.srt",
                "timestamp": {
                    "absolute": "%Y%m%d"
                }
            }
        }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants