1,295
edits
Talk:MediaStreamAPI: Difference between revisions
→I don't understand what the 'streamaudio' attribute is for
Notmasteryet (talk | contribs) No edit summary |
|||
| Line 4: | Line 4: | ||
In the examples it seems to be used to tell the original video element not to play its own audio, and instead audio is streamed (and optionally filtered) to a separate audio element, while the original video still plays. If that's the design, isn't a similar attribute needed to hide the video if that's what's being processed? | In the examples it seems to be used to tell the original video element not to play its own audio, and instead audio is streamed (and optionally filtered) to a separate audio element, while the original video still plays. If that's the design, isn't a similar attribute needed to hide the video if that's what's being processed? | ||
''roc: No. You can use CSS (e.g. display:none) to hide video. There is no CSS property for muting audio.'' | |||
Would the attributes' use be more obvious if they were called 'muteaudio' and 'mutevideo'? Is there not already CSS for that? | Would the attributes' use be more obvious if they were called 'muteaudio' and 'mutevideo'? Is there not already CSS for that? | ||
''roc: There's already a 'muted' attribute, but I don't want to use that here because it's often exposed directly to the user. For example if the user is playing a video with some effects processing, the "mute" UI for the video needs to alter the audio that feeds into the effects processor.'' | |||
It seems like a complicated way to do simple things. Maybe this is an argument for the mediaresource element, as a non-displaying source. Could the graph output be fed back to the original element for display? Could that be the default? | It seems like a complicated way to do simple things. Maybe this is an argument for the mediaresource element, as a non-displaying source. Could the graph output be fed back to the original element for display? Could that be the default? | ||
''roc: If you just want to stream audio, you can use an <audio> element. Any better ideas that don't hit the problem mentioned above? <mediaresource> seems like overkill for now so I've removed it for now.'' | |||
== There's no way for workers to signal latency to the scheduler == | == There's no way for workers to signal latency to the scheduler == | ||