According to the prompt in the Alexa developer's console, one should be able to click and hold the mic image and then speak to Alexa. This feature seems to be disabled for me (the microphone image is crossed out with a red cross, not sure what the significance of it is):
This occurs in various browsers, Firefox, Chrome, etc. I'm on Mac:
What can be causing this not to work as designed?
This works for me
try clearing your browser's privacy settings and make sure it prompts you for permission to use the microphone. Grant permission to use the microphone and try again. To use the microphone it must not have an X and you click while speaking to the browser.
Related
Appetize.io or Browserstack.com can't access it normally in China, so I want to implement a tool myself. Like Appetize (or Browserstack), I can use my different versions of mobile devices to debug my webpage online, but I don't know where to start. Thank you.
Look at the Network Activity tab of Chrome Dev Tools while you are on the demo page for Appetize.io. You will see a bunch of JPEG images being streamed to the browser as you interact with the device "screen" on the browser. Most likely an emulator/simulator is fired up in the backend and screenshots are taken at regular intervals and streamed to the browser.
That would be a good start. The next thing to look at would be how to capture input (typing and screen taps) on the browser and then "execute" those type/taps on the emulator in the backend.
I have been testing the Apple CoreMediaIO sample camera on Mac OS X 10.9 Mavericks.
Locally the applications i have tried could detect and recognize the sample camera automatically (like Skype, AVRecorder - Apple's AVFoundation capture API sample)
In Mozilla Firefox and Opera browsers the camera has been detected automatically on the Flash Player based sites that i have checked (for example Adobe's Cirrus sample), although in Safari and Chrome the sample camera was missing from the video input devices list.
How could i make these browsers recognize the CoreMediaIO sample camera on such a website?
Safari:
The problem causing this to happen is that on Mavericks the current Safari uses a sandboxed Flash Player which refuses to detect the sample camera.
You can solve this by allowing sites to run Flash Player in unsafe mode: (make sure you have allowed the website to use your cameras on the Flash Player pop-up window)
Go to Safari/Preferences.
Go to the Security page.
Click Manage Website Settings.
On the left pane select Adobe Flash Player.
Select the website you have allowed to use the camera and want to use the camera with.
Click on the combobox.
Select Run in Unsafe Mode.
On the pop-up window choose Trust.
Refresh the website.
From now on, Safari can detect the sample camera on the specific website.
I could not find a better/all-around solution yet.
Chrome:
This problem is mainly based on the Mac OS X AVFoundation API being disabled by default in the current Chrome (the CoreMediaIO sample uses it).
There are various methods to make Chrome detect the sample camera.
So far my best solution is the following:
Open a new tab in chrome.
Go to chrome://flags.
Search for "Enable use of Mac OS X AVFoundation APIs, instead of QTKit, Mac" entry.
Set the above-mentioned entry to Enabled.
Relaunch Chrome.
As far as i could get, the key AVFoundation flag's internal ID is IDS_FLAGS_DISABLE_AVFOUNDATION_NAME.
As long as you try to use AVFoundation based things in Chrome (OS X Mavericks) you will probably need this. (I don't really know why the default value is disabled, but i hope they will change it as Apple tends to deprecate QTKit.)
Other solutions that i prefer less:
Disabling Pepper Flash (PPAPI) and using NPAPI Flash Player instead.
Open a new tab in chrome.
Go to chrome://plugins.
Hit the plus (+) sign in the upper right corner next to Details.
Search for the Adobe Flash Player plugin section.
Locate the Pepper Flash version (PPAPI type).
Click Disable.
Refresh the website.
Google intends to deprecate NPAPI Flash Player soon, which leaves the Pepper Flash (PPAPI) as the only alternative, that was the reason to try and find a better solution than this. I don't recommend to rely on this solution considering the future of NPAPI Flash Player.
There is another temporary solution involving Mozilla Firefox. I don't know why exactly this works and i think this might easily change in the future, but i tried and verified that it works at the moment:
Close Chrome entirely (Chrome/Quit Google Chrome or Command+Q).
Start Firefox.
Go to the website you would like to use the camera with (any Flash Player based site works that calls for camera list).
Open Chrome.
Close Firefox.
Go to the website in Chrome.
If you close Chrome you will have to redo the process from Step #2. It seems like Firefox initializes something that makes the Chrome startup different and causes it to detect the sample camera. I don't recommend to rely on this though.
I'm experiencing issues with the YouTube player failing to load when the power save mode is enabled in Safari 6.1 and 7 on OSX. The issue doesn't happen if the youtube user is using the experimental HTML5 player, but it's still in beta and most people are still using the Flash player. The "disable plugins to save power" option is on by default in most new versions of Safari and this causes the YouTube iFrame API to enter an endless loop as it tries to initialize the player.
Is there any attribute on the window or navigator objects that would possibly indicate that the power save mode is enabled so that I can warn users?
This issue is semi-intentional. The Power Saver mode in Safari deliberately stops flash content. You can read more about it in this article.
If the flash content is 'front and centre' (within a 3000 x 3000 pixel boundary starting at the top left corner of the document) it should still play. So it may help, if the youtube video is off to the side of the page, to try and centre it. Apple says content will not play if it is in the margins (see this page under the Safari Power Saver heading).
Well i do not think there is any readable JS property to know that,
if so Apple would have a flawed design, and the Safari Users would get nagged to disable that mode, in order to have the web site working "properly" ...
What you could do of course is to try to make a server call on your web site via flash, and then try to read the changed session variable via JavaScript, then you would know ...
I work with SpeechRecognitionEngine from the namespace System.Speech in inproc-mode for doing some automation work. The speech recognition is started via RecognizeAsync.
It works fine, however, when the computer gets locked, speech recognition stops. As soon as the computer gets unlocked, the recognition is active again.
While this is probably a meaningful behavior for most applications, for mine, it is an issue. I have searched the web, but not found a solution to disable this behaviour.
How can I parameterize the SpeechRecognition not to stop when the computer is locked?
(Please note: The app is a conventional Windows WPF application, not a Windows Store App)
Some ideas which might be too crazy to work to hopefully trigger some ideas that might work:
Using ControlChannelTrigger to keep pinging your app to wake up and try recognizing speech at intervals? This listener allows your app to process network data in the background.
Try out Google Chrome's hotword (OK, Google) extension and see if it works behind the lock screen. If they can do it, then it's possible.
Do you have to lock the screen, isn't it possible to not have it locked?
Some references:
http://msdn.microsoft.com/en-us/library/windows/apps/dn263238.aspx
http://msdn.microsoft.com/en-us/library/windows/apps/hh977056.aspx
Similar questions:
http://gotspeech.net/forums/thread/11826.aspx
http://social.microsoft.com/Forums/en-US/2ab82528-0d1c-492e-9c15-38730d88b3e9/speechrecognitionengine-pauses-on-lockscreen?forum=Offtopic
Do you have "Enable voice activation" option enabled in Windows?
It looks like the behavior you describe is expected when "Enable voice activation" option is disabled in Control Panel | Speech recognition. Though, it can be unrelated to locked Windows.
See "Setting speech options":
Enable voice activation
Sets Speech Recognition to start in sleep mode and allows Speech Recognition to enter sleep mode when you
say "stop listening."
On the other hand, I don't think that using Speech Recognition with locked device is valid operation (security reasons). Unless you are going to spell your password instead of typing it. :)
See this article on how to launch an application on the secure desktop (a.k.a. lock screen).
I am tearing my hair out. I have a complicated Flash player application which I want to run on my local Mac, 10.7.4. I set this up a year or so ago on earlier Mac OS, with earlier Flash players, and sometimes I had to fiddle with global settings, etc, but it always worked. But now flash has decided (sensibly) to handle the security settings surrounding this use of Flash from the local System Preferences. Here's the appropriate screen which should let me tell Flash that I am opening files in the folder:
You can see my desperate attempts to get flash to let me open files in /Users/peter/BTDE2/ etc -- all failing.
Why? How do I get around this? or do I just give up on flash as a horrible bad job...
It appears from the documentation at http://help.adobe.com/en_US/FlashPlayer/LSM/WS6aa5ec234ff3f285139dc56112e3786b68c-7ff0.html#WS6aa5ec234ff3f285139dc56112e3786b68c-7feb that there should be a fix. According to this, there should be a 'Developer Tools' control on the 'Advanced' panel, which gives access to 'Trusted Location' settings. Well, here is the Advanced panel in Flash System Preferences and it shows no such choices. Looks like someone screwed up somewhere.
In the Flash Player panel are you not able to scroll down to reveal the Developer Tools?