I'm trying to play TTS on the node-red dashboard. Luckily I thought there's the Audio Out node, where you feed a string in, some TTS service converts it to audio and then it's played via the browser you opened the dashboard UI.
Which works fine on my pc while trying, but not on raspberry pi chromium in kiosk mode... There it only prints a notification box which states the text it was supposed to speak...
Anybody ran into this issue?
I have node red installed on docker on RPI3B+ 1, and RPI3 2 with touchscreen as the UI running chromium in kiosk mode.
Chromium plays audio (tested with youtoube) well... so that's not the issue.
Edit
Seems like audio out is trying to do speech synthesis in the browser, but chromium doesn't show providers?!?
Ok easy solution:
Use node-red-contrib-google-tts to get an URL to tts output, feed it through msg.url into a http request nice with binary payload and feed this to the audio out node... And here we go
Related
Environment
Browser: Chrome 87.0.4280.141
OS: Windows 10 Home
Zoom Version: 5.4.6(59296.1207)
I have a website that can access the the user's camera and take a short video on request. I am attempting to achieve this using the MediaDevices web api.
This is all working fine except in two scenarios. When I am in a Zoom or MS Teams meeting on my Windows laptop (with camera on), I have noticed that my webapp fails to capture my video. If I use the web clients for zoom or msteams then it works as expected. Also, if I use mac OS instead of my Windows laptop then this works fine.
When I debug this I get the following error message thrown when trying to access userMedia.
DOMException: Could not start video source
The code that I am using to access UserMedia is the following:
return await navigator.mediaDevices.getUserMedia({video: true});
Is there anything I can do to allow me to user my webcam in the browser as well as on the MS Teams or Zoom clients?
Is there anything I can do to allow me to user my webcam in the browser as well as on the MS Teams or Zoom clients?
No, sorry to say.
The native videoconference client programs attach to your webcam, and so does the browser when you use gUM. The first process to attach wins.
A second webcam may solve your problem by letting your videoconference progam use one and your browser use the other. If you use Chrome, pick the camera you want to use with your browser from the pulldown menu on this page.
chrome://settings/content/camera
I have installed on raspberry Pi3 Google Assistant every thing is fine works perfect.
But when I try to ask to show me a picture or to open youtube is telling me that the monitor is not connected
how can I fix this, to connect the monitor on raspberry pi whit google assistant
thanx
Currently, the Google Assistant SDK doesn't provide support for displaying contents.
This issue is related to playing media in Firefox. While trying to stream audio after moving workstations, I get the following error in the console:
Media resource [...] could not be decoded [...] NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b) Details: OnMediaSinkAudioError
In this case, it's not down to the website setup or contents of the audio stream, as they were working before.
Searching online for OnMediaSinkAudioError or NS_ERROR_DOM_MEDIA_MEDIASINK_ERR only seem to turn up with code commits or repositories for Firefox itself, so this doesn't appear to be a common problem.
It turns out that in this scenario, the error is quite misleading, since it is caused by a misconfiguration of the Windows audio output device.
After swapping my headphones from the rear audio ports to the front and restarting the workstation, everything worked fine. Restarting Firefox may have also been sufficient.
I had the same problem more than once, this time after showing the Console (on Soundcloud) I saw the NS_ERROR_DOM_MEDIA_MEDIASINK_ERR error logged and googled it to find this SO question. What fixed this issue for me was the 1st solution at drivereasy (restarting the Windows Audio service), without even restarting Windows or Firefox.
Hold Down Windows logo and press R key. A Run dialog box will pop up.
Type services.msc in the run box and click OK button.
In right Services Window, find Windows Audio from the “Name” list and right-click on it. Click Restart in the pop-up menu. Then the audio service will restart.
A cmd oneliner would be net stop AudioSrv && net start AudioSrv, run as Administrator.
If you are using VS CODE Live Server extension, Javascript Audio() won't play sound. Try running the site without the extension.
I was receiving the similar error (Media Resource xxx could not be decoded.) in Firefox 46.0.1 and it turns out, the browser does not support .wav files, it worked fine with mp3 audio files.
I had to use embed element with type="application/x-mplayer2" which triggered vlc component to play the file. We were okay with this work around as we only use this website internally and had to stick to older version of Firefox for some reasons.
Though, the audio wav files worked fine in Google Chrome and Mozilla Firefox latest versions.
I have an app installed on Android Wear Emulator that I can directly run from Start->MyApp. However when I want to start it with voice command i.e. Start MyApp, it keeps waiting for something but does not complete. What could be reason for this?
There is a limitation of the current emulator that it does not support voice actions via the keyboard, even though the text appears on the display. You will need to start the application by clicking on the display, then the red G, and then going to the start menu and picking the app from there. You can also quickly start the application using something like this from your development machine:
adb shell am start -n com.example.android.test/.TestActivity
The watch needs to be connected to a phone (device or emulator) with an internet connection for the voice commands to work.
I did everything verbatim on this sample (How do I discover a Chromecast device using Android?).
The chromecast icon turns to white on indicating there are devices available.
When I pressed it, the application unfortunately stops.
What can be going wrong? The only step so far I want to achieve is list all available devices.
Cheers!