Note that there are some explanatory texts on larger screens.

plurals
  1. POWebRTC audio playback in Android Chrome
    primarykey
    data
    text
    <p>I'm working on <a href="http://nathanathan.com/ShowAndTell/" rel="nofollow">this app</a> and the audio recording feature comes close to working in Chrome for Android, but it fails for a reason I haven't yet identified. (It works property in Desktop Chrome and the latest Firefox). The actual recording seems like it might be working, as microphone access is requested and I think audio blobs are created. However, I can't play the audio back.</p> <p>I'm using WebRTC to record and the demo <a href="https://www.webrtc-experiment.com/RecordRTC/" rel="nofollow">here</a> also fails to play back audio in Android Chrome. This seems like it's a bug in the browser, but I'm wondering if there is a work around. It seems like there could be since the WebRTC demo <a href="https://apprtc.appspot.com/" rel="nofollow">here</a> successfully streams audio to other clients from Android Chrome. And I'm wondering what the root of the problem is. Is the recording not properly created, or is the audio element just incapable of playing it back? I haven't been able to play back audio created from the Windows Chrome version of my app in Android Chrome, so I suspect there could be a playback issue.</p> <p>EDIT: I've determined that there is a playback issues since I was able to play audio recorded in Android Chrome Beta (that I could not play on the device) in desktop Chrome. Could using an AudioContext instead of an Audio element for playback avoid the issue or do they both have the same limitations?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload