undefined | Better HN

0 pointsInclinedPlane10y ago0 comments

The output quality is terrible, very crackly (on chrome and firefox). I don't see any reason for that in the code so I assume it's just due to the way web audio is in general. I can understand why it isn't used more often.

0 comments

pippy10y ago

it sounds your processor can't keep up with your sound buffer. you can start Google chrome up with --audio-buffer-size=2048 to increase it

All audio technologies have buffer issues, it's a pretty basic problem. it's not unique to web audio.

djrogers10y ago

> it sounds your processor can't keep up with your sound buffer

Is this 1994? We've been playing fancy, high definition, multi-channel audio on our computers for decades now, and it's been ages since I've seen it impact the CPU.

> All audio technologies have buffer issues, it's a pretty basic problem. it's not unique to web audio.

I would say that in 2015, for most people it is unique to web audio. Generally speaking when someone wants to play audio on their computer it just works.

vortico10y ago

This is because "fancy, high definition, multi-channel audio" has >40ms latency, so you cannot compare it with Web Audio, which is meant to be real time like in digital music settings, where often <8ms is required. You clearly do not understand the problem you are claiming to be simple.

1 more reply

InclinedPlaneOP10y ago

Nope, that's not it, makes no difference.

Saying that all audio technologies have issues is a dodge. Technology is hard, software is about dealing with problems not about passing the buck and saying "sorry it sucks, it's hard and I gave up". Computer audio isn't exactly rocket science, tons of products get it right, browser makers just can't be bothered to invest in it.

TeMPOraL10y ago

> Computer audio isn't exactly rocket science

Ironic, in the context of this article.

j / k navigate · click thread line to collapse