-
Notifications
You must be signed in to change notification settings - Fork 157
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
no H.264 format video track: #41
Comments
@dgibbs64 You're getting that error because the video your'e trying to convert doesn't contain any H.264 format video track. Very likely you're trying to use What does You can get the |
@dgibbs64 Did you ever figure out what's going on here? Did the media file actually contain H.264 video? |
yeah the media did contain H.264. I will need to investigate again as I have been busy and not been able to test this in a while. I will look at this again once I have settled in to my new house in a few weeks :) |
@dgibbs64 Any update on this? |
Will be doing a fresh install once I get my VMware server installed :D. I will test then |
Just setting up my new VM I can confirm I still have the issue with an mkv file that does contain a H.264 track. |
here is a sample output from mediainfo
|
@dgibbs64 Thanks. Is it possible to upload this file somewhere so I could download and test it? |
@dgibbs64 If uploading is not possible, can you run this command on the input and paste the output here:
|
@dgibbs64 BTW, the reason why I need the output of a HandBrake scan is that's what the |
@dgibbs64 Any chance to try that |
Hope this helps |
It may be worth seeing if you can setup an Ubuntu VM and replicate that way. If I remember correctly your using Mac? It could be some slight differences in the software that are causing the issue? This is retested on just released Ubuntu 16.04 LTS and still the same issue. |
@dgibbs64 Can you include the entire scan? You're missing the first few lines which contain the HandBrake version number. Thanks. |
@dgibbs64 Are you using a development/nightly build of |
Im just using whatever the default is for Ubuntu 16.04 Installed:
edit: I have just added the official PPA to get the latest version however there is no release for 16.04 of the repo currently. |
@dgibbs64 Maybe the version is 0.10.2 but it's hard to tell with all that noise from
Specifically, the first line of that output. That's the crucial version information. |
@dgibbs64 BTW, getting back to the scan output. This is the crucial line I use to detect whether an input file contains a valid H.264 video stream:
And there's nothing wrong with that line. My parser should see that. So, I have no idea why it's failing. This means I need to go back to your original attempt to use
See that Please paste in ALL of the output from that command -- from the first line to the last line. Thanks. |
Output of HandBrakeCLI --preset-list
Output of convert-video -vv "/path/to/video.mkv"
|
@dgibbs64 Thanks! But most of that is still formatted as regular text. Can you can re-edit that comment to format it as code? |
@dgibbs64 Nevermind. I realized I could edit it myself. :) |
@dgibbs64 OK, I see the problem now. Sorry that I missed it the first time but it's very subtle. For some strange reason, your particular version of I've never seen that output from any other version of |
That's great news you have spotted the issue. Hopefully you can figure out a work around. Good Luck! |
@dgibbs64 Looks like this has to do with the version of libavcodec to which HandBrake is linked. Because libavcodec contains the code which generates the steam information in the scan output. And different versions of libavcodec use different punctuation. Go figure. Anyway, (I think) I can fix this in my parser by being a little more lenient about about the stream identifier. So, I'll put this on the list of things to fix for 0.8.0. Probably due out next week. Stay tuned! And thanks for going through all these hoops with me. :) |
@dgibbs64 OK, the fix has been released in version 0.8.0. Just update to get it. Please test on your configuration and let me know if it actually works. Thanks again! |
Hey,
Im currently getting this error when testing out convert-video. Not sure why. Any suggestions?
Just to confirm the video track is H264
The text was updated successfully, but these errors were encountered: