No picture on Mobile iOS 11 in case of HLS and Videogular player
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Use case: Angular 6 + Videogular2 player + AFame + HLS
On Mobile, iOS11 Video player is working but no picture.
On Desktop everything is working perfectly.
- AFrame version 0.8.2
- Videogular2 version 6.2.2
- HLS.js version 0.10.1
I have created Showcase where you can see the code and the demo.
Video player without AFrame working everywhere, but with AFrame I can see the only black screen but the player is working.
GitHub: https://github.com/Samuel-Ayvazyan/videogular-aframe-live-streaming
Demo from this repo: http://videogular2-aframe.freedom-dev.com/video-aframe
I suppose that issue can be one of this but required the advice of Aframe contributors:
- In Videogular we are giving src to ".m3u8" by attribute [vgHls] so it is rendered to the player in the correct way. So maybe Aframe trying to get src before this.
- Maybe there is some configuration of AFrame to set Color or Alpha channel for IOS, but I didn't find it.
This is not a duplicate of any other issue, checked all of them and I think this is not a case we had before.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked videogular-aframe-live-streaming showcase and compare the video-only path with the A-Frame path on Mobile iOS 11. Reproduce the black screen with HLS, then trace when the video source becomes available to A-Frame; done means the cause is identified and a verified fix or clear project guidance is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript
- Domain
- audio-video-rtc, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100