How to put local audio to chrome cast in iPhone - objective-c

I want to play local audio file to chrome cast device,I am getting MPMedia item and i created server in iPhone using iPhonehttpserver.
My problem is how to send MPMediaitem to chromecast device using httpserver. Please help me

You need to send the url that points to your (locally) served media to chromecast; your local server on iPhone provides a url through which other clients can access the media, send that url to chromecast so it can play the media.

Related

Azure Media Services - Can't connect to RTMP

I wanted to stream from my mobile device (iPhone 7 Plus / V14.1) with Larix and GoPro App to Azure Media Services:
rtmp://test-livestream-usso.channel.media.azure.net:1935/live/xxxxxxxxxxxxxx70af
Both devices can't connect to the RTMP on Azure. When I tip the rtmp url into my OBS, it works perfect. Any idea what the issue could be here?
Bests,
Yanick
OBS and a lot of encoders automatically add on a stream key at the end of the path.
Just add an additional /whatever after the GUID to make it work.
Also make sure you are not sending >30fps. We only accept up to 30fps 1080P.
BTW, my GoPro Hero 8 works just fine adding an additional stream key path after the ingest path GUID.

react-native-af-video-player "Oops! there was an error while playing this video please try again later"

I'm using this library "react-native-af-video-player" for playing videos from my remote server, and its working perfectly on android, but on iOS its giving this error "Oops! there was an error while playing this video please try again later".
I tried giving a random dummy .mp4 url and it worked normally, only the videos from my server are not being read.I added my servers url to the "Exception Domains" in "App Transport Security Settings" in info.plist file but it didn't work. Any help would be appreciated.
Apparently, HTTP servers hosting media files for iOS must support byte-range requests, which iOS uses to perform random access in media playback. (Byte-range support is also known as content-range or partial-range support.) Most, but not all, HTTP 1.1 servers already support byte-range requests.
If you are not sure whether your media server supports byte-range requests, you can open the Terminal application in OS X and use the curl command-line tool to download a short segment from a file on the server:
curl --range 0-99 http://example.com/test.mov -o /dev/null
If the tool reports that it downloaded 100 bytes, the media server correctly handled the byte-range request. If it downloads the entire file, you may need to update the media server to support byte-range requests.

How RTSP stream can be loaded to an HTML5 player to support multiple OS and browsers?

I am trying to play an rtsp format url in browser .i used video js to do it. But i cant play it or the browser is not streaming it.
I tested in IE,Chrome, and Firefox.
Could you please help me to find a solution?

Kurento Media WebRTC to RTP

I am using kurento's master git to make a WebRTC to RTP bridge.
MediaPipeline pipeline = kurento.createMediaPipeline();
WebRtcEndpoint webRtcEndpoint = new WebRtcEndpoint.Builder(pipeline).build();
HttpGetEndpoint httpEndpoint=new HttpGetEndpoint.Builder(pipeline).build();
org.kurento.client.Fraction fr= new org.kurento.client.Fraction(1, 30);
VideoCaps vc= new VideoCaps(VideoCodec.H264,fr);
httpEndpoint.setVideoFormat(vc);
AudioCaps ac= new AudioCaps(AudioCodec.PCMU, 65536);
httpEndpoint.setAudioFormat(ac);
webRtcEndpoint.connect(httpEndpoint);
However inspite of this the output video playing is encoded to webm . I have tried various other approaches as well ( using RTP ENdpoint , using Gstream filter , using VLC HTTP to RTP streamer ) . however no method gives me a video playable on safari and IE ie H264 encoded . Requesting media developers and kurento team for help .
Safari and IE do not support RTP/H.264. From you code, I understand that you are trying to create a WebRTC to tag bridge. In that case, the HttpGetEndpoint will provide media through HTTP pseudostreaming. However, Kurento only provides that type of live HTTP pseudostreaming in WebM format. To be best of my knowledge, neither Safari nor IE support WebM, hence what you want to do will not work independenlty on the caps you force to the HttpGetEndpoint. You will be only able to see it working on Chrome, Fireforx or other browsers with WebM support.
The only solution for you could be the HttpGetEndpoint providing media in MP4 format (or any other format supported by IE and Safari), but creating the live stream in that format is very tricky and we (the Kurento team) did not had the time for implementing that and this feature is not in our short term roadmap.
However, we have many users integrating WebRTC with IE and Safari using RTMP. In that case, you need to integrate Kurento with an RTMP capable media server (this can be done in different ways) and later let the RTMP media server to serve media to the browsers.

Android MedioPlay How to play http or rtsp stream?

I'm trying used mediaplay play http or rtsp protocol uri from server, when I play the
address as http://**.wma or *.mp3 ,it can working,but I tryed played the address as
"http://qr.fm.qq.com/qqradio?qqradio",it didn't working.
and also I'trying used VideoView play rstp protocol uri from server,when I play the adress as
“rstp://*.sdp”,it can working ,but I tryed play the adress as "rtsp://vs1.thmz.com/radio31"
,it didn't working.
Anybody help me and tell me how
These are live streams, not static files, so, while it may play back some .wma and .mp3 content - these live streams are not defined like that.
Are you sure the first stream link is valid? After a quick scan with nmap, it seems you may need to be in china to connect to this feed (qq.com Registrant Country Code - CN) I get 1000 scanned ports all filtered, usually means a firewall blocking specific geographic regions.
rtsp://vs1.thmz.com/radio31 -> This is a Windows Media Audio stream, using WMA2 codec, delivered via RTSP, which according to the Android Supported Media Formats: http://developer.android.com/guide/appendix/media-formats.html - is NOT supported.