Recherche avancée

Médias (0)

Mot : - Tags -/médias

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (58)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (9215)

  • FFmpeg android video processing does not return error message

    25 août 2018, par Дмитрий Мельчин

    friends. I am creating a program that puts the sound and picture to video. I’m using the ffmpeg library https://github.com/bravobit/FFmpeg-Android.
    The command looks like this :

    String command = "-i /data/user/0/com.radpony.vhs.camcorder/files/RADVHS/camcorder_video.mp4 -i /data/user/0/com.radpony.vhs.camcorder/files/RADVHS/watermark_png.png -i /data/user/0/com.radpony.vhs.camcorder/files/RADVHS/playarrow.png -filter_complex [0]crop=720:720[croped];[1]scale=w=143:h=50[tmp];[croped][tmp]overlay=x=577:y=10[overlayed];[overlayed][2]overlay=x=150:y=10[overlayed2];[overlayed2]drawtext=fontfile=/data/user/0/com.radpony.vhs.camcorder/cache/VCR_OSD_MONO_1_001.ttf:text='PM 11\:06Aug..25 2018':fontcolor=white:fontsize=48:x=50:y=600[withdate];[withdate]drawtext=fontfile=/data/user/0/com.radpony.vhs.camcorder/cache/VCR_OSD_MONO_1_001.ttf:text='Play':fontcolor=white:fontsize=48:x=50:y=30 -codec:a copy -c:v libx264 -preset ultrafast /data/user/0/com.radpony.vhs.camcorder/files/RADVHS/rendered_video.mp4";

    It works great for Android 6, but on the Samsung devices with Android 7 while processing of video ffmpeg just stops without displaying an error message.
    If someone knows the solution to this problem, help, please

  • ffserver : Add client requested urls to the status page

    29 novembre 2016, par Michael Niedermayer
    ffserver : Add client requested urls to the status page
    

    Fixes Ticket3791

    Reviewed-by : "Reynaldo H. Verdejo Pinochet" <reynaldo@osg.samsung.com>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] ffserver.c
    • [DH] tests/ffserver-regression.sh
    • [DH] tests/ffserver.regression.ref
  • How to handle differing .mp4 file types from different sources ?

    10 octobre 2017, par Dave502619

    If I take a .mp4 recorded on my mobile (Samsung S5) and pass it through FFmpeg with the below command, the output file (fileX.avi) is a greyscale bitmap uncompressed video file.

    • The offset values in fileX.avi (output from FFmpeg) to allow me to locate the video frame data are always 5680 bytes for the file header.

    • And 62 bytes for the inter frame header.

    • The data is uncompressed RGB24 so i can easily calculate the size of a video frame from height x width x 3.

    So my C# application can access the video frames in fileX.avi always at these above offsets.
    (This works great).

    My FFmpeg Command is :

    ffmpeg.exe -i source.mp4 -b 1150 -r 20.97 -g 120 -an -vf format=gray -f rawvideo -pixfmt gray -s 384x216 -vcodec rawvideo -y fileX.avi

    However... I recently took an .mp4 file from a different source (produced by Power Director 14 instead of direct from my mobile phone) and used this as the input source.mp4. But now the structure of fileX.avi differs as the offset values of 5680 + 62 bytes from the start in fileX.avi do not land me at the start of the video data frames.

    There seems to be different file formats for .mp4 - and obviously if there are my crude offset approach will not work for them all. I suspected at the time I wrote the code my method was all too easy a solution !

    So can anyone advise on the approach I should take now ? Should I check the original .mp4 or the output file (fileX.avi) to determine a "file type" to which I can determine the different offsets ?

    At the very least I need to be able to identify the "type" of .mp4 file that works so I can declare the type that will work with my software.