Video Tutorial Instala y Visualiza videos de Youtube en Reproductores Dune HD

[Cirus]

Video Tutorial Instala y Visualiza videos de Youtube en Reproductores Dune HD con plugins como este.

[rdsparla]

Hola, yo quiero reproducir videos flv grabados en el disco duro y no puedo. No reconoce este formato. En cambio aparentemente si por el navegador pero no tengo internet. Creeis que hay algun sitio donde puedo pedir que se tenga en cuenta en la próxima actualización de firmaware. Además en la página de actualizaciones hay una opción de creación de aplicaciones con flash lite. Pero no pone como se instalan. Alguien sabría orientarme sobre estos temas.

[terrorman]

en la web de dune, rebuscando un poco, hay un apartado para el tema del flashplayer, es posible cargarselo por el usb.

[Cirus]

Dune FlashLite information
++++++++++++++++++++++++++

General information
===================

Dune FlashLite is based on Adobe Flash Lite for the digital home. It is a
Flash player implementation optimized for Dune player software and hardware
platform. Dune FlashLite features Flash player 8 rendering capabilities and
Flash player 10 media support. It can be viewed also as Adobe Flash Lite
3.1 implementation supporting ActionScript 2.0 for developing Flash
applications. However there are some differences between Flash Lite 3.1 and
Flash Lite for the digital home. For details please refer to document
"Developing Applications for Adobe Flash Lite for the Digital Home".

Media URL for SWF file
======================

FlashLite SWF files can be launched directly from Dune GUI or via
dune_folder functionality. In both cases SWF files must have "swf"
extension. Syntax of SWF file URL in dune_folder.txt is as follows:

media_url = swf://<url>[:::<params>]

Syntax for <url> is described in dune_folder documentation. <params> (also
known as "flashvars") is list of names and values of Flash variables in
name=value form separated by ampersand. Names and values should be URL
encoded. E.g.:

media_url = swf://http://192.168.1.1/player.swf
media_url = swf://http://192.168.1.1/player.swf:::id=29&vid=33

<params> list is passed to FlashLite instance. Variables from <params> list
can be accessed directly from ActionScript, e.g.:

if (id != "29")
trace("Error: invalid id " + id);

If HTTP URL is specified in media_url Dune player downloads corresponding
SWF file to local temporary file. This local file is used for running
FlashLite instance. Download is done every time dune_folder.txt is run.

Since firmware version 110127_2105_beta special parameter with name "fip"
can be used in URL. Value of this parameter is displayed on Dune player's
FIP (for models without FIP the parameter is ignored). E.g., for the
following URL:

media_url = swf://http://192.168.1.1/player.swf:::id=29&fip=PLAY

FIP will display word PLAY. Note:

- FIP can display only a few characters;
- scrolling of text on FIP is not supported in Dune FlashLite;
- FIP text is displayed on start of FlashLite instance and cannot be
changed while FlashLite application is running;
- normally it is good idea to use capital letters and digits only for FIP
text.

SWF file name
=============

Dune FlashLite implements additional platform specific features for SWF
files running on Dune player. They are abilities to:

- specify output window size;
- select OSD size;
- choose between speed and quality of rendering.

At the moment listed features are not supported for SWF files loaded via
HTTP URLs.

All parameters are specified in SWF file name. Overall syntax is as
follows:

file_name[__<width>x<height>][__(480p|576p|720p|1080p)][__(speed|quality)].swf

Note, the double underscore symbol is used as separator between parameters.
Order of parameters is significant: first is window size, second is OSD
size, and third is speed/quality parameter. Any or all parameters can be
skipped, but if present they must be last in SWF file name and follow the
order. For example:

test_1__640x480__720p__quality.swf
test_2_a__576p.swf
test3__200x400__speed.swf

Window size specifies size of FlashLite instance window used for displaying
FlashLite application. Window is <width>x<height> pixels. If FlashLite
application has different stage sizes, the stage is scaled up or down to
the window. If window size is not specified full screen (see OSD size
parameter) is used. Aspect ratio of FlashLite application's stage is
preserved in case it is scaled up or down to window or full screen. Note,
some TVs have overscan area that is not shown to user. FlashLite
application should be implemented in such a way that it displays essential
information in safe area only.

OSD size parameter allows to select size of full screen window. Supported
OSD sizes are:

- 480p (720x480 pixels);
- 576p (720x576 pixels);
- 720p (1280x720 pixels);
- 1080p (1920x1080 pixels).

By default, if not specified, OSD size coincides to resolution of current
video mode of Dune player. E.g., for 720p video mode OSD size is 1280x720
pixels. Note, if aspect ratio of selected OSD does not correspond to aspect
ratio of current Dune player video mode, FlashLite application output may
look distorted. Note, if OSD size is lesser the performance of FlashLite
application may be better.

Dune FlashLite application can be run in one of two modes: "quality" or
"speed". If mode is not specified in SWF file name, "quality" is used.

- In "speed" mode rendering of FlashLite application is done by Dune
FlashLite to rendering plane of size equal to application's stage size.
After that result is scaled up or down to output window (or full screen) by
Dune player hardware. As a result rendering is performed faster (since
output window in most cases is larger than stage), but quality is poorer.

- In "quality" mode rendering and scaling of FlashLite application is done
by Dune FlashLite to rendering plane of size equal to window (or full
screen). As a result rendering is slower, but quality provided by software
scaling is noticeably better.

Security model
==============

Adobe FlashLite supports two security modes that FlashLite instance runs
in. They are "trusted" and "sandboxed". Dune FlashLite always uses
"trusted" security mode and it cannot be changed. In "trusted" mode
FlashLite application can access local filesystem and the network at the
same time independently of mode specified in SWF file.

Flash quality setting
=====================

Adobe FlashLite supports three values for rendering quality: "low",
"medium" and "high". Dune FlashLite always uses "high" rendering quality
and it cannot be changed.

Number of FlashLite instances
=============================

Although Adobe FlashLite supports up to four FlashLite instances running
simultaneously, Dune FlashLite supports only single FlashLite instance at
the moment. It means only single SWF file can be played by Dune player at
the same time. From other side FlashLite application has means to load
additional SWF files if needed, e.g. with help of MovieClip class.

Dune ActionScript extensions
============================

Dune FlashLite extends Adobe FlashLite with additional functionality by
implementing new ActionScript classes. At the moment all available
functionality is implemented in ExtCommand class. The class is implemented
using ActionScript extensions mechanism. It means the class has
ActionScript declaration and corresponding C++ implementation specific to
Dune player. ActionScript declaration of ExtCommand class is as follows:

intrinsic dynamic class ExtCommand
{
public static function exitFlash():Void;
public static function requestWebBrowserOnExit(url:String):Boolean;
public static function requestWebBrowserOnExitWithReturn(url:String):Boolean;
public static function cancelWebBrowserOnExit():Void;
public static function requestFilePlayerOnExit(url:String):Boolean;
public static function requestFilePlayerOnExitWithReturn(url:String):Boolean;
public static function cancelFilePlayerOnExit():Void;
public static function getMainStoragePath():String;
public static function getSerialNumber():String;
public static function getProductId():String;
public static function getFirmwareVersion():String;
public static function sync():Void;
}

The ExtCommand class has the following methods:

- exitFlash() - finishes FlashLite instance. Since Adobe FlashLite does not
support fscommand("quit") functionality, this extension was added to allow
FlashLite application to terminate running FlashLite instance;

- requestWebBrowserOnExit() - requests launching of Web browser with given
URL on exit from FlashLite instance. If FlashLite application is terminated
some time later, Web browser with that URL is started by Dune player.
Function returns true if request succeeded and false otherwise. E.g., usage
scenario might look as follows: FlashLite application shows advertisement,
user presses URL RC button, at this moment application calls
requestWebBrowserOnExit() function, sends advertisement notification
request to server and upon receive of reply calls exitFlash(). In result
Dune player opens Web browser with specified advertisement URL;

- requestWebBrowserOnExitWithReturn() - this method will be available in
next firmware releases. The method is similar to requestWebBrowserOnExit()
except after finish of Web browser, FlashLite application called this
method is started again by Dune player;

- cancelWebBrowserOnExit() - cancels request to launch Web browser on exit
from FlashLite instance. This function is opposite to
requestWebBrowserOnExit() and requestWebBrowserOnExitWithReturn();

- requestFilePlayerOnExit() - by analogy with requestWebBrowserOnExit()
requests launching of File player with given URL on exit from FlashLite
instance;

- requestFilePlayerOnExitWithReturn() - this method will be available in
next firmware releases. The method is similar to requestFilePlayerOnExit()
except after finish of File player, FlashLite application called this
method is started again by Dune player;

- cancelFilePlayerOnExit() - cancels request to launch File player on exit
from FlashLite instance. This function is opposite to
requestFilePlayerOnExit() and requestFilePlayerOnExitWithReturn();

- getMainStoragePath() - returns absolute Unix path to main storage.
FlashLite application can open then user files on this storage;

- getSerialNumber() - this method is available since firmware version
110127_2105_beta. It returns serial number of Dune player;

- getProductId() - this method will be available in
next firmware releases. It returns product id of Dune player;

- getFirmwareVersion() - this method will be available in
next firmware releases. It returns firmware version of Dune player;

- sync() - this method is available since firmware version
110127_2105_beta. It does sync on all file systems (performs sync() system
call), so all data not flushed from applications or operating system
buffers are written to disks. The function is useful, for example, when
SharedObject class is used for storing persistent application data.

Note, methods requestWebBrowserOnExit(),
requestWebBrowserOnExitWithReturn(), requestFilePlayerOnExit() and
requestFilePlayerOnExitWithReturn() are mutually exclusive ones. It means
only last call to one of these methods from FlashLite application takes
effect, previous calls are ignored.

SharedObject implementation details
===================================

ActionScript class SharedObject can be used for managing persistent
objects: storing them on filesystem, retrieving, modifying and deleting
them. Dune FlashLite implementation uses internal directory for storing
persistent data. Every object is stored in separate file in separate
subdirectory identified by SWF file.

One FlashLite application cannot manage persistent objects of another one.
E.g., if SWF file is changed persistent objects will be stored in new
subdirectory.

Contents of data directory is not preserved between reboots of Dune player.
Because of this persistent objects are removed every time player is turned
off (including hardware standby but not software one) or rebooted.

Dune FlashLite has two limits on size of persistent data. First limit is
total size of persistent data per SWF file. Dune FlashLite has it set to 1
KB. Second limit is total size of all stored persistent data. Dune
FlashLite has it set to 64 KB.

The following improvements take place since firmware version
110127_2105_beta:

- contents of data directory is preserved between reboots of Dune player
(including power off), so SharedObject class can be used for storing really
persistent data;

- limits on size of persistent data have being increased. Limit on total
size of persistent data per SWF file is set to 16 KB. Limit on total size
of all stored persistent data is set to 1 MB.

Access to data files
====================

FlashLite application can access data files that are stored on Web server
or on local to Dune player storages. For this purpose the following classes
can be used.

LoadVars class provides access to text files, that has key=value format.

XML class provides access to XML text files.

MovieClip class provides access to images, video clips and SWF files.

All three classes can be used in Dune FlashLite with HTTP URLs, relative
Unix paths and absolute main storage path (see
ExtCommand.getMainStoragePath() function) in order to access data on
corresponding storages.

Remote control button mapping
=============================

Mapping of remote control (RC) buttons implemented by Dune FlashLite
differs from one implemented by Adobe FlashLite. For convenience of Flash
programmer Dune FlashLite offers DuneKey ActionScript class. The class
contains mapping of all supported RC buttons.

Several Dune RC buttons are mapped to standard Key class values:

- DuneKey.UP = Key.UP;
- DuneKey.DOWN = Key.DOWN;
- DuneKey.LEFT = Key.LEFT;
- DuneKey.RIGHT = Key.RIGHT;
- DuneKey.ENTER = Key.ENTER;
- DuneKey.0 = Key.0;
- DuneKey.1 = Key.1;
- DuneKey.2 = Key.2;
- DuneKey.3 = Key.3;
- DuneKey.4 = Key.4;
- DuneKey.5 = Key.5;
- DuneKey.6 = Key.6;
- DuneKey.7 = Key.7;
- DuneKey.8 = Key.8;
- DuneKey.9 = Key.9.

DuneKey class contains the following mapping for Dune RC specific buttons:

class DuneKey extends Key
{
public static var CLEAR:Number = BACKSPACE;
public static var SELECT:Number = SHIFT;
public static var VOLUME_UP:Number = 16777217;
public static var VOLUME_DOWN:Number = 16777218;
public static var MUTE:Number = 16777219;
public static var PAGE_UP:Number = 16777220;
public static var PAGE_DOWN:Number = 16777221;
public static var PLAY:Number = 16777223;
public static var PAUSE:Number = 16777224;
public static var FWD:Number = 16777226;
public static var REW:Number = 16777227;
public static var SLOW:Number = 16777228;
public static var NEXT:Number = 16777230;
public static var PREV:Number = 16777231;
public static var MODE:Number = 16777232;
public static var ZOOM:Number = 16777233;
public static var POPUP_MENU:Number = 16777234;
public static var INFO:Number = 16777235;
public static var ANGLE:Number = 16777236;
public static var SHUFFLE:Number = 16777237;
public static var RETURN:Number = 16777238;
public static var AUDIO:Number = 16777239;
public static var SUBTITLE:Number = 16777240;
public static var REPEAT:Number = 16777241;
public static var SEARCH:Number = 16777242;
public static var URL:Number = 16777243;
public static var SETUP:Number = 16777244;
public static var TOP_MENU:Number = 16777246;
public static var RED:Number = 16777247;
public static var GREEN:Number = 16777248;
public static var YELLOW:Number = 16777249;
public static var BLUE:Number = 16777250;
}

Other RC buttons are processed in special way. They are:

- POWER OFF - finish FlashLite instance and send Dune player to standby;
- EJECT - eject optical disk drive (if exists);
- STOP - finish FlashLite instance.

Dune FlashLite extensions
=========================

Dune FlashLite extensions described in this document (ActionScript classes
ExtCommand and DuneKey) are available for download in single archive:
http://dune-hd.com/firmware/flash/Du...Extensions.zip. To use the
extensions implement your own FlashLite application, compile it with
supplied classes and run with Dune FlashLite.

Links to documentation
======================

"Developing Adobe Flash Lite 2.x and 3.x Applications"
http://help.adobe.com/en_US/FlashLit...de2/index.html

"Adobe Flash Lite 2.x and 3.x Adobe ActionScript Language Reference"
http://help.adobe.com/en_US/FlashLit...ce2/index.html

"Getting Started with Adobe Flash Lite for the Digital Home"
http://www.adobe.com/content/dam/Ado...ng_started.pdf

"Optimizing Adobe Flash Lite for the Digital Home"
http://www.adobe.com/content/dam/Ado...gital_home.pdf

"Developing Applications for Adobe Flash Lite for the Digital Home"
http://www.adobe.com/content/dam/Ado...gital_home.pdf

"Developing ActionScript Extensions for Adobe Flash Lite for the Digital
Home"
http://www.adobe.com/content/dam/Ado...gital_home.pdf

[rdsparla]

Esto ya lo había leido. La cuestión es, si creo un programa con flash lite, como lo instalo en el disco duro que tengo por Usb. En la Web de dune en inglés me respondieron que por ahora no hay opción de reproducir estos archivos .flv desde el disco duro. Lo que me interesa es como instalo una aplicación que yo creo con el flash lite. Gracias otra vez por tu respuesta.

[terrorman]

pues ya lo has dicho tu, no puedes.

la solucion es obvia, si va el flash usando el navegador, seria necesario poner es flash que tu haces en alguna web gratuita, enviando por ftp, y desde el navegador, si acepta flash, si podrias visualizar ese contenido.


luego si no quieres rayarte mucho, puedes montar tu propia web en el pc, y hay es donde debes poner los ficheros swf, para luego acceder como una web normal.

http://www.apachefriends.org/es/xampp.html