After record a video with "Record a video" voice command,
and if you say "Share this with", you see a list of apps via which you can share the video.
I want to attach my app to this list of apps in order to let the user to share the video via my app.
I picked up "SHARE_THIS_WITH" default command and define it as our trigger like below.
<trigger command="SHARE_THIS_WITH" />
But this simply adds "Share this with" command in the top voice command list shown after initial "ok glass" instead of showing my app after "Record a video -> Share this with" flow.
How can I add my app to the end of "Record a video -> Share this with" flow ?
And how I can get video data when triggered by this flow ?
I cannot find any document for this.
With the GDK, there is no direct way to be a share target for media at this time. The best solution at this point is to have your service monitoring for new media that shows up and processing it.
You can setup share contacts under the Mirror API, however. If your processing involves a network, you may wish to investigate this avenue.
Related
I need to configure live streaming using OBS studio software, live streaming has already been setup on AWS using ElementalMediaLive(auto wizard). but I am unable to figure out the way to find the server address and stream key which are required the configure the OBS studio.
can some one please guid me where can I find the above required information into AWS panel?
Thanks
That is the "stream name" in the rtmp ingest point URL. The format would be something like
rtmp://domain:1935/live/streamname
stream key in OBS is streamname
For detail, please refer to page 7 and 8 of this pdf: https://d2908q01vomqb2.cloudfront.net/fb644351560d8296fe6da332236b1f8d61b2828a/2020/04/14/Connecting-OBS-Studio-to-AWS-Media-Services-in-the-Cloud-v2.pdf
Have a look here:
https://aws.amazon.com/de/blogs/media/connecting-obs-studio-to-aws-media-services-in-the-cloud/
Especially this document:
https://d2908q01vomqb2.cloudfront.net/fb644351560d8296fe6da332236b1f8d61b2828a/2020/04/14/Connecting-OBS-Studio-to-AWS-Media-Services-in-the-Cloud-v2.pdf
Where it says:
STEP C: CONFIGURE THE APPLIANCE
Launch OBS Studio on the source system. Choose Settings to open the settings window. Choose Stream to access the streaming settings.
Complete the fields:
For Stream Type, choose Custom Streaming Server.
For URL, copy one of the endpoint URLs from the input you created in Step B. Remove the /<stream_name> at the end of the URL.
For Stream key, type the stream name.
Leave the Use authentication box unchecked.
Choose Apply to save your changes.
What OBS refers to as "stream key" is the App Instance.
Regards,
I have a Sumerian Host that acts basically as a front-end for a Lex chatbot.
However, in some cases, I need to to some processing based on the actual user utterance (that is, the text of what the user says). Is there a way I can use "Send Audio to Lex" action (or a different one) to get a text version of the user audio (so, to perform speech-to-text)?
Could someone inform what is the most correct way to verify what is the information sent by the GTM event tag screenshot to an Recommendations AI project?
Confirm your triggers are not misfiring by using the preview mode in GTM: https://support.google.com/tagmanager/answer/6107056?hl=en
As Eike mentioned, open the Developer's console Network tab https://developer.chrome.com/docs/devtools/network/
Clear the log in the Network tab. And select All in the Network filters.
Conduct an action that triggers your tag.
In the Network tab, there are now new activity is shown. Select the one that looks like your endpoint and that has a valid response code (it's almost always 200)
Scroll down to the Query String parameters and assess your payload:
Like so:
I am creating HITs on MTurk Sandbox using JAVA API. I am able to create HITs and also work on it by searching through worker UI. But those hits are not showing up in the "Manage" tab of the requester UI.
So as to interact with my own MTurk tasks I have developed a rudimentary management console to monitor, review, manage, and download data from API-launched tasks.
The management console is entirely JavaScript based and runs locally in your web browser. It replicates most of the basic functionality removed with the Manage HITs individually module in the December 2017 changes. You will need your API keys to use the tool but these are not stored nor transmitted to myself or any third-party.
You can download a copy from GitHub: https://github.com/jtjacques/mturk-manage/archive/master.zip
Please see the included README for comprehensive information about the tool, available on the GitHub project page https://github.com/jtjacques/mturk-manage
The "Manage" tab in the MTurk Requester Website is for managing Batches created with the MTurk Requester Website (using the Create) tab. If you need/want to view HITs that you create with the API, you can use the ListHITs API method either with the API directly (using your Java code) or using the AWS Command Line Interface (CLI).
Here's a blog explaining how to do this with the AWS CLI:
https://blog.mturk.com/tutorial-managing-mturk-hits-with-the-aws-command-line-interface-56eaabb7fd4c
The blog shows how to use aws-shell, which is a more interactive shell that sits atop the AWS CLI. It has autocomplete and shows you inline "man" pages on each command. I personally prefer this.
The CLI and aws-shell will also let you write filters and formatters for results. So you can do things like this:
aws mturk list-hits --output table --query 'HITs[].{"1. HITId": HITId, "2. Title": Title, "3. Status":HITStatus}' --endpoint-url https://mturk-requester-sandbox.us-east-1.amazonaws.com --max-results 5
This calls ListHITs, on the Sandbox (--endpoint), getting only 5 results (--max-results), formats the output as a table instead of the default JSON (--output) and filters that JSON for the HITs object (HITs[]) pulling down only the fields HITId, Title, and Status while also setting titles for those fields as "1. HITId", "2. Title", and "3. Status".
There used to be a link in the MTurk Requester Website for a GUI to manage HITs individually which would show HITs from the API, but it was deprecated this month. There's a brief thread on it here: https://forums.aws.amazon.com/thread.jspa?threadID=267769&tstart=0
I am tired of one problem so please make things clear to me.
Please read these following three points and help me out.
(1)
I have simply followed this https://www.wowza.com/docs/how-to-start-and-stop-live-stream-recordings-programmatically-livestreamrecordautorecord-example#documentation
I have attached my Application.xml. Now when I publish live stream name "test1" via FMLE it get recorded on server but when I run different instance of FMLE on different PC and publish live stream name "test2" it does not get record and I think it goes to previously recorded file "test1" (means no separate file being record, however there should be two files recorded test1 and test2).
Why this happenning ?
Is this com.wowza.wms.plugin.livestreamrecord.module.ModuleAutoRecordAdvancedExample for single stream recording ? means If I publish stream A B C D , it will record them in one single file ? (probably the output file will be A.mp4 as A was first published stream ?)
(2) What is this https://www.wowza.com/docs/how-to-start-and-stop-live-stream-recordings-programmatically-imediastreamactionnotify3#comments module for ?
I have implement this code in Eclipse and successfully put jar in lib folder and configured everything. Now again I am not able to record different streams with their corresponding name. Means If I publish stream1 and stream2 then desired output should be two different files (in content folder) but again I see one single file being record ?
(3) Can I use ModuleLiveStreamRecord.java ? This was in older version of WOWZA but I have properly imported required jar and tested it.
My requirement is very simple:
As soon as users start publishing, WOWZA should start live recording. If 10 users publishing live, 10 files should be generate.
Don't make things more difficult than necessary (assuming you have Wowza 4.x; if you still have 3.x then I highly recommend to upgrade for free)
Open the Engine Manager (http://your.server.com:8088)
Go to "Applications" from the top menu
Select your application from the left menu (e.g. "live")
In the setup window for this application, click the blue Edit button
Enable "Record all incoming streams"
Click "Save"
Click the orange "Restart now" button at the top
Done
Every stream that is published via this application will now automatically be recorded. The default folder for recordings is the /content folder in your Wowza installation. You can change this on the same page under "Streaming File Directory" (make sure it's a directory on your local system, unless you really well understand how Wowza works)
The filename is always the streamname + ".mp4", but when you start a new recording while the file already exists, the old file will be renamed first.
Want to control recording manually? Start publishing first, then select "Incoming streams" from the left menu and use the big red dot button behind a stream name to start recording.
If your server produces any different behavior with regards to the file (re)naming or recording, then you may need to review your Wowza setup.
I appreciate your response KBoek.
I sorted out issue but there were really debugging need if one doing custom module. I had to write custom module for live auto recording because I wanted HTTP authentication and then custom name of live recording.
thanks again