31 Aug
2014
31 Aug
'14
9:42 p.m.
On Sat, 30 Aug 2014 07:38:33 -0300
Iain Mott <mott(a)reverberant.com> wrote:
Hi list,
I'm thinking of updating some of my web pages to use multi-platform
flash/html5 audio players, at present they use flash only and won't
play on iPads for example.
Due to some problems I was having with pulse audio in relation to my
HDSP interface I have recently disabled it and all my audio is
running via jack/alsa and the HDSP interface. With flash in firefox,
there are no problems and the audio plays. My .asoundrc is configured
with the following:
pcm.rawjack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
pcm.jack {
type plug
slave { pcm "rawjack" }
hint {
description "JACK Audio Connection Kit"
}
}
pcm.!default {
type plug
slave { pcm "rawjack" }
}
HTML5 players in firefox don't play however via jack. When pulse was
enabled, HTML5 content would play through the computer's built-in
sound card. Now that it's disabled I can't get it to play through
jack.
An example page with a HTML5 player is here:
http://www.html5tutorial.info/html5-audio.php
Any suggestions please? A modification of the .asoundrc?
I'm running Ubuntu 14.04
Thanks,
I'm not surprised. I am very much against anything audio (or
multimedia) in browsers. Nowadays browsers do pretty much everything,
but badly. One constant grieve for me since years has been that there
are virtually no audio settings for the browser (for example search
for 'audio' in firefox about:config). It just takes whatever it can
find, whatever is default on the system, and plays back through the
first two channels. It may work for 95% of the users, but if you're
part of the remaining 5% you can't do anything about it.
For that reason alone doing any specialised multimedia thing for the
browser is just crazy, there is basically no user control.
In your particular case I think it is the flash plugin itself that
handled audio output, and now with html5 it is the browser that does
it,and probably does something stupid. Maybe the way it rubs the ALSA
API the wrong way. It is really hard to say what's going on in a
browser.
Sorry to be of little help.
Philipp