I'll try to create a sample with odd initial I-frame placement and check it with my local ffmpeg build. I have a few mpeg2 samples somewhere locally. The client may be misreporting the limitations of the device, leading it to try direct playing first. I'm pretty sure you're right about it being unable to handle a 1080p h.264 file (specs claim 720p30 profile 3.1 iOS also doesn't like mkv containers). I suppose it's possible too that their code is based on a revision of libav prior to the commit/regression mentioned in the bug report, so it wouldn't run into the same issue.Ĭan you attach the server and transcode logs from the iPad playback testing? Sounds like an unrelated issue, but I'm sure Luke/ebr would like more detail there and might need its own thread. I haven't looked at their code in quite some time and don't know just how much detail their logging provides regarding that stuff, so I can't be sure of what it's really doing. Handbrake may actually be failing to decode with hardware, but not letting you know and just software decoding it silently. That's pretty good performance for an i5 doing a software decode of HEVC, though That command line also is more for benchmarking/checking the chosen decoder since it just dumps the raw uncompressed video to null rather than re-encoding it (just FYI). You would have to add the proper decoder option prior to the input file (-i) for it to decode with hardware (-c:v h264_qsv or -c:v hevc_qsv). In the ffmpeg reports, it looks like it's not being told to use hardware decoding, so those will use software decoding and you should see a lot of load with that particular command line (especially with the HEVC file).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |