New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 775769 link

Starred by 2 users
Status: Fixed
Owner:
w...@chromium.org
Closed: Oct 2017
Cc:
█ jam...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 2
Type: Bug

Blocked on:
issue 776163


Sign in to add a comment

Content Shell (and derivatives) can output audio (yay!) on Fuchsia but only --single-process.

Project Member Reported by w...@chromium.org, Oct 18 2017 
Using not-quite-fully-landed patches we're able to run the Chromium Cast Audio Shell and demonstrate content-generated audio playing back on a Fuchsia device.

Unfortunately, this requires running with --single-process, otherwise we get no audio.

--single-process means we're skipping FDIO unwrap/transfer/wrap, so there's most likely some bug in that logic that needs chasing out.

Comment 1 by w...@chromium.org, Oct 18 2017

Summary: Content Shell (and derivatives) can output audio (yay!) on Fuchsia but only --single-process. (was: Chromium Cast Audio Shell can output audio (yay!) on Fuchsia but only --single-process.)
Fixing title, since this is also true for content_shell, etc. Since Cast Shell has a different media playback path, this supports that the issue is earlier on, at the common renderer->browser IPC step.

Comment 2 by w...@chromium.org, Oct 19 2017

Blockedon: 776163

Comment 3 by jamesr@google.com, Oct 24 2017 

This is fixed now - content_shell and more complex programs (like cast_shell) can play audio in multi process mode.

Comment 4 by w...@chromium.org, Oct 26 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment