TWS flash player (free and light version) ========================================= The following information is necessary to read to be able to use light version tws flash player. One orientates himself by headings and then begins only to read informations. (1) General availability and usability light version of tws flash player. (2) Light version tws flash player has following properties. (3) Light version of tws flash player has following specific features. (4) Creation, setting and control of light version of tws flash player. (5) Media and their playlists of light version of tws flash player. (6) Static administration of light version of tws flash player. (7) Dynamic administration of light version of tws flash player. (8) Local administration of light version of tws flash player (beyond the internet) (9) XLM-playlist-file example (10) Administration mimie types of media on apache-webserver ---------------------------------------------------------------------------------------------------------------------------------------------------- (1) General availability and usability light version of tws flash player. Light version of tws flash player was programmed and produced by www.twseite.de. The tws flash player used on www.twseite.de is not a light version, not free and not available freely. Only light version of tws flash player can be used by everybody and is available freely. This generosity excludes the duty to the support and also the duty to a guarantee. Email inquiries are possible: primarily tws@twseiten.com or secondarily tws@twseite.de Tip: For commercial purposes various Paywaren are suitable, perhaps, better. Light version of tws flash player may not be used against remuneration for the purpose of the profit achievement. Light version of tws flash player may not be used in responsibility of the player manufacturer (including media an playlists). Who is to the opinion to want to hand on light version tws flash player to others, this can act together with the tip (1) General availability and usability light version of tws flash player. The expenditures connencted with the wide reaching and costs are neither caused by the player manufacturer nor are refunded. Who uses the player and wants to allow to sponsor himself at the same time, this can act with the tip that the player manufacturer is not concerned by the Sponser. ---------------------------------------------------------------------------------------------------------------------------------------------------- (2) Light version tws flash player has following properties: SWF-Flashplugin from version 10 recommended. The player must be activated in a HTML document. There is no Standalone version. If is the web page on hard disk, does not become by the player online gone (unless, this requires by entry in playlist). The player can be seated without temporal limitation locally by hard disk or on a web page (e.g., HTTP server). Recommendation: Web page, player, playlists and media on the same domain should lie. Accesses by and on an Adobe-Streaming-Sever (liable for costs) are not implemented. Hence, media is completely loaded as a file and then only is reproduced (normal download of the data). The player is advertising-free (except the permanent player TWS logo). It can be switched with the player even no advertisement. The player TWS logo is held so small, so that media can cover this logo with the reproduction. The player contains no ADWare, does not call up home, does not sniff (neither out of vision nor online) and also puts no cookies as well as no bookmarks. Supported media are: FLV Video H.263 Audio 44,1 kHz as long as other sample rates are not permitted in Flash (no DVD audio 48 kHz). createable by FFMpeg: No codec must be installed, because is brought. mp4 Video MPEG-4 AVC / H.264 Width and height should be ever quite divisible by 2. Audio AAC mit 44,1 kHz as long as other sample rates are not permitted in Flash (no DVD audio 48 kHz). createable with XMediaRecode only as a MPEG-4 AVC / H.264: No codec must be installed, because is brought. FFMpeg generates mp4, perhaps, in such a way that it cannot reproduce of the flash player (video is absent). Then one should use XMediaRecode. mp3 Flash supports, perhaps, no free codecs like WebM, Ogg or Theora, so that the extension of the media support is not necessary then. Graphically User Interface (GUI): Normal picture, full image mode not activateable. right-click object menu. Playlist as a simply structured XML file. Controller bar (volume, next, prev, time bar) automatically blanked (switch). Play and pause button. Minimum control by mouse (use right-click object menu). Media dimension is customised in player dimension. However, zoom is not possible. ---------------------------------------------------------------------------------------------------------------------------------------------------- (3) Light version of tws flash player has following specific features: No watermark during reproduction. With not loaded medium the TWS logo of the player is indicated. Full image mode not activateable. No autostart 1st track. Autostart the next track by object menu administerable. No Javascript remote control of the player. No Stream ability. Only the file download is supported. Adobe server not inevitably. Minimum control by mouse (use right-click object menu, time bar, buttons): If the mouse cursor reaches the time bar, the hand cursor appears. In the following the operations of the mouse on the time bar if at least 1x a reproduction has been launched: MouseDown: pauses the song in actual position (Pause At Pos). But if (the next) song is not loaded yet, he is loaded and played from the beginning. Drawing of the mouse on the time bar changes the position of the reproduction. MouseUp (the pressed mouse button let go): Song in the actual mouse position is further played (Play At Mouse Pos). If the mouse cursor on the time bar was moved to MouseDown and before MouseUp, the start position of the reproduction has also moved itself with it. ---------------------------------------------------------------------------------------------------------------------------------------------------- (4) Creation, setting and control of light version of tws flash player. (4a) Creation: (4aa) statically by HTML coding. (4ab) dynamically by Javascript (in Microsoft Internet Explorer may be with problems). (4b) Control: (4ba) statically by playlist file in the XML format. (4bb) dynamically by mouse, however, not by Javascript. (4bc) dynamically by playlist file (media as a file download and not as a stream). (4c) Setting (4ca) statically by HTML coding. (4cb) dynamically by Javascript (in Microsoft Internet Explorer may be with problems). ---------------------------------------------------------------------------------------------------------------------------------------------------- (5) Media and their playlists of light version of tws flash player. Supported media are: FLV Video H.263 Audio 44,1 kHz as long as other sample rates are not permitted in Flash (no DVD audio 48 kHz). createable by FFMpeg: No codec must be installed, because is brought. mp4 Video MPEG-4 AVC / H.264 Width and height should be ever quite divisible by 2. Audio AAC mit 44,1 kHz as long as other sample rates are not permitted in Flash (no DVD audio 48 kHz). createable with XMediaRecode only as a MPEG-4 AVC / H.264: No codec must be installed, because is brought. FFMpeg generates mp4, perhaps, in such a way that it cannot reproduce of the flash player (video is absent). Then one should use XMediaRecode. mp3 Flash supports, perhaps, no free codecs like WebM, Ogg or Theora, so that the extension of the media support is not necessary then. External playlist file in the XML format Light version of tws flash player must be supplied about an external XML file with media entries. Because the player cannot communicate with Javascript, the supply of the XML data is senseless by Javascript. Per media file are required in the XML file: Title or creator as a free text (creator) Subject as a free text (title) File path and filename of the media file (location) Duration in milliseconds for the display in the playlist-bar of player width of media, see siehe (2) Light version tws flash player has following properties. height of media, see (2) Light version tws flash player has following properties. The structure of the XML file playlist trackList track creator title location duration width height track ... track creator title location duration width height track trackList playlist Other descriptions Read absolutely the information in the XML file twsflpd.xml. ---------------------------------------------------------------------------------------------------------------------------------------------------- (6) Static administration of light version of tws flash player. Flash is widespread in the web and is often used as a design instrument for HTML pages. There are web pages, they contain only Flash elements. These web pages are very often static and have only by media dynamic contents. Web pages, the Javascript are of use, are able object-oriented, e.g., as follows to be administered: The production of the flash player occurs at the run time with the help of scripts 1. script contains exactly 1 program code to the HTML production for all (future) player. 2. script contains the data, those of 1. script are evaluated. Should the web page be changed, only the data must be customised. Shortcut 1. and 2. Script: The identical data which appear as multiple can be generated standardised at the run time. For HTML his document object model (CATHEDRAL) is selectable directly by Script, e.g., Javascript. The HTML-DOM describes a web page and their elements. The HTML-DOMis specific for browser implement (divergences of the standard are the rule). Further below the static HTML structure light version of tws flash player is explained which must be generated for every player and be customised, one wants to administer statically. It makes no difference what contains the web page if one wants to administer Flashplayer dynamically. Light version of tws flash player following static HTML code structure has: The Microsoft Internet Explorer can activate Flash not only with the help of ClassID, but also with the help of TYPE. Because also Opera knows TYPE, it is not used ClassID any more. Attention: There is a dreadful mess (browser manufacturers deal apparently nothing else): Internet Explorer expects Flashvars in PARAM NAME="movie". ignores Flashvars in PARAM NAME="flashvars". Opera ignores Flashvars in PARAM NAME="movie". expects Flashvars in PARAM NAME="flashvars". The DATA attribute is required neither by the Internet Explorer nor by Opera. To handle to however other ones, how the abovementioned unexpected nonsense, the DATA attribute is coded. OBJECT ID="aaaa" TYPE="application/x-shockwave-flash" WIDTH="bbbb" HEIGHT="cccc" DATA="dddd" PARAM NAME="movie" VALUE="dddd?PMF=x1&PGL=x2&PCB=x3&PLB=x4&PLT=x5&OA=x6&OLF=x7&OLO=x8&OWF=x9&OWO=x10&OWR=x11" PARAM NAME="bgcolor" VALUE="eeee" PARAM NAME="wmode" VALUE="ffff" PARAM NAME="allowScriptAccess" VALUE="gggg" PARAM NAME="allowNetworking" VALUE="hhhh" PARAM NAME="quality" VALUE="iiii" PARAM NAME="play" VALUE="jjjj" PARAM NAME="loop" VALUE="kkkk" PARAM NAME="scale" VALUE="llll" PARAM NAME="menu" VALUE="mmmm" PARAM NAME="devicefont" VALUE="nnnn" PARAM NAME="salign" VALUE="oooo" PARAM NAME="align" VALUE="pppp" PARAM NAME="base" VALUE="qqqq" PARAM NAME="allowFullScreen" VALUE="rrrr" PARAM NAME="flashvars" VALUE="PMF=x1&PGL=x2&PCB=x3&PLB=x4&PLT=x5&OA=x6&OLF=x7&OLO=x8&OWF=x9&OWO=x10&OWR=x11" OBJECT Explanations to the static HTML code structure light version of tws flash player: The Microsoft Internet Explorer deviates in the integration of the Flash of program part (SWF file which contains a Flash player) from other browser manufacturers unexpectedly. The Microsoft Internet Explorer 8 (IE 8) deviates manufacturer-partly in principle, at present considerably in the range of HTML-5 media (is not supported by the IE) and in the range of the dynamic administration of Flash. The static administration assumes knowledge about the HTML structure to be customised. "aaaa" The character string which serves as a password of the player and may be used not several times in the HTML document. "bbbb" Digit sequence as a maximum width in pixel of all media to be indicated in the player, also MP3 must get a width. The media which is broader is automatically reduced on this width. "cccc" Digit sequence as a maximum height in pixel of all media to be indicated in the player, also MP3 must get a height. The media which is higher is automatically reduced on this height. Height raise, perhaps, so that the control bar of the player are indicated under the medium. "dddd" File path and filename of the demo player. Filename is always "twsflpd.swf". "eeee" Hexa digits #rrggbb of the background colour of the player window in the RGB format. # is always to be given rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. "ffff" Transparency of the display surface (except surface of the controls, time bar) "transparent" so background of the web page shines through (the player indicates the TWS logo, however, always). "opaque" or "window" so background of the web page does not shine through (the player indicates the TWS logo, however, always). Recommendation: "transparent" "gggg" Access of the web page to Flash (SWF) permit by script (the player has implemented no access by script) "sameDomain" SWF and web page must lie on identical domain. "always" SWF and web page can lie on different domains. Recommendation: "sameDomain" "hhhh" Network properties of Flash (SWF) permit (the player has implemented no access by script) "all" Flash System Network- and javascript interface are both full usable, file of Flash loadable. "internal" Flash System Network interface partial and javascript interface full usable. ""none" Flash System Network- and javascript interface are both not usable. Recommendation: "all" "iiii" Quality of the display of media (not quality of the media) "low" no anti-aliasing "autolow" automatically set to low "autohigh" auto anti-aliasing "medium" "high" "best" Recommendation: "best" "jjjj" SWF with loading immediately activate "false" not immediately activate "true" immediately activate Recommendation: "false" Because the player reacts only to mouse clicks, the activation with loading changes nothing. "kkkk" SWF with every achievement of the end once more activate "false" with every achievement of the end not once more activate "true" with every achievement of the end once more activate Recommendation: "false" Because the demo player never ends, the activation of the loop changes nothing. "llll" Precision of the display of media (not quality of the media) "showall" exact display "noborder" and "exactfit" not exact display (distorted indicate) Recommendation: "showall" "mmmm" right-click object menu permit "false" does not permit "true" does permit Recommendation: "true" The player generates own menu. "nnnn" device font "false" "oooo" alignment of the player in the HTML document One should use CSS or STYLES to the OBJERCT tag, or remove the OBJECT in a container (e.g., DIV) and on this CSS or STYLES apply. "false" "pppp" alignment of the player in the HTML document One should use CSS or STYLES to the OBJERCT tag, or remove the OBJECT in a container (e.g., DIV) and on this CSS or STYLES apply. "false" "qqqq" Base path for file relations by Flash The player uses no base. "" (empty string) "rrrr" Display permit in the picture extent according to display "false" does not permit "true" does permit Recommendation: "true" Because the player does not indicate full image, the activation of the full image changes nothing. x1 File path and filename of the playlist XML file. Suffix must be "xml". x2 Player GUI language, true for German, false for English. x3 Hexa digits rrggbb of the background colour of the player control bar in the RGB format. rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. see "eeee" background colour of the player window x4 Hexa digits 0xrrggbb of the background colour of the player playlist bar in the RGB format. 0x is always to be given rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. see "eeee" background colour of the player window x5 Hexa digits 0xrrggbb of the text colour of the player playlist in the RGB format. 0x is always to be given rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. see "eeee" background colour of the player window x6 Permission of the display of the MP3 oscillator (wave form display) "true" does permit "false" does not permit and ignore other properties of oscillator automatically set to false, if OLO and OWO both set to "0" (set to full transparent, nothing to display). Recommendation: "true" x7 Hexa digits 0xrrggbb MP3 oscillator color of origin line, (0 level recorder line) 0x is always to be given rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. see "eeee" background colour of the player window x8 MP3 oscillator opaque of origin line, 0 - 100 0 full transparent (background color ignored) 100 full opaque (full non transparent) Recommendation: 20 x9 Hexa digits 0xrrggbb MP3 oscillator color of wave 0x is always to be given rr part red 00 bis FF corresponds 0 bis 255 (RGB-format) gg part green 00 bis FF corresponds 0 bis 255 (RGB-format) bb part blue 00 bis FF corresponds 0 bis 255 (RGB-format) There is freeware, they can indicate colours and convert to Hexa. see "eeee" background colour of the player window x10 MP3 oscillator opaque of wave, 0 - 100 0 full transparent (background color ignored) 100 full opaque (full non transparent) Recommendation: 20 x11 MP3 oscillator wave grid true detailed grid and high performance of CPU false non detailed grid and low performance of CPU Recommendation: false ---------------------------------------------------------------------------------------------------------------------------------------------------- (7) Dynamic administration of light version of tws flash player. The Microsoft Internet Explorer 8 (IE 8) deviates manufacturer-partly in principle, at present considerably in the range of HTML-5 media (is not supported by the IE) and in the range of the dynamic administration of Flash. Should the dynamic administration with the Internet Explorer not function, one must use the static administration. It makes no difference what contains the web page if one wants to administer a Flash player dynamically. There are only following least standards which must be fulfilled. 1. Loading of the necessary Script files Javascript must be activated in the browser. The loading of the Javascript files occurs in the HEAD, so that these files are parsed if the BODY is processed. The necessary structure add in the head of the web page: HEAD SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript" SRC="twsflpdjs/twsflpdc.js" SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript" SRC="twsflpdjs/twsflpdd.js" HEAD The paths can be customised. twsflpdc.js contains the program code which generates all player dynamically. is not to be customised. twsflpdd.js contains values for all player, but only the values of (6) Static administration of light version of tws flash player. can take up data for arbitrarily many player. is read out by the program code in twsflpdc.js. 2. Provide the container in which player are dynamically generated At that place in the BODY of the web page in which a player should appear a container must be integrated, e.g., the structure DIV ID="AAAAAA" DIV The DIV contents are completely overwritten with the player. AAAAA is the id of THIS container, and may not be used once more. Per player to be installed a container with precisely HIS ID must be inserted in the HTML code of the web page. How many containers, this makes no difference. Per player must be deposited in twsflpdd.js his data. and his Playlisten XML file must be generated of course. twsflpdc.js create automatically static HTML code like in (6) Static administration of light version of tws flash player. 3. Activation of the programme that the player dynamically generates Directly at the end of the BODY a Javascript must be integrated that the production activates, provides so for the fact that the program code uses in twsflpdc.js the data from twsflpdd.js and generates then the player directly in the containers. SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript">twsflpdcfd() twsflpdcfd () is the start routine of the programme in twsflpdc.js. 4. Additional change the player Player can be changed afterwards, be added, be dequeued. change: The file twsflpdd.js is to be customised. That's all. add: create playlist XML-file. In the HTML code of the web page paste the (empty) container (see 2. Provide the container in which player are dynamically generated). The file twsflpdd.js is to be customised: Add there the data. That's all. remove: In the HTML code of the web page remove the (empty) container (see 2. Provide the container in which player are dynamically generated). The file twsflpdd.js is to be customised: Remove there the data. Es ist die Datei twsflpdd.js anzupassen: Dort die Daten entfernen (index sequence may have no gaps). Remove entries in playlist XML-file. Remove Media files. That's all. ---------------------------------------------------------------------------------------------------------------------------------------------------- (8) Local administration of light version of tws flash player (beyond the internet) Adobe thinks highly of security and tries to follow to security. Not only Adobe applications are larded at the same time with accesses to the Internet, so that the application of a router firewall is worthwhile (e.g., from Fritz's box AVM). To go online without being asked, this hears to the good tone many not only known software manufacturer of freeware to payware. And data are collected without end and thus user are nosed out (systematically). Adobe has implemented with Flash a security which offers an unnecessary access to the internet. This concerns the local use of a SWF of hard disk (not by the HTTP server). SWF can be reproduced by hard disk only if that is permitted by Flash. It is current to go online, and to make the SWF "playable". But the crack dot, above all off-line, lies somewhere else: On the hard disk. The installed Flash must be able to check whether the SWF lie in a festival disk partition which is valid for Flash as safe. And these are ONLY paths which lie in a text file, the Flash automatically reads in. Every other path is not used and the SWF lying there are not played. Example: SWF lies in the folder F:\test\33\flash\test\ The user knows that he wants to use in future also other folders on F:\for SWF. The disk drive F:\is to be announced therefore as a path safe for Flash. The text file, the Flash reads out, and it contains the paths, must be removed under German Windows in the folder C:\Dokumente und Einstellungen\xxxx\Anwendungsdaten\macromedia\flash player\#security\flashplayertrust\ mit XXXX name of user and his account (not passsword of account of user). Construction of the text file: ASCII (for example not in format of MS Office Word) Suffix must be "cfg". Prefix is any. f.e. FlashPfade.cfg The contents of the text file are: # this is a comment line # # Suffix must be "cfg". # Prefix is any. # # The paths which the Adobe Flash classifies as authentically # per path 1 line # # f.e. the whole disk drive F, so that at every place the SWF become playable: F:\ In the folder of the file other cfg files can still lie. It also reads in Flash. Perhaps, still cfg files from as uninstalled to valid applications lie there. ---------------------------------------------------------------------------------------------------------------------------------------------------- (9) XLM-playlist-file example Creator 1 flv ../media/1.flv 21028 500 281 Creator 2 mp3 media/2.mp3 29000 200 200 Creator 3 mp4 ../media/3.mp4 29000 128 96 ---------------------------------------------------------------------------------------------------------------------------------------------------- (10) Administration mimie types of media on apache-webserver The allocation Multipurpose Internet Mail Extensions type to the file type occurs in general by AddType MIME-TYPE FILE-EXTENSION [FILE-EXTENSION] ... f.e. AddType video/ogg .ogv AddType audio/ogg .oga .ogg AddType video/webm .webm AddType audio/webm .webm AddType audio/mp4 .mp4 .m4a AddType video/mp4 .mp4 .m4v AddType application/x-shockwave-flash .swf AddType video/x-FLV .flv AddType audio/mpeg .mp3 AddType audio/wav .wav AddType audio/midi .mid .midi AddType application/pdf .pdf AddType application/zip .zip .7z The types are informed by file .htaccess to the server. The file .htaccess is generated by hand and copied on the web server in the folder with the media. (By FTP the ASCII mode must be activated what modern FTP programmes recognise independently.) There stored .htaccess also works on all unterfolders of the folder. In .htaccess stand only the allocations of media which are in the folder: Per line 1 allocation. f.e. AddType video/ogg .ogv AddType audio/ogg .oga .ogg AddType video/webm .webm AddType audio/webm .webm AddType audio/mp4 .mp4 .m4a AddType video/mp4 .mp4 .m4v AddType application/x-shockwave-flash .swf AddType video/x-FLV .flv AddType audio/mpeg .mp3 AddType audio/wav .wav AddType audio/midi .mid .midi AddType application/pdf .pdf AddType application/zip .zip .7z Tips: Not every browser needs this.htaccess file and their entries. Opera gets by without.htaccess. Firefox must find a.htaccess file, because only the media data are indicated after the loading. Firefox could deliver no indicateable media data, as soon as Streamen, e.g., by AddType application/octet-stream.zip.pdf.mp3.mp4.ogv.oga.ogg.webm.flv in .htaccess was deposited, in addition. The media support in the HTML code needs the HTML attributes to TYPE and CODECS. However, the HTML tag which should indicate the media must not own these attributes. The HTML tag SOURCE owns to TYPE and CODECS, however, can indicate no media. HTML-5 media fair video are coded as follows in HTML: if