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

Warning from ffmpeg #26

Open
scribblemaniac opened this issue Apr 1, 2016 · 3 comments
Open

Warning from ffmpeg #26

scribblemaniac opened this issue Apr 1, 2016 · 3 comments
Labels

Comments

@scribblemaniac
Copy link
Collaborator

scribblemaniac commented Apr 1, 2016

I am getting the following warning from ffmpeg when doing a merge job:

Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly

Sounds ominous :P

I tried a few different things to solve this, but none of them worked.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32480275-warning-from-ffmpeg?utm_campaign=plugin&utm_content=tracker%2F513466&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F513466&utm_medium=issues&utm_source=github).
@morevnaproject
Copy link
Collaborator

Something to do with this - http://trac.ffmpeg.org/ticket/5189#comment:1

Or, somehow, we need to set "setpts=PTS-STARTPTS" for every input file: http://superuser.com/a/892161

The setpts filter is used because the concat filter documentation states: For this filter to work correctly, all segments must start at timestamp 0.

http://ffmpeg.org/ffmpeg-filters.html#concat

Maybe we should rewrite our code to use concat filter instead of concat demuxer. In this case, we have to read .txt file and dynamically generate ffmpeg commandline. But this can produce VERY long commandline for files with many parts. And we can exceed the length of commandline. :-/

@morevnaproject
Copy link
Collaborator

Ah, I see now! According to this, seems we need to specify duration for every file - https://www.ffmpeg.org/ffmpeg-formats.html#Examples

@scribblemaniac
Copy link
Collaborator Author

You seem to be on the right track, however I just tried adding a duration and rendering manually, and it still seems to be throwing that warning. Perhaps you will have better luck ^_^

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

No branches or pull requests

2 participants