Comments on: HTML5 audio caching

By: Peter Parente

Peter Parente — Thu, 15 Jul 2010 19:21:58 +0000

There wasn’t much to figure out other than the browser caching is what it is until it gets better. Have a look at http://mindtrove.info/jsonic-speech-and-sound-using-html5/ for pointers to code that I managed to get working.

By: Jeremy Volkman

Jeremy Volkman — Sat, 03 Jul 2010 23:21:25 +0000

Did you ever figure this out? I’m running into the same thing and it’s somewhat annoying.

By: Peter Parente

Peter Parente — Mon, 26 Apr 2010 02:19:03 +0000

The clipping was fixed in Chromium recently: http://code.google.com/p/chromium/issues/detail?id=30452

By: Bruno Garcia

Bruno Garcia — Thu, 22 Apr 2010 06:27:32 +0000

Ack, same problem, caches fine in FF but not in Chrome. I’m also getting clipped audio in Chrome.

By: Bruno Garcia

Bruno Garcia — Thu, 22 Apr 2010 06:09:06 +0000

Are you using the Cache-Control and Expires headers?

By: Peter Parente

Peter Parente — Fri, 26 Feb 2010 03:14:24 +0000

I’m interested in what we could accomplish with self-voicing apps. The screen reader has access to the DOM, but has limited knowledge of the meaning behind it. A self-voicing app can provide a considerably better user experience. Plus, relying on a screen reader limits the focus of audio web apps to people that own them. The potential usefulness of such apps goes beyond access for people with visual impairments (e.g., eyes-free, background notifications, multimodal supplements).

By: Michael

Michael — Tue, 23 Feb 2010 20:20:08 +0000

Why js tts? Why not let a screen reader do this? It sounds quite interesting but I think I’ve missed the point