![]() Note: Please do not include any personally identifiable information from the viewer in this data. This value is not aggregated with other errors and can be used to provide detailed information. You can use player_error_context to provide instance-specific information derived from the error such as stack trace or segment-ids where an error occurred. To make error aggregation as useful as possible, these values should be general enough to provide useful information but not specific to each individual error (such as stack trace). The error message and code are combined together and aggregated with all errors that occur in your environment in order to find the most common errors that occur. For instance, if your library has two different conditions for network errors, both should have the same player_error_code but different messages. In general you should not send a distinct code for each possible error message, but rather group similar errors under the same code. However, for custom errors, you should choose a number greater than or equal to 100. If the errors match up with the HTML Media Element Error, you can use the same codes as the corresponding HTML errors. The player_error_code must be an integer, and should provide a category of the error. The player_error_message should provide a generalized description of the error as it happened. When triggering an error event, it is important to provide values for player_error_code and player_error_message. now ( ) // Initialize Mux Data monitoring by passing in the "id" attribute of your video player There must be an issue with the encoding.Import mux from 'mux-embed' const playerInitTime = mux. Has anyone a clue what's going on there? Thanks in advance!Įdit: Safari and Chrome both throw MEDIA_ERR_SRC_NOT_SUPPORTED Error on iPad. This is needed to get partial content from the server. My Apache has AddType video/mp4 mp4 m4v f4v f4pĪnd byte-ranges are enabled. I read this article on Video on the web, especially this part and only serve the "right" file with the "right" type without a posterattribute set. All work in the environments listed above except for iPhone and iPad. I tried various ways: own implementation with own interface, controls and stuff from browser vendors and video.js just to check whether i'm too studip for this. Last thing is adding the right MIME type. With Modernizr I detect which format is "supported" and add it to the src or the video tag. In fact the ffmpeg cmd looks like this: ffmpeg -i _inputfile_ -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3.0 -b:v 200K -r 17 -bt 800K -c:a libfdk_aac -b:a 85k -ar 44100 -y _outputfile_lowversion_.mp4 I found various requirements for iOS devices like this and this, also someone mentioned to add the yuv420p pixel format when converting. Stream #0:0(eng): Video: h264 (Constrained Baseline) Stream #0:1(eng): Audio: aac (LC) (mp4a / 0圆134706D), 48000 Hz, stereo, fltp, 56 kb/s (default)Įdit: Whole ffprobe output (slight changes in bitrate etc.The MP4 (h.264 + acc-lc) is converted like this (with profile: baseline and level 3.0 for maximum compatibility with iOS): The only problem I'm experiencing is, that it won't play on iPad and iPhone (Safari of course). In Safari on Windows and Mac my MP4 version works, too. For Firefox, Chrome and Opera WEBM works as expected. I want to display HTML5 video to my users using the video tag.
0 Comments
Leave a Reply. |