Videojs: 0.4.1.1 results in 64k-aac while 0.3.5 results in 2040K-video
Nobody has claimed this yet.
- Dominant language
- ActionScript
- Stars
- 744
- Forks
- 259
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm working on integrating flashls into videojs. First of all, thanks for all the hard work - we really appreciate it, :).
Issue: When using the forked version of [video-js.swf](https://github.com/mangui/video-js-swf), I get drastically different behavior from release version 0.4.1.1 and 0.3.5. I have a "soccer" video which in 0.4.1.1 plays the 64k audio stream (ie no video), and in 0.3.5 it plays the 2040K video stream.
Expected behavior: In 0.4.1.1 the 2040K video stream should play.
Actual behavior: In 0.4.1.1 the 64k audio stream plays.
Steps to reproduce:
1) Go to my page for 0.3.5 with my soccer video: http://rawgit.com/tommyh/602b085e5f973b09c411/raw/8b439e84ce85ec61dedb294731336d810514b54b/version_0-3-5_with_soccer_video.html
2) Click play and notice how you see video content.
3) Look at the developer console and you should see this:
```
INFO:https://github.com/mangui/flashls/releases/tag/v0.3.5
INFO:HLSProvider: new level index 0 bitrate=64000, width=0, height=0
INFO:HLSProvider: new level index 6 bitrate=2040000, width=0, height=0
INFO:video size changed to (1024,576)
```
4) Go to my page for 0.4.1.1 with my soccer video: http://rawgit.com/tommyh/602b085e5f973b09c411/raw/8b439e84ce85ec61dedb294731336d810514b54b/version_0_4_1_1_with_soccer_video.html
5) Click play and notice how hear the audio but see no video content.
6) Look at the developer console and you should see this:
```
INFO:https://github.com/mangui/flashls/releases/tag/v0.4.1.1
VM334:1 INFO:HLSProvider: new level index 0 bitrate=64000, width=0, height=0
```
For reference, I also made test pages with your sample video, but your sample video plays fine in both versions:
http://rawgit.com/tommyh/602b085e5f973b09c411/raw/8b439e84ce85ec61dedb294731336d810514b54b/version_0-3-5_with_demo_video.html
http://rawgit.com/tommyh/602b085e5f973b09c411/raw/8b439e84ce85ec61dedb294731336d810514b54b/version_0_4_1_1_with_demo_video.html
Environment: Mac OS X 10.8.5, Chrome 44.0.2403.125 (64-bit), Good internet connection
Can you reproduce this behavior as well? Or is it just me?
Note: For right now I am sticking with version 0.3.5 and that looks good to me. But wanted to reach out with this issue as soon as I could to put it on your radar.
Thanks,
Tom
PS: I've started to make a videojs plugin for flashls to make the integration slightly easier. The main thing it does is register a source handler w/ videojs, so the developer can set the content type of their m3u8 source to "application/x-mpegURL": https://github.com/tommyh/videojs-flashls/blob/master/videojs.flashls.js. Do you think you'd want to put this into the flashls readme?
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue using the linked 0.3.5 and 0.4.1.1 soccer-video pages, then compare the HLSProvider console output and selected levels between those releases. Trace the release behavior responsible for selecting only the 64k audio stream; done means the 0.4.1.1 page selects and plays the 2040K video stream as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100