Media_Dev
-
DASH (Dynamic Adaptive Streaming over HTTP)Media_Dev 2013. 1. 29. 14:19
Multimedia tech of DASH is available on this website.We already used to Dynamic Adapted Streaming control with box of moov in mp4 file, however this standard of media can apply to h264 , vod, live especially support Main profile of AVC. http://www-itec.uni-klu.ac.at/dash/ http://en.wikipedia.org/wiki/Dynamic_Adaptive_Streaming_over_HTTP http://dashif.org/
-
How to implement to PAUSE and PLAY via the RTSP protocol.Media_Dev 2012. 2. 7. 20:55
http://www.ietf.org/rfc/rfc2326.txt 10.5 PLAY The PLAY method tells the server to start sending data via the mechanism specified in SETUP. A client MUST NOT issue a PLAY request until any outstanding SETUP requests have been acknowledged as successful. The PLAY request positions the normal play time to the beginning of the range specified and delivers stream data until the end of the range is re..
-
RTSP,OPTION, how to get information base time second from RTSP.Media_Dev 2012. 1. 12. 14:49
After Descirbe , you can get the SDP. then you can see the :range:npt = 0- , that is live. - OPTION rule in RTSP 1. How to use that what kind of Rtsp mathod. ex ) C to S OPTION S to C You can use these methods as like PLAY , PAUSE, DESCIBE 2. Is you live as frequntly. How to play RTP with base Time. - Rtp time stemp - base time = how much spended to time. - RTP time stamp - base time (after reci..
-
Analysis F4M file for fragments streaming.Media_Dev 2011. 11. 18. 19:16
00 00 00 9E : 158 byte 61 62 73 74 : abst 01 : version 00 00 00 00 00 1B FA 21 : 00 00 03 E8 : timescale 1000 00 00 00 00 04 95 DF EF : current media Time 1 76931055/1000 = 76931 sec. 00 00 00 00 00 00 00 00 : curretn emdai Time 2 0 /1000 = 0 sec. 00 : Movieidentifier String is NULL 01 : Server Entry Count 1 00 : Server Entry Table (server URL) 01 : Server Quality Entry count 00 : Server Quality..
-
SSRC: 32 bitsMedia_Dev 2011. 10. 10. 10:22
SSRC: 32 bits The SSRC field identifies the synchronization source. This identifier SHOULD be chosen randomly, with the intent that no two synchronization sources within the same RTP session will have the same SSRC identifier. An example algorithm for generating a random identifier is presented in Appendix A.6. Although the probability of multiple sources choosing the same identifier is low, all..