My Question is
I push HLS steram to gnh(google nest hub) by action.devices.commands.GetCameraStream response format.gnh do nothing but show loading UI some seconds.
It's somthing wrong with my HLS file?
How to get log from gnh to help me debug?
As I know
I am tried to push mp4(1080p/under 60 fps) url to gnh, that's work well.
I am tried to convert mp4 to hls by some lib,include ffmpeg,Bento4.
Here is my JSON send to gnh:
{
"payload": {
"commands": [{
"status": "SUCCESS",
"states": {
"cameraStreamAccessUrl": "http:/path/of/steram.m3u8"
},
"ids": ["....."]
}]
},
"requestId": "My_Request_Id"
}
It seems that you are missing the required property cameraStreamSupportedProtocols. Try adding the protocol and see if you are able to get the stream to work. This will load the default cast camera receiver since you are trying to play HLS content. If you are still seeing an issue with playback, it could be that your stream is malformed and needs to be revised.
Playback logs will only be available to you if you create your own basic receiver app and specify this in your response using the cameraStreamReceiverAppId property. To see more about creating a cast receiver app refer to the overview page (https://developers.google.com/cast/docs/web_receiver) and how to create a basic receiver (https://developers.google.com/cast/docs/web_receiver/basic) for more information. We also do have a default camera receiver sample located in our sample github (https://github.com/googlecast/CastCameraReceiver)
Related
I am currently implementing Stream chat SDK in my react native app. When implementing push notifications, I was able to test and receive messages using stream chat:push:test --user_id command and actually sending messages in the app, but the payload I receive from Stream is always just
Here is the generic rendered notification payload that will be sent to
your devices: {
"sender": "stream.chat",
"type": "message.new",
"version": "v2",
"message_id": "88280bc0-23d6-43b9-b9e3-062b3a1a3dca",
"id": "88280bc0-23d6-43b9-b9e3-062b3a1a3dca",
"channel_type": "shellterChat",
"channel_id": "courseChatENES462JamesGreen202201",
"cid": "shellterChat:courseChatENES462JamesGreen202201" }
Currently, I am running client.getMessage() with the messageId from the payload to fetch the actual message, and display using Firebase Notifee, but this is problematic because I can't do the fetching when the app is at quit state (at index.js in my react native app). Am I missing something? Should the stream push payload include the actual message (including title, body, etc for push)? The document just says SDK will automatically handle it, which doesn't really make sense to me. Thank you for your help in advance.
React Native Firebase library provides a nice to handle background and quit state of the application as mentioned here - https://rnfirebase.io/messaging/usage#background-application-state
I've got a link from Tuya API explorer using the service "IoT Video Live Stream". I want to know where I can use this link for stream my camera's video. I have the video on my tuya APP, but I want use this link.
Here's an example of the API return.
{"result": {
"url": "rtsps://eb3ba0.....aa418b.....:4UBYKMX9T.....T0#aws-tractor1.tuyaus.com:443/v1/proxy/echo_show/b6721582601.....b46ac1b71.....bbb3d*****bf7.....},"success": true,"t": 1642462403630}
I am trying to embed a Facebook Video in an Apple News Article Body.
According to the documentation iframes are not supported so I am left with EmbedWebVideo and Video Components.
EmbedWebVideo seem to only support YoutTube and Vimeo so I am left with Video component.
I tried both, EmbedWebVideo and Video componet but no luck. Both do not work. The Video component displays the player but video does not load. This was tested locally on a macbook (using News Preview). When using the same Video component with a link to an example apple video https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_4x3/bipbop_4x3_variant.m3u8 the component loads the video and is playable.
Are facebook videos supported at all? Do I need a specific link? I tried both, the short and long links that I can get from requesting embed video code.
Components and variations of link types I tried:
{
"role": "video",
"url": "https://www.facebook.com/plugins/video.php?href=https%3A%2F%2Fwww.facebook.com%2FPageName%2Fvideos%video-number%2F"
},
{
"role": "video",
"url": "https://www.facebook.com/PageName/videos/video-number/"
},
{
"role": "embedWebVideo",
"url": "https://www.facebook.com/plugins/video.php?href=https%3A%2F%2Fwww.facebook.com%2FPageName%2Fvideos%video-number%2F"
},
{
"role": "embedWebVideo",
"url": "https://www.facebook.com/PageName/videos/video-number/"
}
Any help would be greatly appreciated.
You can embed a Facebook video using the FacebookPost component, but you have to modify the structure of the URL to get it to pass validation. A structure of https://www.facebook.com/{username}/posts/{video-id} for the url should work (note it uses /posts/ instead of /videos/.
I am refereeing the code from GitHub for audio AND video conference using Kurento composite media element, It work's fine for audio AND video streaming over WebRTC.
But I need only audio conference using WebRTC, I have added changes in above GitHub code and new code is uploaded on GitHub Repository.
I have added below changes in static/js/index.js file
var constraints = {
audio: true, video: false
};
var options = {
localVideo: undefined,
remoteVideo: video,
onicecandidate : onIceCandidate,
mediaConstraints: constraints
}
webRtcPeer = kurentoUtils.WebRtcPeer.WebRtcPeerSendrecv(options, function(error) {
When I am running this code, no error for node server as well as on chrome console. But audio stream does not get start. It only showing spinner for long time. Chrome console log is here.
As per reply for my previous stack overflow question, We need to specify MediaType.AUDIO in java code like below
webrtc.connect(hubport, MediaType.AUDIO);
hubport.connect(webrtc, MediaType.AUDIO);
But I want to implementing it in Nodejs using kurento-client.js, I did not get any reference to set MediaType.AUDIO to connect with hubPort and webRtcEndpoint in Nodeja API.
Please someone can help me to do code changes for same in Nodejs or suggest me any reference so I can implement only audio conference using composite media element and Nodejs.
This should do
function connectOnlyAudio(source, sink, callback) {
source.connect(sink, "AUDIO" , function(error) {
if (error) {
return callback(error);
}
return callback(null);
});
}
We are in the process of improving the documentation of the project. I hope that this will all be made more clear in the new docs.
EDIT 1
It is important to make sure that you are indeed sending something, and that the connection between your client and the media server is negotiated correctly. Going through your bower.json, I've found that you are setting the adapter dependency as whatever, so to speak. In the latest releases, they've done some refactoring that makes the kurento-utils-js library fail. We haven't yet adapted to the new changes, so you need to fix the dependency of adapter.js like so
"adapter.js": "v0.2.9"
i'm using the Box View API to convert a PDF file to HTML, i'm using the /documents/{id}/content.{extension} section.
The response for this GET call is a .zip file, however i don't know how to retrive it and make downloadable.
Also note that i'm using node.js.
Thanks for your help
You can set your own webhook URL that will be called by Box when your document status changes (one POST on your webhook for "document.viewable", and one for "document.done" plus one "document.error" if an transformation error occured).
Just listen to the "document.done" status and download the assets then. Format that is posted to the webhook you have set looks like :
[{
"type": "document.done",
"data": {
"id": "4cca28f1159c4f368193d5014fabc16e"
},
"triggered_at": "2014-01-30T20:33:04.798Z"
}]
Beware of the docs and check the format programatically. Their API docs are often no quite correct and they post multiple webhooks at the time i'm writing (which is a bug i've reported).
For more info and Box View API docs