Can anyone tell me, how can I check what protocol is in use, when I watch video by Youtube application on Android? I wonder if it is normal HTTP, or RTSP? I tried to find some information about this, but with no results... Thanks for advance!
You can use Wireshark to view the packets, but YouTube probably use SSL. I suggest using Burp SSL MITM to view the SSL packets, assuming YouTube app don't use SSL pinning.
Related
I am working on an application for google tv with Visio device , i want to know which streaming protocols are avalable for google tv out of these. Can any body give me the reference along with the reply.
HTTP, RTMP, PNM, RTSP, MMS, RTSPU, RTSPT, MMSU, MMST.
Please help any kind of help will be appreciated.
Many thanks
HTTP is going to be your best bet on Vizio wrt ease of setup and development. You can use VLC to experiment with different stream proto's. The thing you should pay close attention to is what codec you are transmitting your media in - https://developers.google.com/tv/android/docs/gtv_media_formats
I am having a wowza server setup and I am able to play my files in iOS ans android. (vod)
Can someone suggest me how can I enable HTTPS for iOS streams and RTMPS for android streams.
As a preliminary steps I have generated my self signed certificate.( I dont know how to use it with wowza server)
please Help me to achieve that. :)
Have you configured vhost.xml file?
http://www.wowza.com/forums/content.php?128
I'm developing mobile apps for iOS and Android. Mostly iOS. One of the clients has a fairly big repository of self-created videos (70+), which the companion website hosts on Vimeo at the moment. I investigated some time to find out, that Vimeo doesn't want and support HTTP live streaming to ease up embedding such videos in an iOS app. But perhaps I'm missing something here.
My question is: What is the best way for hosting videos to embed them in an (iOS) app? I explicitly don't want to use an HTML frame, like UIWebView, for this.
I already have some solutions in mind:
self-hosting, since HTTP live streaming isn't rocket science anymore (think real networks streaming services a few years ago)
YouTube
Vimeo (they got their own iOS app, so they have to do some streaming for themselves, perhaps sniffing the network traffic can lighten things up)
I'm afraid this list isn't complete. So perhaps somebody has some superb ideas on that topic. And yes, commerical plans aren't a show stopper if they're reasonable priced.
Google will be presenting a YouTube API in a few weeks at the Google I/O - perhaps that might be perfect for you.
I just found out that Vimeo has introduced another paid plan apart from the established »Plus« plan: »Pro« for companies ($199/year). One of its features is HTTP live streaming. A staff member states on the forum:
We do support http live streaming. And to answer your initial question, our normal embed code will not recognize when http live streaming is appropriate, nor will it automatically switch over to it. Consequently, you will need to use a third party player with the Http live streaming link in your video's Settings page for your video to play with http live streaming.
But there's a one caveat at the moment: you can't directly access the link to the HTTP streaming playlist via Vimeos API. There's a post on their API forum where people can vote for certain features: Vimeo API forum: http live streaming link through API
I wanna develop a simple two way video call functionality and integrate it within my app.
I found two solutions:
Using Android SIP - i will need to handle sending and receiving streams
Using XMPP - Jingle - i will need to implement the whole protocol
Problem is that i am pretty new to SIP and do know really understand what the SIP protocol on android already handles and how much of development will be needed. I know on the other hand that XMPP on android is not easy as well especially when working with video streams.
I would love to have people thoughts on which solution would be the best to implement knowing that i want:
1. a simple working 2way video chat at first
2. extend the functionality to a system of users (i was thining that using XMPP with openfire will cover this easily but im kind of scared regarding the ammount of work to integrate jingle)
If you have any easier solution to integrate audio/video functionality on android i would be glad to hear from you.
Both solutions are the same in a lot of ways.
SIP and XMPP both take care only of the signaling. The media part (video streams, UDP, etc) are done "elsewhere" and with the same set of protocols: RTP and RTCP for transport and control. H.264/VP8 for the video codec, some other codec for voice.
I'd look into WebRTC to see if it has any available code on Android - that would take care of the media parts nicely.
After carrying out a lot of research I have come to the conclusion that Java and the Java Media Framework (JMF) is not suitable for developing a streaming server that supports the RTSP protocol on the server side for streaming video and audio. I have read very good things about Live555 media server and the testOnDemandRTSPServer source code for a basis of design. My only worry is that this is written in C++ and I am a predominantly Java programmer. This server is a large portion of my final year project at university so my degree kind of hangs on its successful implementation and I am running out of time. If any one has any experience with implementing a RTSP server that can stream to an android handset or belive they can point me in the right direction to learn how to do it, please let me know. Thanks in advance.
My project also has the RTSP server module to be run on Android phone. I think we can build rtsp library as name.so file and can interface with java by using JNI.
This also works for Android!
http://net7mma.codeplex.com/
You can see the article on CodeProject # http://www.codeproject.com/Articles/507218/Managed-Media-Aggregation-using-Rtsp-and-Rtp
The live555 RTSP server is a fully fledged RTSP server that implements most payloads (H.263, H.264, MPEG2, PCM, AMR, AAC, etc. You can read up on the website whether it already supports the media types you want to stream. It also features an RTSP client. With respect to streaming to an android handset: that is the whole point of RTSP: it doesn't matter what type of client you're streaming to, and as for the server side development, there isn't really much dev to do, unless you need to implement an unsupported media type. The code can be quite complex if you're not well versed in c++, but it sounds like your goal is more related to setting up streaming to android as opposed to implementing the RTSP server and client? So check if live555 supports your media types and if it does, I wouldn't bother writing one in JAVA, that can be quite involved. If you do choose to go that route, your best friend is of course the RFC (http://tools.ietf.org/html/rfc2326).
As for the client, I'm not sure if android already has an RTSP library/client. The one other thing you have to consider is which media types are supported by android.