Search Results

Search found 59 results on 3 pages for 'webm'.

Page 1/3 | 1 2 3  | Next Page >

  • Nautilus and file command in 11.04 don't show metadata for WebM files

    - by Pili
    The file-name extension .webm is used for media files using the WebM multimedia format, which consists of the WebM container (a subset of the Matroska container) and audio and video streams with independet enconding and quality settings. Description of the issue: For files in the WebM format, the program file says that files are raw data, instead of determining and displaying the real file-format, which is WebM. Besides, Nautilus doesn't display the technical metadata of files in this format. Why is the file program not displaying the file format for WebM files?

    Read the article

  • Google sort un outil qui permet le support de WebM dans IE9, en collaboration avec Microsoft

    Google sort un outil qui permet le support de WebM dans IE9 En collaboration avec Microsoft Quelques jours après la sortie du navigateur de Microsoft Internet Explorer 9 en version finale, Google propose une version préliminaire d'un outil permettant le support du format vidéo open source WebM. L'application, baptisée WebM Media Foundation (MF) Components for Microsoft Internet Explorer 9, utilise l'API Microsoft Media Foundation pour permettre une intégration transparente avec Windows de WebM. A signaler, la réalisation de cet outil a été faite en étroite collaboration avec Microsoft. Etant donné que l'applicatio...

    Read the article

  • Google I/O 2010 - WebM Open Video Playback in HTML5

    Google I/O 2010 - WebM Open Video Playback in HTML5 Google I/O 2010 - WebM Open Video Playback in HTML5 Chrome 101 Kevin Carle, Jim Bankoski, David Mendels (Brightcove), Bob Mason (Brightcove) The new open VP8 codec and WebM file format present exciting opportunities for innovation in HTML5 video. In this session, you'll see WebM playback in action while YouTube and Brightcove engineers show you how to support the format in your own HTML5 site. For all I/O 2010 sessions, please go to code.google.com From: GoogleDevelopers Views: 4 0 ratings Time: 40:02 More in Science & Technology

    Read the article

  • WebM dans Firefox, le nouveau codec vidéo open-source fait son apparition dans une version développe

    Mise à jour du 11/06/10 WebM dans Firefox Le nouveau codec vidéo open-source fait son apparition dans une version développeur du navigateur Jusqu'ici tout le monde était d'accord (sauf Apple) au sujet du WebM, le nouveau codec open-source issu du VP8 de Google. Mais une question de licence (lire par ailleurs) avait posé quelques problèmes pour le début de son implémentation dans les navigateurs. Ces problèmes sont aujourd'hui et réglés et Mozilla tient p...

    Read the article

  • Introducing WebM, an open web media project

    <b>WEBM Project:</b> "Though video is also now core to the web experience, there is unfortunately no open and free video format that is on par with the leading commercial choices. To that end, we are excited to introduce WebM, a broadly-backed community effort to develop a world-class media format for the open web."

    Read the article

  • Google sortira des plug-ins pour Safari et Internet Explorer afin que ceux-ci supportent WebM

    Google sortira des plug-ins pour Safari et Internet Explorer Afin que ceux-ci supportent WebM Google annonce qu'il va bientôt sortir des plug-ins pour Safari et Internet Explorer qui permettront à ces navigateurs de supporter les vidéos au format WebM. Cette annonce fait suite à de nombreuses critiques qu'auraient reçu la firme après sa décision d'abandonner la prise en charge du codec video H.264 dans son navigateur Google Chrome. Pour mémoire la firme avait annoncé il y a juste quelque jours l'arrêt d...

    Read the article

  • WebM and VP8 land in Chromium

    A developer preview of WebM , a high-quality, open, freely implementable, and web-optimized video format was announced today. Initial support for WebM, including its video codec VP8 will...

    Read the article

  • Webm videos converted with avconv not working properly

    - by user285943
    I'm converting mp4 videos to webm with the following command: avconv -i INPUT.mp4 -c:v libvpx -qmin 10 -qmax 42 -maxrate 500k -bufsize 1000k -threads 2 -c:a libvorbis OUTPUT.webm Am I doing something wrong? Should I use all of these parameters? I just want to make the videos compatible with all the browsers/devices. The videos are not working on Firefox on most devices and on Chrome in a specific Android device that I have. EDIT: When i play the embeded videos on firefox, on any android device, it goes straight to the end and doesn't play. It only plays if i click in the progress bar. If i open the videos on firefox without embedding them in a html page, they seem to have a bigger width box outside then, while the video is inside it. I uploaded a video that i converted. Try it in firefox: https://mega.co.nz/#!cg9FVZJD!CpC6X3NXH8rAVdBiS9ZqqwyITdyPb_qkKAKsvQXRpzI This is a comparison between the videos, after and before the conversion: ![Image here]: http://i.imgur.com/V2FijCQ.jpg

    Read the article

  • Swift and predictable reactions to WebM

    <b>LWN.net: </b>"Google unveiled something that many in the open source community had been expecting (and which the Free Software Foundation asked for in March): it made the VP8 video codec available to the public under a royalty-free, open source BSD-style license."

    Read the article

  • webm html5 videos lose connection with apache server

    - by Jizbo Jonez
    webm html5 videos that are played through a domain on my server sometimes lose connection. A video that is playing will start to buffer and then stop part of way through with that message "Video playback aborted due to a network error." displayed on the html5 video player. I am delivering the webm videos via a php script on an LAMP server. There doesn't seem to be any errors in the server logs. Is there any php.ini settings or httpd.conf that I need to set? I recently set 'Keep Alive" to "on" in httpd.conf could that be causing this?

    Read the article

  • FFSERVER - streaming an ASF video as Webm output

    - by Emmanuel Brunet
    I'm trying to stream an IP webcam ASF live stream to a ffserver to output a webm video format. The server starts successfully but the ffserver commands used to feed the ffserver fails and generates a core dump. Environment Debian 7.5 ffmpeg 2.2 Input stream $ ffprobe http://account:password@webcam/videostream.asf Input #0, asf, from 'http://admin:alpha1237@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 25 tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/s ffserver configuration my ffserver configuration is : Port 8091 RTSPPort 554 BindAddress 192.168.1.62 MaxHTTPConnections 1000 MaxClients 100 MaxBandwidth 1000 CustomLog - <Feed webcam.ffm> File /tmp/webcam.ffm FileMaxSize 500M ACL allow localhost ACL allow 192.168.0.0 192.168.255.255 </Feed> <Stream webcam.webm> # Output stream URL definition Feed webcam.ffm # Feed from which to receive video Format webm # Audio settings AudioCodec vorbis AudioBitRate 64 # Audio bitrate # Video settings VideoCodec libvpx VideoSize 640x480 # Video resolution VideoFrameRate 25 # Video FPS AVOptionVideo flags +global_header # Parameters passed to encoder # (same as ffmpeg command-line parameters) AVOptionVideo cpu-used 0 AVOptionVideo qmin 10 AVOptionVideo qmax 42 AVOptionVideo quality good AVOptionAudio flags +global_header PreRoll 15 StartSendOnKey # VideoBitRate 32 # Video bitrate </Stream> <Stream status.html> Format status # Only allow local people to get the status ACL allow localhost ACL allow 192.168.0.0 192.168.255.255 </Stream> ffmpeg feed I run the following command that fails $ ffmpeg -i http://account:password@webcam/videostream.asf http://192.168.1.62:8091/webcam.ffm http://192.168.1.62:8091/webcam.ffm Input #0, asf, from 'http://account:password@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 25 tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, mono, s16p, 32 kb/s [swscaler @ 0x36a80c0] deprecated pixel format used, make sure you did set range correctly Segmentation fault I tryed $ ffmpeg -i http://account:password@webcam/videostream.asf -pix_fmt yuv420p http://192.168.1.62:8091/webcam.ffm But it raises the same error. Thanks for your help Edit For an easy testing (I thought), I tried to publish the whole ASF stream as is, meaning connecting the ASF webcam output stream to the ffserver that outputs ASF format too. And thus with mirrored encoding so I changed the ffserver configuration to ... <Stream webcam.asf> Feed webcam.ffm Format asf VideoFrameRate 25 VideoSize 640X480 VideoBitRate 256 VideoBufferSize 1000 VideoGopSize 30 AudioBitRate 32 StartSendOnKey </Stream> ... And the output is now : Input #0, asf, from 'http://admin:alpha1237@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 1k tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, mono, s16p, 32 kb/s [swscaler @ 0x3d620c0] deprecated pixel format used, make sure you did set range correctly Output #0, ffm, to 'http://192.168.1.62:8091/webcam.ffm': Metadata: creation_time : now encoder : Lavf55.40.100 Stream #0:0: Audio: wmav2, 22050 Hz, mono, fltp, 32 kb/s Metadata: encoder : Lavc55.64.100 wmav2 Stream #0:1: Video: msmpeg4v3 (msmpeg4), yuv420p, 640x480, q=2-31, 256 kb/s, 1k fps, 1000k tbn, 1k tbc Metadata: Stream mapping: Stream #0:1 -> #0:0 (adpcm_ima_wav -> wmav2) Stream #0:0 -> #0:1 (mjpeg -> msmpeg4) Press [q] to stop, [?] for help Segmentation fault I can't even forward the stream.

    Read the article

  • ffserver-2.2 - streaming an ASF video as Webm output with ffserver on Debian 7.5

    - by Emmanuel Brunet
    I'm trying to stream an IP webcam ASF live stream to a ffserver to output a webm video format. The server starts successfully but the ffserver commands used to feed the ffserver fails and generates a core dump. Input stream $ ffprobe http://account:password@webcam/videostream.asf Input #0, asf, from 'http://account:password@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 25 tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/s ffserver configuration my ffserver configuration is : Port 8091 RTSPPort 554 BindAddress 192.168.1.62 MaxHTTPConnections 1000 MaxClients 100 MaxBandwidth 1000 CustomLog - <Feed webcam.ffm> File /tmp/webcam.ffm FileMaxSize 500M ACL allow localhost ACL allow 192.168.0.0 192.168.255.255 </Feed> <Stream webcam.webm> # Output stream URL definition Feed webcam.ffm # Feed from which to receive video Format webm # Audio settings AudioCodec vorbis AudioBitRate 64 # Audio bitrate # Video settings VideoCodec libvpx VideoSize 640x480 # Video resolution VideoFrameRate 25 # Video FPS AVOptionVideo flags +global_header # Parameters passed to encoder # (same as ffmpeg command-line parameters) AVOptionVideo cpu-used 0 AVOptionVideo qmin 10 AVOptionVideo qmax 42 AVOptionVideo quality good AVOptionAudio flags +global_header PreRoll 15 StartSendOnKey # VideoBitRate 32 # Video bitrate </Stream> <Stream status.html> Format status # Only allow local people to get the status ACL allow localhost ACL allow 192.168.0.0 192.168.255.255 </Stream> ffmpeg feed I run the following command that fails $ ffmpeg -i http://account:password@webcam/videostream.asf http://ffserver_ip:port/webcam.ffm http://192.168.1.62:8091/webcam.ffm Input #0, asf, from 'http://account:password@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 25 tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, mono, s16p, 32 kb/s [swscaler @ 0x36a80c0] deprecated pixel format used, make sure you did set range correctly Segmentation fault I tryed $ ffmpeg -i http://account:password@webcam/videostream.asf -pix_fmt yuv420p http://ffserver_ip:port/webcam.ffm But it raises the same error. Thanks for your help Edit For an easy testing (I thought), I tried to publish the whole ASF stream as is, meaning connecting the ASF webcam output stream to the ffserver that outputs ASF format too. And thus with mirrored encoding so I changed the ffserver configuration to ... <Stream webcam.asf> Feed webcam.ffm Format asf VideoFrameRate 25 VideoSize 640X480 VideoBitRate 256 VideoBufferSize 1000 VideoGopSize 30 AudioBitRate 32 StartSendOnKey </Stream> ... And the output is now : Input #0, asf, from 'http://admin:alpha1237@webcam/videostream.asf': Duration: N/A, start: 0.000000, bitrate: 32 kb/s Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 1k tbr, 1k tbn, 1k tbc Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, mono, s16p, 32 kb/s [swscaler @ 0x3d620c0] deprecated pixel format used, make sure you did set range correctly Output #0, ffm, to 'http://192.168.1.62:8091/webcam.ffm': Metadata: creation_time : now encoder : Lavf55.40.100 Stream #0:0: Audio: wmav2, 22050 Hz, mono, fltp, 32 kb/s Metadata: encoder : Lavc55.64.100 wmav2 Stream #0:1: Video: msmpeg4v3 (msmpeg4), yuv420p, 640x480, q=2-31, 256 kb/s, 1k fps, 1000k tbn, 1k tbc Metadata: Stream mapping: Stream #0:1 -> #0:0 (adpcm_ima_wav -> wmav2) Stream #0:0 -> #0:1 (mjpeg -> msmpeg4) Press [q] to stop, [?] for help Segmentation fault I can't even forward the stream. Thanks for your help again.

    Read the article

  • Google intègre le support de WebM à Chrome et rechange la licence du nouveau codec vidéo issu du VP8

    Mise à jour du 07/06/10 VP8 vs H.264 : Google intègre le support du WebM à Chrome Et rechange la licence du nouveau standard vidéo issu du VP8 Les choses s'accélèrent pour le projet WebM issu du VP8, un standard vidéo que Google a décidé de rendre open-source, et du Ogg-Vorbis (lire ci-avant). Première nouvelle, Chrome intègre à présent le support du WebM. Firefox et Opera avaient déjà fait savoir qu'ils travaillaient sur le sujet. Tout comme Microsoft. La version pour développeurs du navigateur de Google (téléchargeable sur le dev channel) permettra donc à tout un chacun de se faire une opinion personnelle sur les qua...

    Read the article

  • Un Web évangéliste de Microsoft critique avec humour la fin du support du H.264 dans Chrome et compare WebM à l'Espéranto

    Un Web évangéliste de Microsoft critique avec humour la fin du support du H.264 dans Chrome Et compare WebM à l'Espéranto Mise à jour du 13/01/11 Tim Sneath, « Windows et Web évangéliste » officiel pour Microsoft, a choisi l'humour pour critiquer la décision de Google d'abandonner le support du H.264 dans les futurs versions de Chrome. Google a motivé sa décision en indiquant qu'il souhaitait se concentrer uniquement sur les technologies ouvertes, et notamment WebM et Theora, deux codecs également soutenus par Mozilla et Opera (lire ci-avant). Tim Sneath, qui s'exprime en son nom propre, parodie cette argumentation en reprenant...

    Read the article

  • mkvmerge: How to merge two videos, one without audio?

    - by ProGNOMmers
    I have two videos, one without audio (the second). Trying to merge them I have this error: mkvmerge concat1.webm +concat2.webm -o output.webm mkvmerge v5.8.0 ('No Sleep / Pillow') built on Oct 19 2012 13:07:37 Automatically enabling WebM compliance mode due to output file name extension. 'concat1.webm': Using the demultiplexer for the format 'Matroska'. concat2.webm': Using the demultiplexer for the format 'Matroska'. 'concat1.webm' track 0: Using the output module for the format 'VP8'. concat2.webm' track 0: Using the output module for the format 'VP8'. concat2.webm' track 1: Using the output module for the format 'Vorbis'. No append mapping was given for the file no. 1 (concat2.webm'). A default mapping of 1:0:0:0,1:1:0:1 will be used instead. Please keep that in mind if mkvmerge aborts with an error message regarding invalid '--append-to' options. Error: The file no. 0 ('concat1.webm') does not contain a track with the ID 1, or that track is not to be copied. Therefore no track can be appended to it. The argument for '--append-to' was invalid. Is there a way to say to mkvmerge to make the audio track longer? Thank you!

    Read the article

  • Le MPEG LA s'attaque au VP8 et au WebM de Google, le consortium cherche des brevets utilisés illégalement par le codec open-source

    Le MPEG LA s'attaque au VP8 Et au WebM de Google, le consortium cherche des brevets qui seraient utilisés illégalement par le codec open-source La lutte qui oppose les industriels soutenant le H.264 et les partisans du libre autour des codecs vidéo est sur le point de se transformer en confrontation devant les tribunaux. L'organisme MPEG LA en charge des droits sur le codec H.264 vient en effet de lancer un appel à tous les industriels qui estiment détenir des brevets potentiellement utilisés par le codec concurrent, le « VP8 », racheté et décliné sous licences libres par Google avec WebM. L'objectif de cet appel est d'étudier la possibilité de constituer une commun...

    Read the article

  • WebM : la justice américaine enquête sur le groupe MPEG-LA et des actions potentiellement anticoncurrentielles contre le format de Google

    WebM : la justice américaine enquête sur le groupe MPEG-LA Et des actions potentiellement anticoncurrentielles contre le format de Google Mise à jour du 07/03/2011 par Idelways D'après un rapport rendu public par le Wall Street Journal, le département de la justice américaine aurait lancé une enquête antitrust sur le groupe de gestion de brevets MPEG-LA, le soupçonnant de vouloir attenter injustement à un rival technologique open-source supporté par Google (VP8). Le groupe MPEG-LA avait lancé mi-février un appel à tous les industriels qui estiment détenir des brevets potentiellement utilisés par le codec concurrent « VP...

    Read the article

  • Microsoft apporte le support du H.264 à Firefox avec une extension qui permet de gérer le codec propriétaire concurrent du WebM

    Microsoft publie une extension pour Firefox Qui permet le support de la vidéo H.264 Microsoft confirme une fois de plus son soutien au nouveau standard du web le HTML5. Après le support de la norme dans son future navigateur Internet Explorer 9 et son moteur de recherche Bing, la firme de Redmond vient de publier une extension en rapport avec ce standard pour... FireFox. Cette extension permettant aux utilisateurs de Firefox sur Windows 7 de regarder des vidéos au format H.264, un codec p...

    Read the article

  • Microsoft Lifecam VX-2000 doesn't work anymore in Cheese

    - by paed808
    I got have two Lifecam VX-2000's and they don't work in cheese anymore. I don't know if it's a problem with a missing package, or a package I installed. Here is the output. (cheese:11122): Clutter-WARNING **: No listener with the specified listener id 29 (cheese:11122): Clutter-WARNING **: No listener with the specified listener id 30 (cheese:11122): Clutter-WARNING **: No listener with the specified listener id 31 (cheese:11122): Clutter-WARNING **: No listener with the specified listener id 32 (cheese:11122): GLib-CRITICAL **: g_hash_table_remove_internal: assertion `hash_table != NULL' failed (cheese:11122): Clutter-WARNING **: Not able to remove listener with id 1 (cheese:11122): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed totem-video-thumbnailer: 'file:///home/myusername/Videos/Webcam/2012-09-20- 191530.webm' isn't thumbnailable Reason: Media contains no supported video streams. ** (cheese:11122): WARNING **: could not generate thumbnail for /home/myusername/Videos/Webcam/2012-09-20-191530.webm (video/webm) Notice the: Reason: Media contains no supported video streams. When I try to record a video it just makes a 13.2KB WEBM file with nothing. When I take a picture it works. Edit: I've been thinking that the problem started after installing the MediUbuntu repository on my system.

    Read the article

1 2 3  | Next Page >