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

ffmpeg merged files have wrong mtime #17156

Closed
trapexit opened this issue Aug 5, 2018 · 3 comments
Closed

ffmpeg merged files have wrong mtime #17156

trapexit opened this issue Aug 5, 2018 · 3 comments

Comments

@trapexit
Copy link

@trapexit trapexit commented Aug 5, 2018

Latest version

When using -f best and getting a single file the mtime is correct but using bestvideo+bestaudio and merging with ffmpeg the resulting file does not get updated with the correct mtime.

@dstftw
Copy link
Collaborator

@dstftw dstftw commented Aug 5, 2018

This is expected behavior since the resulting merged file does not exist on remote server thus mtime does not exist as well.

@dstftw dstftw closed this Aug 5, 2018
@trapexit
Copy link
Author

@trapexit trapexit commented Aug 5, 2018

Why does it matter if it's on the remote server? The data is relevant and not provided in any other way. At least include it in the file naming template so the precise time is available.

@dstftw
Copy link
Collaborator

@dstftw dstftw commented Aug 5, 2018

Because mtime is set from last-modified header reported for concrete file.

@ytdl-org ytdl-org locked and limited conversation to collaborators Aug 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.