header_graphic
header_gradient
 
  • Posted by ESA
  • Comments Off

Here we provide solutions for problems that you may encounter when using the HD Media Player. If you experience any other problems, please contact us, and we’ll do our best to evaluate the problem and provide a solution.

Player SWF doesn’t load on page: You must have Flash Player 10 installed (you will probably have to close and reopen your browser to complete the installation), and you must provide a valid path to the SWF on your web server. If you are loading a SWF file that is NOT hosted on the same server as the page where it is being displayed, you must use a crossdomain.xml file in the root of the website that contains the SWF file (this is part of the Flash Player security model).

XML playlist doesn’t load in player: You must provide a valid path to your XML (using FlashVars, ActionScript, JavaScript, or the Component Inspector), and your XML can not contain errors (check all your media paths and use one of our default XML files to check your syntax). If you are loading a XML file that is NOT hosted on the same server as the page where it is being displayed, you must use a crossdomain.xml file in the root of the website that contains the XML file (this is part of the Flash Player security model).

Bandwidth detection doesn’t work: You must provide a valid path to your bandwidth test location (using a parameter in the XML or Component Inspector). Please refer to our “Automated Bandwidth Detection” tutorial for more information.

Fullscreen doesn’t work or player doesn’t resize correctly when exiting fullscreen: You must have Flash Player 10 installed (you will probably have to close and reopen your browser to complete the installation); you must be testing your SWF in a web page using a web browser (will not work on your desktop); and you must set the “allowfullscreen = true” in your embed code. If you have altered the size and/or location of any objects on the stage, you also have to modify a few lines of action script to account for the new layout. Please refer to our “Fullscreen Setup and Resizing” tutorial for more information.

JavaScript interaction doesn’t work: You must provide valid paths to all of your media files; you must define the “id & name” of your SWF in the embed code; you must test your SWF on a web server using a browser (i.e. will not work locally, swf must be embedded in a webpage, and the SWF can not be inside a <form> tag); and you must have JavaScript enabled in your browser. Please refer to our “JavaScript Interaction” tutorial for more information.

H264 (mpeg-4) files cannot be seeked before they are completely downloaded: The MOOV atom in your H264 files is located at the end of the file. To fix this problem you should re-encode the file using Adobe Media Encoder or QuickTime Pro. Alternatively, you could try using the QTIndexSwapper, but it may not work in all cases.

MP3 playback is too fast or too slow: Your MP3 contains variable bit rate encoding or unsupported sample frequencies (e.g. 48Khz). To fix this problem you should re-encode the track using constant bit rate encoding and a supported frequency (11, 22, 33, or 44 kHz), which can be done with iTunes.

Video duration/dimensions are wrong or progress bar/scrubbber doesn’t work: Your media file does not include metadata. To fix this problem you can manually define the duration using the “dur” attribute in <media> node of the XML, or you can re-encode the file using Adobe Media Encoder (FLV & H264 files), QuickTime Pro (H264 files), or  iTunes (MP3 files). Alternatively, you could try using the Buraks FLV Metadata Injector, but it may not work in all cases.

Progressive (http) FLV file doesn’t work: You must provide a valid path to your progressive media file. If you are using a relative path it must be relative to the location of the page where it is being used (not the location of the SWF). If you are using a Windows 2003 server (Microsoft IIS Server 6.0), make sure the FLV mime type has been added to the server (link to simple instructions).

Streaming (rtmp) file doesn’t work: You must use a supported server type (FMS 3.x, Wowza, or Red5); you must provide a valid path to your streaming media file (correct syntax based on file type); and you must use the correct ”instance” setting to help the player parse your rtmp path. Please refer to our “Working with a Flash Media Server” tutorial for more information.

footer_graphic

Support - Documentation - Skin Wizard - Sample Skins - Tutorials
Copyright © 2003-2011 Earth Science Agency, LLC - All Rights Reserved