
Recherche avancée
Autres articles (112)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
De près ou de loin...
29 avril 2011, parIls ne le savent pas forcément mais sont indispensables
MediaSPIP est un logiciel open-source, il se base sur d’autres logiciels, et d’autres logiciels lui sont également nécessaires pour fonctionner ... Les personnes ici listées ne savent pas forcément qu’elles ont un rôle important dans le développement, elles ont apporté leur connaissances dans le cadre de la création d’une partie de ces éléments nécessaires ou ont écrit des articles permettant de comprendre certaines choses... il semble indispensable (...)
Sur d’autres sites (4475)
-
HTML5 - ffmpeg encoded x264 video fails to play in Chrome/IE
11 août 2014, par Saren ArteriusI have totally no idea why http://jiro.wtako.net/video/39 does work in all browsers while http://jiro.wtako.net/video/40 only works in Firefox.
1 is encoded by MediaCoder (x264 + Nero encoder) and 2 is encoded by Arch Linux ffmpeg.
ffmpeg version :
ffmpeg 1:2.3.1-1
x264 version :
libx264 1:142.20140311-6
It seems that video size, frame rate, profile, level, bitrate does not affect whether the video can be played, because I have tried all these parameters, none of these works :
$ ffmpeg -i in.avi -c:v libx264 -crf 25 -pix_fmt yuv420p -preset veryslow -vf scale=640:360 -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 25 -pix_fmt yuv420p -preset veryslow -vf scale=640:360 -c:a aac -strict -2 -b:a 128k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -b:v 2000k -pix_fmt yuv420p -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -level:v 3.2 -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -profile:v baseline -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4Here is the media info of the video that does work in all browsers.
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 12.5 MiB
Duration : 1mn 52s
Overall bit rate mode : Variable
Overall bit rate : 932 Kbps
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.1
Format settings, CABAC : Yes
Format settings, ReFrames : 15 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 52s
Bit rate : 768 Kbps
Maximum bit rate : 1 307 Kbps
Width : 640 pixels
Height : 360 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.056
Stream size : 10.7 MiB (86%)
Writing library : x264 core 128 r2216 198a7ea
Encoding settings : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x3:0x133 / me=tesa / subme=11 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=9 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=16 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=abr / mbtree=1 / bitrate=768 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 1mn 52s
Bit rate mode : Variable
Bit rate : 124 Kbps
Maximum bit rate : 133 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 1.66 MiB (13%)
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37Here is the media info of the video that does work only in Firefox.
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 57.4 MiB
Duration : 2mn 48s
Overall bit rate mode : Variable
Overall bit rate : 2 856 Kbps
Writing application : Lavf55.33.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.0
Format settings, CABAC : Yes
Format settings, ReFrames : 16 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2mn 48s
Bit rate : 2 655 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.048
Stream size : 53.3 MiB (93%)
Writing library : x264 core 142 r2397M b7a50c1
Encoding settings : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=crf / mbtree=1 / crf=25.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 2mn 48s
Duration_LastFrame : -19ms
Bit rate mode : Variable
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 3.79 MiB (7%) -
HTML5 - ffmpeg encoded x264 video fails to play in Chrome/IE
11 août 2014, par Saren ArteriusI have totally no idea why http://jiro.wtako.net/video/39 does work in all browsers while http://jiro.wtako.net/video/40 only works in Firefox.
1 is encoded by MediaCoder (x264 + Nero encoder) and 2 is encoded by Arch Linux ffmpeg.
ffmpeg version :
ffmpeg 1:2.3.1-1
x264 version :
libx264 1:142.20140311-6
It seems that video size, frame rate, profile, level, bitrate does not affect whether the video can be played, because I have tried all these parameters, none of these works :
$ ffmpeg -i in.avi -c:v libx264 -crf 25 -pix_fmt yuv420p -preset veryslow -vf scale=640:360 -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 25 -pix_fmt yuv420p -preset veryslow -vf scale=640:360 -c:a aac -strict -2 -b:a 128k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -b:v 2000k -pix_fmt yuv420p -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -level:v 3.2 -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4
$ ffmpeg -i in.avi -c:v libx264 -crf 28 -pix_fmt yuv420p -profile:v baseline -preset veryslow -c:a aac -strict -2 -b:a 192k out.mp4Here is the media info of the video that does work in all browsers.
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 12.5 MiB
Duration : 1mn 52s
Overall bit rate mode : Variable
Overall bit rate : 932 Kbps
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.1
Format settings, CABAC : Yes
Format settings, ReFrames : 15 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 52s
Bit rate : 768 Kbps
Maximum bit rate : 1 307 Kbps
Width : 640 pixels
Height : 360 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.056
Stream size : 10.7 MiB (86%)
Writing library : x264 core 128 r2216 198a7ea
Encoding settings : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x3:0x133 / me=tesa / subme=11 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=9 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=16 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=abr / mbtree=1 / bitrate=768 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 1mn 52s
Bit rate mode : Variable
Bit rate : 124 Kbps
Maximum bit rate : 133 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 1.66 MiB (13%)
Encoded date : UTC 2014-05-01 13:14:37
Tagged date : UTC 2014-05-01 13:14:37Here is the media info of the video that does work only in Firefox.
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 57.4 MiB
Duration : 2mn 48s
Overall bit rate mode : Variable
Overall bit rate : 2 856 Kbps
Writing application : Lavf55.33.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.0
Format settings, CABAC : Yes
Format settings, ReFrames : 16 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2mn 48s
Bit rate : 2 655 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.048
Stream size : 53.3 MiB (93%)
Writing library : x264 core 142 r2397M b7a50c1
Encoding settings : cabac=1 / ref=16 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=crf / mbtree=1 / crf=25.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 2mn 48s
Duration_LastFrame : -19ms
Bit rate mode : Variable
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 3.79 MiB (7%) -
Progress with rtc.io
12 août 2014, par silviaAt the end of July, I gave a presentation about WebRTC and rtc.io at the WDCNZ Web Dev Conference in beautiful Wellington, NZ.
Putting that talk together reminded me about how far we have come in the last year both with the progress of WebRTC, its standards and browser implementations, as well as with our own small team at NICTA and our rtc.io WebRTC toolbox.
One of the most exciting opportunities is still under-exploited : the data channel. When I talked about the above slide and pointed out Bananabread, PeerCDN, Copay, PubNub and also later WebTorrent, that’s where I really started to get Web Developers excited about WebRTC. They can totally see the shift in paradigm to peer-to-peer applications away from the Server-based architecture of the current Web.
Many were also excited to learn more about rtc.io, our own npm nodules based approach to a JavaScript API for WebRTC.
We believe that the World of JavaScript has reached a critical stage where we can no longer code by copy-and-paste of JavaScript snippets from all over the Web universe. We need a more structured module reuse approach to JavaScript. Node with JavaScript on the back end really only motivated this development. However, we’ve needed it for a long time on the front end, too. One big library (jquery anyone ?) that does everything that anyone could ever need on the front-end isn’t going to work any longer with the amount of functionality that we now expect Web applications to support. Just look at the insane growth of npm compared to other module collections :
Packages per day across popular platforms (Shamelessly copied from : http://blog.nodejitsu.com/npm-innovation-through-modularity/) For those that – like myself – found it difficult to understand how to tap into the sheer power of npm modules as a font end developer, simply use browserify. npm modules are prepared following the CommonJS module definition spec. Browserify works natively with that and “compiles” all the dependencies of a npm modules into a single bundle.js file that you can use on the front end through a script tag as you would in plain HTML. You can learn more about browserify and module definitions and how to use browserify.
For those of you not quite ready to dive in with browserify we have prepared prepared the rtc module, which exposes the most commonly used packages of rtc.io through an “RTC” object from a browserified JavaScript file. You can also directly download the JavaScript file from GitHub.
Using rtc.io rtc JS library So, I hope you enjoy rtc.io and I hope you enjoy my slides and large collection of interesting links inside the deck, and of course : enjoy WebRTC ! Thanks to Damon, JEeff, Cathy, Pete and Nathan – you’re an awesome team !
On a side note, I was really excited to meet the author of browserify, James Halliday (@substack) at WDCNZ, whose talk on “building your own tools” seemed to take me back to the times where everything was done on the command-line. I think James is using Node and the Web in a way that would appeal to a Linux Kernel developer. Fascinating !!