M3u8 Not Playing after first ts segment
Nobody has claimed this yet.
- Dominant language
- ActionScript
- Stars
- 744
- Forks
- 259
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
I have been trying to play a m3u8 file with segments having byte ranges. The file works smoothly till end if no action is performed(pause/play). But when pausing and playing the file, it doesn't play or even when you seek the audio, it doesn't resumes.
When debugged, found that when the first segment is playing(around first 10 secs), any action(pause/play) can be done it works fine, but when the second segment is loaded after that no actions can be done as the exoplayer stuck and never recovers. The Exoplayer stays in **STATE_BUFFERING** state and doesn't recovers to **STATE_READY** state after first segment is over and any action is performed after it(After first segment).
On further debugging, we found that **TsExtractor** class was not able to extract the segments as the **payloadReader** was getting **NULL** after first segment, might be **tsPayloadReaders** is not working properly. There could be a issue with the m3u8 file as well.
There's no further clue to solve this issue, kindly help me resolving this issue. I'm **attaching** the m3u8 file inside zip
[audio.m3u8.zip](https://github.com/mangui/flashls/files/2114055/audio.m3u8.zip)
.
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
Start with the attached audio.m3u8 file and reproduce pause/play or seeking after the second segment loads. Trace TsExtractor and the tsPayloadReaders path where payloadReader becomes null. Done means playback returns from STATE_BUFFERING to STATE_READY after those actions.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100