Showing posts with label html5. Show all posts
Showing posts with label html5. Show all posts

Thursday, October 10, 2013

Real-time ASCII representation of your webcam video stream




See it in Action: http://idevelop.ro/ascii-camera/

Real-time ASCII representation of your webcam video stream
http://idevelop.github.com/ascii-camera

ASCII Camera uses the HTML5 getUserMedia API to transform a video stream from your webcam into a real-time ASCII representation.

Supported browsers

  • Chrome ≥ 21 
  • Firefox ≥ 17 (requires media.navigator.enabled = true in about:config) 
  • Opera ≥ 12 

Libraries used

  • Camera input is done using the camera.js library. 
  • ASCII transformation is adapted from jsascii library by Jacob Seidelin. 

Author

  • Andrei Gheorghe

Thursday, April 26, 2012

YouTube 3D Video



See this link:
YouTube 3D Video  



  •  Upload 3D Content
  • Convert 2D video to 3D 


  • Watch 3D Content



    Set up HTML5 Stereo View

    HTML5 stereo view allows you to view 3D video on YouTube using specialized hardware and software. We currently support the following solutions for viewing YouTube 3D video through HTML5 stereo view:
    NVIDIA 3D Vision Configure 3D Vision for watching YouTube 3D (provided by NVIDIA)

    For help setting up your hardware or software for HTML5 stereo view, select a link from the above list. Please note that the above links are not controlled nor content on them endorsed by YouTube.

    Why is it called HTML5 stereo view?

    HTML5 stereo view is a standards compliant way of watching 3D content using special hardware and software:
    • HTML5 is the technology that we use to display video
    • Stereo view stands for stereoscopic view, meaning the ability to show you a different image for each eye

    HTML5 stereo view adheres to web standards so that new devices can easily support watching 3D on YouTube. YouTube aims to expand support for additional standards compliant devices in the future.


    Sunday, April 15, 2012

    CAPTURING AUDIO & VIDEO IN HTML5

    Hot from the W3 standards committee
    HTML Media Capture   W3C Working Draft 14 April 2011


    HTML5 ROCKS site has a great article on this.

    "Audio/Video capture has been the "Holy Grail" of web development for a long time. For many years we've had to rely on browser plugins (Flash or Silverlight) to get the job done. Come on!

    HTML5 to the rescue. It might not be apparent, but the rise of HTML5 has brought a surge of access to device hardware. Geolocation (GPS), the Orientation API (accelerometer), WebGL (GPU), and the Web Audio API (audio hardware) are perfect examples. These features are ridiculously powerful, exposing high level JavaScript APIs that sit on top of the system's underlying hardware capabilities.

    This tutorial introduces a new API, navigator.getUserMedia(), which allows web apps to access a user's camera and microphone."


    I've done a little exploring and getUserMedia isn't quite ready for prime time. So far for PC's it only works with in Chrome and Opera. My first hand experience, I only tested on Chrome, was that it was grabbing the wrong camera device and there was no way to select which camera device to capture from. 

    It seems a lot of these new api's are driven by phone developers that have found HTML/JavaScript an easy way to write universally supported application.  So there are a number of tools that basically take your web site and turn it in to an Android or iPhone application.  

    Support:
    • Android 3.0 browser - one of the first implementations. Check out this video to see it in action.
    • Chrome for Android (0.16)
    • Firefox Mobile 10.0


    From my notes:

    Web video input

    Monday, November 21, 2011

    The Trials and Tribulations of HTML Video in the Post-Flash Era

    From Wired:


    The Trials and Tribulations of HTML Video in the Post-Flash Era

    Adobe reversed course on its Flash strategy after a recent round of layoffs and restructuring, concluding that HTML5 is the future of rich Internet content on mobile devices. Adobe now says it doesn’t intend to develop new mobile ports of its Flash player browser plugin, though existing implementations will continue to be maintained.
    Adobe’s withdrawal from the mobile browser space means that HTML5 is now the path forward for developers who want to reach everyone and deliver an experience that works across all screens. The strengths and limitations of existing standards will now have significant implications for content creators who want to deliver video content on the post-flash web.
    Apple’s decision to block third-party browser plugins like Flash on its iOS devices played a major role in compelling web developers to build standards-based fallbacks for their existing Flash content. This trend will be strengthened when Microsoft launches Windows 8 with a version of Internet Explorer that doesn’t support plugins in the platform’s new standard Metro environment.
    Flash still has a significant presence on the Internet, but it’s arguably a legacy technology that will decline in relevance as mobile experiences become increasingly important. The faster pace of development and shorter release cycles in the browser market will allow open standards to mature faster and gain critical mass more quickly than before. In an environment where standards-based technologies are competitive for providing rich experiences, proprietary vendor-specific plugins like Flash will be relegated to playing a niche role.
    Our use of the phrase post-Flash isn’t intended to mean that Flash is dead or going to die soon. We simply mean that it’s no longer essential to experiencing the full web. The HTML5 fallback experiences on many Flash-heavy sites still don’t provide feature parity with the Flash versions, but the gap is arguably shrinking — and will continue to shrink even more rapidly in the future.

    Strengths and weaknesses of HTML5 video

    HTML5 has much to offer for video delivery, as the HTML5 video element seamlessly meshes with the rest of the page DOM and is easy to manipulate through JavaScript. This means that HTML5 video offers significantly better native integration with page content than it has ever been possible to achieve with Flash. The open and inclusive nature of the standards process will also make it possible for additional parties to contribute to expanding the feature set.
    A single company no longer dictates what can be achieved with video, and your video content is no longer isolated to a rectangle embedded in a page. HTML5 breaks down the barriers between video content and the rest of the web, opening the door for more innovation in content presentation. Three are some really compelling demonstrations out there that showcase the use of video in conjunction with WebGL and other modern web standards. For example, the video shader demo from the 3 Dreams of Black interactive film gives you a taste of what’s possible.
    Of course, transitioning video delivery in the browser from Flash to HTML5 will also pose some major challenges for content creators. The standards aren’t fully mature yet and there are still a number of features that aren’t supported or widely available across browsers.
    For an illustration of how deep the problems run, you need only look at Mozilla’s Firefox Livepromotional website, which touts the organization’s commitment to the open web and shows live streaming videos of Red Panda cubs from the Knoxville Zoo. The video is streamed with Flash instead of using standards-based open web technologies.
    Flash is required to see the Red Panda cubs on Mozilla's website
    In an FAQ attached to the site, Mozilla says that it simply couldn’t find a high-volume live-streaming solution based on open codecs and open standards. If Mozilla can’t figure out how to stream its cuddly mascot with open standards, it means there is still work to do.
    Two of the major technical issues faced by HTML5 video adopters are the lack of adequate support for adaptive streaming and the lack of consensus surrounding codecs. There is currently an impasse between backers of the popular H.264 codec and Google’s royalty-free VP8 codec. There’s no question that a royalty-free video format is ideal for the web, but the matter of whether VP8 is truly unencumbered by patents — and also meets the rest of the industry’s technical requirements — is still in dispute.
    There is another major issue that hasn’t been addressed yet by open web standards that could prove even more challenging: content protection. The vast majority of Flash video content on the Internet doesn’t use any kind of DRM and is trivially easy to download. Flash does, however, provide DRM capabilities and there are major video sites that rely on that technology in order to protect the content they distribute.

    Can DRM be made to play nice with open standards?

    DRM is almost always bad for regular end users and its desirability is highly debatable, but browser vendors will have to support it in some capacity in order to make HTML5 video a success. Many of the content creators who license video material to companies like Netflix and Hulu contractually stipulate a certain degree of content protection.
    Mozilla&’s Robert O’Callahan raised the issue of HTML5 video DRM in a recent blog entry shortly after Adobe’s announcement regarding mobile Flash. He expressed some concern that browser vendors will look for a solution that is expedient rather than inclusive, to the detriment of the open web.
    “The problem is that some big content providers insist on onerous DRM that necessarily violates some of our open web principles (such as web content being equally usable on any platform, based on royalty-free standards, and those standards being implementable in free software),” O’Callahan wrote. “We will probably get into a situation where web video distributors will be desperate for an in-browser strong DRM solution ASAP, and most browser vendors (who don’t care all that much about those principles) will step up to give them whatever they want, leaving Mozilla in another difficult position. I wish I could see a reasonable solution, but right now I can’t. It seems even harder than the codec problem.”
    O’Callahan also pointed out in his blog entry that the upcoming release of Windows 8, which will not support browser plugins in its Metro environment, means that the lack of DRM support in standards-based web video is no longer just a theoretical concern. Microsoft may need to furnish a solution soon, or risk frustrating users who want to watch commercial video content on the web in Windows 8 without installing additional apps or leaving the Metro shell.

    Netflix stands behind DASH

    Flash evangelists may feel that the limitations of HTML5 video and the problems that content creators are sure to face during the transition are a vindication of the proprietary plugin model. But the advantages of a truly open, vendor-neutral, and standards-based video solution that can span every screen really dwarf the challenges. That is why major stakeholders are going to be willing to gather around the table to try find a way to make it work.
    Netflix already uses HTML5 to build the user interfaces of some of its embedded applications, including the one on the PS3. The company has soundly praised the strengths of a standards-based web technology stack and has found that there are many advantages. But the DRM issue and the lack of suitably robust support for adaptive streaming have prevented Netflix from dropping its Silverlight-based player in regular web browsers.
    The company has committed to participating in the effort to make HTML5 a viable choice for all video streaming. Netflix believes that the new Dynamic Adaptive Streaming over HTTP (DASH) standard being devised by the Motion Picture Experts Group (MPEG) will address many of the existing challenges and pave the way for ubiquitous adoption of HTML5 for streaming Internet video.
    DASH, which is expected to be ratified as an official standard soon, has critical buy-in from many key industry players besides Netflix, including Microsoft and Apple. An early DASH playback implementations is already available as a plugin for the popular VLC video application.
    The DASH standard makes video streaming practical over HTTP and addresses the many technical requirements of high-volume streaming companies like Netflix, but it doesn’t directly address the issue of DRM by itself. DASH can be implemented in a manner that is conducive to supporting DRM, however.

    DASH and DRM

    Ericsson Research, which is involved in the DASH standardization effort, has done some worthwhilepreliminary research to evaluate the viability of DRM on DASH. Ericsson produced a proof-of-concept implementation that uses DRM based on the Marlin rights management framework. Marlin, which was originally created by a coalition of consumer electronics vendors, is relatively open compared to alternate DRM technologies and makes use of many existing open standards. But Marlin is still fundamentally DRM and suffers from many of the same drawbacks, and adopters have to obtain a license from the Marlin Trust Management Organization, which holds the keys.
    The architecture of the Marlin rights management framework
    Ericsson explains in its research that it chose to experiment with Marlin for their proof-of-concept implementation because it’s available and mature — other similar DRM schemes could also easily be adopted. Existing mainstream DRM schemes would all likely pose the same challenges, however, and it’s unlikely that such solutions will be viewed as acceptable by Mozilla. More significantly, an implementation of HTML5 video that relies on this kind of DRM would undermine some of the key values and advantages of openness that are intrinsic to the open web.
    The ease with which solutions like Marlin can be implemented on top of HTML5 will create pressure for mainstream browser vendors to adopt them quickly. This could result in the same kind of fragmentation that exists today surrounding codecs. As O’Callahan said, it’s easy to see this issue becoming far more contentious and challenging to overcome than the codec issue.

    What next?

    The transition to HTML5 and standards-based technology for video delivery will bring many advantages to the web. There are some great examples that show what can be achieved when developers really capitalize on the strengths of the whole open web stack. The inclusiveness of the standards process will also give a voice to additional contributors who want to expand the scope of what can be achieved with video on the web.
    There are still some major obstacles that must be overcome in order for the profound potential of standards-based web video to be fully realized in the post-Flash era. Open standards still don’t deliver all of the functionality that content creators and distributors will require in order to drop their existing dependence on proprietary plugins. Supplying acceptable content protection mechanisms will prove to be a particularly bitter challenge.
    Despite the barriers ahead, major video companies like Netflix recognize the significant advantages of HTML5 and are willing to collaborate with other stakeholders to make HTML5 video a success. The big question that remains unanswered is whether that goal can be achieved without compromising the critically important values of the open web.

    Wednesday, November 09, 2011

    Microsoft Killing Silverlight?

    From Slashdot:

    "Silverlight 5 might be last version released by Microsoft. Several industry insiders and partners for the last few weeks have heard from their own Microsoft sources that there won't be new versions released after Silverlight 5. Status on service packs and support for Silverlight is unclear, as Microsoft haven't yet released lifecycle support end date even for the previous Silverlight 4. By their support page they will give full year head-up before ending support. With Adobe ending development of Flash for mobile browsers and Microsoft ending development of Silverlight, HTML5 video looks a lot more promising. But will content providers be able to give out their material without DRM and how does HTML5 perform with non-video side of Flash and Silverlight?"

    Tuesday, November 08, 2011

    Illusions in the Web: a real-time video editor built in HTML5 | Mateu Batle's Blog

    http://mbatle.wordpress.com/2011/11/02/illusions-in-the-web-a-real-time-video-editor-built-in-html5/

    Illusions in the Web: a real-time video editor built in HTML5

    From the article:
    I am excited to blog about the current project I am working on and deeply enjoying. In Collabora, we have developed a tech demo of a simple video editor application running in the WebKit based web browser using HTML5 video technology. Well to be honest, not just plain HTML5 video, but we will get to that point later on. Keep in mind it is not a fully functional application, just a demo with some basic functionality like:
    • Media library browser for images and videos.
    • Drag and drop clips to build the media timeline.
    • Set the inpoint and outpoint for each video clip.
    • Real-time seamless preview of the media timeline.
    • Basic touch based interface, although there is room for a lot of improvement here.
    The main advantage is that all processing is done locally and all the data is kept locally too, so no need to upload all the source material to a server or download the final video from a server, which might take some time specially when working with HD resolutions. Another nice feature is that you can actually preview the final video in real-time, instead of waiting for the server to process it.

    Saturday, September 10, 2011

    Inside Netflix's WebKit-Based UI For TV Devices - Slashdot

    Link to presentation.
    http://cdn-0.nflximg.com/us/presentations/htmltvui/oscon-2011/Netflix%20Webkit-Based%20UI%20for%20TV%20Devices.pdf

    From Slashdot:
    http://tech.slashdot.org/story/11/09/10/0543231/Inside-Netflixs-WebKit-Based-UI-For-TV-Devices

    DeviceGuru writes with this interesting snippet on a modern approach to GUI design: "Netflix uses WebKit, JavaScript, HTML5, and CSS3 to build user interfaces that are delivered to millions of game consoles, Blu-ray players, Internet-connected TVs, and devices such as the Roku player and D-Link Boxee Box. Matt McCarthy and Kim Trott, device UI engineering managers at Netflix, have just published 50 presentation slides from their recent talk at OSCON 2011 in which they explained how Netflix develops its WebKit-based user interfaces."

     

    Saturday, August 13, 2011

    Three reasons HTML5 will own the living room too

    From Gigaom : Three reasons HTML5 will own the living room too

    Interfaces, apps and complete TV experiences will increasingly be rendered in HTML5 as HTML5 takes over the entire living room.
    As evidenced by the news this week of the new HTML5-based Kindle Cloud Reader, much of the news about HTML5’s rapid ascent has centered on mobile devices. But the fast-growing technology won’t just be a one-screen phenomenon. In fact, HTML5 is set to completely invade the living room in the coming years, as the slow trickle of browsers and HTML onto TV screens grows into a flood. The sofa web speaks HTML5 When the HTML-on-TV trend was [...]

    Sunday, July 31, 2011

    HTML5 Javascript video Chromakey.

    I thought I had already posted this, but I hadn't and I wanted to show it to someone asking me a few questions.  I had to search everywhere to find it again.



    It's a demo of HTML5 doing live chromakey on the client side.


    The code for that is here:  Manipulating video using canvas

    Friday, July 29, 2011

    The WebM Project

    http://www.webmproject.org/

    WebM is an audio-video format designed to provide a royalty-free, open video compression format for use with HTML5 video. The project's development is sponsored by Google.
    A WebM file consists of VP8 video and Vorbis audio streams, in a container based on a profile of Matroska.

    The project releases WebM related software under a BSD license and all users are granted a worldwide, non-exclusive, no-charge, royalty-free patent license. Despite this, some in the industry have called upon Google to provide indemnification against patent suits.

    http://en.wikipedia.org/wiki/Webm

    WebM is supported by Mozilla, Opera, Adobe, Google and more than seventy other publishers and software and hardware vendors.

    Tuesday, July 12, 2011

    Pandora Drops Flash for HTML 5

    Internet streaming music service Pandora announced it is phasing out Flash in favor of HTML 5. The change means users won't have to rely on the Flash plug-in in their Web browser to listen to the service's music offerings, and the company claims switching to HTML 5 has improved overall performance, too.

    'The front-end technology has been rebuilt in HTML 5 and together with a host of other improvements results in a much faster experience,' 
    the Pandora Web site stated.

    Tuesday, June 21, 2011

    Video conferencing in html5

    Web Real-Time Communication:


    http://www.youtube.com/watch?v=cx4rZH7fLpM

    https://labs.ericsson.com/apis/web-real-time-communication/

    Through emerging web standards, it will soon be possible to build web applications with support for real-time voice and video communication without the need for plug-ins. By downloading and running this browser, experimentation can be done with these new features.

    Thursday, May 19, 2011

    JavaScript audio synthesis with HTML 5

    From Acto.net

    JavaScript audio synthesis with HTML 5

    HTML5 had a few new features like

    Can you use JavaScript to stream live data into these media tags?
    Enter the JavaScript audio synth. It generates a handful of samples using very basic time-domain synthesis, wraps them up in a WAVE file header and embeds them in

    Wednesday, June 02, 2010

    HTML5 vs. Flash — the Case For Flash

    From Slashdot:

    "InfoWorld's Peter Wayner offers seven reasons why web designers will remain loyal to Flash for rich web content, despite 'seductive' new capabilities offered by HTML5. Sure, HTML5 aims to duplicate many of the features that were once the sole province of plugins (local disk storage, video display, better rendering, algorithmic drawing, and more) and has high-profile backers in Google and Apple, but as Wayner sees it, this fight is more about designers than it is about technocrats and programmers. And from its sub-pixel resolution, to its developer tools, to its 'write once, play everywhere' functionality, Flash has too much going for it to fall by the wayside. 'The designers will make the final determination. As long as Flash and its cousins Flex and Shockwave remain the simplest tools for producing drop-dead gorgeous websites, they'll keep their place on the Internet.'

    Tuesday, May 18, 2010

    With new video player, Hulu goes with Flash over HTML5

    Hulu has introduced a new online video player and opted to stick with Adobe Flash technology as opposed to the HTML5 platform that Apple has been championing. "When it comes to technology, our only guiding principle is to best serve the needs of all of our key customers: our viewers, our content partners who license programs to us, our advertisers, and each other," said Hulu Vice President Eugene Wei. "We continue to monitor developments on HTML5, but as of now it doesn't yet meet all of our customers' needs."

    Read more at: InformationWeek

    Sunday, May 09, 2010

    html5: see some..... non - flash videos

    From William Wallace:

    see some..... non - flash videos (using Ogg Theora and Vorbis format)  ....   from http://www.dailymotion.com/us
               http://www.dailymotion.com/video/xd68al_cute-bengal-kitten-fights-a-tiger-t_animals#hp-v-v12

    ..... anyway, I was looking into .... new rules for lexing and parsing  and came up with this.. info-spin-off ....

     Those (mostly apple, some linux and 386bsd), waiting for html5 instead of just going with flash videos,
    possibility, will have a longer wait then to be expected, and it probably won't be worth the options pending availability,
    a that point in time...because:  1.Codecs remain to be found that are not proprietary and browser engines will not co-operated enough with each other to make it a mainstream technology within a reasonable length of time. Google seems to, as usual, have the lead on this, as "Chrome" seems to be the only feasible player in the field, at the present time and with their acquisition of On2 , thereby getting VP8    

    .... to be continued...later.... maybe ( opinion derived from ref: below) ....  

    ref:   http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28HTML5%29
            http://en.wikipedia.org/wiki/HTML5_video
            http://en.wikipedia.org/wiki/Html5

    Wednesday, March 31, 2010

    Wikipedia's Assault On Patent-Encumbered Codecs

    From Slashdot:
    Wikipedia's Assault On Patent-Encumbered Codecs

    "The Open Video Alliance is launching a campaign today called Let's Get Video on Wikipedia, asking people to create and post videos to Wikipedia articles. (Good, encyclopedia-style videos only!) Because all video must be in patent-free codecs (theora for now), this will make Wikipedia by far the most likely site for an average internet user to have a truly free and open video experience. The campaign seeks to 'strike a blow for freedom' against a wave of h.264 adoption in otherwise open HTML5 video implementations."

    Monday, February 15, 2010

    HTML5 Video comming fast

    http://tech.slashdot.org/story/10/02/15/2010230/Five-Years-of-YouTube-and-Forced-Evolution

    Five Years of YouTube and Forced Evolution on

    NakNak writes to mention that the DailyMaverick has a feature looking back at five years of YouTube, some of the massive changes that have been forced through as a result of its overwhelming popularity, and what changes might be necessary going forward. "Google, which bought YouTube less than two years after it was founded for what was then considered outrageously expensive $1.65 billion, does not want Microsoft or Apple (or anybody else) to own the dominant video format. So it has become the biggest early tester of HTML5. Your browser doesn't support HTML5? Google launches its own browser, Chrome. Need to use Internet Explorer at work because that's all your IT department supports? Google launches a Chrome framework that effectively subverts IE and makes it HTML5-compatible. The final blow will be the day that YouTube switches off Flash and starts streaming only to HTML5 browsers. On that day all browsers will be HTML5 compatible or they will perish in the flames of user outrage."