Recherche avancée

Médias (91)

Autres articles (101)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

Sur d’autres sites (7663)

  • How to make timelapse with ffmpeg from files with date-time names ?

    4 novembre 2019, par LA_

    I understand how to make timelapse video from the sequence of files.
    But what if my files have names like YYYYMMDDHHmmSS.jpg ? How can I pass them in the correct order ? I would prefer not to rename them (there are 55’000 files, almost 10 Gb).

  • Android : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"

    11 juillet 2019, par gview

    I’ve converted the video to an mp4 with ffmpeg using the h264 codec and AAC, and used the baseline profile.

    Videos are 540x360x250kbps

    I then ran qt-faststart on the file to move the atoms into the right order.

    I’ve stuck the file up on a wiki we use and created a link to it.

    My test phone is a Samsung Galaxy S3.

    When I browse to the page that has links to the mp4’s on it, and I click on them, I get a popup window with 2 options : Internet and Video.

    If I download the videos using the "Internet" option, I can play them on the phone without issue.

    I’ve done other encodings with the main profile as well, and these also play fine. I thought that a powerful phone like the s3 would be able to handle the more advanced compression schemes available in h264, however I’ve also browsed the Android docs in regards to supported video formats, and it seems to state that only the "baseline" compression profile is supported.

    Regardless, what doesn’t work is trying to use the "Video" option which I assume tries to stream the video.

    For the wiki in question, clicking on the link reveals that the content-type and content-length headers are being set :

    Content-Length  6175996
    
Content-Type    video/mp4;charset=UTF-8

    Clicking on the link with a browser invokes a player (Quicktime in most cases) that can play the mp4’s.

    Is there more to having the file HTTP streamable beyond making a link to it ? Why won’t my Android 4 play these files ?

    UPDATE :
    I decided to make a quick HTML5 page using the video tag, and the videos do play on both my Galaxy S3 and the latest IOS.

  • Android : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"

    14 janvier 2014, par gview

    I've converted the video to an mp4 with ffmpeg using the h264 codec and AAC, and used the baseline profile.

    Videos are 540x360x250kbps

    I then ran qt-faststart on the file to move the atoms into the right order.

    I've stuck the file up on a wiki we use and created a link to it.

    My test phone is a Samsung Galaxy S3.

    When I browse to the page that has links to the mp4's on it, and I click on them, I get a popup window with 2 options : Internet and Video.

    If I download the videos using the "Internet" option, I can play them on the phone without issue.

    I've done other encodings with the main profile as well, and these also play fine. I thought that a powerful phone like the s3 would be able to handle the more advanced compression schemes available in h264, however I've also browsed the Android docs in regards to supported video formats, and it seems to state that only the "baseline" compression profile is supported.

    Regardless, what doesn't work is trying to use the "Video" option which I assume tries to stream the video.

    For the wiki in question, clicking on the link reveals that the content-type and content-length headers are being set :

    Content-Length  6175996
    
Content-Type    video/mp4;charset=UTF-8

    Clicking on the link with a browser invokes a player (Quicktime in most cases) that can play the mp4's.

    Is there more to having the file HTTP streamable beyond making a link to it ? Why won't my Android 4 play these files ?

    UPDATE :
    I decided to make a quick HTML5 page using the video tag, and the videos do play on both my Galaxy S3 and the latest IOS.

Navigation