There are lots of causes of playback failures. You can locate the problems in the following steps:
Theoretically no. As the VOD system does not set any limits, it allows an unlimited number of online viewers to watch videos at the same time.
If the video file itself is ruled out as the cause, lagging may be attributable to low device specification or poor network environment (e.g., bandwidth and latency). You can change the device used for playback or the network environment if possible. If the problem persists, please contact us.
The browser blocks the video for security reasons. Please make sure that videos using HTTP are played back on the webpage using the same protocol, and the same is true for HTTPS videos.
Please contact us to help you locate the problem and restore CDN resources.
Please check whether referer or key hotlink protection has been enabled and whether there are authentication parameters during playback.
This is because the WeChat browser blocks the video. You need to appeal to WeChat to remove the blockage.
To play back videos with Flash on PCs, the
crossdomain.xml file and correct access policy need to be configured and cross-domain access need to be enabled for the video storage server.
www.a.comdomain needs to access a file in
www.b.com, SWF first checks whether the
crossdomain.xmlfile is in the root directory of the
www.b.comserver, and if not, the access will fail; if the file is there and access is allowed for the
www.a.comdomain, the communication will be normal.
crossdomain.xmlcontains the domain name configuration of the SWF file.
To play back videos in HLS or FLV format by using HTML5 in modern PC browsers, CORS needs to be configured for the video server.
Generally, the above two policies are configured automatically by Tencent Cloud. If you have any problems, please contact us.
Please transcode the video. For detailed directions, please see Processing Videos. Please make sure that the video codec is H.264 and container format is MP4 or HLS.
VOD only allows specifying image or text watermarks during transcoding and does not support dynamic watermarking for different viewers.
Yes. For more information, please see video compositing in the video processing features of VOD.
You need to first find out whether there is any problem with the source video. If the problem is caused by transcoding, please contact us.
Generally, web playback depends on the decoder of the browser or the Flash decoder. If playback is not supported, error code
4 will be returned.
Flash is required for playing back RTMP and FLV videos as well as any videos in IE. Please install and enable it.
If Flash is not supported, the player will use MSE to play back videos in HLS or FLV format; if MSE is not supported either, you will have to change or upgrade the browser. Currently, browsers that support MSE include Microsoft Edge, Chrome, Mozilla Firefox, and Safari 11+.
Generally, there is no corresponding video decoder in the browser kernel of some PC software programs or applications in integrated or lite editions. Please upgrade the browser kernel in them or integrate with Flash and allow it to be called.
To play back a video online is to download it first and then play it back, so it is impossible to prevent a video from being downloaded by others. If you want your videos not to be played back after being downloaded by others, please see video encryption in VOD.
The playback process of an HLS-encrypted video is different from that of ordinary videos. Generally, you need to get the right key. The steps to fix this problem are as follows:
You are recommended to avoid playing back the source video; instead, transcode it first in VOD. Please select the HTML5 playback mode rather than use Flash. When a video is too short, there is generally only one keyframe, so dragging for playback is not supported.
Autoplay of multimedia files is prohibited in many browsers, especially mobile ones. However, some browsers allow autoplay of muted videos or videos with no audio tracks, so you can try to mute the player. If this still does not work, there will be no effective solutions currently.
The multimedia autoplay attribute needs to be set in the WebView:
Whether a web player displays the first video frame depends on the support from the browser. Currently, not all browsers support showing the first video frame. You can fix this problem by setting a cover for the video.
Currently, only some modern browsers support adjustable-speed playback in HTML5, and this feature is not supported by Flash. Therefore, adjustable-speed playback is allowed only in browsers that support HTML5.
You can try the HTML5 mode for playback; if the adjustable-speed playback button does not appear, this feature is not supported; if the button appears but the speed cannot be adjusted, the player has detected that the current browser supports setting adjustable-speed playback, but the settings fail to take effect. In this case, you are recommended to hide the adjustable-speed playback button.
The player controls are the browser's built-in controls. You need to stop pinning the video by using the method provided by the browser vendor. Currently, there are no general solutions.
You can try to hide the video tag, which can be displayed again when playback starts.
Ad placement (e.g., ads appear when playing a video on WeChat) is a kind of hijacking by browser vendors. You have to block ads as permitted by browser vendors. Currently, there are no general solutions.
Tests show that there no effective frontend solutions. This is because after hijacking video playback, the browser fails to optimize the viewing experience effectively. You can try to use the video tag directly (not generated by the player) or draw the video by using Canvas. If the problem persists, it can only be solved by upgrading the browser.
Please make sure that the aspect ratio of the player is the same as the actual ratio of the video.
For example, if a video's resolution is 1280 * 720, the size of the player can be set to 640 * 360 or 1280 * 720. As long as the ratio equals to 16:9 (1280:720), the video can be fully displayed with no black bars. If the video has black bars itself, they need to be cut off during transcoding to change the resolution.
Currently, a web player is unable to detect landscape/portrait mode switching during a push, so this problem has to be addressed in other ways.
For example, assume that the portrait mode is used when a push starts, and the aspect ratios of the upstream video and the web player are both 9:16; if the push is not interrupted on the device (depending on the support from the push SDK) and the portrait mode is switched to the landscape mode, the aspect ratio of the upstream video will change to 16:9. If the aspect ratio of the downstream video also changes to 16:9, reconnection to the web player will be needed before the video can be played back at the new aspect ratio. In order to reconnect, the web player needs to be notified by an external API. If the aspect ratio of the downstream video is still 9:16, the video will be played back at 9:16.
A VOD playback address does not support the DNS protocol of HTTP currently.
Flash needs to be enabled in PC browsers.
The ad placement feature is not available yet. You can use the rolling feature of the player or customize the web player for adverting. For more information, please see TCPlayerLite.
Transcoding is not mandatory in VOD; however, playback of files not transcoded may fail on third-party platforms; therefore, transcoding is recommended.
You can configure the target bitrate to be the same as the original bitrate. The encoder will also assign a bitrate accordingly. There may be cases where the actual transcoded bitrate doesn't need to be very high, and the bitrate will be thus decreased. If the decrease is significant, please submit a ticket for assistance.
No. The video can be played back and cached only after being decrypted.