As you can see HTML5 support varies from browser to browser.
Suggested video media files format for Flash player are FLV or MP4 with H.264/AAC.
HTML5 player doesn't accept FLV format, and depending on browser accepts MP4 with H.264/AAC and/or webM format.

So as you may guess, if you wish to support HTML5 best option would be to configure multiple optional file sources, separate for Flash and HTML5.
From version 6 Nuevoplayer allows to use advanced configuration and player's fallback for best possible flash and HTML5 support.

By default Nuevoplayer's fallback is: Flash -> HTML5 -> Links
This means that first Nuevoplayer check browser for Flash support, next for HTML5 and finally if both not supported display media file links.
Nuevoplayer allows to define alternate video source files for different type of players.

Default tag for video file is <file>.
Altrnate video files for HTML5 player can be defined as:
<html5> - for mp4 h264/AAC file
<webmb> - for webm format
<ogg> - for ogg video format

<script id="nuevo" type="text/javascript" src="/nuevo/nuevo.js" charset="utf-8"></script>

<div id="nuevoplayer"></div>
<script type="text/javascript>

   nvplayer.start( {
      id:'nuevoplayer',   // id of DIV object to be replaced by player
      regkey: xxxx,   // your registration key for flash player
      file: 'http://www.yourdomain.com/video.flv',
      webm: 'http://www.yourdomain.com/video.webm',
      html5: 'http://www.yourdomain.com/video.mp4',
      width:'740',
      height:'464',
      skin:silver   //optional other than default skin name
}); 

</script>

As you may remember from Flash player, each flashvar (now also javascript variable)
can be defined inside separate XML file and delivered to player as config variable.
Below you can find how setup for such configuration can look like:

<script id="nuevo" type="text/javascript" src="/nuevo/nuevo.js" charset="utf-8"></script>

<div id="nuevoplayer"></div>
<script type="text/javascript>

   nvplayer.start( {
      id:'nuevoplayer',   // id of DIV object to be replaced by player
      config: 'http://www.yourdomain.com/config.xml',
      width:'740',
      height:'464',
}); 

</script>

And here's the link to config XML file used in this demo.
Note that we use dynamic PHP laguage to generate XML content. This allows to generate XML file based on video ID passed to PHP file.
This is short PHP overview how it can be done.

<?php

   header("Content-Type: text/xml");
   print "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n";
   print "<config>\n"; 
	
	print "<regkey>xxxxxxxx</regkey>\n";
	print "<image>http://www.yourdomain.com/previewimage.jpg</image>\n";
	print "<file>http://www.yourdomain.com/video.flv</file>\n";
	print "<filehd>http://www.yourdomain.com/videohd.mp4</filehd>\n";
	print "<webm>http://www.yourdomain.com/video.webm</webm>\n";
	print "<html5>http://www.yourdomain.com/video.mp4</html5>\n";
	print "<url>http://www.yourdomain.com/videos</url>\n";
	print "<embedcode>embed code here</embedcode>\n";
	print "<related>URL to related XML</related>\n";
   
   print "</config>\n"; 

?>

As you can see, instead of long javascript implementation on website you can define any of available flashvars
or javascript variables inside one config XML file, which can be parsed through PHP.
Flash player flashvars documentation is available here.


Many webmasters are happy to use built-in youtube plugin in flash version of Nuevoplayer.
But what about HTML5 ?
As Youtube stated, their HTML5 player API is experimental feature.
However we did tested new youtube API a lot and did best what was possible to do.
The only issue with youtube video and Nuevoplayer for HTML5 is not suggested to implement
as an item of playlist with multiple different type of videos.
Standalone youtube video is working well with Nuevoplayer for HTML5.