-
Notifications
You must be signed in to change notification settings - Fork 88
Too many packets buffered for output stream. #91
Comments
It seems to be related to TrueHD perhaps?
|
You're right. Try using git version. Report back if that doesn't work. |
Hmm same result, different error:
|
Please run in debug and provide query as you did previously. |
Whoops forgot the query! Anyways, I'll post the entire log instead: here |
Seems like a ffmpeg issue. You might take it up with ffmpeg devs and tell them you are trying to run: ffmpeg -i Monsters, Inc..mkv -y -acodec copy -vcodec libx265 -filter:v crop=1920:1038:0:22 -c:s copy -c:d copy -pix_fmt yuv420p -map 0:0 -map 0:1 -map 0:2 -map 0:3 -metadata:s:0:3 title=English -metadata:s:0:3 DISPOSITION:default=0 -map 0:4 -metadata:s:0:4 title=English -metadata:s:0:4 DISPOSITION:default=0 -map 0:5 -metadata:s:0:5 title=English -metadata:s:0:5 DISPOSITION:default=0 -map 0:6 -metadata:s:0:6 title=English -metadata:s:0:6 DISPOSITION:default=0 -crf 23 -preset medium /mnt/nas/purchased/movies/Monsters, Inc. (2001)/h265/Monsters, Inc..mkv Otherwise I suggest 2 alternatives. Run h265ize with |
Yeah I think this squarely falls in their camp. I'll just demux the video and audio separately or something. Thanks for looking into this :) |
Thought I'd update here:
|
Posting for time travelers from Google. So That's about as simple as it gets. I'm going path of least resistance on this one and demuxing as I said above :D EDIT: |
Are you using the latest ffmpeg? |
Yeah I custom compiled the latest version. |
:( |
You're telling me lol. For posterity:
|
Interesting, it may be a regression. I recompiled and had the same issue, but the default ubuntu-16.04 old ass ffmpeg works!
|
Hopefully final update! This also works in the latest stable release:
So indeed a regression. |
Good to know. At least it doesn't happen in stable. |
Yeah, the git log on their stuff is irritating to go through, so I'm not sure if it's a known regression or what. Since it is the |
Haha, agreed. |
For anyone running across this issue, I've been having this problem on various files with Per this post on stackoverflow, #128 and setting the value to 1024 seems to fix it. |
Hello!
Using latest version in npm (
h265ize 0.4.3-r2
) I seem to get this on some movies:It will consistently do this for the movie in question, but I'm unable to figure out why.
Thanks!
The text was updated successfully, but these errors were encountered: