Video play error: Failed to send audio packet for decoding
Reported by
sky00140...@gmail.com,
Nov 28
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Open the video with chrome 2. It will stop at 0:25, chrome://media-internals shows: 00:00:26 497 error Failed to send audio packet for decoding: timestamp=26412018 duration=1688980 size=32 side_data_size=0 is_key_frame=1 encrypted=0 discard_padding (us)=(0, 0) 00:00:26 497 error audio decode error 00:00:26 516 error audio error during playing, status: PIPELINE_ERROR_DECODE 00:00:26 517 pipeline_error PIPELINE_ERROR_DECODE 00:00:26 517 pipeline_state kStopping 00:00:26 519 pipeline_state kStopped 00:00:26 519 event PAUSE What is the expected behavior? The video should play complete(1:36) What went wrong? The video stoped at 0:25 with an error. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 70.0.3538.77 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I test it at chrome63, it's ok.
,
Nov 28
Thanks for filing the issue... Tried to reproduce the issue on reported chrome 70.0.3538.77 and latest chrome 72.0.3623.0 using windows 7. Attaching screencast for reference. Steps: ----- 1. Launched chrome 2. Opened the video with chrome As we are observed that the video stops at 0:25 (From chrome M-64 to latest chrome M-72) and from M-60 to M-63 video stops at 0:31 as per attached screencast. @Reporter: Could you please check the attached screen cast and confirm the issue. Thanks..!
,
Nov 28
Probably just damaged audio packet, Chrome is strict about this. Will double check it's not a bug.
,
Nov 30
0:31-1:36 is static video using a screenshot， that's right. But chrome70 will report a error, that cause our player exit, while chrome63 can continue to play. This is a piece of live stream video, there is other content after the screenshot, but decode error so that we can't play the left part. Is this can fixed? or how can we adjust the video to adapt chrome's requirements.(the video is made by our stream server,so we can adjust that)
,
Nov 30
Your video shows that M-60 to M-63 video did not stops at 0:31, It continues play 0:32 0:33 etc... with no error. You can see that in controlbar. chrome70 will really stop at 0:25, controlbar time did not move, and there is a pipeline error.
,
Nov 30
$ ffmpeg -err_detect explode -i lianmai.mp4 -vn out.wav ffmpeg version N-92214-gdb4771af81 Copyright (c) 2000-2018 the FFmpeg developers built with clang version 8.0.0 (trunk 344066) configuration: --enable-shared --enable-nonfree --enable-gpl --cc=clang --ld=clang --disable-hwaccels --enable-libvpx --enable-libopus --enable-libaom --enable-libx264 --enable-libx265 libavutil 56. 19.101 / 56. 19.101 libavcodec 58. 33.101 / 58. 33.101 libavformat 58. 19.100 / 58. 19.100 libavdevice 58. 4.105 / 58. 4.105 libavfilter 7. 33.101 / 7. 33.101 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc 55. 2.100 / 55. 2.100 <snip> [aac @ 0x2501240] Number of scalefactor bands in group (60) exceeds limit (49). Error while decoding stream #0:1: Invalid data found when processing input Looks like the file is damaged, Chrome 69+ are more strict about these errors now. You'll need to re-encode the file and identify why your streaming server is producing invalid AAC encodings.
,
Dec 4
I'll have a try, thank you.
,
Dec 11
Closing as WontFix due to content issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Nov 28