Chrome html5 video decoding performance - possible limitations regarding playback speed / "smoothness" - judder effect?
833 views
Skip to first unread message
Benedikt
Oct 27, 2011, 6:11:11 PM10/27/11
to Chromium-discuss
hi,
after experimenting with some test videos in 1080p (24fps) or 720p (50
fps) hd resolution I'm wondering if there are some limitations (ffmpeg
itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
builds up to 17 on windows 7) that make it hard to play hd content
without some more or less noticeable "lags". These lags can be
recognized as some kind of a judder effect, especially in scenes with
slow motions.
All files were encoded as h264 in 1080p and are embedded via html5
video. Some examples are the Sintel trailer (
http://ftp.nluug.nl/ftp/graphics/blender/apricot/trailer/sintel_trailer-1080p.mp4
) or Big Buck Bunny in mp4 format.
The computer itself should be powerful enough to playback these kind
of video files without any problems, even if everything is software
decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
ram. When you are looking at the task manager, cpu load is always at
around 30 % while playback.
Chrome itself doesn't report any dropped frames via
videoElem.webkitDroppedFrameCount (tested with video-statistics.html
from http://www.opensource.apple.com/source/WebCore/WebCore-7534.48.3/manual-tests/video-statistics.html).
Has anyone experienced some similar issues with hd video in chrome? It
seems to be some kind of a general limitation. A mac version of chrome
(15 or canary) on a totally different machine has the same problems
with judder (the mac used is a mac pro quad xeon 2,66 ghz with 15 gb
ram). So the hardware shouldn't really be the problem.
It seems to me that this a general chrome issue?
Has anyone some tips e.g. for video encoding for hd content to avoid
this judder effect? Or has anyone experienced similiar issues?
Benedikt
after experimenting with some test videos in 1080p (24fps) or 720p (50
fps) hd resolution I'm wondering if there are some limitations (ffmpeg
itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
builds up to 17 on windows 7) that make it hard to play hd content
without some more or less noticeable "lags". These lags can be
recognized as some kind of a judder effect, especially in scenes with
slow motions.
All files were encoded as h264 in 1080p and are embedded via html5
video. Some examples are the Sintel trailer (
http://ftp.nluug.nl/ftp/graphics/blender/apricot/trailer/sintel_trailer-1080p.mp4
) or Big Buck Bunny in mp4 format.
The computer itself should be powerful enough to playback these kind
of video files without any problems, even if everything is software
decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
ram. When you are looking at the task manager, cpu load is always at
around 30 % while playback.
Chrome itself doesn't report any dropped frames via
videoElem.webkitDroppedFrameCount (tested with video-statistics.html
from http://www.opensource.apple.com/source/WebCore/WebCore-7534.48.3/manual-tests/video-statistics.html).
Has anyone experienced some similar issues with hd video in chrome? It
seems to be some kind of a general limitation. A mac version of chrome
(15 or canary) on a totally different machine has the same problems
with judder (the mac used is a mac pro quad xeon 2,66 ghz with 15 gb
ram). So the hardware shouldn't really be the problem.
It seems to me that this a general chrome issue?
Has anyone some tips e.g. for video encoding for hd content to avoid
this judder effect? Or has anyone experienced similiar issues?
Benedikt
Chromiom-zlf
Oct 28, 2011, 3:35:04 AM10/28/11
to Chromium-discuss
Dear,
I think I have the similar problem with you!
I built Chromium by myself for my BeagleBoard,it can not play when I
move my video in chromium,But I user "apt-get chromium-browser"
command to download the google release,It works well.
And I have tried to build ffmpeg, and installed yasm, but failed too!
On 10月28日, 午前6:11, Benedikt <kastlbened...@googlemail.com> wrote:
> hi,
>
> after experimenting with some test videos in 1080p (24fps) or 720p (50
> fps) hd resolution I'm wondering if there are some limitations (ffmpeg
> itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
> builds up to 17 on windows 7) that make it hard to play hd content
> without some more or less noticeable "lags". These lags can be
> recognized as some kind of a judder effect, especially in scenes with
> slow motions.
>
> All files were encoded as h264 in 1080p and are embedded via html5
> video. Some examples are the Sintel trailer (http://ftp.nluug.nl/ftp/graphics/blender/apricot/trailer/sintel_trail...
I think I have the similar problem with you!
I built Chromium by myself for my BeagleBoard,it can not play when I
move my video in chromium,But I user "apt-get chromium-browser"
command to download the google release,It works well.
And I have tried to build ffmpeg, and installed yasm, but failed too!
On 10月28日, 午前6:11, Benedikt <kastlbened...@googlemail.com> wrote:
> hi,
>
> after experimenting with some test videos in 1080p (24fps) or 720p (50
> fps) hd resolution I'm wondering if there are some limitations (ffmpeg
> itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
> builds up to 17 on windows 7) that make it hard to play hd content
> without some more or less noticeable "lags". These lags can be
> recognized as some kind of a judder effect, especially in scenes with
> slow motions.
>
> All files were encoded as h264 in 1080p and are embedded via html5
> ) or Big Buck Bunny in mp4 format.
>
> The computer itself should be powerful enough to playback these kind
> of video files without any problems, even if everything is software
> decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
> ram. When you are looking at the task manager, cpu load is always at
> around 30 % while playback.
> Chrome itself doesn't report any dropped frames via
> videoElem.webkitDroppedFrameCount (tested with video-statistics.html
> fromhttp://www.opensource.apple.com/source/WebCore/WebCore-7534.48.3/manu...).
>
> The computer itself should be powerful enough to playback these kind
> of video files without any problems, even if everything is software
> decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
> ram. When you are looking at the task manager, cpu load is always at
> around 30 % while playback.
> Chrome itself doesn't report any dropped frames via
> videoElem.webkitDroppedFrameCount (tested with video-statistics.html
Chromiom-zlf
Oct 28, 2011, 3:36:51 AM10/28/11
to Chromium-discuss
and i want to ask you what the version of your chromium? Is it
yourself version??
Thank you!
> > Benedikt- 引用テキストを表示しない -
>
> - 引用テキストを表示 -
yourself version??
Thank you!
>
> - 引用テキストを表示 -
PhistucK
Oct 28, 2011, 5:28:02 AM10/28/11
to kastlb...@googlemail.com, Chromium-discuss
You have not mentioned the strength of your GPU, I believe (though really not sure) Chromium is playing video using the GPU (for decoding (when possible) and/or compositing/drawing/painting/whatever). So your GPU might have something to do with these issues, as well. Make sure you have the latest drivers.
☆PhistucK
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss
Benedikt
Oct 29, 2011, 4:31:09 AM10/29/11
to Chromium-discuss
It is the version which comes with google Chrome (latest for canary
17.0.920.1, dev channel 16.0.912.9 or beta 15.0.874.106). So building
is not the issue, as it's the version directly from google.
17.0.920.1, dev channel 16.0.912.9 or beta 15.0.874.106). So building
is not the issue, as it's the version directly from google.
Benedikt
Oct 29, 2011, 4:39:00 AM10/29/11
to Chromium-discuss
Chromium does NOT use GPU for video decoding at the moment. (http://
www.chromium.org/developers/web-platform-status, section Multimedia
"Currently we do everything in software (decode and rendering)").
Drivers for GPU are up to date.
GPU is kind of weak, but i've tested it with various other computers
with better graphics cards, but it didn't solve the problem.
On 28 Okt., 11:28, PhistucK <phist...@gmail.com> wrote:
> You have not mentioned the strength of your GPU, I believe (though really
> not sure) Chromium is playing video using the GPU (for decoding (when
> possible) and/or compositing/drawing/painting/whatever). So your GPU might
> have something to do with these issues, as well. Make sure you have the
> latest drivers.
>
> ☆*PhistucK*
> > ).
www.chromium.org/developers/web-platform-status, section Multimedia
"Currently we do everything in software (decode and rendering)").
Drivers for GPU are up to date.
GPU is kind of weak, but i've tested it with various other computers
with better graphics cards, but it didn't solve the problem.
On 28 Okt., 11:28, PhistucK <phist...@gmail.com> wrote:
> You have not mentioned the strength of your GPU, I believe (though really
> not sure) Chromium is playing video using the GPU (for decoding (when
> possible) and/or compositing/drawing/painting/whatever). So your GPU might
> have something to do with these issues, as well. Make sure you have the
> latest drivers.
>
>
> On Fri, Oct 28, 2011 at 00:11, Benedikt <kastlbened...@googlemail.com>wrote:
>
>
>
>
>
>
>
> > hi,
>
> > after experimenting with some test videos in 1080p (24fps) or 720p (50
> > fps) hd resolution I'm wondering if there are some limitations (ffmpeg
> > itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
> > builds up to 17 on windows 7) that make it hard to play hd content
> > without some more or less noticeable "lags". These lags can be
> > recognized as some kind of a judder effect, especially in scenes with
> > slow motions.
>
> > All files were encoded as h264 in 1080p and are embedded via html5
> > video. Some examples are the Sintel trailer (
>
> >http://ftp.nluug.nl/ftp/graphics/blender/apricot/trailer/sintel_trail...
> On Fri, Oct 28, 2011 at 00:11, Benedikt <kastlbened...@googlemail.com>wrote:
>
>
>
>
>
>
>
> > hi,
>
> > after experimenting with some test videos in 1080p (24fps) or 720p (50
> > fps) hd resolution I'm wondering if there are some limitations (ffmpeg
> > itself, or webkit) in chrome (used chrome 15, 16 dev or various canary
> > builds up to 17 on windows 7) that make it hard to play hd content
> > without some more or less noticeable "lags". These lags can be
> > recognized as some kind of a judder effect, especially in scenes with
> > slow motions.
>
> > All files were encoded as h264 in 1080p and are embedded via html5
> > video. Some examples are the Sintel trailer (
>
> > ) or Big Buck Bunny in mp4 format.
>
> > The computer itself should be powerful enough to playback these kind
> > of video files without any problems, even if everything is software
> > decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
> > ram. When you are looking at the task manager, cpu load is always at
> > around 30 % while playback.
> > Chrome itself doesn't report any dropped frames via
> > videoElem.webkitDroppedFrameCount (tested with video-statistics.html
> > from
> >http://www.opensource.apple.com/source/WebCore/WebCore-7534.48.3/manu...
>
> > The computer itself should be powerful enough to playback these kind
> > of video files without any problems, even if everything is software
> > decoding. The computer has a quadcore intel i5-650 cpu and 4 gb of
> > ram. When you are looking at the task manager, cpu load is always at
> > around 30 % while playback.
> > Chrome itself doesn't report any dropped frames via
> > videoElem.webkitDroppedFrameCount (tested with video-statistics.html
> > from
> > ).
>
> > Has anyone experienced some similar issues with hd video in chrome? It
> > seems to be some kind of a general limitation. A mac version of chrome
> > (15 or canary) on a totally different machine has the same problems
> > with judder (the mac used is a mac pro quad xeon 2,66 ghz with 15 gb
> > ram). So the hardware shouldn't really be the problem.
>
> > It seems to me that this a general chrome issue?
>
> > Has anyone some tips e.g. for video encoding for hd content to avoid
> > this judder effect? Or has anyone experienced similiar issues?
>
> > Benedikt
>
> > --
> > Chromium Discussion mailing list: chromium-disc...@chromium.org
> > Has anyone experienced some similar issues with hd video in chrome? It
> > seems to be some kind of a general limitation. A mac version of chrome
> > (15 or canary) on a totally different machine has the same problems
> > with judder (the mac used is a mac pro quad xeon 2,66 ghz with 15 gb
> > ram). So the hardware shouldn't really be the problem.
>
> > It seems to me that this a general chrome issue?
>
> > Has anyone some tips e.g. for video encoding for hd content to avoid
> > this judder effect? Or has anyone experienced similiar issues?
>
> > Benedikt
>
> > --
Chromiom-zlf
Oct 29, 2011, 10:10:35 PM10/29/11
to Chromium-discuss
Is there any parameter before make ?
./configure --disable-ffmpeg ??
On 10月29日, 午後4:39, Benedikt <kastlbened...@googlemail.com> wrote:
> Chromium does NOT use GPU for video decoding at the moment. (http://www.chromium.org/developers/web-platform-status, section Multimedia
>
> - 引用テキストを表示 -
Mark Rathjen
Aug 15, 2013, 12:57:59 PM8/15/13
to chromium...@chromium.org, kastlb...@googlemail.com
Its been quite some time since this discussion was used, but I'm curious to know what the current state of Chrome is in regards to video decoding. Do they now detect video decoding abilities in hardware and use them, or do they still only do software decoding? Is there somewhere I can check to get the current status?
Reply all
Reply to author
Forward
0 new messages