Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(id3): ignore unsupported id3 frames #437

Merged
merged 1 commit into from
Mar 21, 2019
Merged

fix(id3): ignore unsupported id3 frames #437

merged 1 commit into from
Mar 21, 2019

Conversation

gkatsev
Copy link
Member

@gkatsev gkatsev commented Mar 20, 2019

When we get an unsupported id3 frame, we don't parse its time. This ends
up coming back to us as NaN in the timing for the frame. Instead of
trying to create a cue for this frame, ignore it whenever the time isn't
a number or when it isn't finite.

Fixes videojs/video.js#5823

When we get an unsupported id3 frame, we don't parse its time. This ends
up coming back to us as NaN in the timing for the frame. Instead of
trying to create a cue for this frame, ignore it whenever the time isn't
a number or when it isn't finite.

Fixes videojs/video.js#5823
@RafalLukawiecki
Copy link

I would be happy to test it using our media. I will get back to you before the weekend, as a little overloaded with workload at the moment. If it does not fix it, I will make example media available for your testing.

@gkatsev
Copy link
Member Author

gkatsev commented Mar 20, 2019

@RafalLukawiecki that would be awesome!

@RafalLukawiecki
Copy link

Pleasure. I just realised that the PR is on the http-streaming component only. Can I get the PR easily applied using a patch to the npm-installed most recent version of video.js or do I need to create a new testing environment for this PR?

@gkatsev
Copy link
Member Author

gkatsev commented Mar 20, 2019

@RafalLukawiecki
Copy link

Thank you, I understand now. In that case it will still require me to make one of our video streams public, so that I can play against your hosted test. Will do.

@gkatsev
Copy link
Member Author

gkatsev commented Mar 20, 2019

since it loads from your browser, as long as you can reach the resource you should be able to test without making it public to the web at large

Copy link
Member

@misteroneill misteroneill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code change looks good, but I haven't tried it.

@RafalLukawiecki
Copy link

I have tested using your very helpful hosted tester. I am very happy to say that this PR fixes the bug that we have encountered. Many thanks! When will it appear in a version of video.js that we can install using npm? Otherwise we have to build from source, right?

@gkatsev
Copy link
Member Author

gkatsev commented Mar 20, 2019

@RafalLukawiecki glad to hear it! If we can test it on our end, it may be out this week, otherwise maybe within a couple of weeks.

@RafalLukawiecki
Copy link

@gkatsev Would it help if I made a video stream available publicly that showed the original issue and which works now? I can have that ready tomorrow.

Copy link
Contributor

@ldayananda ldayananda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed, and tested with one source

@gkatsev gkatsev merged commit 7040b7d into master Mar 21, 2019
@gkatsev gkatsev deleted the untimed-id3 branch March 21, 2019 15:18
brandonocasey added a commit that referenced this pull request May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants