[meta] Multiple channel support for Cubeb
Categories
(Core :: Audio/Video: cubeb, enhancement, P3)
Tracking
()
People
(Reporter: sebastian.fisahn, Assigned: chunmin)
References
(Depends on 4 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
Reporter | ||
Updated•11 years ago
|
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
Assignee | ||
Comment 4•9 years ago
|
||
Comment 5•9 years ago
|
||
Assignee | ||
Comment 7•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 8•9 years ago
|
||
Comment 9•8 years ago
|
||
Updated•6 years ago
|
Comment 11•6 years ago
|
||
The remaining parts are;
- Bug 1325023 if it still stands. :chunmin should know about it (NI)
- Multichannel in android. If we want it there we haven't done anything.
Assignee | ||
Comment 12•6 years ago
|
||
We have implemented multi-channel in Windows, Mac OS, and PulseAudio, but we don't support other platforms like Android and ALSA. I've asked the reporter of bug 1368938 to check the layout issue again. Bug 1325023 should close if bug 1368938 is solved.
Assignee | ||
Comment 13•5 years ago
|
||
I find the same questions for audio channel layout setting come times and times again and reporters usually don't know how to check those settings. To avoid answering the same questions again and again, I wrote a FAQ post to address some common issues. I hope we can paste that post to answer the reporter's issues directly in the future.
I am not sure where I can post the official FAQ page, so I just post it on my blog for now. Here is the link: https://chunminchang.github.io/blog/post/firefox-faq-audio-channel-layout
That post include some common issues:
- how to set up and check the audio channel layout
- how to file a bug with info that helps us to address the reporter's issues
The FAQ is mainly for Mac OS now. I'll add the Windows and Linux parts in the future.
Comment 14•4 years ago
|
||
Creative XFI APO's are again breaking the legacy Rear Right/Left on AAC tests.
Comment 15•3 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Description
•