I've a Windows Media Player box on me page, but...
The Windows Media Player will overlap every peace of html code how can I get it to the back and that I can still use it? And my second problem is that everybody that visit my page needed a plugin for loading it, but veryone has Windows Media Player installed on his PC? Who can help me and explain something :< Thanks already :D
<object id='mediaplayer' classid='clsid:6bf52a52-394a-11d3-b153-00c04f79faa6' type='application/x-oleobject' width='100%' height='150px'>
<param name='url' value='SONG.mp3'/>
<param name='autostart' value='1'/>
<param name='showcontrols' value='1'/>
<param name='stretchtofit' value='0'/>
<param name='enablecontextmenu' value='0'/>
<param name='ShowStatusBar' value='1'>
<embed src='SONG.mp3' width='100%' height='150px' autostart='1' type='application/x-
mplayer2' pluginspage='http://www.microsoft.com/Windows/MediaPlayer/'
transparentatstart='0' animationatstart='0' showcontrols='1' autosize='0' displaysize='0'
showtracker='0' ShowStatusBar='1'></embed>
The first part of your question is difficult to answer without some sample code to work with.
I would recommend added a presized container div to hold the player in your desired location on the page.
To answer the senond part of your question.
Embedding media player in your webpage means users will be executing the file through their web browser. A plugin for the users specific browser is required to play back the files.
This is standalone from windows media player and will allow users who do not have media player to play the files from their desired browser and operating system.
If you want people to use there installed media player then a link to download the file and execute it on their own computer is required.
Related
I have been trying playing rtsp source files in my web page. I have googled it on net and found that adding VLC activex plugin can do the trick. i have used following code to achieve this and its working so far ..
<object classid="clsid:9BE31822-FDAD-461B-AD51-BE1D1C159921"
codebase="http://downloads.videolan.org/pub/videolan/vlc/latest/win32/axvlc.cab"
width="640" height="480" id="vlc" events="True">
<param name="Src" value="rtmp://192.168.0.102/vod/20141022_162503.mp4" />
<param name="ShowDisplay" value="True" />
<param name="AutoLoop" value="False" />
<param name="AutoPlay" value="False" />
</object>
Now I just want to improve the look and feel of the player. Is there is any way I can add some skin files to it or by some other way.
Vlc Web Plugins has no skinnig capabilities. Absolutely.
So if you need something like this, you have following options:
Dig into Vlc Web Plugins sources and implement what you need (very long way);
Use Vlc Web Plugins with enabled windowless mode and create UI over plugin window with html (way with very poor perfomance, and not working with Vlc ActiveX);
Use FBVLC or WebChimera (in FBVLC compatibility mode) and enabled windowless mode, and create UI same way as in (2). Still will have poor perfomance, but at least it will work on IE;
Use WebChimera and write any UI you like wihout any perfomance penalties - this project was created exactly to solve this task;
If you want to know what WebChimera is - just google it, you will find it on the first page of seach output.
P.S.: WebChimera based on libvlc and supports Win/Mac/Linux platforms
We run an IIS 7 server hosting a site that plays short 10-20 second MP3's. The code we use for our player is:
<audio autoplay="autoplay" controls id="audio_player" preload="auto" >
<source id="mp3_src" src="path_to_mp3/clip.mp3" type="audio/mpeg">
<source id="ogg_src" src="path_to_ogg/clip.ogg" type="audio/ogg">
<!-- BEGIN fallback -->
<object type="application/x-shockwave-flash" data="/flash_mp3_player.swf" width="340" height="50">
<param name="movie" value="/flash_mp3_player.swf" />
<param name="wmode" value="transparent" />
<param name="flashvars" value="filename=path_to_mp3/clip.mp3;autostart=true" />
<embed href="html5-mp3player.swf" width="340" height="50" name="player" align="" type="application/x-shockwave-flash" flashvars="filename=path_to_mp3/clip.mp3;autostart=true"/>
</object>
<!-- END fallback -->
For most users, this is not an issue. We serve and play about 50 clips every few minutes, and have users on almost every major platform that you'd expect (Win XP-8, OS X 10.4+, iOS 5+, Android 2+, etc.).
Recently, as our work load has increased, we're seeing a large number of people who say the clips aren't playing for them. Most of the time we hear of no specific error, but when we do, it's almost always IE9+ reporting "Error: Unknown file type or invalid file path".
At this point, we're stumped. The IIS box is not struggling physically, and this site is the only one on it. Below are a list of variables about the environment that may help.
Windows Server 2008 with IIS 7
MIME types are configured properly
MP3 clips live on a virtual directory, although some are on the server itself. Both locations can fail to play
There are no errors logged by IIS during a fail to play for a client
This happens at all times of the day and night
This happens seemingly randomly with over 200,000 different files
All MP3's are encoded at 128kbps # 44100
The HTML5 and Flash portions are both prone to failure
Usually, requests are 206, although it isn't uncommon to see 200 responses
There's 1 application pool set up for the site and configured to use only 1 worker process
We have never been able to reproduce the error, either on or off of the network the site is served from
Often, users can refresh (multiple times) and actually get the clip loaded and played through
Any help or a point in the right direction would be greatly appreciated.
Thanks!
We've done several things to try and solve this issue. We moved a portion of the media to an aws s3 bucket and refactored some code.
Essentially, we were adding listeners to the audio element by ID and by tag reference and those were both called from two different locations. After we consolidated the code to stay in the external js file, and set all listeners within a function that gets called from the ajax page, things seemed to start working out.
We still see some (very few) issues with IE9+, but have an error listener monitoring this. Each time a user reports an error, the error listeners reports a status code of 4 (MEDIA_ERR_SRC_NOT_SUPPORTED), which is odd.
So, problem is mostly fixed. Now to track down the error code 4 for IE (even though all files will eventually play through it). Perhaps it has something to do with the media player installed on the machine that's in charge of MP3 playback?
I am using a moving flash logo on my website. I am using the code below:
<object width="248px" height="148px" id="flashContent">
<param name="movie" value="http://domain.co.uk/flash/Flash_logo.swf">
<param name="wmode" value="transparent" />
<object type="application/x-shockwave-flash" data="http://domain.co.uk/flash/Flash_logo.swf" width="248px" height="148px">
<param name="movie" value="http://domain.co.uk/flash/Flash_logo.swf">
<param name="wmode" value="transparent" />
<img src="images/global/logo.png"/>
</object>
</object>
Basically the code above will show the flash logo unless flash is not available.In which case the image logo.png will be used as a replacement. This works perfectly fine. However problems arise with Firefox when it detects that flash is not up to date.
Instead of showing the flash file or the logo.png firefox displays a big box stating that the plugin is vulnerable and must be updated. To be honest my flash files serves not other function that to add a little extra style to the site and with the plugin problem my site loads without a logo at all which is less than ideal.
I suppose my question is... Is it possible to edit my code above so that if the plug in is out of date then just the logo.png is loaded instead of Firefox detecting the plugin problem?
First of all, it is not just Firefox and/or outdated Flash.
Users can set any plugin incl. Flash to click-to-play in recent Firefox versions, not just outdated ones.
Chrome also has a preference that allows you to set plugins to "click-to-play".
There is no reliable way to detect click-to-play (due to outdated plugins and/or user preferences), neither in Firefox nor Chrome.
Sometimes it is recommended to construct a plugin in javascript, wait for it to load and then try to interact with it, and if that fails go to a fallback method. However, you still cannot distinguish between the plugin being autoloaded and the user just being a fast clicker.
Your best option is not to use Flash at all, if you don't really need it or it doesn't worth the fuzz. Otherwise try the detection thing.
I am having an issue in WordPress. I've embedded a .swf as an object, but in IE 8 it shows really small. I've attached a screenshot of the IE issue. It's that really small picture on the left. To see a working version, check out the page here on another browser.
I would love to disregard this issue, but unfortunately our company runs on IE so I need to fix this.
This is all created in WordPress. The .swf is hosted externally. Here is the code:
<object width="680px" height="300px">
<param name="movie" value="http://www.pplweb.com/ppl-generation/~/media/PPLWeb/Generation/Media/PPL%20Susquehanna/nuclear.swf">
<embed src="http://www.pplweb.com/ppl-generation/~/media/PPLWeb/Generation/Media/PPL%20Susquehanna/nuclear.swf" width="100" height="100">
</embed>
</object>
Embed it using SWFObject, it's the most reliable way to insert SWF files. WordPress already comes bundled with it, so you just need wp_enqueue_script('swfobject');, and then use the script embedding accordingly.
Or you can use a plugin: wordpress.org/plugins/search.php?q=swfobject.
I have created an application using Adobe Flex. I took all the files from the 'bin-release' folder and put it on the server. Then when someone connected to the server through http it is forwarded to the "index.htm". The "index.htm" page is the HTML page created automagically by Adobe Flex during compile time, I just renamed it to that name (from visco.html if it matters). The SWF file remained the same.
The problem is that most of the time when I go to the server, I get forwarded to the "index.htm" file and it loads the SWF perfectly. The other 30% of the time, it doesnt load! The background of the page turns blue (same as my SWF) and if I right-click it, it shows an Adobe Flash dropdown, so it looks like its sort of loading, but the application doesnt fully start even though it has been 100% reliable during debugging and when loading the SWF file manually.
What do I need to do to get the SWF file to load and start reliably?
here is where I embed the SWF file:
<noscript>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
id="visco" width="100%" height="100%"
codebase="http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab">
<param name="movie" value="visco.swf" />
<param name="quality" value="high" />
<param name="bgcolor" value="#869ca7" />
<param name="allowScriptAccess" value="sameDomain" />
<embed src="visco.swf" quality="high" bgcolor="#869ca7"
width="100%" height="100%" name="visco" align="middle"
play="true"
loop="false"
quality="high"
allowScriptAccess="sameDomain"
type="application/x-shockwave-flash"
pluginspage="http://www.adobe.com/go/getflashplayer">
</embed>
</object>
It turns out the problem was with the embedded board used to serve the SWF file, not the file itself.
It sounds like it is throwing an exception somewhere and failing silently (roll on FP10.1!!).
Upload a debug version to the server and try and re-create. It will give you more information than a blank screen.
Remember that if you upload a debug version, you can debug remotely from Flex Builder (which is always a plus).
If it fails in production but not in testing, that usually suggests bad data, hardcoded URLs (localhost being the biggest culprit), or timing issues.
Your first job is to find what the exact conditions it's failing under, and for that you'll need a debug build.
try installing the debug player in your browser and it should popup the stack trace dialog that should give you a clue what's wrong if the app throws an exception like gregor suggested. other debugging methods on a release build is to use firebug network monitor tool which can show if the app is making a call to a url that returns 404 and maybe the app is not handling the error. but that's limited to this. some other ideas i can think of is that in your oncomplete/initialize/preinitialize event you are trying to access a null object or property so the app stops there and prevents it from loading.
The problem was actually with the hardware used to serve up the SWF file. The code used to access the SD card (where the SWF was stored) wasn't working quite right.