Open Bug 978672 Opened 10 years ago Updated 2 years ago

HW Video Codec Resource Management for Multi-instance

Categories

(Core :: Audio/Video: Playback, defect, P3)

x86
All
defect

Tracking

()

People

(Reporter: bwu, Unassigned)

Details

To separate from bug 977438, it is different topic.

Since there are some use cases using one more video codec instances on the devices with multi-instance codec supported, a resource management is required. 

1. Need to consider encoder as well, since most the HW codec resource are shared with encoder and decoder. 
2. How to handle currently-used codec instances 
   Assuming the device supports multi-instance, one instance is used in the background and another is used in the foreground. How to balance the resource to let user have a better user experience? Sometimes background user may occupy too much resource and impact the foreground. The possible use case is there is a transcoding/encoding in the background and a video playback is running in the foreground.
For good user experience, it would be better to let the foreground users have sufficient resource. In this case, a possible solution is to let the speed of background decoding/encoding slow or even paused.
Hi Michael, 

Do you know is there any way to know where we can know/read how many instances supported?
Flags: needinfo?(mvines)
If no, I think we can set the number of instances in Media_Codecs.xml. 
How do you think?
Flags: needinfo?(mvines)
see also bug 1079519
Assignee: nobody → bwu
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
Is this covered by bug 1112219?
Rank: 32
Flags: needinfo?(bwu)
Priority: -- → P3
(In reply to Randell Jesup [:jesup] from comment #5)
> Is this covered by bug 1112219?
No. 
Bug 1112219 is to make MediaResourceManager cross-platform, not only on B2G. 
More info about this bug is in comment 0.
Component: Audio/Video: MediaStreamGraph → Audio/Video: Playback
Flags: needinfo?(bwu)
Assignee: blakewu0205 → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.