Opened 4 years ago
Last modified 5 months ago
#1463 assigned task
html5 video support enabled by default
| Reported by: | Antoine Martin | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | major | Milestone: | 5.0 |
| Component: | html5 | Version: | trunk |
| Keywords: | Cc: | devurandom@… |
Change History (16)
comment:1 Changed 4 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 4 years ago by
- MediaError.message may be able to help us diagnose the underlying problems
- Real Time Streaming to HTML5 (with out webrtc) just using video tag
- or maybe look at using RTP / webrtc
comment:4 Changed 4 years ago by
Since this isn't making any progress, turn it off until someone fixes it: r16672
comment:5 Changed 4 years ago by
| Milestone: | 2.2 → 3.0 |
|---|
comment:6 Changed 4 years ago by
Links that may help:
- h264-live-player based on:
- Broadway - double check the x264 arguments:
2M -bt 4M -coder 0 -bf 0 -flags -loop -wpredp 0 -an
comment:7 Changed 3 years ago by
New links:
- Video buffering in IE/Edge using Media Source Extensions
- Frame by frame decode using Media Source Extension: Now every MP4 created will have the MEHD fragment duration set to 0 which causes Chrome to process it as a live stream
- Streaming a video with Media Source Extensions: The Source Buffer emits an event before and after updating, you have to wait until it fires the updateend event before appending another Media Segment.
- Media Source API: Automatically Ensure Seamless Playback of Media Segments in Append Order: Chrome 50 adds additional support to the SourceBuffer? mode attribute, allowing you to specify that media segments are played back continuously, in the order that they were appended, no matter whether the media segments initially had discontinuous timestamps
comment:8 Changed 3 years ago by
These plans may be scuppered by chrome: Chrome 66 will try to block unwanted noisy autoplaying video
comment:10 Changed 3 years ago by
| Cc: | devurandom@… added |
|---|
comment:11 Changed 2 years ago by
This could still be used but triggered by the user using a click on an "acceleration option"?
See also #2165
comment:12 Changed 2 years ago by
New "preloading" option idea: prepare a video context whenever we get a user event (click in window) then tell the server that we support more encodings (ie: h264+mp4) and use it when we get a new stream.
comment:14 Changed 21 months ago by
| Milestone: | 4.0 → 4.1 |
|---|
comment:16 Changed 5 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1463
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2021
Looks like we may also need to special case phones and tablets: HTMLMediaElement.play() Returns a Promise and turn off video if it requires user interaction to play.