Hi
I'm trying to embed Windows Media Player in Wordpress so that I can
stream mp3's with Firefox (v1.0.7) and IE browsers.
I've found loads of implementations and they all seem to work except
for one problem...
Whenever I use Firefox, the embeded media player autostarts
automaticly... I really don't want this to happen because I want to
embed more than one media player object (with different source mp3's)
in the same page.
I've tried adjusting the 'autostart' parameter to 'true', '0' and
'-1', but although the parameter is effective in IE (i.e. it doesn't
autostart) Firefox seems to ignore the paremeter and autostart anyway.
The code i'm using at the moment is as follows:
<OBJECT id='mediaPlayer' width="320" height="285"
classid='CLSID:22d6f312-b0f6-11d0-94ab-0080c74c7e95'
codebase='http://activex.microsoft.com/activex/controls/mplayer/en/nsmp2inf.cab#Version=5,1,52,701'
standby='Loading Microsoft Windows Media Player components...'
type='application/x-oleobject'>
<param name='fileName' value="http://www.wintertactics.com/test/buuren.mp3">
<param name='animationatStart' value='false'>
<param name='transparentatStart' value='false'>
<param name='autoStart' value="false">
<param name='showControls' value="true">
<param name='loop' value="false">
<EMBED type='application/x-mplayer2'
pluginspage='http://microsoft.com/windows/mediaplayer/en/download/'
id='mediaPlayer' name='mediaPlayer' displaysize='4' autosize='-1'
bgcolor='black' showcontrols="true" showtracker='-1'
showdisplay='0' showstatusbar='-1' videoborder3d='-1' width="320" height="285"
src="http://www.mysite.com/mydir/myfile.mp3" autostart="-1"
designtimesp='5311' loop="false"> </EMBED>
</OBJECT>
I've spent ages trying to solve this problem but the same bug (?)
presents itself time and time again.
One more thing... I want to avoid using Javascript.
Thanks!
Alex
http://www.wintertactics.com |
Request for Question Clarification by
sublime1-ga
on
13 Oct 2005 13:18 PDT
dogtanian...
Since you're providing several MP3s, and want the visitors
to have the option of choosing between them, I'm not clear
on why you'd insist on embedding multiple players, especially
since not every visitor will have WMP installed.
Why not just provide links which can be opened (or not) with
the default player of the visitor?
sublime1-ga
|
Clarification of Question by
dogtanian-ga
on
13 Oct 2005 16:44 PDT
Hi Sublime1
Yeah - I completely see what you mean... coming down on the WMP option
was a pretty painful decision to make, particularly because I myself
occasionaly use Knoppix/Mandrake as an OS.
I know my rationale probably kinda sucks, but since the audio will be
part of a blog entry I guess I just wanted it to look 'Pretty' and
present it so that users could simply click on a "Play" button, rather
than decide whether to save the audio to their HD etc.
Also some of my audio files will be quite big; I want the user to be
able to buffer+stream it. I suspect that some users will be running
audio playback software that'll want to download the entire file
before playing it. As far as i'm aware, anybody running post win2k/me
has WMP bundled witht eh OS anyway.
Finally, I toyed with the idea of using a plain old EMBED that would
allow the browser to decide which helper application to use depending
on the MIME type, but since Mozilla tends to like Quicktime for
rich-media playback, I wanted to avoid people having to download
anything.
I really hate the fact that I'm shunning non-Windows users, but I
guess I'll try and justify it by convincing myself that people using a
Linux platform will have far better things to do than listen to my
bits of streaming audio.
|
Clarification of Question by
dogtanian-ga
on
13 Oct 2005 16:54 PDT
By the way... I've just managed to find the answer to my question:
I've tried using autostart="0" again, and it seems to work now.
My conclusion is that Firefox has a minor bug (although it's not so
much a bug than an omission in the object handler thingie for the
OBJECT/EMBED TAG).
Seeing that I've now solved the problem myself, I'd now like to
allocate the $10 to anyone who submits this issue as a bug-report to
Mozilla in accordance with Mozilla's bug-reporting process.
|
Request for Question Clarification by
sublime1-ga
on
13 Oct 2005 21:11 PDT
dogtanian...
I started the process of writing up a bug report, but, aside
from the extensive searching needed to preclude the possibility
of submitting a duplicate bug report, they would need specifics
which are best provided by showing them the page on which the
script is failing.
I'll pass...
sublime1-ga
|
