Also, the cloud is online H.265 from the coded decoding to the CDN distribution, the complete end-to-end adaptive solution; provides video upload, video storage, video coding, video distribution, video decoding, etc. It is also advisable to provide a large company to more companies with a cloud service.
What problems do you need to solve the video website support H.265?
Compared with H.264, it has 2 times compression efficiency (Photo Via WWDC)
Higher compression ratio requires more advanced technology, H.265 handles images through more intelligent algorithms, maintaining lower bit rate while maintaining quality, but also pays a certain price: significantly increased compression effect, depending on The algorithm complexity requires several times the current 2K resolution deployment of the H.264 codec to support, and this capability requires a large number of servers to support.
In addition, given that some clients do not support H.265 videos, it is also necessary to effectively identify the client, respond to the video of different copies to the client.
Also shoot cloud H.265 video adaptive plan
Also shoot cloud H.265 video adaptive solution integrates video upload, video storage, video coding (transcoding), video distribution, video decoding and other functions.
Video transfer code: Use another cloud storage, you can meet the needs of the video upload acceleration, transcoding, storage. On the basis of using cloud storage, the user selects the video stored by the uploaded H.264, and synchronizes to H.265 encoded video storage; video asynchronous transcodation: for H.264 encoded on the clouds Video, through another cloud asynchronous transcoding service, can be converted to H.265 video storage, while retaining H.264 video copy; H.265 distribution advice: H.265 distribution adaptation feature in again and cloud CDN level, Intelligent identification can be performed on different clients, responding to different encoded video resources while user access.
How does CDN identify H.265 video request?
CDN Current Identification Client Support H.265 Decoding is judged by HTTP Request Head: Accept-Encoding: H265, the CDN receives the request, and then determines whether the CDN node has a H.265 cache copy, otherwise directly returns the original Video resources.
As can be seen from the flow chart, the H.265 video resource responds to the head of Content-Encoding: H265.
H.265 Video Resource Access Process
• Step 1: Client requests H.265 video resources, for example: http: //video.example.com/test..., http request header carrying accept-encoding: H265, convenient CDN intelligent identification;
• Step 2: The CDN node determines whether there is a H.265 video copy. If there is, it will respond directly to the client, the entire process ends; if not, enter the third step;
• Step 3: CDN Node Return to the H.265 video resource, if it is directly responsive, and caching in the CDN node; if not, enter the fourth step;
• Step 4: The source station returns the original video resource, and the default cache is 6 minutes by default, and the resection of the back source after the expiration.
How to access another cloud H.265 video service
Scene 1: Use another cloud storage
Use and shoot storage, you can meet the needs of video upload acceleration, video transfer (including encoding), video storage. If your video has been transferred to H.265 encoded video, ignore the video transcoding step.
Video upload and storage
Also shoot the cloud object storage service provides a variety of uploading methods such as API, FTP / FTPS, UPX, CURL, SDK, and supports massive safety storage, more, please refer to: also shoot cloud storage service introduction, and shoot cloud storage developer developers tool
Video asynchronous transcodation
If you exist, the original video of the cloud object storage service is H.264 encoded video, while you want to synchronize to H.265 video, we can provide asynchronous video transfer services. See also: also shooting the cloud video processing service
Video distribution
As can be seen from above, you can store two different copy of video resources on another cloud object storage service, one is a H.264 video copy, here is called raw video; the other is the H.265 video copy, so Can meet different client access. You want to support the H.265 video client access to the H.265 video, the client that does not support H.265 video can access the original video copy, at this time, CDN can achieve intelligent recognition through a certain agreement And respond to video resources of different copies.
Mobile SDK decoding
Also shoot the cloud currently supports the mobile H.265 decoding, supports the iOS and Android platforms. See quite: Android SDK and iOS SDK
Scene 2: Use another cloud CDN (user self-source)
Use the user's autonomy, and the cloud does not need to provide the video file storage, and the user will turn the video to the H.265 encoding format, and you can upload itself. The services we can provide include adaptive distribution, mobile SDK decoding.
Direct use of the cloud CDN service needs to follow certain specifications:
HTTP request head
The client needs to initiate Accept-Encoding: H265 request head according to the agreement specification, and the CDN node determines whether the client supports H.265 decoding according to this request. See the above: CDN how to identify H.265 video requests. E.g:
Get / Test.mp4 http / 1.1
Host: http://zhangchao.charmelady.net
User-agent: CURL / 7.43.0
ACCEPT: /
Accept-encoding: H265
H.265 video storage specification
The source station is to distinguish the original video and H.265 format video, the H.265 video storage path requires the agreement to be: URL.H265 to distinguish the original video and H.265 video. E.g:
The original video store path is: /test.mp4h.265 video storage path is: /test.mp4.h265
Recommended reading:
Let Chrome can't see the WWDC live HLS technology detailed
How far is the IPv6 started five years?
Related resources: H265Player: A set of complete web version H.265 player solutions, very suitable for learning ...
Our other product:
